Infinite processes, imagination is the only limit

An employee requests time off, their manager approves it, and HR is told. Long requests go up a level.

1. 1Request leave (form)
2. 2Policy check (automation)
3. 3Manager approval
4. 4Revise request, if changes are asked for
5. 5More than 3 days? Skip-level approval
6. 6Tell HR and the team calendar

Everything that has to happen before and during someone's first week, run in parallel across HR, IT and their manager.

1. 1New joiner details (form)
2. 2In parallel: laptop and accounts, payroll and documents, desk and buddy
3. 3Manager confirms the first-day plan
4. 4Day one checklist for the new joiner
5. 5Week-one check-in

A manager asks for a role with the reason and the budget; the department head approves the need, finance confirms the headcount, and HR opens the vacancy.

1. 1A manager asks for a role
2. 2The department head approves the need
3. 3Finance confirms the headcount and the budget
4. 4HR opens the vacancy
5. 5The manager is told it is open

A manager gives notice of a leaver and a last day; IT reclaims the accounts and equipment, finance settles the final pay, and HR confirms everything is closed.

1. 1A manager records the leaver and the last day
2. 2IT reclaims accounts and equipment
3. 3Finance settles the final pay
4. 4HR runs the exit conversation
5. 5HR signs off that nothing is outstanding

Somebody claims an expense with a receipt, the budget owner approves it, and finance pays it out.

1. 1Submit claim with receipt (form)
2. 2Check the amount against policy (automation)
3. 3Manager approval
4. 4Over the limit? Finance approval as well
5. 5Mark as paid and notify the claimant

A request to buy something, approved by the budget holder and — above a threshold — by finance, then tracked to delivery.

1. 1Describe what is needed and why (form)
2. 2Budget holder approval
3. 3Over the threshold? Finance approval too
4. 4Procurement raises the order
5. 5Wait for delivery, then confirm receipt

A rep asks for a discount on a deal and says why; the sales head approves, and anything past the floor goes to finance before the quote goes out.

1. 1A rep asks for a discount
2. 2The sales head approves the ask
3. 3Past the floor? Finance approves the margin
4. 4The rep sends the quote
5. 5The decision is logged against the deal

An employee requests a trip with dates, destination and estimated cost; their manager approves, finance approves anything over the limit, and admin books it.

1. 1An employee requests a trip
2. 2Their manager approves
3. 3Over the limit? Finance approves the spend
4. 4Admin books it
5. 5The trip goes in the calendar

Anyone raises an IT issue, it is triaged by urgency, assigned, and closed only once the reporter confirms.

1. 1Raise a ticket (form)
2. 2Triage the urgency (automation)
3. 3Assign to the IT queue
4. 4Urgent? Notify on-call immediately
5. 5Reporter confirms it is fixed
6. 6Close, or reopen and reassign

Somebody submits a contract with the counterparty and the value; legal reviews and can send it back with comments, and anything over the limit needs the finance head before it is signed.

1. 1Somebody submits a contract
2. 2Legal reviews it and can send it back
3. 3Over the limit? Finance approves the commitment
4. 4The owner signs and records the date
5. 5Renewal is put in the calendar

Support logs a complaint with the customer and severity; an owner investigates and proposes a resolution, the support head signs off on anything involving a refund, and the customer is told the outcome.

1. 1Support logs a complaint
2. 2An owner investigates and proposes a fix
3. 3A refund? The support head signs it off
4. 4The customer is told the outcome
5. 5Serious ones are reviewed a week later

It reads your office

Existing tables and forms in the room you choose, your departments, reporting heads, job titles and policies.

It proposes, you decide

Reuse the leave table you already have or create a new one; widen the audience; change who approves. The choices are listed one at a time.

It builds the real thing

Tables, views, forms, approvals, automations, reminders and calendar entries — ordinary artifacts, in your room, that outlive the workflow.

You change it by talking

A month in, say “anything over $50,000 also needs finance”. The agent redesigns those steps and shows you the diff.

An audience

Who the process covers — the whole company, a workspace, a department, or a head and their team. Nobody else is bothered by it.

Approvals with a deadline

Each approval names a rule rather than a person, carries an SLA, and knows where to escalate if nobody answers.

The exception path

Over a threshold, under a limit, a rejection, a request for changes — the cases that actually cost time are on the map.

A place for the data

A table for the case, with the columns the form asks for, the formulas that decide thresholds, and a view to watch it.

Who gets told, and how

Notification, email or room chat, chosen by whether the person is inside the room or somewhere else in the company.

An end that means something

Approved, rejected, delivered, closed — named outcomes your reporting can count and compare over time.

Start from a template, or from a sentence

We will build your process live — one of the eleven templates or any custom process you describe — against your own departments, reporting heads and rooms.