Websites, applications, integrations, automations, care.
Five things, done properly, instead of everything done thinly. Nearly every job starts as one of them and grows into another — and you are told which one you are buying, and what it costs, before you pay for anything.
What is the thing that is costing you the most right now?
Pick whichever sounds most like your week
We will tell you which of the five it usually turns into, and what the first step would be.
Read about itA site that loads fast, reads well on a phone, and is yours to change.
Two-thirds of the people looking at your site are holding a phone, and most older South African business sites were built before that was true. A refresh keeps what works and fixes the rest. A rebuild starts again when the foundation cannot be saved.
Same structure, new everything else
When the content is right and the pages are roughly in the right order, but it looks its age and falls apart on a phone. Same platform, same sitemap, new design and new front end.
- New visual design and typography
- Rebuilt to work properly on a phone
- Speed and search basics fixed
- You keep your content and your URLs
When the foundation is the problem
When the site is built on something abandoned, nobody has the login, or every change needs a developer. We rebuild it on something you can edit, and hand you the keys.
- New structure, written from what people actually search for
- You edit the content yourself, without us
- Forms, bookings or payments where they earn their keep
- Old URLs redirected so you keep your search position
Not included unless we say so: copywriting, photography, stock images, and any third-party licence or subscription. We tell you before any of those are needed.
The system your business runs on once the spreadsheet stops coping.
The workbook was the right answer at twelve records. At twelve hundred, with four people in it, the copy nobody merged becomes the invoice nobody sent. We build the thing that replaces it — shaped around how you already work, not around how a generic package thinks you should.
What it usually replaces
- A shared workbook with a version in someone’s email
- A process that lives in one person’s head
- An off-the-shelf package you only use a tenth of
- A paper form that gets captured twice
What you get instead
- One record, one version, several people at once
- A history: who changed what, and when
- Rules enforced by the system, not by memory
- Reports that build themselves
Where we tend to be useful
- Insurance and broking — policies, claims, commission
- Utilities and metering — vending, reconciliation, field jobs
- Professional services — matters, time, billing
- Anything with a workflow and an audit trail
Two systems that should have been introduced years ago.
The expensive version of this problem is not the typing. It is the day the two systems disagree and nobody can say which one is right.
Whatever the older system allows
A modern API if there is one. A nightly file drop if there is not. A read-only view over the database if that is all we are given. The age of the system is our problem, not yours.
Logged, both ends
Every transfer recorded with what went, when, and what came back. A missing record becomes a question with an answer instead of an argument.
We hear about it before you do
Failures retry. If they keep failing, we are told. The point of an integration is that you stop thinking about it, which only works if somebody else is.
The jobs that are done by hand because they have always been done by hand.
These are usually the cheapest thing we will ever fix for you, and the one people are most surprised by. A morning that disappears every week is a week and a half a year.
Reports and reconciliations
Pull the figures, clean them, check them against the other system, build the report, send it. On a schedule, including the Monday you are on leave.
Quotes and documents
A quote, a contract or a certificate generated from data you already have, in your layout, without anyone opening a template and saving over last month’s.
Alerts and follow-ups
The thing nobody notices until it is late: a contract expiring, an invoice ageing, a job sitting unassigned. Told to the right person, before it matters.
Someone watching your software, so you do not have to.
Optional, monthly, and cancellable on a month’s notice. It starts when the 30-day warranty on a delivered project ends.
What the monthly fee covers
- Hosting, or administering yours
- Monitoring, with alerts to us rather than to you
- Security patches and dependency updates
- Daily backups, with restores actually tested
- A few hours of small changes each month
What we would quote separately
- New features, or a new module
- Third-party licences and subscriptions
- Infrastructure beyond the included allowance
- Work caused by someone else changing your systems
We will never take your application offline or delete data because an invoice is late. You get 30 days’ notice before we stop hosting anything.