Business applications
The system your company runs on when no product fits: scheduling, operations, quoting, field work, customer portals. Built around how you work rather than around how a product assumes you do.
Custom software
When the product stops and your business keeps going.
Most of what we build is not for sale on a pricing page. It is the system a company runs on, written for the way that company actually works — and maintained by the same people who wrote it.
Is this you?
The five things companies say just before they call us.
- A spreadsheet has become the system of record and nobody can change it safely.
- Two teams keep the same information in two places and it disagrees.
- The product you bought does 80% of the job and the other 20% is done by hand.
- A report someone assembles every month takes a day and is out of date the moment it is sent.
- The person who built your current system has moved on and nobody will touch it.
If more than one of those is familiar, the problem is usually smaller than it feels — and almost never the thing everyone is blaming.
What we build
Six kinds of work, one team.
Integrations
Two systems that were never meant to speak, made to. Accounting to e-commerce, CRM to ERP, a supplier feed nobody has a connector for.
Reporting and analytics
You already have the data. We build the reports and dashboards that make it answer a question, without a monthly seat licence per person who wants to look.
Cloud, DevOps and databases
Deployment that is repeatable, backups that are tested, and databases that stay fast as they grow. Including moving off something older without stopping the business.
Web and mobile
One codebase where that is the right answer, native where it is not, and honest advice about which of those you are actually looking at.
Taking over existing software
Somebody built it and moved on. We pick it up, document it, make it safe to change, and keep it running while we do.
How we work
No discovery phase that produces a document nobody reads.
We watch the work
Before anything is designed, we sit with the people who do the job. Half of what gets asked for on day one turns out to be a workaround for something else, and the software gets simpler once you know which half.
A scope you can hold to
A written scope, a fixed price where the work allows one, and a plan in phases so you see something running early rather than at the end.
Build in the open
You get a working environment from the first phase and you use it while we build. Feedback lands while it is still cheap to act on.
Handover, or we keep it
Documented and handed over to your own team, or maintained by us on a support agreement. Your code and your data are yours either way.
What we build it with
Boring technology, chosen on purpose.
Everything here is something a team other than ours could pick up in five years. We would rather your system outlive its fashion than be interesting to write.
IC Accounting itself is built on exactly this stack — so when we say it holds up under a real workload, we are describing software we run ourselves.
- Java & Spring BootAPIs and business logic
- AngularWeb applications
- PostgreSQLData that has to be right
- DockerRepeatable deployment
- Linux & NginxHosting we manage
- REST & OAuthIntegrations
Tell us what the work looks like.
Not a specification — just what happens today and where it goes wrong. We will tell you honestly whether we are the right people, including when the answer is no.