AIU Blueprint
BlueprintThe AI requirements studio

You have the idea. It writes the spec.

Bring a fuzzy idea — the kind you can't quite put into words. Blueprint runs the interview, predicts an answer for every decision so you mostly just confirm, and once you ratify it writes the whole plan into RoadWork to be built.

For founders · domain experts · anyone with an idea they can't spec.

Start a blueprint See a real one

Both buttons open the real studio — a young build: your work stays in this browser; saving is being built.

Read it in three secondsThe studio steps through it live — a fuzzy idea → the interview (you confirm, don't write) → the decided plan, ratified into RoadWork — with one thing (D7) kept honestly open because Blueprint won't invent a fact it can't stand behind. That last part is the whole promise.

Who it's for
The founder

An idea, a blank page

You can see the thing in your head. Turning it into something a team — or an agent — can build is the part that stalls for weeks.

"I know what I want. I just can't write the spec."

The domain expert

Deep in the work

You know your field cold — the clinic, the classroom, the trade. You're not a product manager, and you shouldn't have to become one to get your idea built.

"I'm a vet, not a software person."

The PM

Faster to decided

You do this for a living — and a studio that drafts the decisions, predicts the answers, and flags the real unknowns gets you to a ratified plan in an afternoon, not a fortnight.

"Get me to 'decided' without the blank-page tax."

What you can do

From a fuzzy idea to a decided, buildable plan — six jobs, most impactful first.

The biggest job is the idea→plan demo up top; the next four are drawn as the path you'd walk through the real studio screens; the last is grouped at the end. Each one drills into the exact screen that shows it.

Bring a fuzzy idea, leave with a decided plan Killer job · shown up top

You arrive with an idea you can't quite put into words and leave with a numbered, buildable plan — no blank page, no spec-speak. That's the idea→decided-plan window at the top of this page.

Start a blueprint
Confirm, don't write — every decision arrives pre-answered

A blank requirements doc becomes a board of numbered decisions, each with a predicted answer drafted from your own words — so your job shrinks from writing the spec to confirming it, one tap at a time.

the old way · a blank doc
Check-in schedule:
Who owns it:
What starts it:
drafts from your words
Blueprint · decisions
▸D4 · Day-3 call + day-10 recheck
✓D2 · Front desk · Confirmed
▸D5 · owner note · Confirm
See the decisions board
Trust that it never guesses a fact it can't stand behind

When the answer is something only you or a vendor knows, Blueprint flags it as an open question and carries it forward as a task — it never invents an answer to look finished.

D7 · a fact only your vendor knows
?Where does the visit data come from?
won't guess
carried honestly
◇D7 · Open question
▸task: confirm the data source
never a made-up integration
See the open question
Answer a few plain questions, one at a time

Instead of a form, Blueprint asks four plain questions the way a sharp product lead would — who it's for, what "done well" means, what exists today, and the one non-negotiable — one at a time.

Interview · Q1 of 4
BPWho is this for first?
MOThe front desk owns the list.
Next
Interview · Q4 of 4
BPThe one non-negotiable?
MOIt never invents a medical claim.
See the interview
Ratify once, and the whole plan writes into RoadWork

When every decision is settled you ratify, and the plan lands in RoadWork as a tracked work-tree — Idea → Task — with each task tagged to the decision it came from.

Ratify
✓9 of 9 settled
✦Ratify & send to RoadWork
ratify
RoadWork · work-tree
◆Idea · Recovery Rounds
P1auto-open a trackD3
P1day-3 + day-10 scheduleD4
each task tagged to its decision
See the handoff
One more it does

Keep it as your store of record

The settled requirements live in the Design Hub as the truth for what it should look like and do — if the build ever drifts, this wins.

See the store of record
Why it's different

Every other tool hands you a blank page. Blueprint hands you an answer.

The hard part of requirements was never the template — it was the blank page. Blueprint reads what you actually said and drafts a predicted answer for each decision, so your job shrinks from writing the spec to confirming it.

Instead of a blank requirements doc a template you still have to fill weeks waiting on a spec
The old way

A requirements template

An empty document with headings. You still have to know what goes under each one — which is exactly the thing you were stuck on.

Check-in schedule: ________________
Blueprint

A predicted answer you confirm

It drafts the answer from your own words and shows you why. You confirm, tweak, or replace — in one tap.

D4 · Predicted Day-3 call + day-10 recheck, adjustable per case Confirm · or change

It never invents a fact it can't stand behind.

When Blueprint can honestly predict an answer, it does. When it can't — when the answer is a fact only you or a vendor knows — it doesn't guess. It flags an open question and carries it forward as a task, so nothing false ever ships into your plan.

Open question — we won't guess D7 · Where does the visit data come from? Whether your practice-management system lets another tool read its records is a real fact only your vendor can confirm. So Blueprint leaves it open and writes a "confirm the data source" task — never a made-up integration.
One real session
An illustrative walkthrough — the flow, end to end
Dr. Mara OkaforOwner-vet BlueprintThe studio Renata SilvaFront-desk lead

Mara brought a sticky-note problem. In one sitting she left with a decided, buildable plan — and knew the one thing she still had to ask her software vendor.

First

Mara types her idea in her own words — no spec-speak. "Recovering patients need follow-up and we keep dropping people."

Minutes in

Blueprint asks four plain questions, one at a time — who it's for, what "done well" means, what exists today, and the one non-negotiable.

Then

It hands her nine numbered decisions, most already answered from what she said. She confirms them with a tap each — the schedule, who owns the list, what starts a follow-up.

On D7

Where does the visit data come from? Blueprint won't guess — it flags an open question. Mara notes: "ask our practice-management vendor." Nothing false enters the plan.

To finish

She ratifies. The plan writes straight into RoadWork as tracked work — each task tagged to the decision it came from.

Next day

Renata, who'll own the daily list, opens the store of record and sees exactly what Recovery Rounds will do on day one — no meeting required.

Walk this exact session
How it works

Bring the idea

Write it rough, in your own words. No spec-speak required.

Open intake

Answer a few questions

One at a time, the way a sharp product lead would ask.

Open the interview

Confirm the decisions

Every open question, numbered and mostly pre-answered. Answer by ID.

Open the decisions

Ratify the plan

One look at the whole thing, then lock it. You can't ratify a half-finished plan.

Open ratify

It writes into RoadWork

Your plan becomes a tracked work-tree — Idea to Task — the agents can build.

See the handoff

Kept as your store of record

The truth for what it should look like and do. If the build ever drifts, this wins.

See the store of record
See it working

Real surfaces you can click today, not screenshots. Honest status: the studio's first production increments are built — your work stays in the browser for now; saving, sign-in, and the RoadWork write are next.

The real thing · click it

The working studio

Every screen, idea to store-of-record. The interactions really work — confirm decisions, hit the ratify gate, see the handoff.

First production build — nothing persisted yet Open the studio The whole path

Design Hub entry

The journey as one clickable picture — idea in to decided plan out — drilling into every screen, diagram, and requirement.

Visual map + drill-downs See the path How it's built + graded

The build packet

Flows, requirements, and numbered test cases — enough that a builder with no context could build it and prove it works. Each screen's spec is one drill-down away.

Spec + test cases Open the packet
Where it fits

Blueprint decides. RoadWork tracks. Agent Engine executes.

BlueprintTurns your idea into a decided plan.Decides
RoadWorkHolds every piece and its priority.Tracks
Agent EngineBuilds and ships the real thing.Executes

Blueprint owns everything up to decided. The moment you ratify, RoadWork takes it from there.

On the AIU homepage, the Blueprint hero row links to this page and carries the same ratified flow line: Blueprint decides → RoadWork tracks → Agent Engine executes. One line, two surfaces — kept in sync so the home page and this landing never drift.

What we're honest about
Newly built — the first increments

The studio you can click is a young production build, grown screen-for-screen from the gated design. The screens and the flow are real; it will keep growing.

Nothing is saved yet

Today the studio holds your work in the browser. The saved data model, sign-in, and the write into RoadWork are being built — flagged, not faked.

Open questions are named, never hidden

The discipline the product uses on your idea (D7) applies to its own build: where the plan isn't settled — how it saves, its exact routes, the RoadWork write — it's written down as an open question, not guessed.

The brand colour is pending a colourblind check

Blueprint's blueprint-indigo is proposed until it clears a deuteranopia + protanopia check — our founder is red/green colourblind, so every colour earns its place by lightness, glyph, and label, never by hue.

Bring the idea you've been sitting on.

Rough is fine. You'll have a decided, buildable plan — and a clear picture of the one or two things you still need to find out — by the end of the session.

Start a blueprint Walk a finished one first Early access — join the waitlist