THE BIGGER PICTURE
Know what’s working.
See what’s next.
Most teams review the week by asking five people how it went. The answers are honest and wrong, because nobody counts their own lost leads. Reporting is only worth reading when it is measured rather than remembered.
01 — IN ONE LINE
Numbers read straight off the real pipeline, so the weekly review stops being a memory test.
And, just as usefully, what it is not:
- Not a wall of charts nobody opens. A handful of numbers that change a decision beats forty that do not.
- Not a scoreboard for punishing people. Response time is usually a staffing problem, not an effort problem.
- Not a forecast. It tells you what happened and what is open, not what will close.
02 — HOW IT ACTUALLY WORKS
Six steps,
in order.
- SourceIt counts what actually arrived
Every conversation is a countable event, so lead volume by channel is a fact rather than an impression.
- SpeedFirst response is timed automatically
Measured from the customer’s message to the first real reply. Nobody logs it, so nobody can round it down.
- StagesMovement is read off the board
Because the pipeline fills itself, the conversion rate between stages reflects what happened rather than what was tidied up before the meeting.
- PeoplePer-person, with context
Volume, response time and outcomes by owner — useful for spotting who is drowning, not just who is behind.
- LeaksIt shows where leads stop
Ageing in a stage and threads with no next step are the two numbers that most often pay for the software.
- ReviewOne screen, every Monday
The point is a short meeting about four specific leads, not a long meeting about how everyone is feeling.
03 — IN DEPTH
What it does,
and what you decide.
Lead volume by source
Which channel and which campaign actually produced conversations, not clicks.
You controlSources are tagged on arrival; you decide the tagging scheme.
Response time
First-response time per channel, per person and per hour of day.
You controlYou set business hours so out-of-hours waits are reported separately.
Conversion by stage
Where leads advance and where they stall, read off the pipeline your team actually works.
You controlStages are yours, so the funnel matches your process.
Per-person performance
Volume handled, response time and outcomes by owner.
You controlVisibility of other people’s numbers is a permission.
Ageing and stalled leads
What has been sitting too long, and what has no next step booked.
You controlYou define what counts as too long, per stage.
Export
Get the underlying rows out when someone wants to do their own analysis.
You controlExport is a permission, because it is customer data leaving the system.
04 — SEE IT MOVE
Try the mechanic,
not a video of it.
Switch the period. Four numbers that change a decision, rather than forty that do not.
Switch the period. These are sample figures, shown to explain the shape of the report.
05 — WHAT YOU CONTROL
Your settings,
not our defaults.
So an overnight wait is not counted as a slow reply.
How incoming conversations are attributed to a campaign or channel.
How long a lead may sit in each stage before it is flagged.
Whether agents see the whole team’s performance or only their own.
A fixed list, so “Lost” is something you can act on next quarter.
Who may take customer data out of the system.
06 — WHAT IT DOES NOT DO
The honest list.
Every tool has one. Most vendors keep it for the sixth week of the implementation, which is a worse time to read it than now.
- It can only measure conversations that came through Flowlines. Replies sent from a personal phone are invisible to it, and will quietly flatter your response time.
- Attribution stops at the conversation. If someone saw an ad, asked a friend, then messaged you, it will record the message.
- It does not forecast. There is no projected-revenue number, because an honest one would need history you do not have yet.
- Revenue figures are only as good as the values your team enters on the deal.
- In the first month the numbers will look worse than reality, because the old process was never measured at all. That is the point, but it is worth warning the team.
07 — GETTING IT LIVE
What the first
two weeks look like.
- Day 1Set business hours
Without them, every overnight enquiry makes your response time look terrible.
- Day 1Agree the closure reasons
A short fixed list. “Other” should be rare.
- Week 1Pick the four numbers you will actually use
Usually volume, first response, stalled leads and conversion. Ignore the rest for now.
- Week 2Run one Monday review off the screen
If the meeting does not change what anyone does that week, the wrong numbers are on it.
- Month 2Compare against month one
The first month is the baseline, not the verdict.
08 — WHERE IT SITS
It is one part
of one system.
Conversion and ageing are read directly off the pipeline, not re-entered.
Response times are measured from real message timestamps.
You can see what the agent handled alone and what it escalated.
Run history shows which sequences actually moved leads forward.
09 — QUESTIONS
What teams
actually ask.
Can we see it by team member?
Yes. Whether each member can see everyone else’s numbers is a separate setting, and worth deciding deliberately.
Does it count out-of-hours messages against us?
Not if you set business hours. Out-of-hours waits are reported separately, which is also the clearest argument for the AI agent.
Can we export it?
Yes, subject to permission. It is customer data, so not everyone should be able to take it out.
Will it tell us our revenue forecast?
No. We would rather not put a number on the screen that we cannot stand behind.
Why do our numbers look bad in month one?
Because they were never measured before, not because the team got worse. Use month one as the baseline and warn people in advance.
Can we get a weekly summary?
Ask in the demo — we will tell you what exists today rather than what is planned.
LET’S KEEP THE CONVERSATION GOING
Bring us the process
you already run.
We will map it into Analytics live, and tell you honestly which parts fit and which do not.
- 5 minYou show us how the work happens today
- 10 minWe build it in front of you
- 5 minYou keep the diagram, either way
