The three opinions the founder holds that their competitors would not say out loud.
afka uses analytics cookies to understand how visitors use the site. No ads, no data sales.
The working manual for setting a client up with the afka content team: LinkedIn run as GTM infrastructure, drafted from what the company actually did, tested before anyone sees it, and approved word by word by the people whose names are on it.
Founders and operations leads of 5 to 50 person companies whose best material is the work they are already doing and never write down. Buyers read the company long before they talk to it, and today the company publishes nothing.
Content looks like a one-person function and is not: the voice belongs to the founder, the material belongs to the whole company, and sales lives downstream of both. Draw the four-row table first.
The founder owns the voice and approves every word published under their name, in the composer or from a Slack card.
Whoever owns GTM reads the weekly plan and decides which post carries which goal, positioning or pipeline.
Anyone on the team can hand the agent raw material through the composer: a launch, a fix, a customer conversation worth writing about.
The meeting agent joins the weekly GTM call on Zoom, Google Meet or Microsoft Teams, and what the team decides about next week's positioning becomes next week's briefs.
The approver is not negotiable in this vertical: the person whose name is on the post approves it, every time, in every mode including Auto. The teacher refines the voice profile as drafts get edited. The audit reader checks that every published word traces to an approval and every claim traces to a source.
The content agent team inside the client workspace: a voice profile built from an interview, research briefs from the company's real events, drafts written against the voice with sources kept, a weekly plan across the funnel, testing against a panel built from the client's ICP, and publishing only with the client's approval, under the content skill pack you fill together.
Guidance is plain language: how the founder argues, what they refuse to say, which words are theirs and which words are banned. Guardrails are code, and in this vertical they are famous for a reason: a draft that names a customer, states a number, or speaks as the agent persona escalates to a human, in every mode including Auto. A guardrail beats any instruction, and the conservative action wins. The interview gathers exactly these answers, and they go straight into the pack:
The three opinions the founder holds that their competitors would not say out loud.
The customers that may never be named, and the numbers that may never be stated, even when true.
The sentence shape and the words the founder reaches for when they disagree with something.
The day and hour the weekly plan is decided, and who is in the room.
Connections run through managed connectors: a popup opens, the client authorizes the sources of what the company actually did, the calendar and the channels, and afka never receives a password. Briefs carry their sources, so every claim in a draft traces to something that happened. The connectors screen shows status, reconnect is one click, disconnecting is revocation within one task cycle.
Run the interview with the founder: how they argue, what they refuse to say, which words are theirs. This becomes the voice profile every draft is written against, and it is the step that cannot be skipped.
A new workspace picks the content function and produces a first finished artifact from seeded sample data in under a minute: a draft with its brief and its sources attached. The founder sees the shape, brief, draft, evidence, before their own material enters the system.
A draft that names a customer, states a number, or speaks as the agent persona escalates to a human, in every mode including Auto. Show the client these gates exist in the guardrail layer before the first real draft, and show that no instruction, theirs or anyone's, can talk past them.
The first drafts arrive tested against a panel built from the client's ICP, with the reasoning attached. The founder edits one, and the edit teaches the voice profile. The client approves one and posts it. The loop from real event to published position, walked once with the team watching, is the deployment.
Set the weekly plan cadence, invite the meeting agent to the GTM call so decisions become briefs, show how engagement feeds the next plan and becomes warm context for sales, and leave the client as the approver of every word that goes out under their name.
Content builds value only on a rhythm, and this rhythm is deliberately small.
Daily, five minutes: the founder clears the approval queue: drafts waiting for a yes, edits waiting for a re-test.
Weekly, on the GTM call: the meeting agent attends, the team decides next week's goals per post, and the decisions become briefs before the call ends.
Weekly, ten minutes: the teacher reviews what the voice profile learned from this week's edits, keeps what sharpened it, rejects what blurred it.
In content the fear is reputational, and the answers should be specific.
Approval, required in every mode including Auto. Publishing happens only with the client's yes, the approver is the person whose name is on the post, and that is by design, not a setting.
Two things. Every brief carries its sources, so a draft's claims trace to something that happened. And a draft that names a customer or states a number escalates to a human regardless of mode, enforced in code.
The voice profile is built from the founder's interview and their edits, it lives in the client workspace, isolated per business, and it never leaves: skills are workspace-scoped by construction, with no transfer path to any other tenant.
The three situations you will actually meet: a draft that misses the voice, which the founder's edit turns into a skill correction; a week with no material, which the briefs solve by mining the audit of what the company shipped; and a post that underperforms, which becomes data in the next weekly plan rather than a crisis. None of the three is an incident.
You earn 30 percent of the client subscription for twelve months from the first paid invoice, with first-touch attribution for 90 days. Your implementation fee is your own business and stays yours. afka publishes no income projections: the terms are the terms.
No. It researches, drafts, tests and schedules; publishing happens only with the client's approval. The client stays the approver of every word.
From the interview and from the company's real events: launches, fixes, customer conversations, market shifts. Every draft is backed by a real source.
A scheduler distributes what somebody already wrote. This team does the work before distribution: research, drafting in the client's voice, testing against the ICP, and planning the week.
The program terms, the agreement and your link are on the deployer page.
The deployer program