The kinds of systems we build, end to end.
Rather than a portfolio of named projects, here is how we approach four system types we build most often: the situation each one solves, the constraints that usually apply, the architecture, and what you own at handover.
We are a small team and we are happy to walk through the technical detail on a call, including arranging references. That tends to answer more than a case-study page would.
An internal desktop tool that replaces a critical spreadsheet
A process that matters runs on a spreadsheet several people edit at once. It works until it does not: figures disagree, someone overwrites a column, and the only person who understands the formulas is on leave.
A customer or dealer portal over systems you already run
Customers or dealers get information by emailing someone in your office. That person looks it up in two systems and replies. It is slow, it does not scale, and it is invisible to management.
A field app that captures work away from the office
Work happens on site and gets recorded on paper. The paper reaches the office days later and someone retypes it. Invoicing waits, and disputes come down to handwriting.
An integration that removes manual data entry between systems
The same information is typed into two or three systems. Errors surface at month end, and the reconciliation is somebody's recurring afternoon.
No system type matches that filter.
Describe what you are building and we will tell you which of these it is closest to.
Ask us instead