Service 05 · Authority

Founder Positioning

Authority architecture for technical founders — built to be discoverable, not promotional. Engineering your existing thinking into surfaces that compound: writing, talks, repos, citations. Designed for founders who would rather build than perform.

Inbound channel
3–8 mo
Until founder distribution starts producing meaningful inbound, depending on starting surface
Effort required
4–6 hrs/wk
Sustainable founder time once the system is running — not a full-time content job
01 · The problem

Most founder content is performance, not architecture

The default playbook for technical founders is: post on LinkedIn, get coached on “personal brand,” try to be more visible. What you end up with is performative content that doesn’t compound, doesn’t reflect how you actually think, and feels uncomfortable to produce.

The real problem isn’t visibility. It’s that your existing thinking — the things you say in calls, the ideas you have in the shower, the frameworks you reach for repeatedly — isn’t being captured in surfaces that compound. Performance gets you views. Architecture gets you authority.

02 · The approach

Capture, structure, compound

I design the system that turns your existing thinking into compounding distribution. The work is extraction (capturing what you already think but don’t write down), structure (organising it into surfaces that build authority), and compounding (making each output reinforce the next).

The engagement starts with a series of working sessions where I extract your actual operating frameworks — the ones in your head, not the ones on LinkedIn. From there we design the writing rhythm, the surface architecture (essays, talks, repos, citations), and the distribution loops that compound over 12–24 months.

None of this requires you to be a “thought leader.” It requires you to be visible in the exact ways you already are — just architecturally.

03 · What’s included

Deliverables

Thinking extraction sessions

4–6 working sessions where I extract your operating frameworks, recurring ideas, and the systems you reach for repeatedly. Recorded, transcribed, and structured.

Surface architecture

The plan for how your thinking surfaces — essays, talks, repos, citations, conference appearances. What goes where and why.

Voice & writing framework

How to write in your voice without it feeling like marketing. Brief templates, structural rules, and the editorial bar that makes content cite-able.

Distribution rhythm

A sustainable publishing cadence — typically 1 long essay per month, plus structured short-form. Designed around your real schedule, not aspirational.

Citation surface optimisation

How your founder identity earns citations from AI search systems. Entity disambiguation, schema, source authority architecture.

System handover

Operating documentation, brief templates, and (optionally) introductions to ghostwriters / editors who can sustain the rhythm long-term.

04 · Process

What 12 weeks looks like

Weeks 1–4

Extraction

4–6 working sessions extracting your operating frameworks and existing thinking. Structured into a working document.

Weeks 5–6

Architecture

Surface plan, voice framework, distribution rhythm. The blueprint document for the next 12 months.

Weeks 7–10

Pilot production

Ship the first 2–3 essays / outputs. Refine the voice framework based on what surfaces. Set up distribution loops.

Weeks 11–12

Handover & rhythm

Long-term cadence, documentation, optional ghostwriter handover. The system that runs forward.

05 · Engagement

Pricing & structure

Option 01

Strategic intensive

$4,500
3-week engagement

Extraction sessions, surface architecture, and 12-month plan. You execute with your team.

  • 4 extraction sessions
  • Surface architecture document
  • Voice framework draft
  • 12-month plan
Option 03

Embedded retainer

$3,500/mo
6+ month retainer

Ongoing founder editorial partner — monthly extraction, content briefs, and architecture refinement.

  • Everything in Architecture sprint
  • Monthly extraction sessions
  • Brief writing & editing
  • Ongoing rhythm support
06 · Proof

A system in action

Case study · Personal Brand Build

Operator positioning through systems, not posts

“A 12-month build of my own discoverability infrastructure — writing rhythm, tooling, AI-citation surface, and the architecture that turned this site into a compounding asset.”

6/mo Inbound enquiries
38 Essays shipped
12 Tools released
07 · Common questions

FAQ

Probably yes — the engagement is explicitly designed for founders who don’t want performative visibility. The work is about architecture, not persona. The output is content that sounds like you (because it is you), distributed in surfaces that compound (because they’re engineered to).
During the engagement: 2–3 hours per week of working sessions. After: 4–6 hours per week sustained, mostly writing. Less if you work with a ghostwriter, more if you go fully solo. The system is designed around founder schedules, not full-time creators.
Most technical founders are better writers than they think — they just need structure. The voice framework removes most of the structural decisions, leaving you to focus on what you actually want to say. If you genuinely don’t want to write, we set up a ghostwriting workflow that preserves your voice.
It shouldn’t — and we explicitly architect to avoid that. Your founder surface and your company surface should complement each other (you’re the operator perspective, the company is the product perspective), not compete. Part of the work is mapping the boundary.
Brand coaches optimise for performance and visibility. I design architecture and distribution. Different disciplines. Most coaches won’t touch the entity / citation / SEO layer because it’s outside their expertise.

Architect founder distribution that compounds.

I take 1–2 Founder Positioning engagements per quarter. If you’re a technical founder ready to build authority architecture rather than personal brand, let’s talk.

Other services