A worked example showing what week one of a 6-Week Build Partnership produces.

About this sample This is a representative Build Audit for a fictional but realistic project. It mirrors the structure, depth, and style of the audits real clients receive in the first week of a Build Partnership. Specific client audits are confidential. This sample exists so you can see what you'd actually walk away with — before you book a call.

The project

Client: Senior PM at a Series-B SaaS company. 38. $310K total comp. Has been building a paid newsletter on the side, called Promotion Math, about how product managers move from senior to staff. Subscriber count today: 1,200 free, 0 paid. Has been "two months from launching paid" for nine months.

Goal stated on first call: "Launch the paid tier. Have at least 25 paying subscribers within 60 days of launch. Stop telling people I'm 'about to launch the paid tier.'"

Time available: 6-8 hours per week, Tuesday + Thursday evenings + Saturday morning.

Constraints: Cannot quit day job. Spouse is launching their own thing in Q4. One kid, age 6.

Week 0 audit summary

The diagnosis is straightforward. There is no shipping problem. There is a commitment problem and a scope problem, and they are reinforcing each other.

The infrastructure is fine. Beehiiv account, working email pipeline, 1,200 list subscribers who already engage at a 38% open rate. The newsletter has shipped 14 free issues. The client knows how to write. The client knows how to ship — at work. They have not been able to do the one specific thing that converts a free newsletter into a paid one, which is to charge for it.

What's actually been blocking the launch:

Pricing indecision. Three pricing models on three different docs. None decided.
Scope creep. The "paid tier" has expanded to include a community Discord, monthly Q&A calls, a private podcast feed, and an email coaching add-on. None of these existed in the original concept four months ago.
Permission gap. No external commitment. No public ship date. No one waiting.
Imposter loop. "I'm a PM, not a media operator. People will see I don't know what I'm doing." Not the real problem. Real problem is item 2.

This is a 6-week project. Currently being scoped as a 6-month project. We are going to fix that on this audit.

V1 lethal minimum

The smallest version of the paid tier that, if real subscribers paid for it tomorrow, would do the one thing the paid tier was supposed to do.

The V1, in one sentence: A paid weekly newsletter at $12/month or $120/year, delivered every Wednesday, that goes deeper than the free newsletter on a single topic per issue.

That's it. That's the whole product.

What's in V1:

One additional weekly issue (Wednesday). Paid only.
Same writer, same voice, same Beehiiv setup. No new tools.
Stripe integration via Beehiiv's native paid tier (already supported).
A landing page with three sections: what is it, who is it for, who is it not for, plus the price and the button. One page. No funnel.
A grandfather discount: $100/year for the first 50 subscribers. Closes on launch day +14.

What is explicitly NOT in V1:

❌ Discord community. Goes on V1.1 doc. Not built. Not promised.
❌ Monthly Q&A calls. Goes on V1.1 doc.
❌ Private podcast feed. Goes on V2 doc.
❌ Email coaching add-on. Goes on "Maybe forever" doc.
❌ Brand redesign. The current Beehiiv default is fine. We will revisit at 100 paid subscribers, not before.
❌ A second writer. You are the writer. We will revisit at 250 paid subscribers, not before.

The decision rule for the next 6 weeks is simple. If the new feature isn't on the "in V1" list, it goes on the V1.1 doc and is not discussed until launch + 30 days.

The 6-week roadmap

Week 1 — Decision lock

Pricing decided in writing: $12/month, $120/year, $100/year founding-member rate for first 50
Launch date set: Wednesday of Week 6 — written on the wall
First three people told the launch date: spouse, plus two friends from the senior-PM Slack group
V1.1 doc created and the four cut features listed there
Cancel the Discord research tab. You don't need a Discord plan.

Time budget: 6 hours total. 3 on the pricing decision, 3 on the public commitment.

Week 2 — Landing page draft

A live, ugly, working sales page at promotionmath.com/paid. Not pretty. Working. Nine sections in order: headline, who-it's-for paragraph, the promise, who-it's-not-for, pricing, first-issue table of contents, about the writer, CTA, FAQ.

Time budget: 6-8 hours. Most of it on the headline, the who-it's-for, and the who-it's-not-for. Hard rule: No design work. The Beehiiv default is the design.

Week 3 — First paid issue, drafted

Write the first paid issue — the one paying subscribers will read on Wednesday of week 6. Has to be the best thing you've written on the topic, ever. ~2,000 words. Specific. Named examples (with permission or anonymized).

Time budget: 6-8 hours. Half drafting, half cutting. Hard rule: No promotion this week.

Week 4 — Pre-launch sequence

A 4-email sequence to your free list in the 7 days before launch. Day -7 soft mention. Day -4 the case for paid. Day -1 first issue's table of contents. Day 0 launch.

Time budget: 4-5 hours. Hard rule: No social posts about the launch yet.

Week 5 — Polish and pressure-test

Run the system end-to-end. Buy your own founding-member tier with a personal email. Confirm Stripe + Beehiiv. Have one trusted reader run the same purchase flow — if it takes more than 90 seconds, fix the friction.

Time budget: 5-6 hours. Hard rule: No new features.

Week 6 — Launch

Wednesday morning. 7am email to free list. 8am one tweet, one LinkedIn post, no threads. Day-2 follow-up email at 7pm.

Acceptance criteria for "shipped": paid tier live, first issue queued, at least one paying subscriber by end of Wednesday.

Hard rule: Do not delay the launch. If something is broken Wednesday morning that's not load-bearing, ship anyway and fix in flight.

Three structural reframes

Reframe 1: The pricing indecision isn't a pricing problem

The three pricing models in three docs aren't a thinking problem. They're a commitment-deferral mechanism. As long as the price isn't decided, the product can't launch. As long as it can't launch, you can't be wrong about the price. Decision is the cost-of-launching.

Reframe 2: The Discord/Q&A/podcast scope isn't ambition

It looks like ambition. It's actually scope-as-permission-not-to-launch. You'd never let a PM on your team launch a paid tier with all four as the V1. We're going to do the same here.

Reframe 3: The imposter loop is solved by shipping, not by becoming worthy

You think you'll feel ready when you've "earned" the right to charge. You won't. People with much weaker resumes than yours have not felt ready either. The feeling resolves after the launch, not before.

What you walk away from week 1 with

This document. Plus a locked launch date written down. A locked V1 scope. A locked price. Three friends who know the launch date. A V1.1 doc that absorbs every "we should add..." thought without disrupting the V1 ship. A 6-week calendar with one specific deliverable per week and time budgets attached. A reframe for the three structural patterns that have been keeping the project stalled.

Nothing on this list is information you couldn't have generated alone. The point isn't novel information. The point is forcing the decisions you've been deferring, in one 90-minute working session, with a second voice in the room who has no incentive to let you push them off another week.

A note on this format

The audits real clients receive are tighter than this one. They run 8-12 pages, not the longer treatment here. This sample includes additional commentary so prospects can see why the structural moves are made, not just what they are.

Real audits also include items not appropriate for a public sample: specific competitor analysis, named relationships, financial assumptions, and confidential project details. Yours would too.

The methodology is the same. The voice is the same. The decision-forcing function is the same.

Build Audit — Sample