Web applications and custom software
We build the system a company runs on: the screens people open every morning, the data model underneath them and the rules that decide who may do what.
What this solves
Most companies outgrow their tools in the same way. A process that used to fit in a spreadsheet now spans three of them. An off-the-shelf product covers eighty percent of the work, and the remaining twenty percent is handled by hand, every day, by people who know the exceptions. Custom software is worth it exactly there: where the process is specific enough that no product will ever fit it, and repeated often enough that the manual version costs real money.
When a business needs it
- ·A core process lives in spreadsheets that only one person fully understands.
- ·Your product does most of what you need, and the rest is manual work.
- ·Different departments keep their own version of the same data.
- ·Reporting takes days because the numbers have to be assembled by hand.
- ·Growth means hiring more people to do the same repetitive steps.
What is included
Data model
The structure underneath everything: entities, relationships, history and the rules that keep them valid.
Interfaces
Screens designed around the actual task, not around a database table, and fast enough to use all day.
Roles and access
Permissions enforced at the data level, so what a user cannot see is genuinely out of reach.
Workflows
Approvals, statuses and handovers modelled the way the company really works, exceptions included.
Reporting
Numbers produced by the system itself, consistent between screens, exports and dashboards.
Deployment
Environments, backups, monitoring and a release process that does not require downtime.
How we approach it
We start from the process, not the feature list. A day spent with the people doing the work usually changes what the first version should contain.
The data model is agreed before the interface, because it is the part that is expensive to change later. Everything else can be adjusted while you use it.
You get a deployed environment early. Feedback on real software is worth more than approval of a design.
Technical depth
- Frontend
- Next.js, React, TypeScript
- Backend
- Node and Python, REST and typed APIs
- Data
- PostgreSQL, migrations, full history
- Jobs
- Queues, retries, scheduled work
- Access
- SSO, row level permissions, audit log
- Hosting
- Your own cloud accounts
Questions we get
Is custom software worth it against an off-the-shelf product?
Sometimes not, and we will say so. It is worth it when the process is a real advantage for you, or when the manual work around a product already costs more than building the missing part.
Can you work with the systems we already have?
Usually yes. If a system has an API we integrate with it. If it does not, we work through exports, files or the database, and we say early if something is not realistic.
Who owns the code?
You do. Repositories and infrastructure live in your accounts from the first day, so nothing is locked to Chronum technically or contractually.
How long does a first version take?
We scope the work around the system you actually need and agree the delivery plan before development starts. The first version usually covers one workflow end to end.