Services
Eleven things we do, written out properly.
Under each one you get what you receive, what we need from you, and the site of ours where we did it. Open the links. That is the point of them.
Service 1
Custom software
Software written for one business, because the ready made product does not fit the way that business works.
What you get
- A working system, not a slide deck. You see it running at the end of every stage.
- The source code and the database are yours, in your own repository.
- Plain English notes on how it works, so the next person can pick it up.
- A test suite that fails when the important rules are broken.
What we need from you
- One person on your side who can answer questions and make decisions.
- The real forms, spreadsheets and emails you use today, even the messy ones.
- The rules that must never be broken, in your own words.
Where we have done this
Service 2
Web applications
A site that does work, not a brochure. Accounts, dashboards, uploads, search, admin screens and the rest.
What you get
- Fast pages. Server rendered, so the first screen arrives before the browser has downloaded everything.
- A phone layout that is checked on a phone, not guessed at on a laptop.
- An admin area where your own team can change content without calling us.
- Security headers, rate limits and server side validation from the first day.
What we need from you
- Your logo and brand colours, or permission for us to choose them.
- The list of jobs a user must be able to finish on the site.
Where we have done this
Service 3
SaaS products
A product you can sell to many customers, with sign up, billing, plans and a till that works.
What you get
- Sign up, log in, password reset and the boring parts that take the longest to get right.
- Stripe billing with plans, one off payments, refunds and a webhook that is tested.
- A customer area and an owner area, kept apart by the server and not by hiding a button.
- Usage limits so one heavy customer cannot run up your supplier bill.
What we need from you
- Your price list, and what happens when somebody stops paying.
- A company bank account for the Stripe payouts.
Where we have done this
Service 4
Automation
The jobs somebody does by hand every week, done by the server instead, with a watcher that shouts when it fails.
What you get
- Your repeated job running on a schedule or on a trigger, in n8n or in code, whichever is simpler to keep.
- A health check that tells you it ran, because a silent job that fails is worse than one that crashes.
- A log you can read later when somebody asks what happened on a certain day.
- A kill switch, so you can stop it without calling anybody.
What we need from you
- One example of the job done by hand, start to finish.
- Access to the tools it has to touch, or a test account on each.
Where we have done this
Service 5
Data and APIs
Public registers, supplier feeds and other systems, read reliably and turned into something a customer will pay for.
What you get
- A clean store of the data, kept up to date, with the date of every reading.
- Caching and limits so a supplier bill cannot surprise you.
- An honest statement of what the data does not cover, printed where the customer reads it.
- Your own API if you need other systems to read it.
What we need from you
- The supplier accounts or the API keys. You hold them, we never ask you to send them to us in a message.
- The licence terms for any paid data, so we stay inside them.
Where we have done this
Service 6
AI features
Useful AI inside a product. Reading documents, answering questions, drafting text, with a human in the way before anything is published.
What you get
- A feature with a job, not a chat box bolted on the side.
- Sources cited, so a reader can check the answer instead of trusting it.
- Approval before anything reaches a customer, unless you decide otherwise.
- A cost ceiling per customer and per day.
What we need from you
- The documents or data the feature should work from.
- A clear line on what it must never say.
Where we have done this
Service 7
Payments and billing
Taking money properly. Cards, plans, invoices, refunds and the paperwork that keeps the bank happy.
What you get
- Stripe set up with the right legal entity, the right statement name and the right support address.
- Webhooks that are verified on the server, so a payment cannot be faked by a browser.
- Invoices with a unique number, and a prefix of your own.
- A test run with real money, and a refund, before the first customer sees it.
What we need from you
- Company details that match your registration exactly, because every provider checks them.
- Your bank account for payouts.
Where we have done this
Service 8
Search and content
Pages that people actually find. Keyword work, page structure, sitemaps, and content written to answer a real question.
What you get
- A page plan built from what people search for, with the volume and the date it was measured.
- Clean titles, headings and structured data, and a sitemap that does not point at the wrong host.
- Search Console set up and verified, so you can see what happens.
- Articles written in plain words, with sources.
What we need from you
- Access to your domain for the verification record.
- Somebody who can approve the wording.
Where we have done this
Service 9
Mobile apps
Android and iOS apps from one codebase, built in Flutter, for the jobs a phone does better than a browser.
What you get
- One codebase, two stores, one look.
- Offline first where it makes sense, so the app still works on a bad signal.
- The store listing text, the screenshots and the privacy policy prepared with the build.
What we need from you
- A developer account on each store, in your company name.
- A decision on what the app must do without an internet connection.
We have built this, but nothing of ours in this line is public yet, so we are not going to show you a link that does not exist.
Service 10
Hosting and care
Somebody responsible for the thing after it goes live. Deployment, certificates, backups and a watcher on top.
What you get
- Deployment in containers, with a certificate that renews itself.
- Backups that are restored once to prove they are real, because an untested backup is a hope.
- A daily health check that reports in one line, and says so loudly when it is unhappy.
- A named route to reach us when something breaks.
What we need from you
- A server, or permission for us to put it on ours.
- The domain, or access to its DNS.
Where we have done this
Service 11
Rescue work
A build that stalled, a developer who left, a site nobody can deploy any more. We read it, write down what is true, and finish it.
What you get
- An honest report first. What works, what does not, and what it would cost to carry on against starting again.
- Access and keys back in your own hands, documented.
- The smallest set of changes that gets you live, before any tidying up.
What we need from you
- The code, wherever it lives, and whatever access still exists.
- The last person who touched it, for one conversation, if that is possible.
We have built this, but nothing of ours in this line is public yet, so we are not going to show you a link that does not exist.
Not sure which of these you need.
That is normal and it is our job, not yours. Describe the problem and we will tell you which of the above it is, or tell you that you do not need us.