Engagement pattern
Engagement pattern: from a free scan to a 90-day build plan.
Status: pattern, not a named case study. This page describes how a typical engagement runs. It names no client, quotes no one and reports no results. When a client agrees to be named, a case study will sit next to it.
For ops leads and executives in mid-market DACH/EU organizations whose week runs across inbox, spreadsheets, chat and three or more SaaS tools, and whose work dies in the handoffs between them.
Starting point
An operations lead in an organization of roughly one to two hundred people. Customer requests arrive in a shared inbox, get logged in a spreadsheet, are discussed in a chat channel and are executed across a CRM, an ERP and a ticketing tool. Nobody can say where a given request is without asking three people.
Step 1: free Constraint Scan
The ops lead answers six questions: 51–200 people, 3–5 SaaS tools, handoffs fail every day, a 90-day horizon, build later. The fixed rubric recommends the Diagnostic: pain is high, but with fewer than six tools the constraint first needs to be located, not planned around. The readout arrives by email with a link to start it.
Step 2: Runway Fuel Diagnostic, €295, 3 business days
After checkout the ops lead sends the intake brief: where requests enter, which spreadsheet columns are re-typed into which tool, who approves what in chat, and what "fixed" has to mean. The delivered Constraint Map + 30-day execution stack has this shape:
Constraint Map (shape)
Each handoff from inbox to spreadsheet to chat to CRM, ERP and ticketing tool, with where work waits, where it is re-keyed and where it loses an owner, ranked by cost.
30-day execution stack (shape)
An ordered list of fixes, each with an owner role, the tool involved, the first action and a definition of done, starting with the handoff ranked first.
Step 3: Runway Fuel Execution Blueprint, €1,950, 5 business days
The map shows the top constraint runs through more systems than a 30-day fix can cover. The ops lead buys the Blueprint to get System map + integration list + 90-day sequence + risk register: which tool connects to which, in what order over 90 days, and what can go wrong. The team can build it internally or hand it to an implementer; the Implementation Deposit starts the build with Runway Fuel.
What is deliberately missing
- No client names, logos or quotes.
- No percentages, hours saved or revenue claims.
- No screenshots of a client's systems.