What we build, run and advise on
Eight lines of work, delivered by one team. Open a service to see what is included and what a typical engagement looks like.
Systems built for one business: order and job management, portals, workflow and approvals, integrations between tools that were never meant to talk. We start from your process, not from a product roadmap.
Typical engagement - 8 to 20 weeks, fixed scope, staged payments. Source code and documentation are yours.
Customer portals, booking and payment flows, internal dashboards, and native-feeling mobile apps for iOS and Android. Accessible, fast on mid-range devices, and instrumented so you can see what people actually do.
Typical engagement - 6 to 16 weeks, design and build, app-store submission included.
Lift-and-shift or re-platform to AWS, Azure or Google Cloud; infrastructure as code; CI/CD pipelines; monitoring and alerting that pages a human. We review your bill as part of the work - most first audits find something.
Typical engagement - a two-week assessment, then migration or a standing platform retainer.
Pipelines and a warehouse your numbers can be trusted from, reporting people actually open, and applied AI where it earns its keep - document extraction, classification, assistants over your own content.
Typical engagement - a proof of value in four weeks against one real dataset, before any platform commitment.
Platform selection without a kickback, configuration over customisation, data migration with reconciliation you can sign off, and training for the people who will live in it daily.
Typical engagement - 10 to 24 weeks by module, with a parallel-run period before cut-over.
Architecture and code audits, build-versus-buy decisions, security and access reviews, and a costed roadmap you can take to a board. Written to be read by non-technical decision makers.
Typical engagement - two to four weeks, fixed fee, findings presented in person.
Test strategy, automated regression suites in your pipeline, performance and load testing, and release checklists - so shipping on a Friday stops being a gamble.
Typical engagement - embedded QA alongside your team, or a one-off suite build and handover.
Monitoring, patching, backup and restore testing, user support and vendor wrangling - with response times in the agreement and a named engineer who knows your setup.
Typical engagement - monthly retainer by user count and system footprint, 30 days' notice either way.
Frontend
Backend
Mobile
Cloud & DevOps
Data & AI
Platforms
Fixed-scope project
A defined outcome for a defined price. Best when the requirement is clear and the budget has to be approved up front.
Quoted per project after scoping · staged payments
Dedicated team
Engineers, QA and a delivery lead working to your backlog. Best for continuous product work where priorities move.
Monthly rate per engineer · one month's notice
Support retainer
Keeping what exists running - monitoring, fixes, small changes and a response time you can hold us to.
Monthly retainer by footprint · SLA in writing
After a scoping session we send a written estimate with assumptions listed. Fixed-scope work is quoted as one number with staged payments; ongoing work is a monthly rate. We do not quote before we understand the requirement.
You do. Source code, infrastructure definitions and documentation sit in your repositories and your cloud accounts from day one, so you are never locked to us.
Yes. We start with a short audit of the code, data and hosting, then give you a stabilisation plan and an honest view on whether it is worth extending or replacing.
Small is fine - an integration, a report, a fix to something that has been broken for months. If it is not a good use of your money, we will say so and point you elsewhere.
A shared board you can see at any time, a demo of working software every two weeks, and one named contact. No status reports written to look busy.
Yes - NDA before the first detailed conversation if you prefer, and a data processing agreement before we touch anything containing personal data.