Nobody gets handed the same system twice

This is the part that is not software. Two of these weeks are us sitting in your business reading how it actually works, because a system built from an assumption about your trade is worth less than the spreadsheet it replaced.

  1. Week 0

    The seven questions

    You rank the six places a week goes, describe a bad one in your own words and give four rough numbers. Eight minutes, and it decides everything after it.

    Your answers, in your words
  2. Weeks 1–2

    We come and read your business

    Your actual quotes, your document set, your regulator, how a job moves from enquiry to final account, who may say yes to what, and the words you use. Not a workshop – reading, and asking.

    A map of where the week goes, with your numbers on it
  3. Week 2

    You name the desks

    Which roles get an agent, what each may touch, what it drafts and where it must stop. Written down before anything is built.

    A scope with an acceptance test per stage
  4. The build

    Built against your business, in stages

    Your history read into your catalogue, your rules written into the agents, your documents generated from your own job file, on accounts in your name.

    Each stage tested before it is invoiced
  5. Handover

    The keys, and the export

    Every account, every credential and a five-part export. If we vanished, you would still be running on Monday.

    It is yours, in writing
  6. After

    It gets better because you use it

    Every draft you correct is a rule it learns. The monthly fee runs it, watches it and improves it – not a licence to something we sell to someone else.

    Your system, not our product

A day, as it runs

What it has already done before anyone opens a laptop. The times are the pattern as it runs for a client today, not a promise.

  1. 07:30

    The brief lands

    What came in overnight, what waits on your approval, what waits on someone else.

    Read in ninety seconds.
  2. 08:12

    An enquiry arrives

    Read within fifteen minutes, qualified against your rules, a reply drafted in your voice and queued for one tap.

    The two questions that decide the site visit are already in it.
  3. 10:40

    You dictate the site visit

    The bill of materials and quote pack are drafted from your own catalogue before you reach a desk.

    Anything the note missed is flagged, never guessed.
  4. 15:05

    A job is signed off

    The closeout pack is generated from the job, and the invoice is drafted on acceptance.

    The signature is yours; the retyping is gone.
  5. 17:00

    The report

    Every job, its stage, what moved and what is waiting on whom.

    The same report daily, so a missing one is a signal.

The questions owners ask

Asked on nearly every call. Answered here so the call can be about your week.

Who approves what?

The agent drafts. A person approves every message, quote and document before it leaves. Money movement and anything filed with a municipality or SARS stay with a person. That is a rule in the build, not a setting you can switch off.

We already have someone doing this.

Good. What happens when they are on leave? The agent drafts, your person approves. It makes them faster; it does not replace them. Most owners keep the person and stop being the second bottleneck behind them.

Do we own it?

Yes. Every account it runs on is registered in your name from day one. On request and on exit you receive a five-part export – schema, data, configuration, documentation and access list. Continuity is a term of the agreement, not a favour.

What if it sends something wrong?

It cannot send. Nothing reaches a client, a supplier or a municipality without a person tapping approve. It can draft something wrong, which you will see before anyone else does, and which it learns from.

How do we know it works?

The acceptance test is in the agreement and it is objective: twenty real messages classified correctly against a key you agree, a quote pack that matches your last accepted quote. If a stage fails, it is not accepted and not invoiced.

What does it run on?

Your email, your WhatsApp Business number, your quote history wherever it lives today, and your accounting package. Where your trade has vendor or regulator portals, those too. Nothing is copied out into ours.

We are not in energy. Does this still apply?

The build is against the shape of your week, not your trade. If you quote bespoke work off a site visit, price it off a bill of materials and owe documents when the job closes, the same six parts apply. What changes is your catalogue, your rules and your document set.

We have branches. Does it handle that?

That is where it earns the most. Each branch runs its own board and catalogue with per-branch isolation and audit logging, while you see all of them. The second and third branch cost a fraction of the first.

Why only three builds a quarter?

Because each one gets the person who built the first. Three at a time is the honest capacity, and a queue you can see is worth more than a promise you cannot.

Are you software or an agency?

Neither in the usual sense. We build one system for one business and hand you the keys. The monthly fee runs it, watches it and improves it. There is no per-seat licence and no version you are waiting for.

Where does our data actually go?

Into a store registered in your name, with an audit log on every write. The models run in your tenancy or on your own hardware, and nothing you give the system is training material for anybody.

What do you need from us?

About four hours in the first two weeks: the diagnostic call, access to the inbox and quote history, and one person who will approve drafts. After that, the 07:30 brief and your yes.

Start with the seven questions.

Eight minutes. Rank where the week goes, describe a bad one and give four rough numbers. You keep the map whether or not we ever work together.

Map your bottlenecks