---

Touchpoint: YouTube

Level:
Awareness

Purpose:
Accumulate proof-of-work and surface thinking to serious operators.

What it is:
A public archive of how RaidGuild thinks and ships.
Not optimized for virality.
Not built around polish.
It is a reference layer more than a broadcast machine.

How we use it:
We publish breakdowns, retrospectives, architecture discussions, recordings, and occasional tighter “hero” pieces.
Unpolished is acceptable. Substance over aesthetics.
Videos should add value immediately and invite the next step (site / newsletter / case studies).

Owner:
Bard Steward

Access & Control:
Channel login: Sign-in with google using clerics@raidguild.org

Operational Rules:

• Every video must add value within the first seconds and make a promise it can keep.
• Titles must reflect the real content (no bait).
• CTA must point to one deeper layer.
• Archive, don’t over-edit.

Cadence:
Irregular but consistent accumulation.
No artificial publishing pressure.

Success Signal:
Watch time.
Click-through to site.
Inbound referencing specific videos.

---

Touchpoint: Twitter (X)

Level:
Awareness

Purpose:
Shape public positioning and occupy narrative territory.

What it is:
A public discourse layer where RaidGuild articulates its philosophy, shows work, and signals standards.
This is where reach matters and positioning is formed in real time.

How we use it:
We publish tactical threads, lessons learned, process transparency, case-study breakdowns, tool how-to’s, and selective commentary on current affairs. We can also celebrate the community and show snippets of our day to day.
Tone is clear, competent, slightly opinionated, and benefit-forward.
Each post should add value immediately and, when appropriate, invite the next step (site / newsletter / Discord).

Owner:
Bard Steward (voice & positioning)
Sync Guild Steward (publishing & formatting)

Access & Control:
Dunno yet

Operational Rules:

• No engagement farming.
• No vague hype or bait.
• Every thread must contain substance.
• CTA must be intentional and relevant.
• Once seeds become a polished longform, it will live here too, as a highlighted post.

Cadence:
Consistent presence. Post at least once a week. Try to create one relevant piece of longform per month.
Priority on clarity over frequency.

Success Signal:
Profile visits.
Link clicks.
Qualified engagement.
Inbound DMs from relevant operators.

---

Touchpoint: Website

Level:
Awareness

Purpose:
Convert discovery into clarity and direct next action.

What it is:
The primary positioning asset.
When someone lands here, they should immediately understand what RaidGuild is, who it is for, what problem it solves, and why it is credible.

How we use it:
We maintain clear positioning, visible proof of shipped work, transparent process, and a singular next step for each relevant vertical.
Language must be benefit-forward.
Remove friction, ambiguity, and ego at every opportunity.

Owner:
Brand Steward
Dev Team

Access & Control:
Hosting and CMS login stored in [password manager name].
Primary admin: [role].
Domain and DNS controlled by [role].

Operational Rules:

• Above-the-fold clarity within seconds.
• Every page must have a defined purpose.
• Each major page must contain one clear next step.
• No outdated projects or stale messaging.
• Clear positioning.
• Social proof.
• Process clarity.
• Singular next step at each point.

Cadence:
Reviewed quarterly.
Updated whenever positioning or offers shift.

Success Signal:
Conversion to newsletter or intake.
Qualified inquiries.
Low bounce on key pages.

---

Touchpoint: Newsletter

Level:
Interest

Purpose:
Build trust density through depth and regularity.

What it is:
A direct channel to serious operators who have opted in.
A place for applied thinking, lessons learned, and process transparency.

How we use it:
Right now we are only publishing the update newsletter “The Raid is On”
We want to move into publishing tactical breakdowns, real reflections, and applied philosophy to segmented parts of the list.
Each issue should leave the reader more capable than before.
CTA is optional and contextual — deeper into funnel when relevant.

Owner:
Bard Steward (voice & editorial direction)
Sync Guild (form and list management and liaison with devs)

Access & Control:
Platform: www.kit.com - login stored in password doc that can only be accessed with clerics@raidguild.org

Operational Rules:

• Strong opening hook.
• Concrete takeaway.
• No filler.
• Always TL:DR at the top. .

Cadence:
Monthly for the whole list
Quality over frequency.

Success Signal:
Open Rate
Click-through to deeper layers.
Conversion to intake / Discord.
Commentary on the daily life of the guild.

---

Touchpoints that are out of scope of BardSchool:

• Direct Conversations
• Active Collaboration
• Deliveries
• Ongoing Participation

Navigate!

bardschool.