A web app your people actually use
When a spreadsheet stops holding the business together. Accounts, admin panels, internal tools — built to be used daily, not demonstrated once.
I answer within one working day, in writing. I never call.
When people come for this
- The spreadsheet broke. Two people edit it at once and the numbers stop agreeing.
- Clients ask for an account — to see their orders, documents and status without writing to you.
- The team retypes the same data between systems, by hand, every day.
- There is a ready-made product, but it costs per seat and still doesn’t do the one thing you need.
What is inside
Roles and access
Who sees what, down to the field. An admin, a manager and a client see three different screens, not one with things hidden by CSS.
The data model
Designed before the screens. A wrong structure is felt six months later, when there is already data to migrate.
An interface for daily use
Built for the person who opens it forty times a day: keyboard, search, no decorative animation in the way.
Integrations
Payments, mail, Telegram, CRM, whatever already runs the business. The app joins the process instead of replacing it.
Import and export
Your history moves in, and it can move out. Nothing is locked inside.
Backups and accesses
Copies on a schedule, and every access handed to you on day one.
How the work goes
You describe the task
A short form: what the business does, what should change. No calls — I answer in writing, within one working day.
You get a quote
Within two working days, one figure for the whole scope, before any work starts. Not a range that doubles later.
You see the first screen
The opening screen as a layout, before anything is built. Wrong direction is cheap to fix here and expensive to fix later.
It gets built
Phone first, then desktop. Checked on a slow connection and on a real device, not only in a browser window.
It goes live
You get every access on day one: domain, hosting, analytics, the code. Nothing is held hostage.
What it costs
An app is priced by what it must do, not by screen count. You get one figure for the whole scope within two working days, before anything starts — and if the scope grows later, the new figure is agreed the same way.
- How many roles and how different their screens are.
- Whether data has to move from an old system.
- What it connects to: payments, CRM, mail, messengers.
- Whether it must work offline or on a phone in the field.
An admin panel that shows where clients disappear
For PMP Group Stroy we built the panel where every request lands, and for this studio — the one with the funnel: visits, requests, sources, ad tags, how far people read, and where they leave. Both run on private storage: a direct link without a token answers 403. The same hands, the same rules.
Access to the panels is given on request — they hold client data, so there is no public link.
See the casesQuestions people ask
How long does an app take?
Longer than a site: the first working version usually comes in weeks, not days. The exact term goes into the quote, before the work — not “we’ll see how it goes”.
Can you take over someone else’s code?
Yes, if the code can be read. I say honestly after looking whether it is cheaper to continue or to rebuild — including when the honest answer costs me the bigger job.
Who hosts it?
Your account, your domain, your data. I set it up and hand over the keys; nothing runs on my personal account.
What if it needs changing after launch?
That is normal, an app lives. Small changes go in as they come; large ones are quoted the same way, one figure before the work.
Do you call?
No. I answer in writing, within one working day, in the channel you left.
Get a price for your app
Describe what it has to do — the figure comes within two working days, before any work begins.
Get a price