Bookings
TodayA register, then a spreadsheet, then the channel manager.
With the systemEntered once. Correct everywhere.
No double bookings
We map the process. Then we build.
Software fails when it is built from an assumption about how a business runs. So we start by watching the work happen, counting the steps that are done by hand, and agreeing in writing which ones should disappear. Only then does anyone write code.
The process
Six steps, and what you hold at the end of each.
Nothing here is a surprise on either side. Scroll through, and the panel keeps pace with you.
Step 01 of 06
We watch the work happen
We spend time with the people doing the job, at the desk, in the store room, wherever it actually happens. Every step gets written down, including the ones nobody mentions in a meeting because they are too obvious.
What you have at the end
A written map of the process as it runs today
- Step 01
We watch the work happen
We spend time with the people doing the job, at the desk, in the store room, wherever it actually happens. Every step gets written down, including the ones nobody mentions in a meeting because they are too obvious.
A written map of the process as it runs today
- Step 02
We count the manual steps
Each step gets a number against it: how often it happens, how long it takes, and where the mistakes creep in. That is what tells us which parts are worth automating and which are fine as they are.
A task-and-time list, ranked by what it costs you
- Step 03
You approve the scope
We come back with what we would build, in what order, at what price, by what date. If a step is cheaper to fix with a habit than with software, we will say so.
A fixed written scope, priced, with dates
- Step 04
We build in stages you can see
The first usable version lands early, and you use it while the rest is built. Weekly updates, and a working link, not a status report about a status report.
A working system, in stages, from week two or three
- Step 05
Your team is trained on it
We train the people who will use it every day, on their own data, before go-live. If something takes more than one explanation, that is our design problem and we change it.
Trained staff, a short handbook, all your credentials
- Step 06
We stay on for what comes next
Rules change, the business grows, someone thinks of a better report. Monthly support keeps the same people available to change it.
A named contact and agreed response times
What changes
The manual steps we look for first.
These four come up in almost every walkthrough, whatever the business does.
Payroll
TodayPaper attendance, added up by hand at month end.
With the systemAttendance feeds payroll. You approve it.
Days down to an afternoon
Follow-ups
TodaySomeone remembers the reminder and the invoice. Or does not.
With the systemSent on schedule. Silence gets flagged.
Nothing rides on memory
Reports
TodayAn afternoon spent assembling numbers from three places.
With the systemOne link, already current.
One version of the truth
What we promise
Secure, simple, scalable, and yours.
These four commitments are written into every scope document we send, not implied by a badge on a homepage.
Security is built in, not audited in laterThe same engineers who harden servers and run penetration tests for our clients review what we build. Access is per-role, passwords are hashed, data in transit is encrypted, and backups are tested by restoring them, not by ticking a box.
It grows without a rewriteWe build on managed cloud infrastructure that scales with load, and we keep the data model clean enough that a second branch, a second property or ten times the records is a configuration change rather than a new project.
Simple enough that training sticksThe people using it are not IT staff. Screens are built around the job, in the fewest steps that do it, and tested with the person who will actually use them before we call it done.
You own all of itYour accounts, your data, your source code, your hosting. Handed over at launch with documentation. Nothing is locked to us, and you can take it to another team whenever you want.
Who does what
Both halves, written down.
Most projects that go badly go badly here, not in the code. So we say it out loud at the start.
What we do
- Spend time on site learning the process
- Write the scope, the price and the dates
- Build in stages you can use as they land
- Train your team on their own data
- Hand over accounts, code and documentation
- Stay available for changes on a monthly retainer
What we need from you
- Access to the people who do the work
- One person who can make a decision
- Honest numbers, because the messy ones are the useful ones
- Feedback on each stage within a few days
- Somebody to be trained, before go-live
Before any of that
What happens when you first write in.
A reply within one business day
You get a short set of questions and a call slot. The person who replies is the person who would run the work.
NDA before the details
We sign a mutual NDA on request, before any commercial or technical detail changes hands.
We say so when it is not a fit
If the work sits outside what we do well, we will tell you on the first call and point you somewhere better.
Aligned with
Standards we build against.
We are not an audit firm and we do not issue certificates. We build and test against the standards your auditor, insurer or enterprise customer will ask about, and our reports are written to be handed straight to them.
- ISO 27001
- SOC 2
- PCI-DSS
- DPDP Act 2023
- GDPR
Common questions
Frequently asked.
What happens in the process walkthrough?
We spend time with the people doing the job, at the desk, in the store room, wherever the work happens, and write down every step, including the ones too obvious to mention in a meeting. Each step gets a frequency and a time against it, which is what tells us where automation is worth paying for.
Do you charge for the scoping?
The first conversation and a short walkthrough cost nothing. A full process map on a larger operation is quoted separately, and the fee comes off the build if you go ahead.
How do you make sure our staff can use it?
Screens are built around the job rather than the database, tested with the person who will use them, and your team is trained on their own data before go-live. If something needs explaining twice, we treat that as a design fault and change it.
What if we only want part of it automated?
That is the normal outcome. We rank the manual steps by what they cost you and you pick where to start. Some steps are cheaper to fix with a habit than with software, and we will tell you which ones.
Ready when you are
Start with the walkthrough.
Tell us which process is costing you the most time. The first conversation is about your business, not our services, and it costs nothing.
You get a reply within one business day, from the person who would run it.