the brief

The pitch is adocument.

Every nyro build starts as a written brief: the product, the model, the build plan, the deal, the risks. It lands within days of the strategy call, and the build does not start until you approve it. This is the anatomy of that document.

Sample pages below · money is redacted, it is agreed per deal

Page 01 · The cover
The week we talk

Build brief & proposal

Yourapp.

Built around your audience.

Built for you · @yourhandle  ·  By nyro

the anatomy

Page by page, before a dollar moves.

The same document, whoever you are: what we will build, what it should make, what could break, and what it costs. Hover the redactions.

Page 02 · Executive summary

Executive summary

Your audience, as a product.

What we are building, why your audience buys it, and what both of us make if it works. One page, no jargon, every claim traceable to a page deeper in.

on the callredacted, agreed per deal

Hero price

on the callredacted, agreed per deal

Your share

Weeks

To first build

100%

Yours, in writing

Page 07 · The model

Revenue model · modeled

The trajectory, three ways.

ScenarioMonth 3Month 6Month 12
Conservativeon the callredacted, agreed per dealon the callredacted, agreed per dealon the callredacted, agreed per deal
Baseon the callredacted, agreed per dealon the callredacted, agreed per dealon the callredacted, agreed per deal
Optimisticon the callredacted, agreed per dealon the callredacted, agreed per dealon the callredacted, agreed per deal

Anchored to the conservative case, always. The upside is the argument for the split; the downside is the one we plan around.

Page 09 · The build plan

Build timeline

Day 0 to launch.

KICKOFF

Brand kit in, scaffolding up, the extraction session on your calendar.

CORE BUILD · MVP review

The product takes shape on proven rails. You review a working MVP mid-build.

FEATURE LAYER · at-risk

The parts that need your voice and your face, front-loaded and scheduled.

LAUNCH

QA, polish, the content session, and the ship. Then the real work starts.

Dates are day-labels, not vibes: the plan holds even if the start shifts. Your calendar drives the two items only you can do.

Page 12 · Day 0, illustrated
# yourappnyro × you · 3 members
DAY 0
N

nyro 5:04 PM

Brief approved 🔥 the clock is live. Kickoff list incoming: brand kit, audience insights, and your calendar for the extraction session.

Y

You 5:11 PM

Locked. Sending the kit tonight.

N

nyro 5:12 PM

Repo scaffolded. Day 0 ✅

Page 14 · The risks

Risks & mitigation

What could break, and the plan.

The content bottleneck

Your voice is the moat and the constraint, so it is front-loaded, batched, and scheduled in the agreement.

The unproven funnel

Instrumented from day one, priced to qualify intent, and modeled on the conservative case for exactly this reason.

Key-person risk

You are the face. The system is built so the product survives your busiest month.

Every risk ships with a named mitigation, not a hope.

Download the sample brief· PDF, 8 pages

Same engine as the real ones. Redactions included.

the standard

Relentless, in writing.

The brief is not a brochure. It is the set of promises the build is held to.

We take accountability.

If a day slips on our side, you hear it from us first, in the channel, with the recovery plan attached. Decisions live in writing so blame has nowhere to hide, including ours.

We tell the truth early.

Your reported numbers get flagged as reported until verified. Projections anchor to the conservative case. We would rather lose a pitch than inflate math.

We ship on a clock.

The brief carries a day-by-day build plan with the risky items marked at-risk in advance, so the clock is visible to you the entire way.

We answer.

Response times are written into the agreement, and you are in the channel with the people doing the work. No account managers between you and the build.

We only eat if it works.

Our share is of what the product makes. If it earns nothing, we earn nothing, which makes your outcome our payroll.

Launch is Day 0, not the finish.

The brief plans past the ship date: what lands in the first month, what waits for real data, and how the product keeps growing.

Not values on a wall. Clauses in the agreement.

what's in yours

Ten sections. Zero mystery.

The table of contents is the same for a chef, a coach, or a comedian. The answers are not.

Reported numbers get flagged as reported. Projections anchor to the conservative case. Mockups are labeled illustrative. The brief treats your numbers the way we will treat the product’s money.

01
The positioning · what the app is, in one sentence you would say out loud
02
The buyer · who actually pays, and the moment they decide to
03
The competitive scan · what every neighbouring app proves, and the gap yours owns
04
The MVP scope · the ruthless feature list, and the explicit not-yet list
05
The tech and the costs · the stack, the infra bill, and the unit math
06
The model · three scenarios, anchored to the conservative case
07
The build plan · day by day, with the at-risk items marked in advance
08
The deal · the split, the ownership, and the obligations, in plain language
09
The risks · what could break, each with a named mitigation
10
The open questions · what we still owe you answers on before the build locks

The next brief has your handle on it.

One strategy call, then the document lands: your product, your model, your plan, your deal. You approve it before anything is built or paid.