We build the website or the app, and then we keep it running. The same people do both, which is why nothing gets lost between the two.
Everything that runs in a browser — the site your customers land on and the system your team logs into. Built with Next.js, React, Laravel and MySQL.
Native Android apps written in Kotlin — for staff who work away from a desk, or for customers. Both apps we've shipped are Android; iOS builds are available on request.
Launch is the start. Every project includes 15 days of support free; after that, keeping it running is an optional monthly agreement you can end whenever you like.
How the work is built, not just what gets built.
These eight are on every project, at every size. They are the difference between software that ships and software somebody can still run in three years.
Every project lives in Git from the first commit, and changes are reviewed before they merge — so nothing reaches your system because one person was in a hurry on a Friday.
The parts that would be expensive to get wrong are covered by tests that run before a release, which is how a change to one screen stops quietly breaking another.
You see the real thing on a staging URL and approve it there. Nothing reaches production that you haven't already clicked through yourself.
Live systems report their own errors and downtime to us. You should not be the monitoring — finding out from a customer is too late.
At handover you get a runbook, not just a zip: how to deploy it, where every account and service lives, and how to run it without us.
On a maintenance agreement dependencies get patched on a schedule, rather than left to age quietly into the vulnerability that takes the system down.
Backups that we have actually restored from. An untested backup is a hope, not a plan, and the day you need it is the wrong day to find out which it was.
Contrast, keyboard access and load time on a mid-range phone are checked before launch — not after somebody complains that they cannot use it.
Whether it’s a one-page site or a multi-role internal system.
Quoted from a written scope before work starts. Changes are priced separately and agreed in advance — never billed after the fact.
Agreed at proposal stage. If anything threatens it, you hear that week rather than at the deadline.
We stay on after launch while real users reach the system, and fix what they find.
Source code, design files and accounts transfer to you at handover. No licence, no lock-in, no fee to keep it running.
Against a written scope, as one fixed number. We work out what the system has to do, who uses it and what it connects to, then quote it — usually within one business day. There is no hourly billing, and change requests are priced and agreed before they're built.
That is most of what we build. Employee and task management, approvals and leave, visitor and gate logging, internal messaging — all shipped as private systems with role-based access, so each person only sees what they should.
Both apps we've delivered so far are native Android, written in Kotlin. iOS is available on request — say so at scoping stage and it's priced into the proposal.
Usually, yes. Send us the repository or the live URL first. We'll look at it and tell you honestly whether it's worth maintaining as it stands, fixing, or rebuilding.
