An invoice, anywhere
The job is marked done. The invoice drafts itself at the rate on that customer's record. A person checks it and sends it.
Get your tools talking
Make the tools you already use pass information to each other
Nothing changes for the people doing the work.
Same screens, same buttons. What changes is that the invoice goes out the day the job closes instead of the following Friday when somebody finally gets to the paperwork. One tool tells the next what happened and nobody retypes it. We keep what you already pay for and build the road between them.
01
What it does to your money
The payment clock starts when you invoice. Invoice on the day the work is done and the clock starts days earlier, on every job, every week.
Work out what a week off your debtors book is worth to you, then apply it to every job you did this month.
The quote that went quiet gets chased on the date it was meant to be chased, not when someone remembers.
And nobody in your office is paid to retype what the previous screen already knew.
02
What this looks like in a normal week
Trucking
A signed delivery note closes the load and drafts the invoice against the load number on the confirmation. Nobody retypes the reference.
Fitness club
A sign-up at the front desk appears on the member list and on tomorrow's class register.
Accounting practice
A signed engagement letter moves the client from enquiry to live and starts the onboarding checklist.
Trades
A quote marked accepted books the crew and sends the deposit invoice.
Travel
A confirmed booking writes the supplier payment deadline into the diary before anyone forgets it.
Retail
An online order tells the shop floor what to pick and tells the customer where it is.
03
How we build it
We watch the job being done
One session on a screen share, with the person who actually does it. Not a questionnaire.
We write the rules in plain words
What triggers what. What happens when a field is empty. Who gets told when something fails, and when it tries again. You read that page and approve it before we touch anything.
We build the smallest useful piece first
One connection, live, in your real working week.
We watch it for two weeks
Real data breaks things test data never does. We fix what breaks in those two weeks at no extra cost.
We hand it over with a page that explains it
Written so the next person who joins can read it, and so another developer could pick it up without phoning us.
04
What usually gets connected
| From | To | What crosses |
|---|---|---|
| The form on your website | Where you keep your customers | Name, phone, what they asked for, and which page they came from |
| Your booking system | Your accounts | Confirmed booking and deposit paid |
| Your job board | Your invoicing | Job closed, hours on site, materials used, and the agreed rate |
| Your online shop | Your stock sheet | Item sold and quantity left |
| WhatsApp and phone enquiries | Your customer list | The number, the first message, who picked it up, and when |
| Your accounts | Your morning screen | What is unpaid, and how many days overdue |
05
Before and after, one enquiry
Today
The enquiry arrives by email. Someone copies the details into a spreadsheet. Someone else asks in the group chat whether it was answered. The quote gets built from a file called Quotefinalv3. Two days later nobody is certain who is following it up.
After
The enquiry arrives by email. It appears once, with the details already in the right boxes and the source recorded. The quote uses the current rate card. The follow-up sits on somebody's name with a date against it.
What we get access to, and what we never touch
You are about to let a stranger reach into the accounts your business runs on, so here is exactly how that works.
You grant the access yourself, from your own admin screens, in your own accounts. We never ask for your password and we never work from your login.
Each connection gets the narrowest access that does the job: one folder, one inbox label, and nothing beyond that. An integration that drafts invoices gets the invoice fields and nothing wider.
You can revoke it in one click, from the same screen you granted it, without asking us and without anything else in your business stopping.
We do not copy your customer list, your rates or your documents onto our own machines to make any of this work. The information moves between your accounts.
Every connection is documented: what talks to what, which account it uses, what it is allowed to touch, and what happens when it fails. That document is yours from day one.
07
When this is not worth doing
Count the lines someone actually retypes in a day. If it is four lines between two screens, an integration will cost more than it saves, and we would rather you spent the money elsewhere.
If one of your tools has no proper way in and no export, any connection to it will be fragile. Sometimes a scheduled export into a shared file is the sensible answer, and it is cheap. Ask us whether your 2014 accounts package is a problem and you get the answer on the call.
If two people in the business would handle the same enquiry differently, decide which way is right before we connect anything. A connection will move the disagreement faster, not settle it. We can sit in on that decision if it helps.
There is no AI in this work. AI comes after, once the information is reaching the right place.
The numbers, in one place
- Connections are quoted per job, and you see the number before anything starts.
- All prices exclude VAT.
- What moves the price: whether each tool has a proper way in, how many tools are involved, how many conditions run between them, and how old the older system is.
- A care plan is for websites and apps, not for integrations.
- After go-live, watching a connection and repairing it when a supplier changes something is quoted per job, and you see the number before anything starts.
- There is no monthly licence and no lock-in either way.
Straight answers
Questions owners ask us
No. Keeping it is the entire point. We work with what you already pay for and what your team already knows. If we ever think a tool should be replaced, we tell you why and leave the decision with you.
Suppliers change things without warning, so the connection is built to tell us when it fails rather than fail quietly. Watching it and repairing it afterwards is quoted per job, and you see the number before anything starts. We come back to you within two working days.
The connections run inside your accounts, not ours, so they keep running whether or not we do. From the day it goes live you own the code, the written build document, every login and the account it runs in. If we stopped working together tomorrow, we hand the lot over and walk your next developer through it on a call. Nothing is locked to us and there is no licence of ours to keep paying.
A first connection between two tools is usually live within two to three weeks, and a good part of that is waiting on access. Bigger builds run in pieces so you get something working early rather than everything at the end.
We work on a screen share by default, wherever you are in the country. If something genuinely needs a person standing next to the work, we say so and arrange it, and in and around Cape Town we come to you.
The next step
WhatsApp us a photo of the two screens your clerk retypes between, on +27 73 932 6852.
We will come back within one working day and tell you whether they can pass information to each other and roughly what it would cost. You can also call that number, email [email protected], or book twenty minutes.
Or email [email protected]. No slides, and no invoice for the conversation.