A software house, not a body shop.

What we actually do

We take a workflow that currently lives in paper, spreadsheets and a WhatsApp group, and turn it into a system that holds: one set of records, an audit trail, and software the people doing the work will keep using after the novelty wears off.

That means we do the unglamorous part properly — the data model, the failure modes, the migration of the opening balances, the runbook the client can follow at 2am without calling us. A demo is easy. A system that survives its second year is the job.

How we work

1. Say what it does not do. Every proposal lists the limits: what is read-only, what stays manual, what is not in this phase. A vendor who cannot describe the limits has not thought about the problem.
2. Scope before price. The scope is written down before the work starts, including what is not in it. Change is a conversation, not a surprise on the invoice.
3. On-premise by default. If the client's data can stay on their own hardware, it does. Cloud is a decision we make together, with the trade-offs on the table — not a default we quietly bill for.
4. One set of records. No sync jobs, no nightly exports, no second copy of the truth for the report to disagree with.
5. Hand it over properly. Deployment, documentation and a runbook the client's own team can follow. Software that only we can operate is a hostage, not a delivery.

What we are not

• Not a staffing agency. We do not rent developers by the month and call it a project.
• Not a reseller. If an off-the-shelf product fits, we will say so and point at it, even when it costs us the build.
• Not a chatbot wrapper. AI is useful in our systems because it reads the same records everything else reads. Bolting a chat window onto a bad data model changes nothing.

Who you deal with

Small team, direct line. The person who scopes the work is the person accountable for it.