Platform
The method, running.
Funnel One is a GTM platform for running a B2B funnel under one set of rules, from first touch to closed-won. This is the platform doing the work, grouped by the job it does: find, capture, engage, improve. AI runs through all four rather than sitting beside them. Everything here is under the same rulebook, and none of it is a separate product you also buy.
Four jobs, one rulebook
Four jobs. The rules don’t change between them.
Most stacks split at exactly these four lines: one tool sources, another captures, a third runs the outreach, a fourth reports on it. Four admins, four stage models, four ideas about who owns a record. Here they are four jobs on one funnel, and the configuration is written once.
Find
Market search, enrichment, signals and imports — all writing to the same record.
Capture
Forms, booking, routing, SLA clocks and the stage rules themselves.
Engage
Motions on a canvas, email from the rep’s own mailbox, calls, sequences.
Improve
Experiments that refuse a bad conclusion, scoring you can simulate, the record.
AI
AI isn’t a feature here. It’s how the platform runs.
There is no AI module, no AI plan and no AI console. There are workers, some of whom are AI, working inside the rules your team wrote — and there is one gated path through which any AI action must pass, whether it was triggered by a step in a motion or by somebody typing a request. Naming the permission, the gate and the record is more useful than naming the capability.
AI workers
One workers table, one row per worker, a database constraint saying a worker is a person or an AI and never both. A manager, a role, a working window, a daily budget and an autonomy level — suggest, act with approval, or act alone. Records point at either kind through the same owner field.
AI in the flow
Steps in a motion can be AI: write and send the email, place the call, pick the next step, hand the step to an agent. Any of them can sit behind an approval node, so a person signs off before it goes out. The step is refused on the same terms a person’s would be.
Ask the platform
Ask for something to be changed and it goes through the same routes and the same validators the screens use — so it cannot take an action the interface could not. Permission is resolved from your session, never from the request. Anything destructive or in bulk needs a confirmation first. And it produces the same record as a click, including when it is refused.
Connections
What we connect to, and what that connection currently does.
Gmail for sending and reply detection. Google Calendar for availability and booking. Google Meet on booked meetings. Slack for task cards and approvals. HubSpot for CRM records, where company and contact fields sync in both directions — what changes here reaches your HubSpot, what changes there reaches us, and the property group decides which side wins a conflict. Salesforce mapping is reviewable and the connection is coming. We would rather list the state of each than write the word “integrations” and let you assume the rest.
| Connection | What it does today |
|---|---|
| Gmail | Sending, and reply detection back into the record. |
| Google Calendar | Availability and booking, from the owner’s own calendar. |
| Google Meet | A link on booked meetings. |
| Slack | Task cards, and approvals answered from the card. |
| HubSpot | Two-way on company and contact fields. The property group decides which side wins a conflict. |
| Salesforce | Mapping is reviewable. The connection is coming. |
Governed Funnel
Every one of these runs under the same rulebook.
That is the only reason this page can be a list without being a catalogue. A capability that governed itself would be another tool to hold together, and holding tools together is the job we are removing.