The ninety days you can actually staff

A ninety-day launch plan, in this house, is a calendar of artefacts and approvals, not a mood board of “go-to-market.” Each week names what will be drafted, who approves it, which claims it may use, which channels it may use, and what happens if an artefact is late. If a week cannot be staffed, it is not in the plan. Ambition that cannot be staffed is how teams announce and then vanish.

Funnel design is next, and it is where founders try to smuggle the 2017 machine back in. We will design a path from professional attention to a conversation, a data room, a waitlist of counterparties, a partner intro. We will not design a public sale path, an allocation queue, or a points mechanic that is a book-build in a hoodie. If the only funnel they want is that machine, we stop.

The content system is a way of making sentences without improvising. Templates for site, X, data-room summaries, founder briefs, partner briefs. Each template is mapped to live claims. A designer who needs “something punchier” is given the prohibited list rather than a pep talk. Punch is not a field on the register.

Community and creator plans are written as operations. Moderation SLA. What the server is for. What moderators may not answer. Which creators, if any, can honour the geography lock. Disclosure. Takedown. If the honest creator plan is “none, yet,” that is a valid plan. It is better than a roster of strangers with mixed audiences.

“Global retail” is a control risk, not a target. Segment by jurisdiction, sophistication and promotion route.