Skip to what it becomes
Client room Go to the pages
Three objects in a row on pale stone: a pencil sketch of a phone screen, a mock-up of the same screen cut from coloured paper, and a phone showing that layout lit.

relative clause what it becomes

which can become an app, a small tool, or both:

Most sentences turn into an app for the people out on the job, a small web tool for whoever organises them, or both. Around those sit the jobs that make software worth keeping.

for the job offline phone apps

an app that keeps working on the job,

Built for both of the main phone platforms from one shared codebase. Storage is local-first: an entry is saved on the phone the moment it is made, changes wait in a queue while there is no signal and pass themselves on when it returns, and the rule for two edits to the same thing is agreed before it is needed.

Screens are sized for gloves and glare, and tried on old, low-end phones as well as new ones.

You hold an app that saves where the work is, with its source code in your account.

for the office internal web tools

a small tool for whoever plans the day,

Job lists, stock counts, the back office behind a booking, a queue of things waiting to be signed off: small web tools that sit behind an app or stand on their own.

Access is by role, such as crew, supervisor and administrator, and each role sees and changes only what it needs. That is the security principle of least privilege, put into plain practice.

You hold a tool your office can run, change and hand on without us.

and around them the work that makes software last

and the jobs that make it worth keeping:

the old data, carried across

Spreadsheets that grew for years carry merged cells, three spellings of one customer and dates typed four ways. We clean them, retype what cannot be read and import the rest, and you get a report of every row that did not fit and why, so nothing disappears quietly.

You hold your data in its new home, and a list of what needed a human decision.

checked so people can read it and press it

For a site or app you already have: a review against WCAG 2.2 level AA, with a keyboard, the built-in screen readers, contrast measurements and target sizes, and then the fixes as well as the findings. Two of those criteria you can try yourself with the contrast and tap-target check.

You hold what failed, what was fixed, and what still needs a decision.

kept safe on the phone it runs on

A baseline for mobile apps aligned with OWASP’s Mobile Application Security Verification Standard: what is stored on the device and how, how data travels, what the platform is trusted with, how the code is built, and what the app does with personal data. Third-party components are reviewed and pinned, and every release is signed so its origin can be checked.

You hold the findings, the fixes, and a list of every component inside the app.

published under your name, not ours

We prepare the store listing, the inputs to your privacy policy and the answers to the store’s data-safety questions, and the app is published under your own developer account. The listing, its reviews and its history then stay with you, whoever maintains the app next.

You hold a listing in your own account, with its privacy answers written down.

and looked after once it is live

Handover moves the code repository to your account, rotates every password and key, and leaves a runbook and a full export of your data. After it comes an agreed support term with security updates and a published way to report a vulnerability, with at least a year’s notice before that support ends.

You hold everything, and a named term of support.

for whom the people at the other end

for businesses whose work is somewhere else,

Micro and small businesses across the UK, from a single owner to around fifty people, whose work happens in workshops, on farms, in vans, in other people’s buildings or behind a counter. At the domestic end of our trade: small single-purpose tools for people at home.

Every piece of work starts the same way, with discovery and a prototype, described stage by stage in how an engagement runs.

and never

  • an app published under our account for your business
  • your data in an account you cannot open
  • a launch date promised before discovery has shown what the work is
  • anything we build called certified, compliant or secure as a promise

↑ ↓ moveEnter goEsc close