The method
Every vendor sells a layer. Nobody sells the base you run them on.
Funnel One is a GTM platform for running a B2B funnel under one set of rules, from first touch to closed-won. The method is called Governed Funnel, and it has four moves: one funnel, one rulebook, one workforce, one loop. They are sequential. You cannot write a rulebook over a span you have not defined, and you cannot apply one across a workforce that lives in two systems.
The seam
Your funnel is already governed — five times over.
Marketing automation governs nurture. The sequencer governs cadence. The CRM governs the forecast. The routing tool governs assignment. Each is genuinely good at the slice it owns, and each enforces its own definition of what a stage is. None of them governs the moment a record crosses between them.
So a person governs it. They hold the mapping between four stage models, they run the cleanup before the forecast call, and they are the reason the numbers hold. None of that is written anywhere a system can read. It was never in the box.
Why tooling can’t supply it
A tool can give you power. It can’t give you a method.
This is not an argument against tools. It is an observation about what a tool can be. A vendor sells capability, you assemble it, and then you govern it yourself — because a tool ships with settings rather than a method, and the method was always the part you supplied. Which is why a stack of five excellent products still needs a sixth thing holding it together. That thing is a person.
Funnel One brings the method as the base the tooling runs on. Rails are what the trains run on. The trains are still the point.
Contents
Move one · One funnel
Define the whole span once, and define it as one thing. Prospecting stages and pipeline stages are rows in the same table, separated by a column that says which phase they belong to. Both run through the same gate. A record does not get exported at the handoff; it changes stage, and the history does not restart.
Move two · One rulebook
Now that the span exists, you can write rules over it. Each stage carries its own entry conditions and they are checked at the moment of the move, not on a report afterwards. A move to Closed Lost does not complete until someone picks a reason from your list. Rules that only apply to the honest path are not rules.
Move three · One workforce
A rulebook only means something if it covers everyone. Marketing, sales and RevOps are three roles inside it. So are AI workers: one table, one manager chain, one owner field, one calendar. An AI worker moving a company hits the same gate a rep does, because it calls the same function.
Move four · One loop
Rules are configuration, not code, so you change them without a deploy. Nothing already recorded changes when you change one, which is what keeps the history honest about what the rules were at the time. Test the work before you commit it: an experiment will not name a winner until the maths earns it. What you cannot yet do is see, in product, what a rule change did to the funnel. We say so plainly on that page.
One method, three jobs
Same rulebook. Three different days.
Marketing
Hands over a lead and can still follow it. The record does not cross a border, so the trail does not stop at one.
Sales
Works a record whose stage means the same thing it means everywhere else. Fills what the stage asks for, at the moment it asks.
RevOps
Writes the rules, and stops being the thing that enforces them. Changes a stage’s conditions in the afternoon and finds out by dinner whether they were right.
The promise
Every other vendor sells you tooling and leaves you to govern it.
We bring the methodology, and the tooling runs on top of it. Every vendor sells a layer. Nobody sells the base you run them on — so you became the base, and holding it together became the job nobody wrote down.