The internal system that currently lives in a spreadsheet
Custom Web Applications
The software your team works in every day, built around how they work rather than the other way round. It opens in a browser, with nothing to install.
Included
What this service covers
The application almost always starts as a spreadsheet that grew too far: ten people share it, nobody knows which copy is the good one, and a typo surfaces weeks later. A web application fixes that with users, permissions and a record of who changed what. It is built in parts: first the flow that hurts most, in production and with people using it, and the rest is added on top of that.
- Users, roles and permissions by area
- Dashboards with the numbers people actually check
- Change history: who did what, and when
- API connections to the systems you already run
- Excel export and scheduled reports by email
- A test environment kept separate from production
What it’s for
What changes in your operation
- 01
One version of the data
No more copies of the file and no more edits overwriting each other: everyone sees the same thing at the same moment.
- 02
Everyone sees only their part
Permissions are set by role, so the system can be opened to the whole team without exposing payroll, costs or customer records.
- 03
It grows in stages
The first flow is delivered working and the rest is built on top. There is no waiting for the whole thing before anyone can use it.
- 04
The process is written into the system
When someone new joins, the application shows them the next step. The operation stops depending on whoever knows it by heart.
The costliest mistake
Building the whole system before anyone uses it
A sixty-page requirement gets written, half a year of development follows, and on delivery day it turns out the real process was never the one in the document. Fixing it at that point costs several times what finding it out in week three would have.
- What usually happens
- Everything is delivered at the end, when there is no room left to change your mind.
- What we do instead
- The first flow goes into production within weeks and the rest is built on what using it taught us.
How the work goes
From the first call to production
The same process on every project, whatever the size.
- 01
Map the real process
We sit with whoever does the work today and document the flow as it actually happens, which is rarely the one in the manual.
- 02
First flow in production
We pick the process that eats the most time and build it end to end, with real users on it before anything else starts.
- 03
Module by module
The remaining flows are added in one or two week deliveries, correcting the earlier ones with what using them reveals.
- 04
Handover
The architecture is documented, the team is trained, and a channel stays open for questions and adjustments.
When it applies
Situations this service solves
If one of these sounds familiar, this is probably the service you’re after.
Your operation lives in several shared spreadsheets
Each area keeps its own, none of them reconcile, and month-end goes into matching them up. The application replaces them without losing the history.
You bought a system that does not fit how you work
When the team ends up keeping control outside the system, building the missing piece costs less than fighting the licence forever.
Clients email you for things they could look up themselves
A portal showing their statement, their documents and the progress of their order takes that load off the team and improves how the service feels.
Plans
What it costs
Prices in US dollars, with the scope written down. If your case fits none of them, that is what the last plan is for.
Diagnosis
Before building anything: what is needed, what it costs and in what order.
$1,500one-time
Includes · 5
- Map of the process as it actually happens today
- Clickable prototype of the key screens
- Proposed architecture and technical decisions
- Fixed price per milestone and estimated monthly infrastructure cost
- The document is yours, whoever executes it
First version
The flow that hurts most, live in production with people using it.
$9,500one-time
Includes · 7
- One complete flow, end to end
- Users, roles and permissions
- Dashboard with the numbers people actually check
- Change history and Excel export
- A test environment where your team can try things safely
- A direct channel to whoever is building it
- Delivered in 6 to 8 weeks, repository in your name
Platform
Several modules, integrations and the whole operation inside.
$19,000one-time
Includes · 7
- Three or more connected modules
- API integration with the systems you already run
- Test environment separate from production
- Scheduled reports and dashboards per area
- Automatic backups with a tested restore
- Technical documentation and team training
- Quarterly review through the first year
Enterprise
Multi-tenant, several countries or compliance requirements.
Based on scope
Includes · 4
- Multi-tenant architecture with isolated data
- Currency, time zone and rules per territory
- Access auditing and traceability
- Written service level agreement
The diagnosis is deducted from the project if you decide to continue, and it produces a fixed price per milestone.
Seasonal pricing, subject to change. The price in your proposal is fixed from the moment you receive it. In USD, local taxes not included.
Also
Services that usually go together
Next step
Which of these do you need?
If you’re not sure, that’s fine too: the first call defines the scope before anyone talks about price.