Automation for finance and operations teams
Back-office work, done and accounted for.
We build a bot for each repetitive admin job your team carries, inside the systems you already use. It does the routine work, flags anything outside your rules and waits for a person’s OK.
Pulled 1,284 bank lines across 4 accounts
Matched 1,251 to the accounts
33 flagged for your OK: no match, or could match two things
Flagged lines answered and posted. Reconciled.
Example data only.
Nothing to install
No new logins and no new screens. We work inside the systems the job already lives in.
It asks before it guesses
Anything that doesn’t fit your rules gets flagged and waits for a person’s OK.
It reports back
It works through every line, then tells you what it did and what it flagged.
A bot on each job. One line from inbox to reconciled.
BotBoys puts one bot on one job. BotPartners is for teams with several. We take them one at a time and join them up, so the work moves from one job to the next without a person carrying it.
- Inbox handling214 emails read and sorted
- Reconciliation1,251 payments matched
- Payment follow-up18 missed payments chased
- Your OK33 flagged items answered by a person
Reconciled
- 01
We sit down with your team
We find the repetitive job that is costing the most, and who owns it.
- 02
We build it
We connect to the systems the job lives in and teach the bot your rules.
- 03
It learns the rhythm
In the first weeks the bot checks in with your people until the job runs in the background.
- 04
Your team messages it
On Teams, WhatsApp or Telegram, whichever your people already have open. It doesn’t clock off.
It works on its own. It does not decide on its own.
The bot does the routine. Your people keep the decisions. The rules are yours, and we set them with you before the bot starts.
| Step | The bot | A person |
|---|---|---|
| Reading statements, payouts and the shared inbox | Does it | Not needed |
| Matching payments to the accounts | Does it | Spot checks, if you want them |
| Chasing a missed payment | Sends the follow-up | Steps in when someone needs a person |
| Anything that doesn’t fit your rules | Flags it and waits | Gives the OK |
| Paying, refunding or deleting anything | Never on its own | Decides |
Access is yours
You grant the access, and you can take it away.
Plain questions
When it’s unsure it asks a plain question where your team already talks. It doesn’t bury it in a report.
We’ll say no
If a bot can’t learn the job, we’ll say so.
Jobs it already does.
Each of these runs in one of our own businesses today, inside tools such as Xero and Stripe. We list a job only once we’ve done it ourselves.
-
Payment collection setup
Builds each customer’s payment record and schedule from your agreements, so payments come in on the right day without anyone keying them in.
Asks when an agreement and a record disagree, or something is missing.
-
Reconciliation
Matches payments to your accounts and lines them up, so the books agree with the bank without a person going line by line.
Asks when a payment matches nothing, or could match two things.
-
Payment follow-up
Checks that each payment has landed. When one hasn’t, it follows up.
Asks when someone needs a person, not another reminder.
-
Inbox handling
Reads the shared inbox and picks out what matters: payments, changes, questions. It acts on the routine items and brings you the rest.
Asks when a message needs a decision that is yours to make.
We ran it on our own business first.
Setting up rent collection for 150 tenants, with the payment platform and accounts configured and reconciled
Weekly reconciliation, checking payments have landed, and chasing the ones that have not
Measured in one of our own businesses in 2026: one person and one bot. This is not a client result, and yours will depend on the job.
Request a briefing.
Tell us the job and who owns it. We’ll come back to you to set up a sit-down with your team.
- You tell us the job.
- We sit down with your team and map it.
- We quote the setup.
- We build the bot and hand it over.