How is a use case different from a solution?

Solutions describe Flow for an industry. Use cases describe one job — like rescuing stalled deals — that applies across industries.

Which use case should we start with?

The one that loses you the most money today. For most teams that’s inbound lead routing or demo follow-up.

Do I need to set up every use case?

No. Each works on its own. Most teams start with one or two and add more after a month.

How does lead routing decide who gets a lead?

By rules you set: territory, company size, product interest or round-robin, with a fallback owner if no rule matches.

Can Flow write follow-up emails?

Yes. It drafts recaps from meeting notes and the deal record. Reps review and send — nothing goes out unreviewed.

When is a deal considered stalled?

When it has no activity for a number of days you set per stage. The default is 10 days.

How does the quote-to-invoice handoff work?

When a deal is marked won, Treepie Books creates the invoice from the quoted line items, tax and payment terms. You need Books for this step.

What happens to deals when a rep leaves?

A manager bulk-reassigns deals, tasks and sequences. All history moves with the deal.

Can Flow manage renewals?

Yes. It creates renewal deals ahead of contract end dates and reminds owners at intervals you choose.

Does Flow track partner-sourced deals?

Yes, with deal registration, duplicate checks, protection periods and partner pipeline reports.

Can we try a use case on our own data?

Yes. Import a CSV during the 14-day free trial, or book a walkthrough and we’ll set up your first use case with you.

Treepie Flow · CRM & sales

What happens next, for every deal.

Eight jobs sales teams repeat every week. Pick one and watch what Flow does, step by step.

flow.treepie.co/deals

TriggerA demo request arrives from a 40-person company in Leeds.

1FlowEnriches the lead and matches it to the UK mid-market territory
2FlowAssigns Priya by round-robin and starts a 15-minute response timer
3PriyaCalls from the lead card; the call is logged automatically

With FlowFirst reply in 9 minutes, not the next morning.

WithoutSits in a shared inbox until someone notices it.

In short

What are the main CRM use cases for Treepie Flow?

Treepie Flow covers the jobs a sales team repeats every week: routing new leads to the right rep, following up after meetings, spotting deals that have gone quiet, running the forecast, turning won deals into invoices and onboarding tickets, handing over accounts, and working renewals. Each use case runs on its own, so teams start with the one that loses them the most revenue.

Use cases: 8, grouped by stage
Start with: One, live in a day
Connects to: Books, Desk, Pulse
Who runs it: Reps, managers, ops

By stage

Every use case, from first touch to renewal.

Grouped by where the deal is. Each one works on its own.

01Capture

Route inbound leads in minutes

First reply in 9 minutes, not the next morning.

Track partner and referral deals

Partners trust that their deals are protected.

02Qualify

Follow up after every demo

Every demo gets a written recap the same day.

03Close

Rescue deals that have gone quiet

Quiet deals surface before they’re lost, not at quarter end.

Run a forecast call from one screen

Forecast calls are 30 minutes and focus on what moved.

Turn a won deal into an invoice

Billing starts the day the deal closes, with no retyping.See the steps →

04Keep

Hand over accounts when a rep leaves

No deal loses its history or its next step.

Never miss a renewal

Renewals are worked a quarter ahead, with support context.See the steps →

Why it works

Most CRMs store deals. These jobs need something to happen.

Each use case is a trigger, a rule and a person. Flow handles the first two so the person only does the part that needs judgement.

Triggers, not reminders

A lead arrives, a meeting ends, a deal goes quiet, a contract nears its end date. Flow watches for each one.

Rules you can read

Routing, stall days and renewal intervals are plain settings, not scripts. Ops can change them without a developer.

Drafts, not auto-sends

Flow drafts follow-ups and re-engagement emails. A rep always reviews before anything reaches a customer.

One record downstream

Won deals become Books invoices and Desk tickets from the same data, so nobody re-keys a quote.

In practice

One week, five use cases, one team.

How a six-person sales team in Manchester uses Flow from Monday to Friday.

Mon

Digest3 stalled deals flagged; manager reassigns one.

Tue

Routing14 inbound leads, all answered within 20 minutes.

Wed

Follow-up6 demos, 6 recaps sent the same afternoon.

Thu

Forecast30-minute call on the 9 deals that moved.

Fri

Won → invoice2 deals closed; Books invoices sent before 5pm.

Illustrative week based on a typical customer setup.

Connects

Use cases that cross into other Treepie apps.

Flow works alone. These get further with a second app on the same record.

Books

Quote to invoice

Won deals create invoices with the quoted items, tax and terms. Payment status shows on the deal.

Desk

Renewals with support context

Open tickets and satisfaction appear on renewal deals, so owners know the risk before they call.

Pulse

Website leads, qualified

Pulse answers visitor questions, captures the lead and passes the conversation into Flow for routing.

Where to start

Start with the leak, not the feature list.

Answer one question. It points to the use case that recovers the most revenue first.

“Leads wait hours for a first reply”Route inbound leads

“Good demos don’t turn into next steps”Follow up after every demo

“Deals slip and nobody notices until quarter end”Rescue stalled deals

“Finance chases sales for what was sold”Won deal to invoice →“Customers cancel before anyone calls them”Never miss a renewal →

More Flow use cases, end to end

6 published

Who it’s for

Which use cases each role relies on.

The same deal record, seen from four seats.

Sales repsRouted leads, drafted follow-ups, a clear next step on every deal.“What do I need to do today to move my deals?”

Sales managersStalled-deal alerts, a forecast that shows movement, clean handovers.“Which deals changed since last week, and why?”

Revenue operationsRouting rules, stage definitions and partner registration in one place.“Did every inbound lead get a reply within SLA?”

FoundersPipeline, won revenue and renewals without asking anyone.“How much renews next quarter, and what’s at risk?”

Compared

Running these jobs, compared.

Category-level differences across the eight use cases.

	Spreadsheets & email	Typical standalone CRM	Treepie Flow
Lead routing	Shared inbox, manual	Rules, often a paid add-on	Rules with response timer, all plans
Follow-ups	From memory	Templates	Drafted from meeting notes
Stalled deals	Found at quarter end	Report you build	Flagged by stage, in the digest
Won to invoice	Re-keyed by finance	Integration to maintain	Books invoice from the quote
Renewals	Calendar reminders	Separate module	Renewal deals with Desk context

Use cases, answered.

Anything else — ask a person.

Capturing and routing leads, following up after meetings, managing pipeline, forecasting, quoting, handing won deals to finance and support, renewals and partner deals.

Pick one job. Have it running by Friday.

Book a walkthrough with your top use case in mind. We’ll set it up on your data during the call.

Start free with Flow →Book a walkthrough

Your first use case in four steps

Day 1Pick the costliest gapUsually routing or follow-up.
Day 1Import your dealsCSV or from your current CRM.
Day 2Set the rulesTerritories, stages, stall days.
Week 1Review and add the nextCheck the digest, then expand.

The other sixCompare all →

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

What happens next, for every deal.

Eight jobs sales teams repeat every week. Pick one and watch what Flow does, step by step.

What are the main CRM use cases for Treepie Flow?

Spreadsheets & email

Typical standalone CRM

Treepie Flow

Lead routing

Shared inbox, manual

Rules, often a paid add-on

Rules with response timer, all plans

Follow-ups

From memory

Templates

Drafted from meeting notes

Stalled deals

Found at quarter end

Report you build

Flagged by stage, in the digest

Won to invoice

Re-keyed by finance

Integration to maintain

Books invoice from the quote

Renewals

Calendar reminders

Separate module

Renewal deals with Desk context