01 · web service development
SaaS, internal systems, booking tools and calculators that people use every day. We start with an MVP, test it on real users and grow the product based on metrics
A subscription service and an internal warehouse system have different users and different reasons to give up on them. We shape the architecture and interface around what you do
You have an idea but no certainty. We build a first working version around one core feature and put it in front of real people
A service people pay for every month. Plans, a free trial and a clear customer account are what matter here
Requests, stock and deals are scattered across a dozen spreadsheets and chats. We move the process into one system where you can see who did what
Customers pick a time, place or specialist themselves, and the schedule always matches what the administrator sees
Customers build an order from options and see the price right away. Your manager gets a ready specification, not a “please call me back”
Opens from a link, installs to the home screen and sends notifications. No app store publishing required
Six steps, and at each one the product is tested in practice, not debated in a meeting room
Who the user is, which of their problems we solve and what will tell us the service is needed. Without that, there is nothing to test
A clickable prototype of the main scenarios. We show it to a few future users before a single line of code is written
Interface, back end and API covering only what the test needs. Every two weeks there is a working build on a staging URL
We open access to a small group, collect feedback and immediately fix whatever stops people completing the main scenario
How many people reached the result, where they dropped off, whether they came back a week later. Decisions are based on numbers, not gut feeling
The next features are planned around what users showed us. What nobody uses gets removed rather than maintained for years
Front end, back end, database and subscription billing are handled by the same people. Nobody passes the buck between contractors
Development stack: React, Next.js, Node.js, PostgreSQL, REST API, WebSocket, Payment gateways, Docker
That is how the sales portal for a property developer works: unit registry, stacking plan, price lists, feeds, reservations and deals in one system. A price changes in one place and goes straight to the stacking plan, the website and listing portal feeds. A working web service sales teams use every day
Most products don’t fail because of the code. They fail because of the process, and we set that up from day one
In that time the market shifts and the money runs out. We show the first version to people within six to eight weeks and refine it based on how they react
Every new button has to answer the question “which user problem does this solve?” If there is no answer, the feature waits its turn
Without numbers you can’t tell whether the service works. We tag key events as early as the prototype stage, so the funnel report is ready at launch
The team knows the product by heart, while a newcomer gets lost on the second screen. We test the prototype on outsiders before development
A fast MVP doesn’t mean a disposable one. We lay down the data structure, roles and API from the start, so you won’t be rewriting everything a year later
Launch is the middle of the journey, not the finish line. Along with the first version you get a roadmap for the months ahead, and we stay on for support
The cost depends on scope. We send a detailed estimate after the brief and don’t change it after kickoff unless the scope changes
Custom quote
6–8 weeks
Custom quote
12–14 weeks
Custom quote
from 16 weeks
An hour-long call about the idea, the users and the core feature. A couple of days later we send an estimate with phases and the MVP scope
A clickable prototype, tested on future users, then the design. Changes happen before development, not after
Every two weeks we show a working version on staging and close the phase with a sign-off. Payment is per phase
We roll out to the first users and watch errors and metrics. A month of support is included
Open 01 of 07
Didn’t find your question? Ask it on Telegram and we’ll reply during business hours
Ask on TelegramIt depends on scope; the estimate is fixed after the brief
The cost depends on the number of roles, integrations and scenarios. We send a detailed estimate after the brief, and it doesn’t change unless the task does. If the budget is tight, we suggest what to keep in the first version and what to postpone
So you don’t spend a year on something nobody needs
An MVP tests the core hypothesis in six to eight weeks. If people use it, we keep building on the same code. If they don’t, you find out before you’ve spent the budget of a full build
Our main stack is Node.js and PostgreSQL
We build the interface with React and Next.js and the back end with Node.js and a PostgreSQL database. If you already have a Python back end, we connect the interface to its API; there is no need to rewrite working code
People read a website; they use a web app
A website tells people about your company and brings in leads. A web application solves a user’s task every day: it stores their data, runs calculations, takes bookings and accepts payments. That’s why it has more logic, more roles and a bigger back end
Usually not at the start
A web application opens on a phone, installs to the home screen and sends notifications. That is enough to test demand. Separate app store apps make sense once you already have an audience
A month of support and a roadmap
For the first month we watch errors and metrics and fix whatever turns up. After that you can continue development in sprints or put the service on hourly support
The code is yours; hosting is your choice
We hand over the source code, access and documentation. We host the service where your users’ personal data is allowed to be stored under the data protection laws that apply to you, or on your own servers
Tell us what problem the product solves and who will use it. We reply within two hours during business hours and send an estimate after the brief