Let the paperwork move itself.
Approvals, documents, payment matching and follow-ups that run on their own, built around the way your team already works. Requests reach the right person on their phone, nothing waits in an inbox, and every step is logged.
Good for Finance teams · Operations · HR and admin · Procurement · Branch networks
Hours back, every week.
We map the processes that eat your team's time, then automate them in the tools you already use or in a system we build. Every step is logged, so you see who did what and when.
Approvals on the phone
LPOs, leave and expense claims reach the right approver and are signed off in a tap.
Documents that fill themselves
Contracts, quotes and letters filled from your data, on your letterhead, ready to sign.
Payments matched daily
M-Pesa and bank statements matched to invoices, so finance only handles the exceptions.
Follow-ups that never slip
Reminders for invoices, renewals and tasks, sent on time by SMS, email or WhatsApp.
Your tools, connected
Forms, sheets, your CRM, accounts and WhatsApp share data instead of being retyped.
Every step logged
A full trail of who requested, approved and changed what, ready for your auditors.
Seven workflows we automate most.
Click through the workflows we build most often. Each runs in your current tools or a system we build, sends people only the steps that need them, and logs the rest.
- Workflows
- Automation
- waiting 3 hrs1
- new2
No records match.
New dashboard
No records match.
Purchase order · Ruiru yard · Step 2 of 2, waiting 3 hours
- Supplier
- Ndegwa Cement Agencies
- Items
- 410 bags of cement, 50 kg, at KES 450
- Amount
- KES 184,500 incl. VAT
- Budget left
- KES 1.2M of KES 3M for October
- Chain
- Yard manager, then finance
- Approved so far
- Paul Gitau, yard manager, 07:41
- Quote
- Q-NDC-2219.pdf attached
- Reminder sent to Grace Mwikali on WhatsApp
- Approved by Paul Gitau, yard manager, and passed to finance
- Budget check: KES 1.2M left for October
- Raised by Peter Njoroge with the supplier's quote attached
New request
- awaiting signature2
- signed2
- sent1
- queued1
- draft1
No records match.
Trade credit v3 · Rongai Hardware · Sent 5 Oct, 15:20
- Customer
- Rongai Hardware Ltd, PIN P052 *** 61K
- Credit limit
- KES 750,000 on 30 days
- Signers
- Francis Kimani, director, and Grace Mwikali
- Filled from
- Customer record and credit approval CR-118
- Sent by
- Email and WhatsApp, link valid 14 days
- Signed so far
- Grace Mwikali, 5 Oct at 15:21
- Reminder sent to Francis Kimani on WhatsApp
- Signed by Grace Mwikali for Tujenge
- Made from Trade credit v3 and sent for signature
- Credit approval CR-118 approved by Joseph Mutua
New document
- to review1
- matched3
- sent to finance1
- part paid1
- credit held1
No records match.
M-Pesa paybill · Tue 6 Oct, 09:47 · No account reference
- Payer
- Samuel Otieno, 0722 *** 115
- Amount
- KES 1,950
- Account entered
- Blank
- Best guess
- INV-8829 for KES 1,950, same name
- Why not automatic
- No reference, two open invoices fit
- Paybill
- 5 *** 21, Ruiru
- SMS sent to Samuel Otieno asking for the invoice number
- Two open invoices fit the amount, so it waits for a person
- Payment received on the paybill with no account number
- INV-8829 issued to Samuel Otieno for KES 1,950
Match payment
No records match.
Payment reminder · WhatsApp · Read at 09:12
- Customer
- Rongai Hardware Ltd, Francis Kimani
- Invoice
- INV-8790, KES 286,000, due 10 Oct
- Paid so far
- KES 150,000 on 6 Oct by M-Pesa
- Balance
- KES 136,000
- Next reminder
- Sat 10 Oct, 09:00, on the due date
- Template
- Due in 4 days, with statement
- Read by Francis Kimani on WhatsApp
- Reminder sent with the statement and paybill details
- Part payment of KES 150,000 matched to INV-8790
- INV-8790 issued on 30 days
New reminder
Each tile is one connection, checked every 5 minutes. Red tiles have stopped and are retrying.
No records match.
Zoho Books · Out to Zoho · Last good run 5 Oct, 18:00
- What it does
- Approved supplier bills posted to Zoho
- Schedule
- Every hour, 06:00 to 20:00
- Failed at
- 6 Oct, 06:00: login expired
- Waiting to send
- 14 bills, KES 1.86M
- Retries
- Every hour, alert after 2 failures
- Alert sent to
- Grace Mwikali and the IT desk
- Retry failed: login expired. 14 bills waiting
- Alert sent to Grace Mwikali after 2 failed runs
- Run failed: Zoho Books refused the saved login
- Run passed: 9 bills posted
New connection
- failed1
- done4
- running1
- retrying1
No records match.
Post supplier bills · Hourly · Failed at step 2 of 4
- Started
- 6 Oct, 10:00:02
- Trigger
- Hourly schedule
- Step 1
- Collect approved bills: 14 found
- Step 2
- Sign in to Zoho Books: login expired
- Steps 3 and 4
- Not run: post bills, mark as sent
- Next try
- 11:00, alert already sent
- Step 2 failed: Zoho Books refused the saved login
- Step 1 done: 14 approved bills collected
- Owner alerted after the second failure
- Last good run: 9 bills posted
Run now
- over target1
- on target4
- watch2
No records match.
Customer refunds · Target 2 days · Last 30 days
- Requests
- 38, KES 1.12M in total
- Cycle time
- 4.8 days on average
- Target
- 2 days
- Slowest step
- Director sign-off, 3.1 days
- Before automation
- 9 days, June 2026
- Owner
- Daniel Ochieng, credit control
- Over target for the third week running
- Weekly summary sent: refunds at 4.8 days
- Weekly summary sent: refunds at 4.5 days
- Target set at 2 days by Grace Mwikali
New process
Dashboard
Requests waiting, payments matched, runs that failed and hours saved across every workflow: what Grace checks first each morning.
Approvals
Requests, LPOs, leave and expenses routed through your approval chain.
- Approval chains by amount and departmentLPOs under KES 50,000 need a manager, larger ones finance too, and above KES 500,000 a director.
- Approve from a phone, email or WhatsAppApprovers get the request with its quote attached and approve or reject in one tap.
- Reminders when a request sits too longA request waiting over 3 hours gets a reminder, then moves to the approver's deputy.
- Full trail of who approved whatEvery step, comment and attachment is logged with the time and the person.
- Deputies for leave and travelApprovers name a deputy for the days they are away.
- Budget check before approvalEach request shows what is left in the department's budget for the month.
- Leave and claims in the same flowLeave, expense claims, petty cash and refunds use the same approval rules.
- Approved LPOs sent to the supplierOnce approved, the LPO goes to the supplier as a PDF without anyone retyping it.
- Send back with a reasonA rejected request returns to the person who raised it, who can fix it and resend.
Document generation
Contracts, quotes and letters filled from templates and sent for signature.
- Templates on your letterheadQuotes, offer letters, credit agreements and demand letters with your logo and wording.
- Fields filled from your systemNames, amounts, dates and KRA PINs pulled from the customer or staff record.
- E-signature and PDF in one stepSent for signature by link, signed on a phone, and saved as a PDF.
- Filed against the right customerEach signed document is stored on the customer or staff record.
- Clause libraryApproved clauses for credit terms, delivery and warranty dropped into any template.
- Template versionsEvery edit to a template is logged, and old documents keep the version they used.
- Sent by email or WhatsAppThe document goes out with a short message on the channel the customer reads.
- Reminders to signUnsigned documents get a reminder after two days and a call task after five.
Payment reconciliation
M-Pesa and bank statements matched to invoices, leaving only the odd ones.
- M-Pesa paybill and till paymentsPaybill and till payments pulled through M-Pesa Daraja as they arrive.
- Bank statements imported dailyStatements imported each morning, from a file or a bank feed where the bank offers one.
- Matched by reference, amount and nameAccount number, invoice number, amount and payer name checked against open invoices.
- Only the exceptions left for financePayments with no reference or the wrong amount wait in a short list for a person.
- Part and over paymentsPart payments reduce the balance, and overpayments are held as credit on the account.
- One payment, several invoicesA transfer that covers three invoices is split across them, oldest first.
- Receipts sent at onceA receipt goes to the customer by SMS or WhatsApp as soon as the payment is matched.
- Posted to your accountsMatched payments are posted to the ledger, so the bank balance and debtors agree.
- Rules you can addWhen a director pays for their company, match it once and the system remembers.
Reminders & follow-ups
Invoices, renewals and tasks chased on time, by SMS, email or WhatsApp.
- Payment reminders before and after dueA polite note 3 days before the due date, then on the day, then 7 days after.
- Renewals, licences and contract datesVehicle insurance, county business permits and supply contracts tracked with their dates.
- Tasks escalated when they slipAn overdue task goes to the owner's manager after the time you set.
- Sent by SMS, email or WhatsAppEach customer gets reminders on the channel they read, with the paybill details.
- Statement with the reminderThe customer's statement goes with the reminder, so there is no back and forth.
- Stops when paidA payment matched in reconciliation stops the next reminder at once.
- Quiet hours and holidaysNothing goes out at night, on Sundays or on public holidays.
- Read receiptsSee which reminders were delivered and read on WhatsApp.
Integrations
Forms, sheets, your CRM and WhatsApp passing data without copy and paste.
- Web and Google forms into your systemQuote requests and credit applications land as records, not emails to retype.
- Google Sheets and Excel kept in syncBranch sheets keep working, and their rows sync both ways with the system.
- CRM, accounting and HR tools connectedCustomers, invoices and staff kept the same in each tool.
- WhatsApp Business messages loggedMessages from the WhatsApp Business API saved on the customer's record.
- M-Pesa and bank feedsPaybill and till payments from Daraja and bank statement files brought in for matching.
- KRA eTIMS invoicesSales invoices submitted to eTIMS, with the details KRA returns saved on each one.
- Retries and alertsA failed sync retries on its own and alerts a person if it keeps failing.
- Webhooks and APIsAny tool with an API or webhooks can send or receive data.
Runs log
Every automated run with its trigger, steps and result, so a failure is seen and fixed fast.
- Every run recordedEach workflow run is logged with what started it, each step and the result.
- Failed steps in plain wordsA failed step shows the error in plain words and the record it was working on.
- Retry from the failed stepFix the cause and rerun from where it stopped, without repeating the steps that worked.
- Alerts on repeat failuresTwo failures in a row send an alert to the workflow's owner.
- Search by recordFind every run that touched an invoice, a customer or a request.
- Run times trackedA workflow that is getting slower stands out before anyone notices.
- Kept for auditRun history kept for 12 months, ready for your auditors.
- Manual runsStart a workflow by hand when you need it outside its schedule.
Process dashboard
Cycle times and bottlenecks for every process, so you fix the slow step.
- Cycle time for each processHow long each LPO, claim, refund and leave request takes from start to finish.
- Where requests wait the longestThe step and the person where work sits, for each process.
- Volumes by team and branchHow many requests each branch and team raises and approves each week.
- Weekly summary in your inboxA Monday email with cycle times, slow steps and hours saved.
- Targets per processSet a target time and see at a glance which processes are over it.
- Hours savedTime saved, estimated from the steps no longer done by hand.
- Before and afterCycle times from before automation kept, so you see the change.
- Drill into any processClick a slow process to see the requests that made it slow.
Custom built, not off the shelf. Every system we build is made to fit the client's needs: the modules, screens, wording and reports follow how your organisation works. The business, names and figures in this demo are examples.
Automate your first process.
- A fixed-scope plan and price within 24 hours
- Live in 21 working days, then hosted and supported by us
- Built around how you work, not squeezed into a template
Your answers go straight to the people who build it.
Approved from a phone, in minutes.
Requests, LPOs, leave and expenses routed through your approval chain.
- Approval chains by amount and department
- Approve from a phone, email or WhatsApp
- Reminders when a request sits too long
Statements matched automatically.
M-Pesa and bank statements matched to invoices, leaving only the odd ones.
- M-Pesa paybill and till payments
- Bank statements imported daily
- Matched by reference, amount and name
Contracts and quotes write themselves.
Contracts, quotes and letters filled from templates and sent for signature.
- Templates on your letterhead
- Fields filled from your system
- E-signature and PDF in one step
Automation at work.
Timeless Timber runs its production stages, stock and dispatch on a system we built and host, with procurement, finance and HR being added to it. Leave and payroll run on JamboHR and sales follow-ups on Pinch CRM, both our own products.
First workflow live in 21 working days.
- 01Days 1 to 3
Map the process
We follow one process end to end, count the hand-offs and agree what to automate first.
- 02Days 4 to 6
Design the flow
Steps, approvers, templates and rules agreed with you, including what happens when someone is away.
- 03Days 7 to 21
Build and test
Built on your tools or ours and tested with real requests, payments and documents.
- 04Then
Measure and add more
The dashboard shows time saved and slow steps. We tune it, then automate the next process.
Tools we use Laravel · n8n · Make · Zapier · Google Workspace · Microsoft 365 · M-Pesa Daraja · WhatsApp Business API · Webhooks
Before you ask.
Which processes should we automate first?
The ones that happen often, follow clear rules and keep someone retyping or chasing. Approvals, invoices, payment matching and reminders are the usual start. We look at volume and time spent, then agree a shortlist with you.
Do we need a new system?
Not always. Many workflows run on tools you already have, such as Google Workspace, Microsoft 365, your accounting package and WhatsApp. Where those cannot do the job, we build the missing piece in Laravel and host it for you.
Can it match M-Pesa and bank payments?
Yes. We pull paybill and till payments through M-Pesa Daraja, import your bank statements, match each payment to an invoice by reference, amount and name, and leave only the unclear ones for your finance team.
What happens when an approver is away?
You set a deputy or a time limit. A request that waits too long gets a reminder, then moves up the chain, and every step is logged with who acted and when.
What does automation cost?
It depends on the processes and the tools involved. After a free scoping call you get a fixed-scope proposal in writing, so you know the price before we start.
Let's automate your busiest process.
A free scoping call, then a fixed-scope proposal in writing.
