How to start working with WAPP
From the first call to launch: what happens at each stage, what it costs, and what you get before you pay for development.
- 2–3 days
- to a budget range after the call
- 1 month
- for specs and prototypes before coding
- Fixed price
- in the contract once specs are agreed
- 1 year
- code warranty after launch
What happens on the first call
The call is there to understand the task and to tell you honestly whether we are a good fit. No sales pitch.
We look at the task
Which process costs time or money today, who will use the system, and where the data lives now: spreadsheets, accounting, CRM, chats.
We check if custom development is needed
If an off-the-shelf service or a change to your current system does the job, we say so right away. Custom software does not always pay off.
We give an order of magnitude
Based on similar projects we give a rough budget and timeline. A written range follows in 2–3 business days.
We agree on the next step
Usually that is discovery: in the first month the team writes the specs and builds prototypes, then the price is fixed in the contract.
What to prepare for the call
You do not need ready specs — the team writes them during discovery. Short answers to six questions are enough.
- 01What problem we are solving, in a paragraph or two.
- 02Who will use the system: roles and rough headcount.
- 03Where data and processes live now: spreadsheets, accounting, CRM, paper, chats.
- 04Which systems it must connect to: payments, accounting, telephony, maps.
- 05When you need the first result and what drives the deadline.
- 06What budget feels comfortable — at least a range.
Stages
- 1
Call and budget range
We go through the task. Within 2–3 business days we send a written budget and timeline range.
- 2
Discovery, specs, prototypes
In the first month the team writes no code: it maps processes and roles and builds clickable prototypes. The result is a fixed price in the contract.
- 3
Development in stages
Work runs in sprints with open access to the task tracker. Regular calls show what is done and what comes next.
- 4
Launch and warranty
We prepare infrastructure for the load, set up monitoring and train your staff. The code warranty is 1 year after launch.
What it costs
These are WAPP's published entry points. We name the exact amount after the call and fix it in the contract after the specs.
For labs of up to 10 people the base LIMS is free, first come first served. Terms
What the contract fixes
Price and scope
A fixed price once specs are agreed. Until scope is fixed we give a range, not a number out of thin air.
Changes
New ideas along the way are normal. Extra scope gets a priced amendment before work starts.
Code ownership
Code, design and database pass to the client under the contract once stages are paid.
Warranty
1 year on the code after launch: bugs made by the team are fixed at no extra cost.
Questions
A full team — analyst, designer, developers, QA, manager — costs about RUB 500K a month. That budget buys a prototype or a simple website, not a system people use every day. Below RUB 1.5M a web app or PWA often fits better than a mobile app.
Let's start with a call
Describe the task in the form below — we reply during business hours and suggest a time for a call.