The work lives in spreadsheets
Several people edit one Google Sheet, versions drift apart, and nobody can restore the change history.
// Services
A system your team works in every day
Client portals, internal CRMs, estimate calculators, admin panels with roles. One tool instead of spreadsheets and e-mail threads.
- We start with a prototype — the logic is agreed before any code is written
- From $6000, first working block in 3–4 weeks
- Development in stages: you see what you paid for and can stop at any point
When you need a web application
Calculations are done by hand
A manager works out the estimate or the price in a calculator by following instructions. Mistakes happen, and speed depends on the person.
Off-the-shelf systems do not fit
You have looked at several CRMs: each has 80% you do not need and lacks the 20% you do. Or it has them, but at the price of a separate project.
Clients have nowhere to see their data
Order status, documents, history — all of it has to be asked from a manager, who spends half the day on it.
Data is scattered across services
Part of it in the CRM, part in the accounting system, part in the mailbox. Putting the picture together is impossible.
You want to sell access
Your tool is useful not only to you — and you are thinking about subscriptions, plans and separate accounts for clients.
Roles and access — the foundation of any system
Roles with different permissions
Owner, manager, client, contractor — each sees their own part.
Restricted data visibility
By department, branch or project.
Action history
Who changed what and when — with the option to roll back.
Two-factor authentication
Where needed, for roles with access to money and personal data.
Working with data — the core of the system
Reference lists, records, relations
A structure built around your entities, not someone else's template.
Search and filters
Handle hundreds of thousands of records without slowing down.
Bulk actions and import from spreadsheets
Bringing over what currently lives in Excel and Google Sheets.
Calculations by your formulas
The same ones the manager uses today, only without the mistakes.
Reports and exports — what it is all for
Summaries by period
By owner, status, business line.
Export to Excel and PDF
In your template, not a generic table.
Printable forms
Contracts, invoices, acts — straight from the system's data.
Dashboard with the key numbers
On the home screen, so you do not assemble the picture by hand every morning.
The outside world — integrations
Notifications
Telegram, e-mail, SMS — whichever suits you.
Exchange with existing systems
CRM, inventory, accounting.
Payments and subscriptions
If it is SaaS — pricing plans and recurring charges.
Your own API
For a mobile app or for partners.
How we run the project
- 01
We map the process
Not "what the system should do", but how the work is organised today: who does what, where the data comes from, where time is lost. Half of the wishes often drop out right here. 3–5 days.
- 02
Prototype without design
A clickable scheme of screens: the logic, the transitions and the data are visible. Changing something here costs hours, not a week of rewriting code. 1–2 weeks.
- 03
Estimate in stages
We split the system into blocks, each with its own price and deadline. You see what goes into the first launch and what can wait. Delivered together with the prototype.
- 04
Development in blocks
Every two weeks — a working block you can open and try. Priorities between stages can be changed.
- 05
Launch and support
We migrate the data, train the team and keep a hand on the pulse for a month. After that — development driven by your tasks.
What it costs
A web app is priced by the complexity of its logic, not by the number of pages. The figures below come from our own projects.
Portal or calculator
from$6,000
one-time
One user role, straightforward logic, a few data types.
- Authentication and profiles
- Formula-based calculations
- History and documents
- Notifications
- Data export
Delivery: 8–10 weeks
Discuss the systempopular
Internal system
from$12,000
one-time
Several roles, your own processes, reports and exchange with existing systems.
- Roles and permissions
- Workflows with statuses
- Reports and dashboards
- CRM and accounting integrations
- Action history
Delivery: from 3 months
Discuss the systemSaaS product
from$20,000
one-time
A subscription service: many customers, plans, payments, data isolation.
- Sign-up and pricing plans
- Recurring billing
- Customer data isolation
- Owner admin panel
- Ready for load
Delivery: from 4 months
Discuss the systemThe first stage — process mapping and prototype — can be ordered separately for $1200. You get a scheme of the system and an estimate you can take to any contractor, not only to us.
When a custom system beats an off-the-shelf one
The "custom or ready-made" question deserves an honest answer, and the answer is more often on the side of ready-made. If your process is typical and there is a service on the market that covers it for reasonable money, building your own system will be more expensive and slower. We are the first to tell clients this.
A custom system is justified in three cases. First, the process does not fit someone else's logic: you adapt the work to the software instead of the software adapting to you. Second, the features you need exist but cost disproportionately: for one required capability you have to buy the most expensive plan for the whole team. Third, the system itself is a product you plan to sell.
The main risk in such projects is not technical — it is that the wrong system gets built. That is why we start not with code but with mapping the current process: who does what, where the data comes from, exactly where time is lost. Half of the initial wishes often drop out at this stage — it turns out a simpler solution covers the task.
Next comes a clickable prototype without design: a scheme of screens, transitions and data. Changing something in the prototype costs an hour; in written code — weeks. This is where logic errors are caught most cheaply.
Development runs in stages, each with its own price and deadline. Every two weeks you receive a part you can open and try. This removes the main fear of large projects: at any moment you can see what you paid for, and at any moment you can stop, holding a working system rather than a folder of code.
Frequently asked questions
A client portal or a calculator with one role — from $6000 and 8–10 weeks. An internal system with several roles, processes and reports — from $12000, from three months. SaaS with subscriptions — from $20000. The exact estimate appears after the prototype.
Because before the process is mapped nobody — neither we nor you — knows the exact scope. A figure can be named at random, but it is either inflated "just in case" or too low, and then extra work "turns up" along the way. We name a range right away and the exact price after the prototype, when every screen is visible.
Often yes, and we will be the first to say so. A custom system is justified when your process does not fit someone else's logic, when ready-made services charge disproportionately for the features you need, or when the system itself becomes a product.
The prototype — 1–2 weeks after the start, and you can already click through it. The first working block that opens in the browser and works with real data — in 3–4 weeks. After that, the next block is added every two weeks.
Laravel on the back end, Next.js or Inertia + React on the front end, PostgreSQL or MySQL — depending on the task. Mobile apps — Flutter. We choose the stack for the project and for whoever will maintain the system afterwards.
Yes, it is a standard part of the launch. We migrate from spreadsheets, CSV exports or directly from the old system's database. Before migrating we show how the data will fit the new structure — so it does not turn out afterwards that something is missing.
For a month after launch we keep a hand on the pulse — this is included in the price. After that, either a development retainer or hourly work on request. The code, the repository and the access are yours: any developer can continue the work.
Discuss the system
Start a project