It never shows up as late.

Nobody owns the gap

The job is finished at both ends. What sits between them belongs to no one, so no one reports it.

Rebuilt every Monday

The same figures pulled into the same sheet by hand, because the report was never wired to the data.

Found out in the meeting

A handover nobody wrote down surfaces three weeks later, in front of the customer.

Most of it was never work.

One quote request, followed twice. Same people, same approval, same care taken over the number.

A worked example, not a client's figures — the shape repeats, the numbers will be yours. Putting real ones here is the first thing The Draw does.

As it runs today 46 h 24 min of clock time from request to sent · 24 minutes of it was work

6 hSits in an inbox overnight

31 hOne number, and it lives in another team

9 hWaiting on approval

The three dark slivers are the whole of the actual work: 4 minutes opening it, 2 minutes pasting a figure, 18 minutes writing the draft. Everything else is hatched, because nothing is happening in it.

Sits in an inbox overnight6 h
Someone opens it4 min
One number, another team31 h
The number arrives2 min
Draft written18 min
Waiting on approval9 h

As it runs wired 40 seconds of machine time, then the same human approval · drawn at its own scale

14 sData pulled from the CRM

18 sDraft built from the template

2 s

6 sSent

Data pulled from the CRM14 s
Draft built from the template18 s
Approval requested2 s
Sent, once a person says yes6 s

The orange line at the left of the first bar is this entire run, drawn on that bar's scale. At the width shown it measures one fifth of a pixel. We did not remove the approval — we removed the hours around it.

Four things that start themselves.

Four illustrative workflows · follow the handoffs

A form is submitted

The record, the folder and the first reply exist before anyone has opened it.

A deal moves stage

Whatever that stage needs signing is drafted and waiting, addressed to the right person.

Monday arrives

The report builds itself from the same records the week ran on. Nobody rebuilds it by hand.

An account changes hands

Everyone who needs to know has been told in writing, and it is on the record.

Timed, wired, watched.

We time the path

A stopwatch on every handoff, including the hours it spends idle.

The worst one first

One path goes into production. You see what it gives back before we touch the second.

Every run is read

We read the history daily for a fortnight. Wiring nobody checks is how quiet failures start.

You hold the switch

Each one turns off on its own and stays off until somebody deliberately turns it back on.

Questions.

A step fails halfway. Then what?

The run halts there and names the step that broke. Nothing half-finished gets written, and nothing reports success it did not have. A failure that announces itself costs an hour; one that hides costs a quarter.

One of our tools has no API.

Then we read it on a schedule, or leave that one step to a person and wire everything around it. Half a path still gives back most of the hours.

Does this replace anyone?

It replaces idle time, not judgement. In the example above, the 24 minutes still belong to whoever was doing them. The 46 hours belonged to nobody.

How do we know it is still running?

A history you can read without us, and a failure notice addressed to a person you name. If something breaks at 3am you hear it from your own system.

Our process changes every few months.

Each step is a separate job, so one gets rewritten without disturbing the others. That is why we do not hand you a single long script that nobody dares touch.

Nobody is late. The work is just waiting.