Four tools. Real problems, solved.
Invoice Consolidation Tool
Importers filing IDFs on KRA's iCMS system often deal with invoices containing hundreds of line items — many of them near-duplicates (same product, different color or minor variation). This increases the risk of mismatches, rejections, and slow manual review.
This tool takes a commercial invoice (PDF, Excel, or CSV) and automatically consolidates it down to under 99 line items, as required for iCMS filing. It groups items by HS code, description, origin, and unit of measure — so items like "Hose Pipe Blue" and "Hose Pipe Yellow" become "Hose Pipes ×2," while keeping genuinely distinct items separate.
Every consolidation is checked against the original invoice to guarantee the totals match exactly — nothing is lost or altered in value, only grouped. The result is a clean, compliant, audit-ready invoice, ready for IDF filing, cutting manual prep time and reducing rejection risk.
Want to try this on your own invoices?
Book a callFrequently asked questions
What file types are supported?
PDF, Excel (.xlsx), and CSV — the formats most commercial invoices already arrive in.
Is my data stored or shared?
Your documents are processed to generate the consolidated output and are not shared with third parties. Ask on your call for full details on retention for your setup.
What compliance standards does this meet?
Output is structured to meet KRA iCMS/IDF line-item requirements — under 99 lines, grouped by HS code, description, origin, and unit of measure.
How long does processing take?
Most invoices are consolidated within minutes, depending on file size and line-item count.
Product screenshots
Sheetsync
Many business owners track M-Pesa spending manually — going through SMS messages one by one to log expenses. Sheetsync automates this.
The app reads incoming M-Pesa messages, automatically extracts the amount, recipient, transaction type, and time, and organizes them into categories (fuel, supplies, utilities, etc.) based on recipient name keywords. Users can manually override the category on any transaction, and overrides sync back immediately.
Every transaction syncs automatically to the user's own Smartsheet — no manual data entry. The result is a live, organized record of business spending that updates itself.
Want to try this on your own expenses?
Book a callFrequently asked questions
Which SMS formats are read?
Standard Safaricom M-Pesa transaction messages — sent, received, paybill, and till payments.
How are categories set or overridden?
Categories are auto-assigned from recipient name keywords. Any transaction can be manually recategorized, and the change is saved immediately.
Is Smartsheet setup required?
Yes — Sheetsync syncs directly into your existing Smartsheet, so a Smartsheet account is required.
How is data privacy handled?
Transaction data is used only to populate your Smartsheet and isn't shared with third parties.
Product screenshots
selfie.ke — Loyalty Points Automation
selfie.ke ran two offline systems at the till: Microsoft Dynamics RMS 2005 for payment and receipts, and Hero Points v3.6.1.0, a legacy add-on with no API and no way to talk to anything external — not WhatsApp, not a spreadsheet, not a phone. The client wasn't willing to touch Dynamics itself, so loyalty tracking was stuck: no automated reward notifications, no audit trail, and roughly 9,500 existing customers' point balances sitting in a system with no export path anyone had actually tested.
We built an internal Django app used by till staff alongside Dynamics — never integrated with it. Staff search for a customer, enter the sale amount, and points are calculated and added automatically, with no field anywhere letting a person type a points value directly. Crossing a reward tier triggers an on-screen celebration and queues a same-evening WhatsApp notification via Meta's Business Cloud API, and marking a gift collected fires a second confirmation automatically.
Points are structurally un-editable — a Postgres trigger rejects any write outside the two functions that calculate them, and a second trigger blocks reversing a collected reward. Migration was validate-then-import, never a blind load: a dry-run report caught dirty data before a single row was written, and historic balances were deliberately not retroactively rewarded, the decision that avoided roughly 1,626 gifts being owed on day one. The result: ~9,500 customers migrated with zero incorrect payouts, and a full audit trail where none existed before.
Want to try this on your own loyalty program?
Book a callFrequently asked questions
What does it integrate with?
WhatsApp Business Cloud API, direct via Meta — no BSP middleman. It doesn't integrate with Dynamics RMS at runtime; that system is untouchable, aside from a one-time, human-reviewed export used for the initial migration.
Is my data stored or shared?
Customer data lives in self-hosted PostgreSQL on a VPS the client controls — no third-party SaaS holds the list, and it's never shared with third parties.
What compliance or security standards does it meet?
WhatsApp messages go out under Meta's stricter Utility category, not Marketing. The app enforces HTTPS with HSTS, a CSP header, and login rate-limiting on top of CAPTCHA-protected admin access.
What does the client need in place before go-live?
A Meta WhatsApp Business Manager account with approved message templates, and a cleaned customer export from Dynamics completed before staff start using the till for real.
Product screenshots
Elimu Masters Hub — WhatsApp Lead Nurture
Elimu Masters Hub runs a business training platform built around the ILO's Start and Improve Your Business (SIYB) program. Registrants were constantly messaging the team on WhatsApp with questions, more than a small team could keep up with, and every message left unanswered hurt the brand.
We built a lead-nurture funnel on Meta's WhatsApp Cloud API, orchestrated in n8n, that responds the moment someone registers. They receive a branded registration confirmation with two buttons: Join Community and Invite a Friend. Tapping Invite a Friend returns a ready-to-forward webinar invite card with the sign-up link, so referring someone takes a single forward.
Tapping Join Community sends the WhatsApp group invite link automatically, and reminders follow within a couple of hours to nudge registrants into the community and their training. Every registrant is taken through confirm, refer, and join on their own, so they get a response straight away instead of waiting on a reply, and the team isn't answering the same questions by hand.
Want to try this on your own lead follow-up?
Book a callFrequently asked questions
What does it integrate with?
Meta's WhatsApp Cloud API directly — no BSP middleman — with the message flow orchestrated in n8n. New leads come in from the client's landing-page registration form, and every message, button reply, and invite link is handled automatically from there.
Do registrants need to install anything?
No. Everything happens inside WhatsApp, which registrants already use. They tap a reply button — Join Community or Invite a Friend — and the next message arrives automatically. There's no app to download and no account to create.
Is lead data stored or shared?
Lead names and WhatsApp numbers are kept only to run the follow-up sequence, and aren't shared with third parties beyond Meta's WhatsApp platform, which delivers the messages. Ask on your call for details on storage and retention for your setup.
What does the client need in place before go-live?
A Meta WhatsApp Business account with a registered number and approved message templates, plus a registration form that collects each lead's WhatsApp number along with their consent to be messaged.