Kuumba Work

Every answer the job needs, one question away.

Kuumba Work is the AI workspace our engineers use every day. It reads SAP Business One, spreadsheets and documents, drafts the report or the request, and waits for a person before anything moves. Your teams can work in it too.

  • Finding the answer

    From Three windows and a callto One question

    Asked in your own words, answered with its sources in view.

  • SAP Business One

    From Export, then pivotto About a minute

    From a sentence, read-only, with your own permissions.

  • The monthly report

    From Rebuilt by handto Regenerated, then checked

    Word, Excel and PDF, in your template, reviewed by a person.

Office blocks with lit windows beside a highway at dusk, blurred from a passing car
Between the office and the site

The week you know

The answer exists. Finding it is the job.

It is in SAP Business One, an Outlook thread, a spreadsheet on someone's desktop, a SharePoint folder called Final, a P6 export and a 300-page PDF. You know exactly where to look. That is the problem: you are the one who has to look.

  • Monday · 07:10

    Three windows for a yes or no.

    Will the gate valves land before the shutdown? The PO is in SAP Business One, the delivery date is in the supplier's email, the need-date is in last week's P6 export. You open all three, then phone the buyer anyway.

    What it costsGartner found that 47% of digital workers struggle to find the information they need, spread across an average of 11 applications.

  • Monday · 09:40

    Three folders called Final.

    Which revision of the GA did the fabricator build to? SharePoint holds Final, Final-2 and Final-issued. The transmittal that would settle it sits in somebody's sent items.

    What it costsThe McKinsey Global Institute estimated that 19% of working hours go on tracking down information.

  • Tuesday · 11:15

    The answer is on page something.

    The fitter needs the torque for the coupling bolts. It is in the vendor's 300-page O&M manual, which is a scan, so Ctrl-F finds nothing at all.

    What it costsA morning of scrolling, or a call to the one person who remembers.

  • Wednesday · 14:20

    Your approval is in someone's inbox.

    The purchase request went to the planner on Monday. He has been underground since, with no signal, and the request now sits beneath forty newer emails.

    What it costsDays, on a part the shutdown is waiting for. The same McKinsey study put email at 28% of working hours.

  • Thursday · 16:05

    The tender went into a public chatbot.

    Someone needed a quick summary of the client's tender, so they pasted it into a free AI tool. It helped. Nobody can say where that text lives now.

    What it costsConfidential client information outside your control, with no way to call it back.

  • Friday · 21:40

    Month-end, rebuilt by hand.

    The same report as last month: export, copy, paste, reformat the table, fix the chart, save as PDF. The numbers changed. The work didn't.

    What it costsA day of every month spent assembling a report instead of reading it.

How our engineers work

One workspace. Four ways to move the work.

Our engineers ask it questions, hand it the drafting, and run their registers and jobs in it, on every service we deliver. Your teams get the same workspace, in an environment of their own.

01 · AskLive

Ask it the way you would ask a colleague.

No report codes, no export. Kuumba reads SAP Business One, your spreadsheets and your documents with your own permissions, lines the figures up, and shows where each one came from.

  • SAP Business One, in plain words. Revenue and P&L comparisons, customer and supplier ageing, purchasing, stock and sales. Read-only.
  • Drop in the document and ask. Word, Excel, PowerPoint, PDF, CSV and scanned pages, read on your own server.
  • Figures you can check. Every number in a data answer traces to a record read for that answer.
  • Whole project libraries.Building Shared project spaces that answer across every file, with the file and page cited.

02 · ActLive

It drafts the work. You decide what moves.

The pack, the request, the note for the morning meeting. Kuumba prepares them in your template, then stops. Nothing is sent, raised or changed until a person approves it on screen.

  • Documents out. Word, Excel and PDF, generated in your template and edited in place.
  • An approval card for every action. What will happen, where, and for whom. Approve, change or decline.
  • Team chat in the same place. Ask a colleague, or the assistant, in the same thread.
  • Sending from Outlook and Microsoft 365.Building Until then, drafts go out by your hand or through team chat.

03 · AutomateBuilding

The weekly grind, described once.

We are building automations you describe in a sentence. They read what they need, build the report, wait for the right person to approve it, follow up on time, and hand anything unusual back to a person instead of guessing.

  • Readable before it runs. Every automation shows as a plain outline you can check, with a test run that sends nothing.
  • Approvals that follow up. Reminders when a step waits too long, and an expiry when nobody answers.
  • Your permissions, not more. It acts as the person who switched it on, with that person's live access.
  • Careful with writes. A step that fails parks for a person to repair, and an uncertain write is never sent twice.

04 · AppsLive

Registers and jobs, as apps the assistant can work in.

The spreadsheets that run the site become focused apps on one sign-in: tables, boards and calendars your team can filter and update. The assistant works inside each one, with the same permissions as the person asking.

  • Jobs, from first visit to sign-off. Planned visits, assignments, materials and QC readiness in one place.
  • SAP Business One, as apps. Finance, inventory, purchasing, and sales and CRM, read live from SAP Business One and never copied.
  • Inspections with photo evidence. Filed from the phone's browser, on site, where the work is.
  • Apps from a description.Building Describe the register you need, and get the table, views and dashboard.

Works in the phone's browser today. Voice, a desktop app and native phone apps are building.

From question to approved work

How a question becomes approved work.

One planner, one shutdown package, ten minutes before the morning meeting. Every step that reads is free. The one step that acts waits for a person.

  1. 07:10Ask

    You ask, from the car park.

    "Which POs on the feed-water package are late, and will they land before the shutdown starts?" Typed on a phone, in plain words, the way you would ask the buyer.

    • You
  2. 07:11Read

    Kuumba reads, with your permissions.

    The open POs in SAP Business One, read-only. The P6 export and the supplier's delivery note you dropped in last night. What you cannot see, it cannot see either.

    • AI reads
  3. 07:12Answer

    An answer you can check.

    Two POs are late, and one will miss its need-date by four days. Each figure carries a numbered source, so you can open the record before you repeat it in a meeting.

    • AI cites
    • You check
  4. 07:15Draft

    The next step, drafted.

    A purchase request for the alternative valve, a chaser for the supplier, and the look-ahead note as a Word document. Drafts, not decisions.

    • AI drafts
  5. 07:18Approve

    Nothing moves until you say yes.

    The request arrives as an approval card: what will happen, where, and for whom. Approve it, change it or decline it. Reads are free; writes wait.

    • You approve
  6. 07:19Done

    Done, with the reasoning attached.

    The request lands in the Stock app for the buyer. The thread keeps the question, the sources and your decision together, so the next person picks up the thread instead of starting again.

    • Your team

What is live, and what is building. Asking, reading, drafting, generating documents and approving work today. Sending email from Outlook, and automations that run the same flow every Monday on their own, are still being built. Until then, a person sends the chaser.

What it connects to

It starts with the systems you already run.

No new system of record, and no migration. Kuumba Work reads what your teams already keep, and says plainly which connections are live and which we are still building.

Connected

  • SAP Business OneRead-only, with each person's permissions. Finance, ageing, purchasing, stock, sales and CRM.
  • Excel, Word and PDFUploaded and asked about, then generated back in your own template.
  • Scanned documentsRead on your own server, so old manuals and signed forms count too.

Connecting now

  • Microsoft 365
  • SharePoint
  • Teams
  • Outlook
  • Power BI
  • Google Workspace

We are building these now. Until they are live, files from them come in by upload.

Brought in as files

  • Primavera P6 and Microsoft ProjectExport the schedule as Excel, CSV or PDF, and Kuumba reads it alongside SAP Business One. There is no live link to the scheduling tool.

Your own environment

Your work stays in a workspace of its own.

The answer to the public-chatbot problem is not a policy memo. It is a workspace your people would rather use, set up for your organisation alone.

How we handle security
  • An environment for each organisation

    Its own server, database, file store and keys. Nothing is shared between clients.

  • Client data stored in South Africa

    Files and records are stored in South Africa. AI model processing happens outside South Africa, on routes asked to keep nothing.

  • Permissions on every request

    The assistant sees only what the person asking can see. Chat access stays off until an admin grants it.

  • A person approves

    Reading is free. Anything that writes, sends or switches something on waits for a yes on screen.

  • Read-only where it counts

    SAP Business One is read with read-only access. Kuumba Work does not change it.

  • Access changes are recorded

    Changes to who can see and do what are kept as audit events your admins can review.

Where AI helps, where people decide

AI does the finding. People do the deciding.

AI does

The searching, reading and first drafts.

  • Reads SAP Business One, the spreadsheet, the export and the 300-page manual in the time it takes to ask.
  • Lines up figures from different places and shows where each one came from.
  • Drafts the request, the note and the report, in your template.
  • Turns registers into Word, Excel and PDF, so month-end becomes a review instead of a rebuild.
  • Keeps the question, the sources and the decision together in one thread.

People decide

What it means, what moves, and who answers for it.

  • Whether an answer is right for the decision in front of them.
  • Every request raised, message sent and change made, approved on screen.
  • Who can see what, granted by your own admins.
  • What goes to a client, a contractor or a regulator.
  • Engineering judgement and sign-off, which stay with accountable people.

Kuumba Work never signs, never approves its own work, and never changes SAP Business One. Any step it cannot be sure only reads is treated as a write, and waits for a person.

Questions engineers ask

Before anyone logs in.

Where is our data stored, and where does the AI run?

Your files, records and backups are stored in South Africa, in an environment that belongs to your organisation alone: its own server, database, file store and keys.

AI model processing happens outside South Africa, on routes we ask to keep nothing. We say that plainly because it should shape what your people put in.

Who can see what?

Each person sees what their role allows: permissions per app, and scopes such as branch or warehouse. The assistant works with the permissions of the person asking, never more.

Chat access stays off until an admin grants it, and changes to access are recorded for your admins to review.

Will it send, approve or change anything on its own?

No. Reading is free. Anything that writes, sends or switches something on stops at an approval card and waits for a person to approve it on screen.

SAP Business One is connected read-only by design, so Kuumba Work cannot change it at all.

Which systems does it work with today?

Today: SAP Business One, read-only, and Word, Excel, PowerPoint, PDF, CSV and scanned documents, which you upload and ask about, and which Kuumba Work can generate in your template.

Connecting now: Microsoft 365, SharePoint, Teams, Outlook, Power BI and Google Workspace. Schedules from Primavera P6 or Microsoft Project come in as exported files.

What does "Building" mean on this page?

That we are building it now and it is not yet switched on for clients. Automations, the Microsoft 365 and Google Workspace connections, voice, and the desktop and native phone apps carry that label.

Everything without the label is in use today. We would rather you read the label here than find the gap later.

Does it replace our engineers, or yours?

No. It takes the searching, copying and first drafts off their plate, so their day goes on judgement. Our engineers work in Kuumba Work on every service we deliver, and they stay accountable for everything we hand over.

Your own teams can work in it directly too, on their own work, with the same approvals in place.