Loading
Internal systems, mobile apps, websites and AI automation. We also take on software you already have and make it work better.
Before and after
Work spread across spreadsheets, inboxes and a WhatsApp group. An idea that needs to become something customers can use. Software that already runs the business and is now too risky to change.
Orders, jobs and approvals in one system, so nobody re-types anything or has to ask where it got to.
What we would build
Three jobs we take on, and what we would actually put in place for each one.
Orders arrive by email, get copied into a spreadsheet, and someone chases the rest.
One system that holds the orders, shows who has what, and connects to the tools you already pay for.
You have an idea and a rough plan, but nothing a customer can use yet.
A first version that does one job properly, released to real users, with a plan for what comes next.
Someone reads every email and copies the details into another system by hand.
We automate the steps that follow a rule, use a model where judgement is needed, and keep a person in charge.
Where it lives
The same system looks different to a manager at a desk, someone out on a job, and a customer.
One screen for the person who has to keep the day moving.
Today's jobs, and somewhere to record what happened on site.
Your existing tools stop needing a person to copy between them.
It reads the same data your team does, and puts the awkward things at the top.
How to start
Pick the one closest to your situation. Each one ends with something you can act on.
You know something is wrong. You do not yet know what the software should do about it.
You describe what is not working. We ask questions and say whether we can help.
A straight answerWe sit with the people doing the job and follow one real case from start to finish.
How it works todayRough screens for the parts that matter, so you can argue with something real.
Screens to react toWhat gets built first, what waits, and what we are deliberately leaving out.
A written scopeWe price the build and put it in order. You choose whether to go ahead.
A quoteThe rule we hold toThe plan is yours, wherever you build it.
Start a projectWhat we build
Most projects need two or three of these at once. You do not have to work out which before you talk to us.
See what each one involvesOrders, jobs, stock, approvals and reports, in one place instead of five.
↗Mobile appsApps for your own staff out on a job, and apps your customers install.
↗Websites and web appsMarketing site, customer logins, online shop, and an editor you can use.
↗AI and automationSteps people do by hand, and existing models put to work inside your systems.
↗How we work
The person who scopes your project writes it, and is still the person who fixes it a year later.
There are five of us. Nobody sits between your question and the person who can answer it.
Working software in your browser, while there is still time to change your mind about it.
We learned to build software before AI could write any of it, so we can tell when it is wrong.
Done properly
Five things, on every release. They are part of building the software, not an upgrade you are quoted for later.
It works with a keyboard, a screen reader and a phone, not only your laptop.
We decide who can see what, and customer data stays where it should be.
Pages load and screens respond on an ordinary phone and a poor connection.
When something breaks we hear it from the software, not from your customers.
How it is built and how to run it is written down as we go, not afterwards.
Questions
We quote per project, once we know what the software has to do. Tell us roughly what you can spend and we will tell you straight whether it can be built for that, and what we would leave out to make it fit.
Getting in touch
Say what you need in a few sentences. If you are not sure what you need yet, say that instead and we will ask.