The most expensive conversation in any project is the one that did not happen in time. The first stage exists precisely to get out of the client's head, and onto the table, everything they currently treat as "well, that's obvious". It is the cheapest point in the project at which you can still change your mind without losing money.
What happens at this stage
The stage combines a consultation with an architect and modelling of the future product. According to our price list it includes four blocks of work.
- Analysing and refining the business idea. Who pays, for what, instead of what, and why now. Who will work in the system every day and what they do without it today.
- Budget options. Different scopes for the first version mean different prices and different launch dates. We show you what can be postponed without hurting revenue.
- Business requirements. High-level requirements for the app and the online services connected to it: roles, key scenarios, constraints and goals.
- A demo sample. The app's main screens and an admin panel for managing data.
The questions we ask
The most valuable part of this stage is not the answers but the questions that were missing from the original brief. Who creates a record and who can change it. What happens to an order if the customer changes their mind. Who sees the money and who only sees the status. Where the data lives today: in Excel, in messengers, in employees' heads. Every question asked here removes a risk that would otherwise surface during development.
What you get at the end
- A business requirements document, usually 1-2 pages of compact text. It is enough to discuss the budget, and it stays with you.
- A visual model of the future product: the main screens, which make it clear what the user will see.
- An admin panel in the sample. Most clients think about the customer-facing app and forget that someone has to manage the data every day. That gap usually surfaces in the third month of development, and it is expensive.
This is not a "what it could look like" presentation. It is material you can use to test your own hypothesis and show it to the people whose approval you need: a partner, an investor, your heads of department.
What it costs and what affects the price
The stage costs $220, and the price is fixed. The first meeting with an architect is free: we use it to understand the task and decide together with you whether this stage is needed or whether you can go straight to the technical specification.
The complexity of the idea does not change the price of this stage. It will show up in later stages, which is exactly why it pays to see it here, for $220, rather than in the development estimate. If you arrive with basic requirements already gathered, the stage can be shortened or skipped.
What breaks if you skip it
Without it, the technical specification is written on guesswork. Phrases like "user account area" get approved because everyone nods. Later it turns out that the marketer means one thing, the accountant another and the developer a third. Fixing this at the requirements level takes hours. The same fix at the coding stage takes weeks.
The second typical failure: the budget is discussed for the entire product at once, even though half the features could have moved to version two. Without a conversation about budget options, the first version ends up more expensive and later than it needed to be.
Who needs this stage most
- A start-up with a strong idea but no technical clarity. The stage separates the real core of the product from attractive but premature features, so the first budget is not burnt on a chaotic MVP.
- An established company with departments, spreadsheets and scattered services. Here the job is not "build an app" but untangle the way work is actually done and turn it into a manageable digital scheme. Without a model of roles and data, such a project almost certainly ends up in rework.
An example from our work
Sklo manufactures memorial products and offers photo design services. From the outside it looks like an ordinary manufacturing and retail business, but behind every order there is a chain of calculations, approvals, layouts and production steps. We did not start with code; we started with business analysis and a process audit.
At that point it was already clear that the company needed neither a website nor a CRM with a spreadsheet, but a digital customer service scheme: from first contact through design and approval to handover to production. We broke the process down into roles, and the system was designed from the outset as three separate apps: for customers, for sales managers and for designers. Read more in the Sklo case study.
That split is the main result of modelling. Chaos usually starts where everyone works in one shared form and responsibility is scattered across messengers and phone calls. When every participant has their own interface and their own set of buttons, the specification can be written against a clear scheme.
Where to go next
The next step is the technical specification for $800, where the business requirements become a data model, an interface model and a development budget estimate. If you order prototyping straight away, the specification is included at no extra charge. The full map of stages is in the app development strategy.
Book a free consultation with an architect. In fifteen minutes we will go through your task, and after the call you will receive a stage-by-stage estimate of cost and timeline.
