Improve
Change something, and know what you changed.
Funnel One is a GTM platform for running a B2B funnel under one set of rules, from first touch to closed-won. Improve is what happens after launch: an experiment that will not name a winner below its own threshold, a scoring change you can run against real accounts before you publish it, attribution that keeps first touch write-once, and a transition record nobody can rewrite. Two of the four refuse things. That is deliberate.
Two of these four are decision-makers with a refusal built in: an experiment that will not call a winner below the threshold, and a scoring change that shows you the damage before you publish it. The other two are the record. Together they are move four — and one of them is honestly incomplete, which is said in its own entry rather than buried.
Improve
Experiments
Experiments are created by the work, not by a form: draw an A/B split and publish, and one exists. Assignment is sticky and the variant is stamped on the enrolment, the send and the call. Below the sample floor nothing is called and there is nothing to promote. Above it, one click.
Improve
Scoring
Build a scoring model as a draft, run it against a real sample of your own companies, and read the tier shift before publishing. Simulations write no scores. Published models are numbered, so you can say which version scored a company on a given day.
Improve
Analytics & attribution
First-party visitor tracking captures first touch once and never overwrites it, keeps last touch current, and stitches to the person when they submit a form — so the campaign that started it is still attached at closed-won. Alongside it, reporting on pipeline, velocity, sequence performance and email. These are views you go and look at. Nothing here watches the funnel for you.
Improve
The record
Every governed move appends a row: from stage, to stage, who, what kind of actor, which reason, which clock. The table is append-only in Postgres — the application role has select and insert and has had update and delete revoked — so neither your team nor ours can rewrite it. It is reachable through the API today. The in-app timeline that reads it is not built yet.
GRANT SELECT, INSERT ON funnel_transitions TO app_user;
REVOKE UPDATE, DELETE ON funnel_transitions FROM app_user; Improve
A refusal you can see beats a number you have to trust.
An experiment that will not call a winner below its own threshold. A scoring change that shows you the damage before you publish it. Both refuse, on the same principle as the stage gate — pointed this time at your decisions rather than at a record’s.