Programme status: PlannedUG-SBDFPilot design

Small Business Programme

Small Business Digital Foundations

From disconnected tools to a maintainable digital operating foundation.

This programme helps active early-stage and micro businesses move from scattered chats, owner-held knowledge and disconnected tools to visible, maintainable operating practices. Participants work on one real business problem, build a practical foundation and follow a supported 90-day adoption plan.

Quick facts

The approved delivery facts.

Full cycle
12-month pilot including discovery, delivery, coaching and adoption follow-up
Intensive
Five consecutive workshop days
Workshop cohort
Up to 15 businesses
Participation
One owner plus one operating colleague where feasible
Intended audience
Active early-stage and micro businesses
Proposed pilot geography
Gauteng
Core post-workshop commitment
At least two hours per week for the following 90 days
Capstone
Digital Foundation Pack

Geography is described as a proposed pilot location. No live cohort has been formally approved and published.

The challenge

Why this programme exists.

Small businesses often adopt tools one at a time without redesigning the operating practice behind them. Customer information remains in personal messages, work depends on the owner’s phone, records are inconsistent, subscriptions accumulate and no one is responsible for maintenance.

This programme begins with the business outcome—not a preferred app. It helps each participant design one minimum viable operating foundation that can be demonstrated, maintained and improved.

Intended participants

Who it is for — and who it is not for.

Entry criteria and exclusions stay on the page rather than behind a toggle, so nobody applies for a programme that cannot help them.

Who it is for

The programme is designed for businesses that:

  • Are already trading or delivering a service.
  • Can identify one recurring operating problem to improve.
  • Can send the owner for all five days.
  • Can nominate the person who will maintain the new practice.
  • Can commit implementation time after the workshop.
  • Are willing to practise with fictional or synthetic customer records.

No formal business registration, advanced digital skill or paid software subscription is required for workshop entry.

It is not designed for

  • Idea-only applicants who need pre-incubation support before operating-process training.
  • Businesses seeking only a once-off website build.
  • Participants seeking regulated accounting, tax, legal or cybersecurity consulting.
  • Businesses unwilling to keep real customer data out of workshop exercises.

Capabilities

What participants can do afterwards.

Business-led technology

Participant outcome

Connect a tool or process change to a defined customer, revenue, cost, time or risk outcome.

Customer operations

Participant outcome

Use a visible lead-to-service workflow and a consistent communication routine.

Records and visibility

Participant outcome

Maintain minimum viable customer, sales, document and activity records.

Tool judgement

Participant outcome

Compare affordability, fit, portability, support and risk before adopting a tool.

Safe practice

Participant outcome

Apply access, backup, privacy, scam-response and incident-escalation basics.

Sustained adoption

Participant outcome

Assign ownership, document routines, review measures and improve the practice over 90 days.

The five-day intensive

Five supported days, each with an evidence gate.

A day is not complete because it was attended. Each day ends at a gate that has to be passed before the next stage of work begins.

Day 1

Business before technology

Day outcome: Participants leave with an evidence-based baseline and one priority operating outcome, not a shopping list of apps.

Sessions

  1. Define the business outcome and constraint.
  2. Map digital readiness and operating pain.
  3. Prioritise the minimum viable foundation.

Practical build

Business Outcome Canvas, Digital Readiness Diagnostic and Five-Day Action Charter.

Evidence gate

The outcome, current-state evidence, named owner and bounded scope must be approved before tool configuration begins.

Day 2

Customer journey and trustworthy visibility

Day outcome: Participants make it easier for the right customer to find, understand and receive a consistent response from the business.

Sessions

  1. Map the real customer journey.
  2. Build a credible, findable digital presence.
  3. Create the customer response playbook.

Practical build

Customer journey and service hand-off map, Presence Card and customer communication playbook.

Evidence gate

Public information is accurate, the account is business-controlled, response templates make no false promises and a maintenance owner is named.

Day 3

Customer, sales and operating records

Day outcome: Participants replace memory and scattered chats with a visible, minimal record of work and commitments.

Sessions

  1. Design the lead-to-cash workflow.
  2. Build minimum viable customer and sales records.
  3. Control files, documents, stock or appointments.

Practical build

Pipeline or register, stage definitions, minimum record specification and one operating control pack.

Evidence gate

A second person can retrieve the correct record, state its status and identify the next action.

Day 4

Productivity, cash visibility and responsible automation

Day outcome: Participants choose affordable tools and automate only a stable, understood process.

Sessions

  1. Create basic cash and activity visibility.
  2. Select tools using fit, cost and exit criteria.
  3. Automate a stable process and document the control.

Practical build

Weekly operating view, tool decision scorecard, tested workflow and operating procedure.

Evidence gate

The process works manually, test data is used, exceptions and approvals remain visible, and ongoing cost is within the participant’s ceiling.

Day 5

Secure, sustain and improve

Day outcome: Participants leave with safer practices, a maintainable operating routine and a verified 90-day plan.

Sessions

  1. Protect accounts, devices and business continuity.
  2. Handle personal information responsibly.
  3. Demonstrate the foundation and commit to 90 days.

Practical build

Security and recovery checklist, data-handling routine, capstone demonstration and 90-day adoption plan.

Evidence gate

Completion requires at least 80% attendance, all critical artefacts, a safe working demonstration or verified simulation, and an approved 90-day adoption plan.

Capstone

What each business leaves with

Digital Foundation Pack

Each participant completes a working Digital Foundation Pack. It is a practice artefact the business owns, understands and can maintain — not a production system delivered on the business’s behalf.

  • Business baseline and priority outcome.
  • Customer journey and service hand-off map.
  • Tested customer or operating workflow.
  • Minimum viable records and control structure.
  • Configured practice demonstration or verified simulation.
  • Written operating procedure.
  • Tool decision and cost control.
  • Security, recovery and responsible-data checklist.
  • Costed 30-/60-/90-day adoption plan.
  • Named maintainer and booked follow-up dates.

The full cycle

The 12-month implementation and evidence cycle.

Small Business Digital Foundations: the 12-month implementation cycle, phase by phase.
PeriodPhaseRequired result
Months 1–2Validate and approveNeeds evidence, delivery partners, funding, governance and participant-access plan approved.
Month 3Recruit and baselineUp to 30 eligible businesses selected across two workshop waves; baseline and support needs completed.
Months 4–5Deliver two intensivesTwo cohorts of up to 15 businesses complete daily evidence gates and capstone assessment.
Months 5–8Implement and coachFortnightly clinics and monthly one-to-one coaching; 30-/60-/90-day evidence recorded.
Months 8–10Adoption and remediationMaintainers demonstrate the practices; stalled cases receive bounded remediation or close.
Month 11Verify outcomesAdoption, performance, safety and ownership evidence independently reviewed.
Month 12Learn and exitLearning brief, partner review, ownership handover and continue/adapt/stop decision.

The figure of 30 businesses is a proposed two-cohort pilot target, not a claim of businesses already supported.

Assessment and completion

Completion is evidenced, not assumed.

Ubuntu Gale records completion, demonstrated competence and portfolio evidence. It does not describe any programme as an accredited qualification.

Assessment is based on evidence, not attendance alone. Participants must:

  • Attend at least 80% of the intensive.
  • Complete all critical artefacts.
  • Demonstrate or explain the practice themselves.
  • Present a safe working demonstration or verified simulation.
  • Name the maintainer and operating routine.
  • Submit an approved 90-day adoption plan.
  • Have no unresolved critical data, safety or conduct breach.

Coaching and follow-through

What happens after the room closes.

Responsible delivery is part of the curriculum

Ubuntu Gale programmes use fictional, synthetic, anonymised or safely aggregated information during workshop activity. Participants do not expose passwords, recovery codes, production credentials or sensitive personal information. Accessibility, low-bandwidth access, safeguarding, cybersecurity basics, source attribution and responsible AI use are designed into the work rather than left to a final checklist.

  • A designated safeguarding and data focal point may pause an activity.
  • Real beneficiary or customer records must not be displayed in shared workshop exercises.
  • Direct contact with children or vulnerable people requires a separately approved safeguarding plan.
  • Photography, recording, partner naming and portfolio publication require explicit approval.
  • Workshop prototypes remain non-production until separately approved.
  • Legal and regulatory questions are referred to qualified specialists.
  • Accessibility support requirements are collected before final cohort confirmation.

Intended measures and evidence

What the programme measures.

These are the measures the programme assesses. They are not results already achieved.

  • Completion of required workshop artefacts.
  • Use of the selected operating practice after the workshop.
  • Customer follow-up consistency.
  • Record completeness and ownership.
  • Tool affordability and continuation decision.
  • Security, recovery and responsible-data routines.
  • Evidence of the selected business outcome against its baseline.

Participation, completion, demonstrated competence, implementation, adoption and outcome evidence are reported separately. See the public evidence ladder

Limits

What this programme does not promise.

  • This is not an accredited qualification and does not lead to a SAQA- or QCTO-registered credential.
  • No revenue, growth, funding or business outcome is guaranteed.
  • Completing the workshop does not make a business POPIA compliant or cybersecure.
  • Workshop configurations and demonstrations are practice artefacts. They are not production-ready systems.
  • Ubuntu Gale does not provide regulated accounting, tax, legal or cybersecurity advice.
  • The programme is not a once-off website or software build service.

Frequently asked

Questions about Small Business Digital Foundations.

Is the programme only five days long?

No. The five-day intensive sits inside a 12-month pilot cycle. Recruitment, baseline, fortnightly clinics, one-to-one coaching, 30-/60-/90-day adoption evidence, independent outcome review and handover continue after the workshop.

Does my business need to be registered?

No formal business registration, advanced digital skill or paid software subscription is required for workshop entry. The business must already be trading or delivering a service.

Will you use my real customer data in the workshop?

No. Workshop exercises use fictional or synthetic customer records. Real customer records must not be displayed in shared workshop activity, and participants do not expose passwords, recovery codes or production credentials.

How much time is needed after the workshop?

At least two hours per week for the following 90 days, plus attendance at fortnightly clinics and monthly one-to-one coaching sessions.

Do I receive a qualification?

No. The programme records completion, demonstrated competence and portfolio evidence against a capstone assessment. It is not represented as an accredited qualification.

Next steps

Choose the route that matches your role.

Every route below leads to the same enquiry form, which asks only for what your role needs.