We build software for businesses that have outgrown the spreadsheet and cannot find an off-the-shelf product that fits how they work.
What we build
Web applications, internal tools, native mobile apps for iOS and Android, and the APIs that hold them together. Most of our work is operational rather than consumer-facing — the system a business runs on rather than the thing its customers see.
How a project runs
A requirements conversation first, then a written statement of work with scope, milestones and a fixed price. Changes go through a written change order before the work happens, so nobody discovers a surprise at invoicing. You see working software early and often rather than at the end.
We will tell you when a project is not worth doing. The most useful thing we say to some prospects is that an existing product covers ninety percent of what they need for a fraction of what a build would cost.
After launch
Software that nobody maintains stops working — dependencies age, platforms change, and the person who understood it leaves. We offer ongoing support and maintenance, and we would rather you took it than watched the thing we built decay.
Ownership
Intellectual property in the deliverables transfers to you on full payment. We retain our own pre-existing tools and libraries and license them to you as embedded in your deliverables. Third-party and open-source components keep their own licences. All of it is written down in our Terms of Service.
Common questions
Do you take over existing projects?
Sometimes. It depends on the state of the code and whether the original team is available to hand over. We will look before quoting.
How long does something take?
We give a date in the statement of work rather than a range. If we cannot estimate it confidently we will scope a short discovery phase first and charge for that alone.