Mobile app — from concept to MVP
Complete BA documentation package for a startup: User Stories, BPMN, wireframes, API contracts, 28-block roadmap.
Developers can't start without clear requirements — and burn your budget on questions and rework. We deliver a complete documentation package any team can work from, and you can compare vendor estimates on the same scope.
01
If between your idea and the code there's a team that doesn't see your business from inside — someone has to translate.
They write great code, but the question "how should the discount work?" eats weeks. You need requirements, not guesses.
Without a spec, estimates from three studios differ threefold because each understood the task its own way.
You need to define the minimum scope that tests the hypothesis and not build the unnecessary.
Development drags for months, the result doesn't match expectations, and no one can say what "done" means.
Two teams or two vendors must agree on a data format — you need an API contract.
From concept to MVP: screens, scenarios, roles, backend — all described before the designer opens Figma.
02
Artefacts we deliver. Scope depends on the project — for small tasks the first three are enough.
Interviews and process map
Stakeholder conversations, AS-IS process, pains, goals, constraints, glossary.
User Stories with acceptance criteria
Each feature as a user story with clear "done" conditions, priorities and complexity estimate.
BPMN diagrams
TO-BE processes in BPMN notation: roles, steps, decisions, exceptions — clear to business and developers alike.
Wireframes and prototype
Screen layouts and a clickable Figma prototype to validate logic before development.
Data model
Entities, relationships, references, statuses — the basis for the database schema.
API contracts
Endpoints, request and response formats, error codes — for frontend, backend and integrations.
Non-functional requirements
Roles and access, security, performance, languages, devices, backups, logging.
Development plan and MVP
Breakdown into stages, what goes into the first release, effort estimate, risks.
Don't see your process?
Describe how it works today — we'll propose a module around your logic.
03
Live systems our clients use every day. Company names are anonymised by agreement.
Complete BA documentation package for a startup: User Stories, BPMN, wireframes, API contracts, 28-block roadmap.
Built a dispatch platform from scratch: weekly board, billing workflow with PDF invoices, payroll module, ApexCharts dashboard, cross-dock management and PRO# autofill.
A designer-made PDF catalog of a medical equipment distributor turned into a code build: one product = one Markdown file, the full 52-page PDF is generated with a single command — no layout designer needed.
04
We identify decision makers, users, budget and time constraints.
A series of conversations with the team, review of current tools, documents, data.
BPMN TO-BE, entities, statuses, roles. First review with you — we catch inaccuracies early.
We write stories with acceptance criteria, draw screens, assemble the prototype.
Contracts for integrations, security, performance, infrastructure.
We present to the team and answer developers' questions during the first sprints.
05
Pricing
from $500
A spec for a small module or integration — from $500. A full package for a system or mobile app with a prototype — $1,500–4,000. The spec cost is credited if we do the development.
06
We pick the stack for the task and your team, not the other way round. Code and data are fully yours.
07
Yes, it's a separate service. You get the documentation package and are free to give it to any team. If we later do the development — the spec cost is credited.
Deeper dive
Every unresolved "how should it work?" is either a pause or a developer's assumption. Assumptions turn into rework, rework into missed deadlines and budget. A business analyst removes those assumptions before start.
Processes (BPMN), roles, entities and their statuses, features as User Stories with acceptance criteria, screens (wireframes), integrations (API contracts), non-functional requirements and a stage plan. Such a document is equally clear to the owner, designer and developer.
"As a manager, I want to see overdue deals on the dashboard so I can react in time." Criteria: overdue counts from the next-step date; the list sorts by age; a click opens the deal. Now the developer knows what to build and the tester what to check.
Our difference: the person writing requirements can implement them. So the spec contains nothing impossible and estimates are realistic. And if you order development from us too — there's no "lost in translation" between document and code.
For small tasks of a few days a short description and a mock-up are enough. We'll say honestly if your task doesn't need a full package and propose a lighter format.
08
Describe what you want to build and who will build it — we'll propose the package composition, timeline and price.
Describe the task — we'll respond within 24 hours