Master Blueprint · Excerpt · Generated by Brieftify, refined by uxlicious
loopd — payments for friends
This is a shortened sample of a real Blueprint Sprint deliverable. The full document an AI build tool receives runs 30–60 pages. This excerpt shows the shape, depth, and format.
ProjectLOOPD
TypeMOBILE — iOS / ANDROID
Target toolLOVABLE
SheetEXCERPT 1 / 1
B-01 — Product Definition
Positioning
loopd is the fastest way to settle money between friends — splitting a bill, paying someone back, chipping in for a gift — without the awkwardness of asking twice. It is not a bank, not a budgeting app, and not a social feed. It does one thing: move small amounts of money between people who already trust each other, in under five seconds.
Primary user
- Who: 22–35, urban, splits costs with friends weekly, already uses one bank app they find tedious.
- Core job: "I owe my friend money and I want it handled before I forget."
- Emotional job: never be the person who didn't pay them back.
Success metric
A new user completes their first send within 90 seconds of opening the app, with no support article and no failed step.
B-02 — Core User Flow: Send Money
The happy path is three taps. Every branch below is specified so the build tool does not invent its own.
[Home] tap Send → [Pick person] recent contacts first, search fallback → [Enter amount] numeric pad, big type → [Confirm] face/PIN → [Sent] animated receipt → returns to [Home] with new activity row on top
Unhappy paths (the part most briefs forget)
- Insufficient balance: block at Confirm, offer "Add money" inline — never after the attempt.
- Recipient not on loopd: send an invite link with the amount attached; funds held 72h then auto-refunded.
- Network drops mid-send: optimistic UI shows "Sending…", reconciles on reconnect, never double-charges.
- Wrong person tapped: 5-second undo on the receipt screen before the transfer commits.
B-03 — Screen Spec: Home
SCREEN 01
Home / Balance
Balance glanceable at top, 3 quick actions, activity feed below. The first thing seen on every launch.
SCREEN 02
Send — Pick person
Recent first, alphabetical search fallback. Avatars, not just names, to reduce mis-sends.
SCREEN 03
Send — Amount
Oversized numeric entry. Note field optional. Primary button anchored, thumb-reachable.
SCREEN 04
Receipt
Confirmation with the 5-second undo. Celebratory but fast — never blocks the next action.
Home — component checklist
- Balance block — 38pt figure, tap to toggle visibility, "Total balance" label above.
- Quick actions — Send / Request / Add Card, equal weight, radius 18, soft elevation.
- Activity feed — newest first, three states: incoming (green +), outgoing (−), pending (muted).
- Empty state — first-run shows "Send your first loopd" with a single highlighted contact.
B-05 — Visual Direction (tokens)
Handed to the build tool as variables so the result is coherent, not "AI-generated default blue."
--accent #2230FF
--ink #16160F
--pos #0A8A4A
--radius 18px
AaGeist / 600
--elev soft
B-06 — Build-Ready Handoff
The blueprint ships as a structured master file. This is the opening of the actual loopd.md an AI tool receives:
# loopd — Master Build Prompt (excerpt)
## App
A peer-to-peer payments app for friends. Mobile-first.
Tone: calm, fast, trustworthy. Not playful, not corporate.
## Build order
1. Home/Balance screen (see SCREEN 01)
2. Send flow, happy path (see B-02)
3. Send flow, all 4 unhappy paths — do not skip
4. Apply design tokens from B-05 globally before styling
## Hard rules
- Never allow a send without the Confirm step
- Every transfer has a 5-second undo before commit
- Optimistic UI on send; reconcile on reconnect
- Empty states are required, not optional
This is what your AI build tool reads instead of guessing. Generic in, generic out — so we don't let the input be generic.
