Web applications
Portals, dashboards and internal tools for teams who live in the software eight hours a day. Fast, keyboard-friendly, and readable on a ten-year-old office monitor.
Six things we do
Services
Six things we do, from the first wireframe to the server it runs on. Most projects use three or four of them.
What we build
Mobile apps
Native iOS and Android for staff in the field and customers at home. Both built against one shared API, so the two stores never drift out of step.
PHP, WordPress and Laravel
The PHP systems you already run. We take them over, secure them and keep them moving, instead of insisting you throw eight years of work away and start again.
Databases and reporting
Schema design, tuning the queries that time out, moving between engines without losing a row, and the reports your team will actually open.
Design and graphics
Interface design, brand marks, print and social artwork, done in-house alongside the build — so what ships looks like what was drawn.
Cloud, DevOps and support
Deployment, backups, monitoring and an engineer who answers the phone when something breaks on a Sunday.
How we can be engaged
Most projects start fixed and move to a retainer once the software is live. You are not locked into either.
Fixed scope
A written scope, a fixed price and a delivery date. Best when you know what you need and want the number up front.
Monthly retainer
A set number of days a month for changes, support and the small things that keep coming up once people are using it.
Team extension
Our engineers working inside your team, your board, your standups, for a stretch you decide.
Work out what your project needs
Tick the parts you actually need. You will get an indicative build time straight away, and you can send the selection to us with one click.
Indicative build time
—
Pick the parts you need and the estimate appears here.
A rough guide, not a quote. Real numbers come after we have seen how you work.
How a project runs
-
1
We start with how you work
We sit with the people who will use the software and write down how the work happens today, including the parts that still run on paper.
-
2
You approve the scope
A written scope, a fixed price and a delivery date, agreed before anyone writes code or draws a screen.
-
3
We build in two-week blocks
You see working software every fortnight, so you can change direction while changing it is still cheap.
-
4
We hand over and stay
Training for your staff, written documentation, source code in your account, and a support contract if you want us to keep the lights on.