Sales Cycle Analytics
Read V2's Sales Cycle card on Reports: the lead-to-close milestone chain, real per-pipeline stage velocity, time to first view, best send day, and lost reasons.
Sales Cycle Analytics
Open Business > Reports, then the Sales Cycle card, or go straight to /reports/sales-cycle. It has its own page and report-tab entry, and measures how quickly leads moved through to a close in the selected range, and where they stalled.
Lead-to-Close Milestone Counts
V1 read the funnel off one fixed 7-stage pipeline. V2 pipelines and stages are configurable per org, so there is no single stage ladder every workspace shares. This card instead counts six real milestones every lead can pass through regardless of which pipeline it is in:
- New Lead — leads created in the range
- Appt scheduled — leads with a booked appointment
- Est. created — leads with a drafted estimate
- Est. sent — leads whose estimate was delivered
- Accepted — leads who accepted the estimate (V1's separate "Approved"
and "Converted" stages both collapse into this one milestone; acceptance is the one event that makes a deal won)
- Deposit collected — leads with a first successful payment
Average Days per Stage
A list shows the average days between each pair of adjacent milestones above (New Lead to Estimate Created, and so on), each with its own sample count. Appointment-scheduled is a count only, not part of this chain, because scheduling an appointment is a date field, not a stage-transition event.
| What to Look For | What It Means |
|---|---|
| Long time to "Est. Created" | Your team is slow to make first contact |
| Long time to "Est. Sent" | Estimates sit in draft too long before sending |
| Long time to "Accepted" | Customers are not responding quickly |
| Long time to "Deposit Collected" | Deposit collection or scheduling is delayed |
Stage Velocity (Real History)
A second list shows average days spent in each of your org's own configured pipeline stages, read from the actual stage-transition history rather than the fixed milestone chain above. V1 fabricated synthetic transitions when its own transitions table was empty; V2 always has real history to read, so this list only appears once your pipelines have transitions to show.
Time to First View and Best Send Day
Time to first view is the average days between sending an estimate and the customer's first recorded view of it. Best send day breaks close rate out by the day of the week the estimate was sent, so you can see whether a particular day tends to close better.
Response-time distribution (how fast the office responds to a new lead) is not available. V2 has no first-contact or first-response timestamp on a lead that is separate from a stage transition, so there is nothing to build the distribution from yet.
Close Rate Trends
A monthly table shows lead count, accepted count, and close rate (won / sent) for each month in the range. V1 charted this as a line; the current report has no charting library, so it renders as a table with the same numbers instead.
A declining close rate signals a problem: rising prices without added value, slower response times, or increased competition. A rising close rate means your sales process is improving; look at what changed and reinforce it.
Breakdown by Estimate Type and by Rep
Two tables break the same lead count, accepted count, and close rate out by estimate vertical (Residential, Commercial, Fleet, Holiday Lights) and by the rep assigned to the lead's estimate.
Sort by close rate to identify your top closer, or watch which vertical closes fastest and which takes longer but tends to be worth more. Use this data for coaching conversations.
Lost Reasons
A list shows decline reasons and their counts for estimates declined in the range, read from the reason recorded when a proposal was declined.
Best Uses
- Use the milestone chain to find where leads actually stall, not just
where a fixed 7-stage funnel assumed they would
- Compare stage velocity across your different pipelines rather than
averaging them together
- Export the card (
sales_cycle) to work rep and estimate-type breakdowns
in a spreadsheet; see Reporting Overview
Related articles
Was this article helpful?
Still need help? Contact support