Adoption is what pays you back.
Buying the system is the easy part. Four packaged services close the gap between a signed order and a business that actually runs on it.
Huchu MineThe Gate ShopsLux LiquorWhy rollouts fail. Every time, the same three.
You should know what happens, week by week.
- Week 1
We follow the real work
We walk the counter, the store room and the office, and map what actually happens — including the exceptions everyone works around. Not the org chart.
- Week 2
The workspace is configured
Products, prices, sites, roles and approval limits are set up against your operation, so what your team sees on day one is their business, not a demo.
Who may see what · The Gate Shops41 people, 6 rolesFind a person or a roleMsasa storeAdd a roleRolePeopleSitesSees takingsMay discountMay voidSees payrollCashier22Own tillOwn shiftUp to 5%Before closeNoSupervisor8Own siteOwn siteUp to 15%Any, with a reasonNoSite manager6Own siteOwn siteAnyAnyOwn siteRegional3Own regionOwn regionAnyAnyOwn regionHead office2All twelveAll twelveSets the ceilingAnyAll twelveAuditor1All twelveRead onlyNoNoRead onlyWhat the grid is doing- Shared loginsA person is a person; a till is a till0None
- Rights follow the personInto every module they open, unchangedOne set
- A cashier at MsasaSees their own shift, at their own till, todayScoped
- Week 3
Your data is moved and reconciled
Opening stock, customer balances and supplier accounts come across, then get checked against your existing totals until they agree.
Trial migration · rehearsal 3 of 3Agreed to the centRecords moved84,112From 4 sourcesDifferences left0Was 214 at rehearsal 1Cutover decisionGoMade on this tableRehearsal 3Rehearsal 2Rehearsal 1What movedSourceYour totalOursDifferenceChecked byOpening stockStock sheetUS$184,206.40184,206.40US$0.00Farai D.Customer balancesLedgerUS$21,447.0021,447.00US$0.00Tendai M.Supplier accountsLedgerUS$38,190.2038,190.20US$0.00Tendai M.EmployeesPayroll bureau14140Chipo S.Item costsStock sheet4,1184,1162Farai D. — two discontinued lines, agreed to dropReconciled against your figures, not ours, and rehearsed three times. Nothing cuts over on a difference nobody has explained.
- Week 4
We test the difficult day
The month-end, the outage, the returned order, the disputed payment. If the system only survives the demo path, it will not survive your Friday.
Till 2 · Msasa storeOffline 41 minutesNetwork down. The counter did not stop.13:04 – 13:45Sales are written to the terminal and replayed in the order they were taken. Receipts print with their real numbers throughout, so nothing is renumbered afterwards.
Retry nowReplayed when it came back9 sales · US$214.60 · in orderSaleTakenTenderTotalSyncedState#1023813:06CashUS$34.2513:45:02Posted#1023913:11EcoCashUS$9.8013:45:02Posted#1024013:19CashUS$7.4513:45:03Posted#1024113:34CardUS$61.1013:45:03Posted#1024213:45CashUS$102.0013:45:04Posted#1024313:41CardUS$18.80—Flagged for a personAnything the replay cannot settle by itself is flagged rather than guessed at. One sale out of nine is a question, not a silent correction.
- Week 5
Champions are trained first
The people closest to the work learn it before everyone else, so on go-live day the person beside you already knows the answer.
Onboarding · The Gate ShopsWeek 3 of 6Booked, with names against itSix weeks, twelve sitesSeptember 2026PreventativeBreakdownMTWTFSS1Walk the floor2Configure3Migrate45678Reconcile910Hard day test1112131415Champions16171819202122Go live23On the floor24On the floor252627282930Who is on it+
Tanaka MoyoLead · on site weeks 1, 5 and 6Named
Farai DubeData · weeks 3 and 4Named- Your championsTrained in week 5, before everyone else4Yours
- Week 6
Go live, with us on the floor
We are on site for the first trading days, because the questions that matter only appear with real customers in the queue.
Support · AugustMedian first reply 22 minutesFind a conversation or a siteAugustOpen a conversationRaisedSiteWhat it wasAnswered byFirst replyClosed3 Sep 08:12Msasa storeFiscal device not signingTanaka M.4 min31 min2 Sep 16:40Mutare depotStock take variance queryFarai D.18 min2 h2 Sep 09:03MachipisaNew cashier, wrong tillChipo S.9 min14 min1 Sep 14:22Gweru counterPrinter roll and settingsTanaka M.26 min48 min29 Aug 11:07Head officeReport definition questionFarai D.1 h 121 dayWhat the plan you are on gets- StartLocal support, in your working hoursIncluded
- GrowPriority queue, same local teamIncluded
- ScaleA named success lead who knows your sitesIncluded
- EnterpriseResponse and resolution written into the agreementContracted
Your data, reconciled against your own totals. Before anyone cuts over.
Reconciled against your figures, not ours, and rehearsed three times. Nothing cuts over on a difference nobody has explained.
Four services, each with a fixed scope.
- Tanaka MoyoLead · on site weeks 1, 5 and 6Named
- Farai DubeData · weeks 3 and 4Named
- Your championsTrained in week 5, before everyone else4Yours
Process workshop, configuration, champion training and go-live support, sequenced over about six weeks.
Reconciled against your figures, not ours, and rehearsed three times. Nothing cuts over on a difference nobody has explained.
Source assessment, mapping, a trial migration you check yourself, and reconciliation against your own totals before cutover.
- Sites and yardsThe twelve Multi-site already holdsReused
- Roles and approval limitsA weigh over tolerance needs the same second nameReused
- SuppliersThe ones Books already invoicesReused
- Its own user listIt does not have one0None
- Platform releases since June7
- That this extension sat out0
- Bespoke work now unsupported0
Custom workflow on the Corelith foundation — using your existing sites, roles and approval limits, posting to the same ledger, upgrading on the same release.
- StartLocal support, in your working hoursIncluded
- GrowPriority queue, same local teamIncluded
- ScaleA named success lead who knows your sitesIncluded
- EnterpriseResponse and resolution written into the agreementContracted
Included in every plan; priority local support on Grow, a named success lead on Scale, contracted service levels on enterprise agreements.
Live in six weeks.Nothing surprising at cutover.
Five stages, all of them visible
Scope, migration, configuration, training, cutover. At any point you can say which one you are in and what is left.
Balances agreed before you trade on them
Your accountant signs off the opening figures. Nobody discovers a discrepancy in the second month.
The people who built it
On WhatsApp, in your working hours, from Harare, during the rollout and every month after it.
Custom, without the dead end. Corelith Build.
A Build extension is not a second system. It starts from what your Corelith already knows about your operation.
Whatever it does, the money lands in the same place — so it never becomes a number somebody has to reconcile by hand.
Most custom software becomes an orphan: unsupported, unupgradable, disconnected. This one moves with the product.
Before you ask.
Guided onboarding is quoted with your plan. Larger migration, multi-site, edition, integration and custom rollout work is scoped separately — and priced in writing — before you commit.
Yes. We assess what your source data is really worth, agree what comes across, run a trial migration you check yourself, and reconcile against your own totals before cutover.
When it is valuable, repeatable, and belongs on the Corelith foundation, Corelith Build extends the platform. We will not build you a disconnected side system — that is the problem we exist to remove.
Every plan includes support. Grow adds priority local support, Scale adds a named success lead, and enterprise service levels are contracted to the obligations your organisation carries.
A rollout you can see the shape of.
We walk through what your launch actually involves, week by week. The scope and the price come back in writing, and the weeks are the ones we publish.