Architecture sketch in 3 days. Before any contract, before any deposit, no strings.
Tell us the task — in three business days you get a document: how to build it, where it will break and what it costs. The sketch is yours either way: build it with us, or walk away with the blueprint.
What you get
Data model
Entities, relations and the things that usually break in year two: change history, multi-currency, roles.
API and integration outline
Which external systems, where idempotency is required, what to do with repeated webhooks and reconciliation.
Infrastructure and running cost
Where to deploy, the monthly bill, what to monitor and how to roll back.
Risk map
Three to five places where the project can genuinely stall, and what to do about each in advance.
Budget range and milestones
A cost range broken into stages — the same logic as our calculator.
How it goes
- Day 0Call30 minutes. The task, the constraints, what you already tried.
- Days 1–3We workDesign and costing. If a question comes up, we ask instead of guessing.
- Day 3HandoverThe document and a half-hour walkthrough. After that you owe us nothing.
What we need from you
- 30 minutes on a call — to unpack the task and its constraints
- Access to whatever exists: code, analytics, a spec, screenshots — any of it
- One person who can answer business questions
Honest limits
- We take two sketches a week — otherwise it stops being three days.
- This is not design, not code and not an 80-page spec. It is an engineering decision on 5–8 pages.
- If the task is worth ₽200k, you don't need a sketch — just email us.
Request a sketch
Describe the task in two or three paragraphs: what the product is, what exists already, what worries you. That's enough to book the call.