Move one

Two systems joined by a sync is not one funnel.

Funnel One is a GTM platform for running a B2B funnel under one set of rules, from first touch to closed-won. Move one defines the span. Prospecting stages and pipeline stages are rows in the same table, separated by a column naming the phase — so a record does not get exported at the handoff to become a different kind of object. It changes stage. Same record, same history, same owner field, first signal to closed-won.

Get a demo Move two: one rulebook

The mechanism

One record, one history, one owner field.

There is one stage table. A phase column says whether a stage belongs to prospecting or pipeline, and both phases run through the same move gate. When a record crosses the phase line it is the same row it was a minute earlier, with the same identifier and the same history behind it.

Ownership travels with it. One owner field on companies, on tasks and on activities, pointing at the same worker record — so a handoff changes who owns the record without changing what the record is. Ask why an account moved and the answer is one query.

Nothing is exported. No object conversion, no create-a-new-record-and-link-it, no mapping table between two stage models that somebody maintains.
Nothing restarts. The activity behind a record does not begin again at the handoff.
One owner field. owner_worker_id on companies, tasks and activities — and it can point at a person or an AI worker.

The cost of the seam

Four things break at the border, and only one of them is reporting.

The history stops. Two systems, two trails, and the join between them is a foreign key someone hopes is right.
The stage stops meaning one thing. Marketing’s “qualified” and sales’ “qualified” are different words that happen to be spelled the same.
The owner stops travelling. Assignment on one side is a different field from assignment on the other, so a reassignment is two edits or it is wrong.
The rules stop applying. A rule written on one side has no jurisdiction on the other, which is why the person in the middle exists.

Questions

Is this a CRM?

No, and it does not replace the one you have on day one. Funnel One runs the funnel as its own system: the stage model, the rules and the record live here. Your CRM stays where finance and the board look. Company and contact fields sync both ways with HubSpot, so the two stay in step without anybody exporting anything. Salesforce mapping is reviewable today and the connection is coming. Whether you eventually consolidate is your decision, and not one we need you to make now.

What happens to prospecting data when a record reaches pipeline?

Nothing happens to it, which is the point. The record does not change identity when it crosses the phase line, so the signals, the activity and the ownership history that got it there stay attached to the same row. A rep looking at a late-stage account can read back to the first touch without opening another tool, and without trusting that two systems agree about which record is which.

Where this sits

Before

Nothing. Move one is where the method starts, because everything after it needs a span to apply to.

Then

The rulebook has something to govern. Conditions attach to stages, and stages now cover the whole funnel.

Define the span once, and the rest becomes possible.

Every move after this one depends on it. A rulebook over an undefined span is unintelligible; a workforce spread across two systems cannot share one. Start here.