Content Strategy
Owner: Ryan (execution) / Luke (direction)
Status: Active
Last updated: 2026-02-26
Feeds from: forge-your-brain.md
Cadence: 7–8 posts/week across LinkedIn (Robert, Uttam, Luke)
How to use this document This is Ryan’s operating guide. It covers what to write about, which CTAs to use, and how each channel works. Writing style is handled by the content system — posts are routed through
robert-gpt,uttam-gpt, orluke-gptdepending on the account. Posts publish from personal accounts (Robert, Uttam, Luke). We rarely post from the company LinkedIn.
The North Star
Almost every piece of content should connect to one idea:
Giving everyone access to the information they need to win.
This is why Brainforge exists. It should be felt — not necessarily stated verbatim — in nearly every post, email, and webinar. If a piece of content doesn’t ladder up to this idea, ask whether it belongs.
Content Pillars
These are the five topic areas we publish from. Each pillar maps to a part of the brand strategy.
Pillar 1: Everyone Can Access the Data
The idea: Insights shouldn’t live with the analyst. They should be available to everyone — the ops lead, the CSR, the founder. That’s not a dream. It’s what we build.
What to write about:
- Stories of non-technical people finally being able to answer their own questions
- The gap between “we have the data” and “anyone can use it”
- What it looks like when information moves freely inside a company
- The cost of information bottlenecks (slow decisions, missed signals, frustrated teams)
Tone: Inclusive and empowering. This pillar is explicitly for the non-technical reader — they should feel seen, not talked down to.
Pillar 2: Custom Is Better
The idea: Off-the-shelf tools are built for everyone, which means they’re built for no one. We build for how your company actually works.
What to write about:
- Why generic AI fails in practice (“it doesn’t learn”)
- The difference between configuring a tool and building something yours
- What “your company brain” actually means in practice
- Stories of tools that didn’t fit vs. systems that did
Tone: Contrarian. This pillar has an edge — it challenges a common default. Don’t soften it too much.
Pillar 3: Your Data Stays Yours
The idea: Privacy isn’t a feature we sell. It’s a principle we operate from. We bring AI to your data — not the other way around.
What to write about:
- What “private cloud AI” actually means (and why it matters)
- The risk of uploading company data to generic AI tools
- Who owns the models, the outputs, the infrastructure
- Why data sovereignty matters more as AI becomes central to operations
Tone: Direct and educational. Not fear-mongering — informative. Many people haven’t thought about this yet.
Pillar 4: Humans Should Do Human Work
The idea: We’re AI-native because we believe your people should spend their time on the work only humans can do. AI handles the low-leverage. People handle the high-leverage.
What to write about:
- What gets freed up when agents handle manual tasks
- The difference between automating busy work and replacing judgment
- What “low-leverage” and “high-leverage” work actually look like inside a company
- The human upside of AI adoption done right
Tone: Optimistic and forward-looking. This is the most hopeful pillar — lean into it.
Pillar 5: The Enemies
The idea: We define ourselves against three broken defaults — The Stack, The Firm, and The Bot. Content in this pillar is contrarian, story-driven, and resonates because it names something clients have already experienced.
What to write about:
| Enemy | Content angle |
|---|---|
| The Stack | The subscription spiral. Tools that don’t talk. Dashboards no one uses. The $50K/month that solved nothing. |
| The Firm | The deck that cost $300K. The junior who didn’t understand the business. The Salesforce pitch that made someone want to throw something. |
| The Bot | The AI rollout that nobody used. The tool that starts from zero every time. “We tried AI” as an excuse not to try again. |
Tone: Sharp, a little irreverent, grounded in real client experiences. These posts should make the right reader think that’s exactly what happened to us.
CTAs
We use three CTAs. Every post ends with one of these — no exceptions, no improvising.
| Post type | CTA | Why |
|---|---|---|
| Partner posts (Gold tier) | Weekly office hours — 30 min, open Q&A | Low lift to start, repeatable, drives MQLs via signups |
| Thought leadership | Newsletter — Forge Your Brain | Ties directly into the positioning we’re building |
| Service posts (Forge Your Brain) | Self-assessment or quiz — “Is your team AI-ready?” | Generates intent signal and qualifies MQLs before the call |
Channel Guidance
Purpose: Primary organic growth channel. Thought leadership, brand building, and inbound lead generation.
Who publishes: Ryan (drafts) → Luke (review/approval). Content distributed across Robert, Uttam, and Luke’s accounts.
Cadence: 7–8 posts/week (reduced from 10–12 to prioritize quality and event-driven MQLs)
Weekly Post Mix
Each week has up to 8 slots. Every slot has a defined owner, audience, and CTA.
| # | Post Type | Account | Audience | CTA |
|---|---|---|---|---|
| 1 | Gold Partner — Omni | Robert / Uttam | Retail data and growth leaders | Weekly office hours |
| 2 | Gold Partner — Snowflake | Uttam / Robert | Data leaders | Weekly office hours |
| 3 | Thought Leadership | Robert | Robert’s ICP | Forge Your Brain newsletter |
| 4 | Thought Leadership | Uttam | Uttam’s ICP | Forge Your Brain newsletter |
| 5 | Forge Your Brain — Service Post 1 | Robert | ICP-specific | ”Is your team AI-ready?” self-assessment |
| 6 | Forge Your Brain — Service Post 2 | Uttam | Same service / ICP as Post 5 | ”Is your team AI-ready?” self-assessment |
| 7 | Partner Announcement (when applicable) | Robert or Uttam | Partner audience | Weekly office hours |
| 8 | Luke Thought Leadership or Service Post (when no announcement) | Luke | Luke’s audience | Forge Your Brain newsletter or self-assessment |
Post Type Briefs
Gold Partner Posts (Omni + Snowflake) Each partner post leads with a client story or demo. The framing is always: the tool is the infrastructure — Brainforge made it work. Omni and Snowflake are the stack; we built the brain on top. Written for the leader who already uses or is evaluating the tool.
- Always embed a client story or demo. No abstract capability claims.
- Omni: retail data and growth leaders. Snowflake: data leaders and technical decision-makers.
- CTA: Weekly office hours.
Thought Leadership (Robert + Uttam)
Pulled from meeting transcripts, voice notes, or direct observations. Source material routes through robert-gpt or uttam-gpt to produce a draft in each person’s voice.
- Source material: meeting transcripts, client conversations, personal observations.
- Pillar guidance applies — but voice comes from the content system, not brand copy.
- CTA: Forge Your Brain newsletter.
Forge Your Brain — Service Posts (Robert + Uttam) Brand-forward posts. Both accounts run the same service/ICP pairing for two consecutive weeks — Post 1 is the concept, Post 2 is the specific service line example. Rotate ICP and service line every two weeks.
- CTA: “Is your team AI-ready?” self-assessment.
Partner Announcements Only when there’s a real announcement or ask from a partner. Not a slot that gets filled for the sake of it.
- Clean write-up plus graphic. No demos unless specifically requested.
- CTA: Weekly office hours.
- If there’s no announcement, this slot goes to Luke.
Luke Thought Leadership or Service Post
Luke’s slot. Agency Intelligence pipeline content or a Forge Your Brain post. Routes through luke-gpt.
- CTA: Forge Your Brain newsletter or self-assessment depending on post type.
North Star check: Before publishing, ask — does this connect to giving people access to the knowledge they need to win? If not, sharpen it.
Email — Forge Your Brain Newsletter
Purpose: Deepening the relationship with warm leads, existing clients, and referral partners. This is the destination for the thought leadership CTA — every newsletter signup comes from a LinkedIn post.
Who publishes: Ryan (drafts) → Luke (review/approval)
Cadence target: 1–2x per month
Email types:
- The Brief — a take on one idea from the content pillars
- The Case Study — a client story with context, challenge, and outcome
- The Resource — a useful framework or explainer tied to the pillars
North Star check: Every email should leave the reader better-informed, not just informed that Brainforge exists.
Webinars
Purpose: Demonstrating depth, building authority, generating warm leads. Webinars are for people who are already interested — they deepen the relationship and accelerate decisions.
Who owns: Hannah
Topic selection: Webinar topics should come directly from the content pillars. A topic is ready for a webinar if:
- It’s something clients ask about repeatedly
- It’s something we have a strong, contrarian, well-evidenced point of view on
- It maps to a specific stage in a buyer’s journey (awareness, consideration, decision)
Suggested topic areas:
- How to build a company brain — pillar 1 + what we do
- Why your AI rollout failed (and what to do instead) — The Bot enemy
- The hidden cost of the SaaS stack — The Stack enemy
- Data privacy in the age of AI — pillar 3
- What does an intelligent company actually look like? — Positioning overview
Format: 45–60 minutes. 30 min content, 15–20 min Q&A.
North Star check: The webinar should make someone walk away thinking I didn’t know that — and now I want to do something about it.
What Good Looks Like
A good piece of Brainforge content:
- Makes the right reader feel like it was written for them
- Says something specific — not something generally true about data or AI
- Connects (directly or indirectly) to giving people access to what they need to win
- Ends with the correct CTA for its post type (see CTAs section)
A bad piece of Brainforge content:
- Could have been published by any SaaS company or consulting firm
- Uses AI or data as set dressing without a real idea behind it
- Hedges when it should take a position
- Uses a CTA that isn’t one of the three