From the first phone call to launch
And what happens after — because that's where you see which companies stay with you.
Six, and none of them skipped
The conversation
An hour in which we learn what you sell, to whom, and what's getting in your way now. No quote on the spot: a quote given before understanding the problem is a guess.
The proposal
We write down what we understood, what we'll build, how long it takes and what it costs. If something can't be done within your budget, we say so then — not halfway through.
The build
We work in pieces you can see. At every step there's something to open and try — you don't wait two months to see the first page.
The checks
Automated tests: pages are opened in a real browser, routes that change data are guarded, and what gets served is checked for invented data.
The launch
We go to production with a rollback ready. If something falls over, we're back on the version that worked in minutes, not hours.
After
A settling-in month is included. After that, maintenance if you want it — or you take your code and carry on with whoever you like.
And what we don't
A supplier who guarantees everything guarantees nothing.
We guarantee
- The code is yours, history included
- The date in the proposal, or notice well in advance
- A settling-in month after launch, included
- Automated tests that stay in the project
We don't guarantee
- First place on Google — nobody serious can guarantee that
- A number of sales: that depends on goods, price and market, not on code
- That nothing will ever break. We guarantee we'll find out quickly and fix it.