// the architect
Describe the business.
Get the blueprint.
Tell the architect what you do and where the hours go. It's free, the draft takes about a minute, and no email is needed to see it.
// you get: the real problem · the system · buy vs build · cost band · risks
worth mentioning: what you do, how many people, where the hours go, what tools you already use.
// your brief
machine-drafted starting point, not a quote. cost bands are ranges from similar builds, not promises. real scoping is a conversation. briefs may be reviewed to improve the architect.
if this blueprint looks like something you'd actually want built — that's the part we do.
want a human to pressure-test it — free
// copied
See one first
Three blueprints this desk has drawn, on composite businesses. Each one is a page.
An ops team with engineers
Carrier emails in a dozen formats, retyped by hand into the system of record.
build $25,500–$36,000 · $110–$275/mo · +$1,500/mo if we run it
A bookkeeping firm, six people
Two people spend every morning chasing documents and typing numbers into the system.
build $24,000–$33,500 · $110–$275/mo · +$1,500/mo if we run it
A financial planning firm
A 20-page PDF fact-finder, then four hours of retyping per new client.
build $23,000–$32,500 · $0–$25/mo hosting · +$400/mo if we watch it
A commercial refrigeration company
Paper tickets sit in trucks until Friday, and installed parts go unbilled.
build $14,500–$20,000 · $0–$25/mo hosting · +$400/mo if we watch it
A tree service, two crews
A dead brochure site, quotes by phone, and calls landing while the crew is in a bucket truck.
build $20,000–$28,000 · $110–$275/mo · +$1,500/mo if we run it
What this is
The architect writes a first draft using the same model and rules we use on real engagements. It reads what you wrote and names the system it would build, whether that is an automation, a website, a backend or a mix.
When the honest answer is "buy a $30-a-month tool and don't hire anyone," it says so. The blueprint is yours to keep and to build with anyone.
Common questions
A short written plan for the software a business actually needs: the components, the data flow, which parts to buy instead of build, a cost band from fixed arithmetic, and the failure modes worth watching. It is the same first document we write on a paid engagement.
It is free and no email is needed to see the blueprint. It renders on the page as it is written. You can copy it, or mail it to yourself with one click.
No. The band comes from fixed arithmetic — how many systems the build touches, how messy the data is, and what a wrong answer costs — so it is consistent between blueprints. A real number takes a real conversation.
You do. It is written to be handed to any competent developer, including one who is not us. That is deliberate: a plan that only works if we build it is a sales document, not a plan.
It goes to the model that writes the blueprint. Briefs may be reviewed to improve the architect, so describe the work rather than pasting anything confidential.
The first words usually land in 20 to 35 seconds, and the full blueprint in about a minute. It is one shot, so the more you say about where the hours go, the better the draft.
studio@anchor163.com
// copied