Services
Four kinds of work.
Each of these says what you get and when it is the wrong answer. Both halves are useful before you spend anything.
Desktop software
The system the business actually runs on.
A Windows application that holds your real records: stock, costs, customers, documents. It lives on your machine, its database is encrypted, and it opens whether or not the internet does.
That last part is not a technical detail. A business whose till stops when the line drops is a business that has bought somebody else’s uptime.
What you get
- An installer, and an application that updates from one link
- An encrypted local database, with backups you can verify
- Roles — who may see cost and profit, enforced in the data, not hidden in the screen
- The documents you print, generated from the record instead of retyped
When it is not the answer. If two or three people need the same live view from different buildings, a web application is the right shape and we will say so.
Websites
Hand-built, fast, and yours.
Marketing sites, catalogues and WordPress themes written from scratch — not a page builder, not a stack of plugins that each want a subscription.
The result is a site that loads quickly on a phone on a bad connection, that works with JavaScript switched off, and that nobody can break by updating a plugin you have never heard of.
What you get
- A design made for your business, not a template with your logo dropped in
- Search, filters and forms that are real links — every result can be sent to somebody
- Enquiries stored before any email is attempted, so a mail problem never loses a customer
- Written so your own people can edit the words without calling us
When it is not the answer. If you need a shop with a hundred products, stock levels and payments, that is a different job with a different budget. Worth saying before we start, not after.
Products & SaaS
Software built once, sold many times.
Some systems are worth turning into a product. Tiff Cardealer began as one dealership’s office system and is now sold to others — the same application, with nothing about the first customer written into it.
That takes a particular discipline from day one: no name, no address, no logo anywhere in the code. If you think what you are building might one day be sold to the business down the road, this is the conversation to have at the start.
What you get
- An architecture that separates the product from the customer using it
- Per-customer branding, settings and documents with no code change
- A build pipeline that produces a signed, downloadable release on every merge
- Licensing that does not make your uptime your customer’s problem
When it is not the answer. Most business software should stay one business’s tool. Productising early costs real money and buys nothing until there is a second customer.
Everything around it
Domains, hosting, email — and someone who answers.
The unglamorous half. Domains and DNS, hosting that suits where your customers actually are, TLS certificates that renew themselves, business email, backups that live somewhere other than the server they are protecting.
None of it is interesting until it fails, which is the argument for having it set up by the person who will pick up the phone when it does.
What you get
- Migrations done on a quiet day, with a backup taken first and kept off the server
- Certificates that renew on their own, and a check that they did
- Analytics and a privacy policy that match what the site actually collects
- A written record of every decision, so the next person is not guessing
When it is not the answer. We do not resell hosting. You own the accounts, you hold the invoices, and you can take them anywhere at any time.
Not sure which of those it is?
That is normal, and working it out is part of the job rather than something to settle before you get in touch.