Service 01
Software development
A web system, dashboard or internal tool built for your process — not for the market's average process.
Context
There's a point where the shared spreadsheet stops coping and the off-the-shelf system charges a lot to do 30% of what you need — and forbids the other 70%. That's where custom software pays for itself.
Inside a monthly contract this changes shape: instead of one large project with a distant delivery date, it's built in usable stages. Every month ends with something live. If the company's priority shifts halfway through, what already shipped stays up.
Signs this is your case
- The off-the-shelf system forces you to change a process that works
- The whole operation depends on a spreadsheet with fragile formulas
- You pay per-seat licences to use a fraction of the product
- You need a dashboard joining data that lives in separate places
What you're left with
- A web application in production, with a reproducible deploy
- Source code yours, in your repository, with no vendor lock-in
- Delivered in usable stages, one usable thing at a time
- Technical and operational documentation
What it isn't
- Rewriting from scratch a system that only needs adjusting
- A project with nobody on the client side able to decide
A workflow in practice
From a spreadsheet to order tracking
An illustrative workflow, not a client case study or a promised result.
See the monthly retainerCapture the order
Your team records it once, with the fields your operation needs.
Track the work
Owner, deadline and pending tasks stay together. Each person sees what they need to do.
See what is stuck
The dashboard shows blocked work and why it is blocked, without another manual report.
Where I start
I start with one workflow that currently lives in a spreadsheet. We agree on states and access with the people using it, then ship a usable first stage.
What continues every month
Following months add what the team needs and maintain the live version. New priorities enter our agreed queue without restarting the system.
Questions about this front
How long until something is live?
The first usable piece is normally live within the first month. Not the whole system: the stage that already solves something on its own. Building in usable stages is what lets priorities change halfway without losing what already shipped.
What if I already have a half-built system?
I take it from where it is, including when somebody else built it. The first week is usually reading what exists and telling you what can be kept — rewriting from scratch a system that only needs adjusting is the most expensive decision there is.