PRODUCTS · BUILT IN HARARE
Four products. Each one replaces a job you are currently doing by hand.
Two enterprise systems and two AI assistants. Below is what each one is for, what it costs, what it connects to here, and how long it takes to get running — so you can rule three of them out quickly.
Free 20-minute call. We will tell you honestly if we are not the right fit.
- Operating since
- 2021
- Projects delivered
- 40+
- Sectors served
- 9
- Average website delivery
- 14 days
No client logos here yet. Two clients are finalising written permission to be named, and until then the numbers on these pages are real and the names are not.
FIND YOUR ROUTE
Start from what is actually going wrong.
Product names are our problem, not yours. Find the sentence you have said out loud in the last month.
- “Nobody can tell me what we made last month.”CheckERP
- “We find out about fee arrears when the term has ended.”ASOFT ERP
- “Enquiries sit unanswered until somebody opens the phone in the morning.”Augustus AI
- “Four people are the only ones who know how anything works here.”Asolen AI
- “We have systems. They do not fit any more.”Custom software
THE FOUR PRODUCTS
What each one is for.
One line on the job it does, one line on what changes, and the price it starts at.
COMPARE
Side by side.
The rows people actually ask about, including the two at the bottom that most vendors leave off a comparison page.
| Product | CheckERPBusiness ERP | ASOFT ERPSchool management | Augustus AIWhatsApp sales AI | Asolen AIPrivate assistant |
|---|---|---|---|---|
| What it is for | ||||
| Who uses it daily | The finance office, stores and sales | The bursary, the office and teaching staff | Whoever answers the sales line | Everybody who asks a procedural question |
| What it replaces | Spreadsheets and a desktop accounting package | Registers, fee books and a spreadsheet | A voicemail and a reply the next morning | Asking the one person who knows |
| How it is bought | Demo, then a scoped implementation | Demo, then a scoped implementation | 14-day free trial, then monthly | 14-day free trial, then monthly |
| Money | ||||
| From | $180/month | $140/month | $60/month | $90/month |
| What moves the price | Named users, modules, migration | Pupils, campuses, modules | Conversations, numbers, catalogue | Seats, documents, questions |
| Free trial | No — a demo on your own figures | No — a demo on your own term | Yes, 14 days, no card | Yes, 14 days, no card |
| Implementation fee | Quoted after scoping | Quoted after scoping | None | None |
| Zimbabwe | ||||
| ZIMRA | Fiscalised invoicing and VAT returns | Fiscalised fee receipts where the school is registered | Not applicable | Indexes circulars you supply, quotes them, does not interpret them |
| Mobile money | EcoCash, OneMoney and ZIPIT reconciliation | Fee payment and reconciliation | Paynow payment links inside the conversation | Answers questions about references from indexed statements |
| USD and ZWG | Both in the same ledger, rate stored per transaction | Both on the same fee account | Quotes in either | Quotes whatever your documents say |
| Statements, invoices and reminders | Parent messaging and attendance alerts | The whole product | Staff ask from WhatsApp | |
| Slow connection | Text-first screens, queued fiscalisation | Registers capture offline, SMS fallback | Runs on Meta’s side, so the customer never waits on you | Text answers, no dashboard to load |
| Getting it running | ||||
| Typical time to live | 6 to 10 weeks | 4 to 8 weeks | 5 working days | 10 working days |
| What we need first | Your last signed accounts | Pupil list and fee structure | Price list and WhatsApp number | Documents and a role table |
| Training included | Yes, in your office, on your own data | Yes, per department, around your timetable | Yes, one hour per role | Yes, one hour per department |
| If you leave | ||||
| Getting your data out | Excel and CSV on every register | Excel and CSV on every list | Full transcript export | Documents and full question log |
| What stays yours | Your ledger, your customers, your history | Your pupil records and fee history | Your WhatsApp number and every transcript | Every document you indexed, and the question log |
You keep your data and your licences per the contract. No hostage-taking.
IN EVERY PRODUCT
What all four have in common.
These are not features. They are the reasons a system built here works here, and the reasons a system built somewhere else usually does not.
Local rails, not a roadmap
Working on the day you go live, not promised for a later release
- Paynow
- EcoCash, OneMoney, InnBucks, ZIPIT and local card through one integration, with the out-of-band confirmation gap handled properly.
- USD and ZWG
- Both currencies together, with the rate stored against the transaction so history does not move when the rate does.
- ZIMRA, where it applies
- Fiscalisation, VAT returns, PAYE and NSSA in the products that touch them, updated when the requirements change.
- Local bank statement formats
- CSV, Excel, OFX, MT940, and PDF where that is all a bank will give you.
Built for the connection you actually have
Tested on Econet mobile data on a mid-tier Android handset
- Text and numbers first
- No screen in any of the four waits on a chart library before a clerk can do their job.
- Queue and forward
- When the line drops, work is held and sent when it returns — visibly, so nobody has to wonder whether it went.
- Usable on a phone
- Approvals, lookups, registers and questions all work on the handset your staff already own.
Your data is yours
Stated here so you can hold us to it
- Export at any time
- Excel or CSV, on every register and every list, without asking us first.
- No hostage-taking
- You keep your data and your licences per the contract. No hostage-taking.
- Deletion on request
- A written request removes your data on an agreed schedule, and we confirm when it is done.
- Backups that have been restored
- Daily backups, and a restore actually performed into a scratch environment rather than a backup job that has never been tested.
Access enforced in the database
Not permission checks bolted onto the screens
- Row-level security in Postgres
- A user cannot reach a figure by editing a URL, and an AI assistant cannot be talked into one. The database is the boundary, not the prompt.
- Audit rows on every change
- Who, when, and what it was before. On postings, approvals, marks, prices and access grants.
- A person in Harare
- Harare-based. When something breaks, someone comes. A named contact, reachable on WhatsApp.
TOGETHER
How they fit together.
Most clients start with one. The reason to buy the second from the same company is that we do the joining, and nobody has to retype anything in the middle.
CheckERP + Augustus AI
Augustus reads live stock and prices out of CheckERP, so the price a customer is quoted on WhatsApp at nine at night is the price your stores manager sees at nine in the morning. The order it takes arrives as an invoice rather than as a note somebody has to retype.
ASOFT ERP + Augustus AI
The school enquiry line answers term dates, fee structures and enrolment questions without the office picking up. Anything about a named pupil goes straight to a person, because it should.
Either ERP + Asolen AI
Asolen answers the procedural questions an ERP cannot: who signs this off, what the credit limit rule is, which version of the policy is current, and whether this supplier is approved.
All three together
A customer asks on WhatsApp. Augustus answers from the ERP. The order becomes an invoice. The staff member handling the exception asks Asolen what the rule is, and gets the paragraph. That is the whole argument for buying them from one company in one city.
QUESTIONS
Choosing between them.
Which one should we start with?
The one that fixes the thing costing you most this month. If you cannot close a month-end, start with CheckERP. If enquiries are going unanswered, start with Augustus — it is the cheapest and the fastest to prove. Schools should start with fees and attendance in ASOFT ERP and add the rest by term.
Can we run more than one at the same time?
Yes, and they are built to be joined rather than merely coexist. Augustus reads stock and prices out of CheckERP or ASOFT ERP, and Asolen answers from both alongside your documents. We do the joining as part of the second implementation, not as a separate project.
Do we have to move everything at once?
Yes. Most clients start with one module or one site and add from there.
Where is our data stored?
On managed Postgres infrastructure with daily backups, and we will tell you the exact region in writing before you sign. You can export everything at any time, in a standard format.
What if none of these fit?
Then say so early and we will tell you honestly. Some processes are specific enough that a package is the wrong answer, and that is what custom software is for. It starts with understanding the process, not with choosing a technology.
What happens if we stop working with you?
You keep your data and your licences per the contract. No hostage-taking.
Do you work outside Harare?
Yes. Remote implementation across Zimbabwe, on-site training by arrangement.
NEXT STEP
Not sure which one? Tell us what is slowing you down.
Twenty minutes on a call. We will tell you what we would build, what it would cost, and whether it is worth doing.
No obligation. No sales script.