One developer tool, seven days, one plan.

Recommendation

Use the first ninety days to build one short-form account into a measurable acquisition channel. The account already holds the proof that the audience responds: a single creator post outperformed the account's entire history combined. What is missing is the system around that result. Start with one account, connect every post to a measurable next step, and expand only after the same result repeats.

01 Asset inventory

Everything the company already owns that can carry attention, ranked by distribution potential rather than by what it cost to make.

• A three-second product moment. The tool catches a real problem on screen, in a real repository, in a few seconds. This is the strongest asset and it is barely used.
• Founder and engineer explanations. Recorded talks and podcast appearances hold clear, opinionated answers to the questions developers ask. They are currently published as long clips with the same caption.
• One proven creator post. A comedy format about the problem the tool solves, gated with a comment keyword. It travelled; nothing was set up to measure what happened next.
• Documentation and changelog. Accurate, detailed, and read only by existing users.
• Customer proof. Approved quotes and logos, usable subject to naming approval.

Ranked by potential: the product moment first, the proven creator format second, the founder explanations third. The documentation is the reference, not the source.

02 Attention-system map

Where the audience spends time, which formats travel there, and who is getting the attention the company wants.

A trailing sweep of reference accounts in the builder niche shows a consistent craft: a face over a screen recording, a cut every one to three seconds, numbered step overlays, and in most cases no voiceover at all. The content that travels is fast product moments, founder momentum and jokes about software built with AI agents. The accounts winning that attention are individual builders and clip pages, not the tool vendors.

The company's own account posts repurposed long-form clips with a boilerplate caption. Median engagement is in single figures. The account is not struggling; it is unopened, which is easier to fix.

03 Distribution gap diagnosis

The constraint is not content. The company produces more than it can place. The gap is between the product moment and the people who would recognise it: the moment lives in documentation and demos that only existing users see, and the one time it reached new people through a creator, the path from attention to trial did not exist.

Three questions the ninety days must answer:

1. Which formats and hooks earn attention from developers who have not tried the tool?
2. Which of those lead to a measurable next step, not only reach?
3. Which publishing and reporting process makes the result repeatable rather than a one-off?

04 Three evidence-backed opportunities

Each one tied to a signal in the market, not a best practice.

1. The problem as the joke, the product as the fix. The audience already jokes about software that breaks after the demo. The reference sweep shows the format travels. The tool is the honest punchline, and the same fifteen seconds can carry both.
2. Proof before the ask. Developers are an ad-resistant audience. A real repository, a real finding, a real fix on screen, then a next step only when it helps the viewer reproduce the result.
3. Rebuild the proven creator format as a system. The one post that travelled was an isolated collaboration. Recut its angle for the company's own account, brief creators on the same format, and put the comment-keyword automation live before the first gated post.

05 Prioritised ninety-day roadmap

Three phases, a decision at the end of each.

• Days 1 to 30, find useful signals. Audit the account, confirm approved product claims, set up keyword automation and tracked links before the first post, and publish a deliberately varied first set: humour about the problem, product demonstrations in real repositories, workflow tutorials, and recut versions of the proven angle. Decision at day 30: choose two or three formats, two audience groups and the strongest gates to test again.
• Days 31 to 60, test whether the results repeat. Variations of the strongest posts, the first creator tests on the proven format, and improvements to what happens after someone comments the keyword. Decision at day 60: continue organic only, or approve a monthly creator budget aimed at the proven format.
• Days 61 to 90, decide where to invest. Increase only the formats, creators and routes that reached relevant people and led to trials. Change or stop weak formats. Decision at day 90: approve the six-month content mix, production level, creator plan and any account or platform expansion.

What to leave alone until the first cycle reports back: additional accounts, additional platforms, and paid amplification of any kind.

06 Channel recommendations

• Operate: one short-form account the company owns, run under its approvals. Every post carries one job and is judged against it.
• Add after evidence: creators briefed on the proven format, then niche pages for burst reach on angles that have already worked on the owned account.
• Ignore for now: a second owned account, long-form platforms, and any channel where the product moment cannot be shown in the first three seconds.

The reasoning holds because the asset is a visual moment. Channels that reward a fast visual moment are where it travels; channels that reward reading are where the documentation already lives.

07 Execution plan

• Formats: the problem-as-joke skit, the real-repository demonstration, the workflow tutorial, the founder explanation cut to one claim.
• Hooks: a face-first opening, a visible constraint, a first-person confession, or the incumbent being questioned. The hook is a separate production unit from the rest of the video and is tested on its own.
• Cadence: a fixed weekly rhythm agreed at kickoff, each post assigned one job before it is made.
• Ownership: Spektra produces, publishes and reports; the company approves claims, supplies a technical reviewer and answers within an agreed window when a post raises a product question.
• First production set: a named list of scripts, each with its format, hook, job and gate, ready to film in the first week.
• The company's time: setup, then about four to five hours a month for reviews and approvals.

08 Measurement boundary

One primary measure: trials started from tracked social clicks. One baseline: the account's current median engagement and the current number of tracked trials from social, which is zero because nothing is tracked yet.

The ladder the weekly report climbs, and how far the instrumentation can support it:

Reach is reported as reach, never as revenue. The Blueprint states the highest level the evidence can reach so that the first cycle is judged against what can actually be measured.

The decision after ninety days

The cycle should lead to one of three decisions:

1. Results are not yet consistent. Keep one account. Improve the content, the hooks and the path from post to trial before increasing production.
2. Several formats work consistently. Produce more of them and scale the creator brief around the proven format.
3. One format grows quickly and leads to trials. Publish related follow-ups while interest is high and make sure keyword comments and new trials receive timely support.

None of this assumes every test will work. It gives the company a controlled way to learn, protect the brand and increase investment only when the evidence supports it.