1
ExperienceOne screen holds everything waiting on you.Web / adminCitations / artifactsStreamingApproval queue
Finished work sits in one place with the sources beside it. You approve it or send it back, and the run carries on from where it stopped.
Otherwise you buildthat screen, and the record of who approved what and when.
The eight layers
1
2
3
4
5
6
7
8
Bring one job your team repeats, and we will tell you which parts of it can be programmed.
There is nothing to prepare. Walk us through the job as it actually runs, exceptions and all, and bring the person who does it if you can. We will name the parts that have to stay with your people as well, before anyone builds anything.
hello@runbook.ae
Hero test v2
One system goes in. After that, every job is one more agent on it.
You start with one job, the one costing you the most people. What gets built underneath it is what every job after it runs on.
Every system the work touches, on one layer
Runbook is the object at the centre
01·Credit and underwriting
The committee memo
Today
A file lands. Someone assembles the pack, spreads the financials by hand, and the committee waits for the memo. The borrower waits for the committee.
Programmed
The pack is pulled, spread and checked against policy as it arrives. The memo is drafted in your committee format. The committee reads it and signs.
The alternatives
Four routes to this, and where each one stops.
Already considered
A consultancy
It ends at the document.
Not finished
Their partner model is built for engagements far larger than this one. Below that line the document is the profitable part and the build is not.
A document. Your team still runs the work themselves.
They encode your judgment, and it leaves with them when the engagement closes. Runbook ends in production. The document is week one.