What happens to our existing deal history?

It imports with dates intact, including closed and lost. History is what makes the forecast credible by month two, so we would rather bring three years of it than start clean. The migration guide covers field mapping and the two things that never map neatly.

Do we need Loop and Books for Flow to be useful?

No. Flow on its own is a competent CRM. What you lose without them is everything after won: the project opens somewhere else and the invoice gets typed by a human. Most companies add Books first, then Loop.

Treepie Flow · Sales & customer management

The customer record the whole company reads.

Leads, contacts, pipelines and deals that keep working after the close — because the record they sit on belongs to the whole company, not to sales.

Book a demo What is inside Flow

4 daysto a real pipeline

0exports to delivery

−31%quote to signature

Pipeline — Q311 deals

AccountStageWeighted

Kanaka FoodsProposal£82,400

Bexley GroupNegotiation£41,900

Ardent LabsDiscovery£18,250

Halstead & CoWon£67,000

Perrin StudioQualified£9,800

weighted values recalculate on stage change

The problem

Selling is the easy part. Keeping the promise is where it breaks.

Most CRMs stop at the signature. The deal is marked won, and then the whole thing is typed again into a project tool, a spreadsheet and eventually an invoice. Flow does not hand over — it simply stops being the only team looking at the row.

BeforeWith Flow

The quoteretyped into the project toolopens the project itself

The forecasta spreadsheet rebuilt every Mondaya view of rows you already have

The handovera document nobody reads twicea change of view, not of system

Inside Flow · 50 features · 7 groups

50 features, grouped the way people actually look for them.

All features →

Group 1 of 7 · 8 featuresPipeline & dealsThe part people open the product for: stages you define, deals that carry their own history, and a forecast that is a view of the rows rather than a rebuild of them.

Pipelines & stagesDeal recordsWeighted forecastingDeal splitsWin/loss reasonsDeal scoringMultiple pipelinesStage automation

All 50 Flow features →

Who opens it

4 people, one row, 4 different mornings.

Sales leadThe forecast, and the reason it moved since Monday.

Account managerEvery conversation on the account, including the ones support had.

OperationsStages, fields and routing that stay tidy without policing.

FinanceWhat was actually agreed, before the invoice needs writing.

One record

Where Flow meets the rest of the company.

Nothing here is an integration. Each line is two products reading the same row from different sides.

See all seven →

Flow + LoopA won deal opens the project on the sold scope — the same lines, not a summary of them.

Flow + BooksThe agreed quote becomes the invoice schedule, including the milestones nobody wants to argue about twice.

Flow + DeskA ticket opens carrying the account, the contract and whatever is currently in delivery for them.

Flow + GrowthThe page that sourced the deal keeps the credit, right through to closed revenue months later.

Kanaka Foods Ltd · 34 staff · food manufacturing

“We did not buy a CRM. We bought the end of typing the same order into three places.”

Priya Nair, Operations Director

6 → 1subscriptions

11 daysto live

−75%quote to invoice

£1,240saved monthly

In practice

What actually changes, and when.

Week oneThe first fortnight is mostly argument about stage names. That is normal and worth doing properly — the stages are the only thing here that is genuinely painful to change later.

Month twoBy the second month the forecast is being read in the same meeting as the delivery plan, because it is the same set of rows. The reconciliation call quietly stops being booked.

The quarterThe change nobody predicts is in support. Once Desk reads the account, the first question on a call stops being “which contract are you on”.

Getting in

Moving your pipeline in takes four days.

Migration guides →

Day 101 / 04Decide the stagesBefore any import. Stage names are the one thing here that is genuinely painful to change in month three.

Day 202 / 04Import into a sandboxDeals, contacts and three years of closed history, mapped and checked before anybody logs in.

Day 303 / 04Wire the routingForms, inbox and owner rules, so a new lead lands on a person rather than in a queue nobody reads.

Day 404 / 04Let the team inSales first, then whoever reads the forecast. The old CRM stays readable for a month.

Under every product

The boring parts, done once.

Permissions, audit, API and backups belong to the record, not to Flow — so they are the same in every product you add.

Security & trust →

Record-level permissionsRoles, teams and field rules. Salary is a separate permission from the rest of the record.

Audit trailWho changed what, when, and what it was before. Retained for the life of the account.

API & webhooksDocumented REST, a token per integration, and webhooks that fire on the same events the interface does.

Imports & bulk editCSV in, CSV out, and a bulk editor that shows you the diff before it commits anything.

Uptime & backups99.9% target, a published status page, and point-in-time restore for the last 30 days.

Data residencyUK and EU regions. Your data stays in the one you pick, backups included.

Honest limits

What Flow does not do.

No marketing automationSequences exist, but this is not a campaign platform. Growth handles the audience side of the problem.

No territory modellingOwner rules and assignment queues, not a quota engine with geographic hierarchies underneath it.

One currency per dealMulti-currency lives in Books. A deal is priced in the currency it was actually sold in.

Pricing

Flow is £14 a seat. Every product you add costs less.

The record underneath is free. Switch on a second product and the whole bundle steps down — up to 40% with all seven.

Flow pricing →Build a bundle

1list

2−10%

3−18%

4−25%

5−30%

6−35%

7−40%

Questions

Flow, answered.

Anything else — ask a person.

Yes, and you should. Flow ships with a default set because a blank pipeline is useless, but almost everybody renames them in week one. Stages, probabilities and required fields are all yours — the only fixed rule is that the stage marked won is the thing that opens delivery.

The other 6.

Compare all →

NestHR & employee management LoopProject & work management DeskCustomer support & ticketing BooksFinance & accounting GrowthSEO & website growth intelligence PulseAI customer & employee assistant