Skip to content
  1. Home
  2. Insights
  3. Deals take longer to close
Funnel analysis

Deals take longer to close

Spots that clearly more days now pass from a request to a sale than before. Leads of two neighbouring quarters are compared, and both get the same time for sales, so long deals of fresh leads are not lost. If the extra time builds up on one funnel stage, the card names it. It also looks at channels and managers: whether the cycle grew for one of them or for all, and whether more sales now come from where deals were always slower.

Funnel analysis

Deals take longer to close

From request to sale it now takes 32.3 days instead of 18.9, 71% longer

Next step: Open the deals on the “Sell the package” stage that stay there longer than usual and find out what they wait for: the client’s answer, a document, an approval, a free manager. If the wait is on your side, set a time limit for the stage and a reminder. If the client is waiting, add a contact that moves them on.

An example of an insight card. The numbers are made up: in the product, the card shows the numbers of your project. What is inside an insight ↓

When you see this card

  • Deals started to close slower, even if the share of sales did not fall
  • The card shows on which stage the waiting builds up, or says that the whole funnel got slower

What it needs

  • A connected CRM
  • A funnel stage marked as won
  • A few months of sales history

Result type

  • Likely a likely problem, worth checking

Questions it works on

The same idea elsewhere

  • Cohort analysis
  • Speed to lead
  • Theory of Constraints · E. Goldratt

Leads are split into cohorts by the date of the request, and for each cohort the days to the sale are counted within the same time limit. The medians are compared with a rank test, and the extra time is split by funnel stages to find where the waiting builds up.

What is inside an insight

The card is a short conclusion. A click opens the breakdown: what the conclusion stands on and how far you can trust it.

  • What we know

    Facts with numbers and their source: what changed, by how much, compared with what.

  • Where exactly

    The channels, campaigns, managers or stages where the change is strongest, with a link to the report.

  • Cross-check

    The conclusion is checked against a second signal: confirmed, not confirmed or cannot be checked. Plus what else changed on the same days.

  • We assume

    Likely causes. A hypothesis is labelled as one and never passed off as a fact.

  • We forecast

    Where the period ends if nothing changes.

  • What to do

    The step, what it gives, how to check the result, and the cost of doing nothing.

  • For

    Owner, analyst or agency client: each role sees the cards in its own order.

  • More than one condition behind a card

    To raise one card, KO goes through the slices of your project, including the fields of your CRM, and compares them with the norm of your own project, adjusted for season, holidays and working days. The conclusion is checked against a second signal. When KO finds the root cause, its effects do not show up as separate cards: you see the cause, not ten symptoms.

Demo

Imagine your project is already in KO

The demo is the project of a made-up company, with ads, website and CRM already connected. Open “What to do now” to see what your insights would look like: each with its breakdown, result type and who it is for.

See it live

No sign-up, no payment

See where your revenue comes from

See what to cut, fix, and scale — using your real data.

Vitaly, co-founder of KO
Vitaly Product & sales
Azat, co-founder of KO
Azat Engineering

You'll meet the founders, not a sales rep — we built KO after years of running growth on broken numbers.

Book a free demo

One business day to schedule. No spam.

Please enter your first name.
Please enter your last name.
Please enter a valid phone number.
Please enter a valid email address.
Please enter your company name.
Please select your role.

By submitting this form, you agree that KO may contact you as described in our Privacy Policy.