For RevOps
Stop being the enforcement layer. Start writing the rules.
Funnel One is a GTM platform for running a B2B funnel under one governance, from first touch to closed-won. You are the reason the funnel holds together — the routing rules, the stage definitions, the field requirements, the cleanup pass before the forecast call. All of that is you, spread across four tools that each enforce their own version. Here the rules live in one place and are applied at the moment of the move.
What changes on Monday
The method stops living in your head.
Required fields on a stage are actually required — not a property you marked required in one system that another system writes around. A move backwards is blocked if you say so. A closed-lost move needs a reason from your list, chosen before the move goes through rather than filled in on Thursday by whoever is closest, and the same conditions apply to a bulk update of two hundred records as to one rep dragging one card. The same conditions. Not similar ones.
Every transition is written to an append-only record: what moved, from where to where, who moved it, what kind of actor they were, the reason and the clock. The application role can insert into that table and read from it. It cannot update or delete a row.
- You change a rule without an engineer. Configuration, not code. No deploy, no ticket.
- Changing a rule does not rewrite history. What was recorded stays recorded, so last quarter still says what last quarter’s rules produced.
- A wrong rule tells you within the hour. It refuses a move somebody is actively trying to make.
- AI workers are inside the same rulebook. Not a parallel policy you also have to maintain.
Straight answer
The reporting on the rulebook is the gap, and you will find it in week two.
You can write the rules, and you can see them applied every time somebody hits one. What you cannot do in the product today is read the record back as a view: no loss-reason breakdown, no stage-to-stage conversion, no transition timeline on a company. The data is written and the API is there. The screen is not. It is the next thing worth building and we would rather you hear it from us.
Where to go next
One rulebook
The gate, the conditions, the reason list, and what happens on a bulk move.
One workforce
Roles, managers, working hours and autonomy — for people and AI workers in the same table.
Security
Row-level security forced on every tenant table, and the build checks that keep it that way.
For RevOps
You wrote the rulebook. It should be the one running.
The routing, the stage definitions, the field requirements — all of it in one place, applied the same way to every path a record can take.