You run the business. I take care of the people who reach out to it.
Four systems. Each one fixes one specific way a business loses money: slow replies, bad-fit leads, mistyped bank details, or repeated questions. The numbers below each system are what it did when it ran, not a target.
Three ways an enquiry turns into a lost sale.
Someone shows interest
A form gets filled in. A slow first reply loses the sale before you know it happened.
Someone gets busy
You're on a call, or it's Friday. The enquiry sits instead of moving.
Someone slips through
Nobody decided to drop it. It just wasn't clearly anyone's job.
You get your hours back. The follow-up no longer depends on someone remembering to do it.
Four problems, four systems, and what each was built to handle.
Each one runs end to end and was tested against real data before I called it done.
Numbers below are measured, not estimated. Where a result is from a business I own rather than a client, that's stated below.
to Payment
Reads the invoice, matches the bank, and holds the payment until a person approves it.
Paying suppliers by hand means typing bank details off a PDF and matching the bank name by eye from a dropdown. It's slow, and the one mistake it invites is expensive: a payment sent to the wrong account is hard to get back, sometimes impossible.
Worth building for
- You pay more than a handful of suppliers each month.
- Invoices arrive as PDFs, not through a portal.
- Someone retypes bank details into banking software.
- A wrong payment would be painful to recover.
Not worth it, and I'll say so
- You pay three suppliers, all on standing order.
- Everything already flows through one integrated system.
- Policy requires a person to key every field by hand.
- You're regulated and must use certified software.
I built the matcher and audited it against a full national bank register: 278 entries, checking abbreviations, trading names, and pre-merger names against the official ones. The same logic carries over to any country's register. Before it touches real money, I run it against your own invoice formats first.
See how it runs
- 01 Collect. Invoices arrive in a folder or inbox. Nothing to upload or rename.
- 02 Extract. Supplier, amount, date, reference, account number, and bank name get pulled from each document.
- 03 Match. The bank name gets checked against the official register for your country.
- 04 Score. A confident match moves on. An uncertain one goes to a person instead of being guessed at.
- 05 Approve. A summary reaches whoever signs off payments. Nothing moves until they answer.
- 06 Pay. The payment goes out through your existing provider, and the record gets written back.
Governance
Gives every enquiry an owner and a deadline the moment it arrives.
When more than one person could pick up an enquiry, everyone assumes someone else already has. Nobody decided to drop it, but it was never assigned, so it never moved. Telling the team to be faster doesn't fix that. A named owner and a deadline does.
Worth building for
- More than one person could pick up an enquiry.
- Inbound arrives on three or more channels.
- One lost job is money you'd notice.
- Customers ring your competitors the same day.
Not worth it, and I'll say so
- You work alone, so there's nobody to assign to.
- Someone already owns the inbox as their whole job.
- Your CRM already routes and chases properly.
- Work doesn't start with an inbound enquiry.
I own a sneaker retail business and use it to test what I build. Weekly closed deals went from four to nine after this went in, from enquiries that used to go unanswered. Enquiry volume didn't change. I also timed replies across firms in one London trade with the same test enquiry: fastest under a minute, slowest over a week. Those firms weren't lazy. They had no owner and no clock.
See how it runs
- 01 Capture. Web form, email, phone, WhatsApp, live chat: all of it lands in one place.
- 02 Deduplicate and clean. A person who fills in the form and then calls you is one record, not two.
- 03 Acknowledge. The customer hears back within seconds.
- 04 Assign. Every enquiry gets a named owner and a deadline.
- 05 Escalate. Miss the deadline and it reminds the owner. Miss it again and it goes up a level.
- 06 Confirm close. When the job is won, the customer is told.
Qualification
Scores new leads against your rules and drafts an opening for the ones that fit.
A list of leads is easy to buy. Working out which ones are worth contacting is the real job, and it eats a day a week by hand. Skip that step and you send the same message to everyone, and most of them were never going to buy.
Worth building for
- You sell to businesses that can be found on a map.
- Someone on your team researches prospects by hand.
- Bad-fit leads waste more time than thin volume does.
- You want to approve what goes out under your name.
Not worth it, and I'll say so
- You need contacts inside large corporations.
- You want thousands of messages a day, regardless of fit.
- Nobody has ten minutes to review drafts.
- Your buyers have no public presence to research.
I ran it live against roofing companies in Tampa. It sourced 14 businesses. Seven cleared the checks and had drafts written. The other seven failed on the campaign's rules, mostly on size, and never reached drafting. Half the run ended in a decision not to contact someone, which is the point. On one run the filters were too tight and output dropped from 109 businesses to 10, so I loosened them and ran it again. That tuning happens with you.
See how it runs
- 01 Source. You name the trade and the area. It pulls businesses from live listings that day.
- 02 Clean. Duplicates get merged. Incomplete records get dropped.
- 03 Filter. Checks run against rules you set, such as review count and company size.
- 04 Read. For the ones left, it reads their website and finds one true, specific detail.
- 05 Draft. It writes the outreach, opens on that detail, and saves it to your Gmail drafts.
- 06 You decide. Nothing sends until you've read it. Send it, edit it, or bin it.
Answering
RAG-ingested AI chatbot
Answers questions from your own website, and says so when the answer isn't there.
Most chat helpers answer from everything they've ever read, not from your site. They sound confident whether they're right or not, which is how a customer gets promised something you don't offer. This one only repeats what's written on your pages.
Worth building for
- People ask you the same things repeatedly.
- The answers are already written on your site.
- Questions come in at night and on weekends.
- Your prices, policies, or hours change now and then.
Not worth it, and I'll say so
- Your website barely has any writing on it.
- Every question needs a person's judgement.
- Questions are about someone's private order or account.
- Your site hides its text from simple readers.
I built and tested this end to end on a public government tax page. The first run read 22 pieces of writing. Every run after, with the page unchanged, read nothing new and cost nothing. It answered questions the page covers correctly, with a link to the source. On questions the page doesn't cover, it said so, every time.
See how it runs
- 01 Read. A program opens your page and copies out the writing. Menus and adverts get dropped.
- 02 Split. The writing is cut into small pieces, small enough to search precisely.
- 03 Tag. Each piece gets a tag, so a later check skips anything unchanged.
- 04 Search. A question comes in, and the closest pieces get pulled out.
- 05 Answer. It answers from those pieces alone, with a link to the source. No match, no guess.
- 06 Log. The question and answer are written to a spreadsheet you can open anytime.
The same shape shows up in all four systems.
Map the real work
Where the work happens now, and exactly where it stalls.
Build the smallest version
One path that fixes the biggest stall point, on real data from day one.
Put a person where it matters
Nothing sends or pays without an approval step first.
Keep it running
Every run is logged. Failures alert you before a client notices.
Ibrahim Ademola
Started in Linux administration and Active Directory, keeping systems running correctly without anyone watching them. Same job now: build systems where the right thing happens at the right time, whether or not a person is looking.
What people ask before saying yes.
Will this replace my staff?
No. It removes the repeat, structural failures. Judgement calls still land on a person, and every payment or message stops for approval first.
What happens when the source information changes?
Each system checks what's different and updates only that. Nothing changed means nothing to re-check.
What if a system can't find an answer?
It says so, in plain language, instead of guessing. Same principle behind the approval step in the others.
What does it cost to run week to week?
Only the parts that changed get processed. A quiet week costs close to nothing, and that's measured, not estimated.
Do you ever say a system isn't worth building?
Yes. Each system above lists the reasons it wouldn't be worth it for a given business. If you fit that list, I'll say so first.