When “almost right” becomes expensive.
At group scale, a system that almost fits shows up everywhere: branches that cannot be compared, controls that live in memos, and a consolidation that takes a fortnight every month.
Huchu MineThe Gate ShopsLux LiquorA group is not a longer list of users. Most software prices it as one.
Every branch. Same definitions. Same morning.
- Today
- Sell
- Stock6
- Customers
- People
- Pay
- Books
- Sites12
- Compliance
“Basket” means the same thing in Bulawayo as in Msasa, because both come off the same entries rather than off two spreadsheets with two definitions.
Six things a subscription can't give you.
- Entities summedUS$18,412.00
- Board figureUS$18,412.00
- Consolidation adjustmentUS$0.00
Companies, branches, warehouses and departments on the reporting lines your board actually uses — so a consolidation is a way of reading the entries, not a project.
Companies, branches, warehouses and departments modelled with the reporting lines your board actually uses — so consolidation is a view, not a month-end project.
- Raiser and approverCannot be the same person on any thresholdBlocked
- Controls bypassed this monthThere is no path that bypasses one0None
- Held for approval right nowOne payout, one write-off2Waiting
Approval thresholds, segregation of duties, evidence requirements and immutable history configured to your obligations — enforced by software, not by memo.
- BackupsTaken, and restored in a rehearsal you attendIncluded
- MonitoringWith a named engineer on the other endIncluded
- Offline continuityOn every environment and every planIncluded
- A different product on privateIt is the same release, on your metalNo
Corelith cloud by default; dedicated or private deployment where your regulator, board or risk profile requires it.
Every row names one owner. A record with two owners is what turns an integration into a reconciliation, so the design does not allow one.
Banking, fiscal devices, identity and legacy systems connected with clear ownership: which system owns each record, what moves live, what exports on schedule.
Reconciled against your figures, not ours, and rehearsed three times. Nothing cuts over on a difference nobody has explained.
Your data cleaned, mapped, reconciled and rehearsed before cutover — with the go/no-go decision made on evidence, not hope.
Tanaka MoyoNamed success lead · HarareYours- Severity 1, out of hoursAn on-call engineer, not a ticket queue24/7
- Calls that reached a call centreThere isn't one0None
Response and resolution commitments written into the agreement, against the obligations your organisation actually carries.
Match the environment to the obligation.
Managed platform, updates, backups and monitoring — the fastest path to live, and the right answer for most groups.
Default recommendationAn isolated deployment with environment-level controls scoped to your organisation.
Enterprise optionFor organisations whose regulator or infrastructure constraints require the platform inside their own boundary.
Assessed case by caseGo live in five stages, with nothing surprising at cutover.
- 01
Discover
Processes, control obligations, systems, sites, data and risk — mapped with the people who run them.
- 02
Prove
The critical chain configured and tested against your real edge cases before anything is committed.
Control design · configured to your obligationsEnforced, not circulatedFind a control or an obligationIn forceAdd a controlControlThresholdWho may releaseEvidence keptEnforced byStateDiscount ceiling5%SupervisorReason, name, timeSoftwareIn forcePayout releaseUS$2,000Two named peopleBoth namesSoftwareIn forceStock write-offUS$250Site managerReason and photoSoftwareIn forcePrice changeAnyHead officeWas, now, reasonSoftwareIn forceVoid after closeAnySite managerReason, name, timeSoftwareIn forceCredit limit changeUS$500RegionalTrading historySoftwareIn forceSegregation of duties- Raiser and approverCannot be the same person on any thresholdBlocked
- Controls bypassed this monthThere is no path that bypasses one0None
- Held for approval right nowOne payout, one write-off2Waiting
- 03
Migrate
Data cleaned, reconciled and rehearsed. Cutover is approved on evidence.
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.
- 04
Launch
Champions trained, sites sequenced, go-live supported, adoption measured.
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
- 05
Improve
Standing reviews of exceptions, control performance and the next workflow worth connecting.
Service level · written into the agreementAugust: every target metSeverityWhat it meansRespond withinActualResolve withinActual1 · Trading stoppedA site cannot sell15 min6 min4 h2 h 412 · Money at riskPayments or fiscal failing1 h22 min1 day5 h 103 · DegradedSlow, or one workflow down4 h1 h 083 days1 day4 · QuestionHow do we do X1 day3 h 40——Who you actually reach- Tanaka MoyoNamed success lead · HarareYours
- Severity 1, out of hoursAn on-call engineer, not a ticket queue24/7
- Calls that reached a call centreThere isn't one0None
Six parts. You see all of them.
What the agreement covers, how many people it covers, and the group shape it is modelled on.
Every piece of implementation work priced in writing before it starts.
Which systems connect, who owns which record, and what we are contracted to respond to.
Before you ask.
When group structure, regulated controls, integrations, private infrastructure, or contracted service levels enter the picture. If you're a single company under 40 users on standard controls, the Scale plan is probably the honest answer — and we'll say so.
Yes. Integration scoping defines which system owns each record, what must move in real time, and where a controlled export is the better answer. Banking, fiscal, identity and legacy connections are itemised in the agreement.
Dedicated and private deployment are available where obligations require them, assessed against your risk, governance and support model. Most groups are best served on Corelith cloud — we'll tell you which you actually need.
Six itemised parts: platform scope, users and structure, edition configuration, migration and rollout, integrations, and service level. Each is scoped in writing before signature — no bundle pricing, no surprises at renewal.
Scope it in writing, line by line.
We go through your group structure, what you are obliged to control, and what has to talk to what. The scope comes back itemised, so you can strike lines off it.