Scaleflow grew out of practice, not theory — it’s the residue of a lot of teams getting it wrong first.
From a lab idea to a coaching practice
The seed ideas go back to the “BananaBananaA task without context — no "why", no link to a real outcome. The thing the method exists to eliminate. Inception” deck in the autumn of 2016. They were codified during a lab project at trivago in September 2019, when the rituals and artifacts were tested against real product work under real deadlines.
Under the working name WhatNow in 2020, the approachThe ApproachThe multi-week narrative roadmap — titled weekly outcomes ("The one where…"), each with a demo, planned backwards from success. matured. By 2021 it had become Scaleflow, run out of Amsterdam. What began as an internal experiment turned into a way of coaching teams through real product work under deadlines and doubt.
The people who shaped it brought roughly a hundred years of combined SaaS experience between them — time spent leading product and engineering through hyper-growth, IPOs, and acquisitions. The method is the distillation of what worked and, more usefully, what didn’t.
WhatNow → Scaleflow
The early version was called WhatNow. The name changed; the obsession with asking “what do we actually know now?” did not. That question — surfaced daily, planned against weekly — is still the spine of the method.
What we learned the hard way
Three lessons shaped the method, each learned by watching good intentions fail:
- Rituals decay into ceremony. A ceremony performed for its own sake stops forcing anything into the open. Every ritual has to earn its place by surfacing reality.
- Metrics drift into vanity. Left unattended, teams measure what’s easy rather than what matters. The fix is to tie measurement to the customer problem.
- Context evaporates unless someone owns it. Shared understanding doesn’t maintain itself. It needs a named owner and a living document, or it leaks away with every hand-off.
Every part of the method is a guard against one of those three failures.
What it has produced
The same approach has shown up in very different companies:
Decodata pivoted from B2C to B2B SaaS in six months and signed its first customers — a turn made possible by cross-functional alignment on what the customer actually needed.
Beerwulf, a Heineken subsidiary, launched a subscription feature that had stalled for over two years. It shipped in six weeks and avoided millions of euros in inventory waste — by confronting the real constraints rather than re-litigating the plan.
Whatagraph closed a $7.2M Series A on the back of cross-functional alignment between product, engineering, marketing, sales, and customer success — teams learning together rather than in silos.