Generate a 90-Day Growth Blueprint

What you'll get

Two documents about one company, built to be used together. The first is the 90-Day Growth Blueprint, a PDF that lays out the strategy. The second is a 90-Day Implementation Tracker, an Excel file built to run that strategy week by week. This is real research rather than a template fill, so plan for the full run to take a working session, not a minute. You need chapter 3 done, and the research gets sharper with every tool you have connected.

What makes this deliverable different

Most strategy documents are a stack of confident claims with no way to check any of them. The Blueprint is built the opposite way, so every claim can be challenged, and that single difference is what lets a leadership team actually run on it:

• An executive summary puts the situation, the central question, and the play on one page.
• An evidence ledger traces every claim to a source anyone in the room can check, so "says who?" gets a thirty-second answer instead of a debate.
• A positioning hypothesis names the company's distinctive mechanism, the proof that exists today, and the proof still missing.
• One binding constraint names the single bottleneck blocking the Day-90 outcome, with its countermeasures, a weekly scorecard, and a decision rule for when to change course.
• Initiatives with Day-30, 60, and 90 targets, each carrying a named owner and its leading, lagging, and guardrail metrics.
• A premortem that lists how the plan could fail, written down before week one begins.
• A "not doing now" list, because focus is mostly subtraction and the things you refuse matter as much as the things you choose.

The steps

1. Ask for the Blueprint.

/marg:blueprint

Give the company briefing when asked: who the company is, what it sells, and any context you already hold. The briefing sets the ceiling on the research, so the more specific you are here, the sharper everything downstream.

2. Let the research run. Marg investigates the company from public sources and your connected tools, then drafts the Blueprint section by section against a strict structure rather than free-form.

3. Wait for validation. Every Blueprint clears a hard validation gate before it renders. If a section fails, Marg fixes it and revalidates instead of shipping a broken document, and any warnings that survive the gate come to you flagged for a human eye.

4. Collect the deliverables. The PDF and the Excel tracker land in your output folder, named after the company.

What comes back

The two files split the work between them. The PDF carries the strategy and its evidence ledger. The tracker carries the execution: the weekly review agenda, the scorecard, the owners, and the targets. They are built from the same plan, which is what makes the tracker the Blueprint translated into Monday mornings rather than a separate document to reconcile. Review both before anything leaves the building, because delivery to a client or a founder is always a human decision here, never something Marg does on its own.

Variations

• For your own company: run it on yourself first. The constraint analysis and the premortem are at their most uncomfortable, and therefore their most useful, when the quarter under the microscope is your own.
• For a prospect or client: advisory firms and agencies use the Blueprint as a high-proof opening deliverable, the thing that wins the room before the pitch. Chapter 9 covers how the advisory team extends it.

If something goes wrong

• Validation keeps failing: the briefing was too thin for the research to ground its claims. Add specifics, the market, the revenue band, the competitors you already know, and rerun.
• The research missed something you know: say so in plain words, and Marg revises the affected sections and revalidates rather than starting over.
• You expected live financials but got ranges: the relevant tools are not connected, so the draft used ranges for the uncertain values by design. Chapter 24 covers connecting them.