Platform
Security companiesMotor dealershipsB2B lead nurturingWholesale and distribution
Quoting & SalesOperationsAssets & ComplianceWorkforceRecruitment
Data & InsightsAutomationsContextual Workspace
PlansResourcesSee it on your business
Training programme · Zorah Technologies

The Future-Proof
Business Programme.

Every delegate maps their own business, fixes one process and builds a roadmap for the technology that comes next. This page sets out exactly what we teach, what we show, what they build and what they take home.

Format2 or 5 days
Sessions13, four parts
They leave withTheir roadmap
FromR19,999 a seat
What it is

You cannot automate what you cannot see.

The Future-Proof Business Programme teaches how a company is run now. What the technology can genuinely do, where the business loses money it cannot see, and how to rebuild the way it works so it can use whatever arrives next.

It is built around one document. Over the week each delegate fills in the Roadmap Book on their own company, one chapter per session, and on the last day assembles it into the Future-Proof Roadmap: one page that says what they will change, in what order, who owns it and how they will know it worked.

It is taught by people who run businesses on this every day. Every session has a live demonstration, every exercise runs on the delegate's own company, and one process is automated and running before they leave.

Executive Briefing · 2 days

For the people who decide

Owners, managing directors, directors and heads of department. They leave able to judge any technology decision and with a roadmap for the company.

Full Programme · 5 days

For the people who will build it

Operations, finance, IT and process owners. They leave with their process mapped, costed and automated, and the method to carry on.

What every delegate receives

The kit.

Five things, handed over on the first morning and filled in all week. Nothing is a folder of slides. The book and the wall sheet are printed; the workbook is the same method as a file the company keeps using.

Future-Proof Business Programme
The
Roadmap
Book
The Roadmap Book
Printed A4 workbook. One chapter per session with the questions already set, so nobody faces a blank page. It is filled in during the week and it is the delegate's record of their own company.
A1 · wall sheet
The Operating Map
The Operating Map
A1 wall sheet with the mapping notation printed on it. Drawn on day three, on the wall for the rest of the week, rolled up and taken home.
The Roadmap Workbook
The same method as Excel templates, nine tabs, so the book becomes a working file the company keeps using. Formulas do the costing and the ranking.
Card 3The twelve words
Card 2The policy line
Card 1The vendor filter
Three reference cards
The vendor filter, the policy line and the twelve words. Pocket sized. The three things people reach for in the first month back.
Certificate of completionThe Future-Proof
Business Programme
The certificate
Issued on the last afternoon, once the delegate has presented their roadmap to the room.
What they build

The Future-Proof
Roadmap.

One A3 page. It starts with where the company honestly sits on the Future-Proof scale and ends with where it will be in twelve months, and between the two it lays out four lanes of work across four horizons. Every session in the week fills in part of it.

The Future-Proof scale · scored on day one, target set on day five
1
In people's heads
The business works because certain people are there. Nothing is written down.
2
On paper and spreadsheets
It is written down, in job cards, notebooks and a spreadsheet three people edit.
3
In systems that do not talk
There is software, several of them, and people retype between them.
4
Joined up
One record for one thing. Information is captured once and moves by itself.
5
Runs on its own numbers
The business measures itself daily and the numbers change what it does.
Example roadmap · a regional parts distributorTODAY · LEVEL 212 MONTHS · LEVEL 4
Lane
This week
30 days
90 days
12 months
Process
Quote requests logged in one place, not four
Quote-to-order redrawn, two steps removed
Quotes built from the price list, never retyped
Every branch on one quote-to-cash process
Data
Customer list cleaned into one sheet
Each customer, quote and job has one number
Cost per job known while the job runs
Five morning numbers, current every day
Systems
One automation running: enquiry to record
Accounting connected to the quote record
Stock and quotes read the same price
Each department connected in turn
People and rules
Policy line signed and sent to staff
Data owners named for each record
Access reviewed; free tools retired
Changed roles redeployed with a skills plan

An illustration of a finished page, not a real client. Each delegate's roadmap is written from their own map, their own costs and their own records, and is challenged by the room before they take it home.

How the week builds it

Six stages, in a
fixed order.

Days three to five are one continuous build on the delegate's own process. Each stage produces something on paper and in the workbook, and each is useless without the one before it.

Session 6See itThe Operating MapYour process drawn end to end on the A1 wall sheet.Workbook tab · Operating map
Session 7Circle the dataThe data inventoryEvery point information is typed, moved or stored.Workbook tab · Data inventory
Session 8Price itThe bleed rankingEach step costed; processes ranked by what they lose.Workbook tab · Process costing
Session 9Remove the workOne automationThe four moves applied; one automation running.Workbook tab · Four moves
Session 10Join it upThe record mapOne record for one thing; the staged path drawn.Workbook tab · Record map
Session 11 to 13Close the loop and planThe Future-Proof RoadmapMeasures, rules and the plan, challenged by the room.Workbook tab · 90-day plan and roadmap

Days one and two lay the ground the build stands on: where the company sits on the scale, the twelve words, the vendor filter, one task from the delegate's own week rebuilt and timed, and the policy line.

The week, block by block

Four blocks a day.

Every block is taught, shown live, built by the delegates or presented to the room. No block is a lecture from start to finish. Select a block to jump to the session.

TaughtShown liveBuilt by delegatesPresented to the room

Monday to Friday. Arrive 08:30, start 09:00, tea 10:30 and 15:00, lunch 12:30, close 16:30. Sessions 5, 8 and 9 are the deep build work and run in the Full Programme only.

The syllabus in full

Thirteen sessions,
four parts.

For each session: the line the room should remember, what we say, what is shown running, what is drawn, what happens in the room, and the Roadmap Book page the delegate fills in, with its questions exactly as printed.

Part one · Day one

Where we actually are

Nothing about this technology is useful until the room agrees on what is real. Day one sets the ground: what the systems honestly do, the words, and what breaks.

01Day 1
09:00 to 12:30Exec · Day 1 · 09:00

The gap that opened

The distance between a company that can see its own data and one that cannot has stopped being a matter of taste.

What we say
  • What these systems do reliably now, what they do badly, and what is marketing.
  • What a piece of thinking work used to cost, and what it costs now.
  • The African position: no legacy systems to protect, which is the advantage; a heavy administrative layer, which is the exposure.
  • The Future-Proof scale: five levels, and why most companies sit at two or three.
Shown live
The first twenty minutes have no slides. A working internal tool is built in front of the room for a business in the room, from a spoken description to a screen that runs. Only then do we take it apart in plain words.
Drawn
The Future-Proof scale on the wall, with every delegate's company placed on it by the delegate.
In the room
The tool built in the first twenty minutes belongs to somebody in the room. That is the example, and it stays on screen all week.
02Day 1
13:15 to 15:00Exec · Day 1 · 10:45

The twelve words, so nobody can bluff you

If you cannot define it, you cannot buy it properly.

What we say
  • The twelve words used in every vendor meeting, each defined by what it does inside a business, never by how it works inside a computer.
  • How to tell a real capability from a wrapper around somebody else's model.
  • Why training is rarely what a business needs, and why it is so often what gets sold.
Shown live
Every word pointed at on one running system, so each definition has a real thing on screen it refers to.
Drawn
One drawing of a business with the twelve words placed where they actually live in it.
In the room
A vendor meeting, role-played at each table: one delegate pitches from a real brochure, the rest ask the questions the words now let them ask.
03Day 1
15:15 to 16:30Exec · Day 1 · 10:45

What breaks, and what it costs

Nothing is claimed in this room that cannot be shown, including the failures.

What we say
  • Confidently wrong answers, and the places in a business where they do real damage.
  • A staff member pasting a client contract into a free chatbot, and where that contract goes.
  • Shadow systems nobody signed off. What POPIA requires of an operating business, in operating terms.
  • The vendor filter: five questions that separate a working capability from a demonstration.
Shown live
We break it in front of the room. A model asked for a source that does not exist produces one, with confidence. The same question grounded in a real document gets it right and shows where from.
Drawn
The failure map: how likely against how much damage, with the room's own examples placed on it.
In the room
Each table runs the vendor filter on a product one of them is paying for today.
Part two · Day two

The personal layer

What changes for one person at a desk. Every delegate rebuilds a piece of their own week and writes the rule that keeps company information safe.

04Day 2
09:00 to 12:30Exec · Day 1 · 13:15

One person, many people's output

Four kinds of work move. Judgement, relationships and accountability do not.

What we say
  • The four kinds of work that genuinely move: reading and summarising, drafting, looking things up across systems, and repetitive entry and formatting.
  • The kinds that do not move, and why pretending otherwise is how people get burned.
  • Timing a task honestly, before and after, so the gain is measured and not claimed.
Shown live
Nicholas Sandu's own setup across three operating businesses, shown live: the desk that assembles the day before he sits down, the engine that drafts and publishes the day's article, a multi-lodge travel quote built from contract rates. Including where it still fails.
Drawn
The four kinds of work as four columns, with the delegate's own week sorted into them.
In the room
Every delegate takes one real recurring task out of their own week and rebuilds it in the room. Timed before, timed after.
05Day 2
13:15 to 16:30Full Programme only

Your own data discipline

One written line covers most of the risk without stopping anybody working.

What we say
  • Where your work actually goes when you paste it somewhere.
  • Company account against personal account against free tool, and why the difference matters.
  • The policy line, and how to roll it out without a memo nobody reads.
  • A personal context store: the files, notes and history that make these tools useful to you instead of generic.
Shown live
A working context store opened on screen: the folder of notes, decisions and documents the tools read before they answer, and the same question answered with and without it.
Drawn
Three circles: the company's tools, personal accounts, free tools. Where each kind of information is allowed to go.
In the room
Each delegate writes the policy line for their own company and sets up the first ten documents of their own context store.
Part three · Days three and four

The organisational layer

The heart of the programme and it runs in strict order: write the business down, circle the data, price it, remove the work, join it up. Each step is useless without the one before.

06Day 3
09:00 to 12:30Exec · Day 1 · 15:15

Your business does not exist until it is written down

A process in three people's heads cannot be improved, delegated, automated, audited or sold.

What we say
  • If your operations manager left tomorrow, where is the business?
  • The mapping notation: trigger, step, decision, handoff, system, time.
  • Choosing the right first process: frequent, painful, and crossing at least two people.
Shown live
One volunteer's process mapped live on the wall. The delegate talks, the facilitator draws, the room watches the business appear.
Drawn
The notation key, then a finished map from a live deployment, anonymised, next to the volunteer's.
In the room
Every delegate maps one end-to-end process from their own company on the A1 Operating Map sheet. It goes on the wall and stays there all week.
07Day 3
13:15 to 14:45Exec · Day 2 · 09:00

Circle the data

Most of what a company knows is not in rows. It is in inboxes, chats, PDFs and scanned job cards, and that pile only recently became readable.

What we say
  • Circle every point where information is created, captured, moved or stored.
  • Three questions at each circle: who captures it, where does it land, what happens to it afterwards.
  • Structured against unstructured, in plain terms, and why the second pile is the biggest change most businesses have not noticed.
Shown live
A stack of real-shaped paperwork, a chat export, a scanned job card, an emailed PDF, read into clean rows in front of the room.
Drawn
The delegate's own map with the circles on it, and the retyped facts joined by a line.
In the room
Everybody finds the same thing and the room goes quiet: the same fact typed three or four times, with three or four versions that disagree.
08Day 3
15:00 to 16:30Full Programme only

What each process actually costs

Never automate the worst process first. Fix the sequence, then automate.

What we say
  • Put a number on every step: salary minutes, waiting, rework and errors.
  • Rank the processes by what they are losing, in the company's own money.
  • Why automating a broken process only makes the mess arrive faster.
Shown live
A volunteer's map costed live in the Roadmap Workbook: the numbers go in, the monthly cost and the ranking recalculate on screen.
Drawn
The map again, each step now carrying its cost, the heaviest steps marked.
In the room
At 16:00 the room walks the wall. One minute per map. The patterns across fifteen companies are the lesson of the day.
09Day 4
09:00 to 12:30Full Programme only

Removing the work

Eliminate, connect, automate, and only then apply a model. Most companies start at move four.

What we say
  • The four moves, in strict order of return.
  • What integration actually means, and why systems that do not talk are the real tax on a growing business.
  • How to write an automation down before it is built: the trigger, the action, who checks it, how you know it failed.
Shown live
An automation built live on a volunteer's process: an enquiry arrives, the record is created, the right person is told and a first reply is drafted for them to approve.
Drawn
The four moves as four gates, with the steps of the delegate's map passing through them.
In the room
AfricaStay, named: a thousand quotes that used to end the day unfinished now clear in the first hour, and capacity is up about thirty percent. Taken apart in front of the room, including what went wrong.
10Day 4
13:15 to 16:30Exec · Day 2 · 09:00

Joining the data up

This quote belongs to this customer, belongs to this job, belongs to this invoice. That is the whole game.

What we say
  • Relationships between records, and one record for one thing.
  • What only becomes possible after this step: true cost per job, real customer value, a forecast that survives questions.
  • The staged path: nothing thrown away that works. Connect what exists, build what is missing, one department at a time.
Shown live
A quote followed through to its invoice in a running quote-to-cash system, one record the whole way, then the report that exists only because of it.
Drawn
The record map: the company's records as boxes, the relationships as lines, and the places each is kept today.
In the room
Anonymised by shape: a print-fleet business that invoices every month from meter readings, and why its invoicing could only be automated once machine, contract and customer were one record.
Part four · Day five

The loop, the risk and the plan

The business starts measuring itself, the rules and the people questions are settled, and every delegate assembles and defends their roadmap.

11Day 5
09:00 to 10:30Exec · Day 2 · 10:45

The closed loop

AI is only worth as much as the data beneath it.

What we say
  • A business that measures its own operation and feeds the measurement back into how it runs.
  • Every number current, decisions on evidence instead of instinct.
  • Why almost everyone who buys AI gets nothing: they bought the model without doing sessions six to ten.
Shown live
A live operations view showing today, next to the month-end pack it replaces.
Drawn
The loop: work happens, it is captured once, it is measured, the measure changes the work.
In the room
The five morning numbers, chosen by each delegate for their own company, then argued over at the table.
12Day 5
10:45 to 12:30Exec · Day 2 · 10:45

Governance, risk and people

The companies that handle the people question badly lose the people they most needed to keep.

What we say
  • Who owns the data, how long it is kept, who can reach it. POPIA obligations as operating rules.
  • When a system makes a decision, who is accountable for it.
  • Vendor lock-in and exit: the questions that belong in the contract before it is signed.
  • The roles that change: redeployment against retrenchment, and what the skills pipeline has to look like.
Shown live
An access map for one real process: who can see each record, who can change it, who can take it out of the building.
Drawn
The data rules table for the delegate's own process, filled in on screen for one volunteer.
In the room
The question every person in the room is privately asking, asked out loud and answered plainly.
13Day 5
13:15 to 16:30Exec · Day 2 · 13:15

The ninety-day plan

One process, one owner, one number that proves it worked.

What we say
  • How to write a plan that survives Monday: one process, the sequence, the owner, the cost, the measure.
  • The three ways it is most likely to fail, written down in advance.
  • Setting the level on the scale the company will be at in twelve months.
Shown live
The Future-Proof Roadmap assembled from chapters one to twelve, on screen, for one volunteer first.
Drawn
The roadmap: four lanes, four horizons, today's level and the target.
In the room
Every delegate presents their roadmap in five minutes. The room takes it apart. Peer challenge, not a facilitator talking. Certificates close the day.
The three reference cards

What they reach for
in the first month.

Card 1 · session 3The vendor filter
  1. Show it running on our data, not on yours.
  2. Where does our data go, and who else can see it?
  3. What happens when it is wrong, and how would we know?
  4. What does it connect to that we already run?
  5. How do we leave, and what do we take with us?
Card 2 · session 5The policy line

Company information goes only into tools the company has approved and pays for, signed in with a company account.

Each delegate adapts it for their own company in session five and leaves with it signed off in the plan.

Card 3 · session 2The twelve words
ModelThe engine that reads and writes. It knows language, not your business.
AgentA model given tools and a job, allowed to take steps on its own.
AutomationA rule that does a step without a person: when this happens, do that.
WorkflowThe sequence of steps a piece of work goes through, start to finished.
APIThe door one system opens so another system can read or write to it.
IntegrationTwo systems joined through their doors so nobody retypes between them.
Structured and unstructuredRows and columns, against inboxes, PDFs, chats and scanned paper.
ContextWhat the model is shown before it answers. Most of the quality lives here.
HallucinationA confident answer that is wrong. Normal behaviour, not a malfunction.
GroundingMaking the model answer from your documents and records, and show where from.
TrainingChanging the model itself. Rarely what a business needs, often what it is sold.
Single source of truthOne record for one thing, that every system reads from.
The Roadmap Workbook · Excel

The book, as a file
they keep using.

Nine tabs, one per stage of the method. The columns match the questions in the book, so what is written on paper on Tuesday is typed once on Thursday. The costing and ranking tabs carry the formulas; the last tab prints as the roadmap.

ProcessTriggerFinished whenOwnerRuns a monthPeopleSystemsPain 1 to 5
1
2
3
4
5

Filled in on day three, before the first map is drawn: every process the delegate can name, so the first one is chosen, not guessed.

How the room runs

Eight rules for
the facilitators.

These are the difference a delegate notices in the first ten minutes, and the reason the programme can carry its price.

01

The first twenty minutes have no slides. Something gets built in front of the room.

02

Nobody talks for more than twenty minutes before the room does something.

03

Every exercise runs on the delegate's own business. No fictional case studies, ever.

04

The wall. Every map goes up on day three and stays up. By Friday the room sees fifteen businesses at once.

05

Diagrams, not bullets. If it cannot be drawn it is not understood well enough to teach.

06

One live demonstration per session, minimum. If it cannot be shown running, it is not in the syllabus.

07

Delegates present to each other on day three and day five. Peer challenge, not a monologue.

08

We show the failures too. Where the technology breaks, we break it in front of them.

What each side gets

What they
take back.

The delegate
  • Their own process mapped, costed and on paper for the first time.
  • One automation running in their business before they leave.
  • A roadmap with an owner, a cost and a measure, already challenged by peers.
  • The words and the filter to hold their own in any technology meeting.
The employer
  • A person who comes back with a working change, not a certificate alone.
  • A written plan for the company, not an opinion.
  • Fewer risks from staff pasting company information into free tools.
Formats and fees

One syllabus,
three ways in.

2 daysExecutive Briefing
R19,999
Per delegate

Sessions 1, 2, 3, 4, 6, 7, 10, 11, 12 and 13. One process mapped with facilitation, the roadmap written and presented. The full kit.

5 daysFull Programme
R24,999
Per delegate

All thirteen sessions, Monday to Friday. Every build on the delegate's own process, one automation running, two peer presentations. The full kit.

In-houseCustomised
Per cohort
Quoted on application

Either format run for one organisation at its premises, with every exercise on that organisation's own processes.

Seats and dates

Put your business
on the wall.

Tell us which format, how many seats, and whether you want it run in-house for your organisation. We will come back with dates.

Ask about a place