Months 1–3
25–35Profiles optimised, content calendar live, targeting proven and the first sequences running at full volume. Expect the first booked calls from week three or four.
Qualified demo leads
Results / line 01, lead generation
What the numbers should look like.
The figures on this page cover the first twelve months of a three-profile lead generation program. They are ranges from programs of this shape and volume, not guarantees. We publish the same numbers every month, including the ones that go the wrong way. How the other three lines are measured is at the bottom of the page.
Lead generation: expected ranges
Ranges from comparable programs. Not a guarantee.
25–35
Qualified demos in months 1–3
40–60
Qualified demos in months 4–6
20–30%
Connection acceptance rate
8–15%
Reply rate on outreach
Quarter by quarter
The first quarter buys the base: profiles, proof and a list tested against real replies. The compounding shows up from the second, then settles into a steady run rate.
Months 4–6
40–60Wider reach, sharper sequences and an audience that already recognises the name. Volume scales on the segments and messages that worked.
Qualified demo leads
Months 7–9
50–70The first list is largely worked, so growth comes from new segments, a refreshed list and warm prospects returning. Content published earlier starts producing inbound replies on its own.
Qualified demo leads
Months 10–12
55–80The engine is steady rather than accelerating. Gains come from adding a market or a profile, referrals from earlier conversations, and nurture tracks converting on their own timeline.
Qualified demo leads
Ranges assume three activated profiles throughout. Two profiles produces proportionally less; five or more produces more, across more markets. Growth flattens after the second quarter because the addressable list is finite. From month seven onward, increases come from widening the list, adding profiles or opening a new market rather than from the same audience working harder.
What counts as a qualified demo
Agreed in writing before the program starts, so there is no argument at the end of the month.
It counts when
- The person holds or influences the budget
- The company matches the agreed firmographic filters
- They have accepted a specific time in your calendar
- They know what the call is about
It does not count when
- The reply is positive but no time is booked
- The company is out of the agreed profile
- The contact is a student, vendor or job seeker
- The meeting is a repeat of an existing opportunity
KPIs we report on
| Metric | Target range | Why we track it |
|---|---|---|
| Connection acceptance | 20–30% | Share of requests accepted. Falls when targeting drifts, so we watch it weekly. |
| Reply rate on outreach | 8–15% | Replies as a share of accepted connections, positive and negative both counted. |
| Discovery calls booked | Monthly target | Agreed with you at the start of each month against your capacity to take calls. |
| Qualified demo leads | 25–35 → 40–60 | Q1 then Q2 on a three-profile program. The number the program is judged on. |
| Content impressions | Month on month | Reach of published posts, tracked as a trend rather than a target. |
| Profile views and followers | Authority signal | Leading indicator that content is landing with the right audience. |
| Pipeline value influenced | Reported monthly | Value of opportunities that started with a CYTEQ conversation. |
| Cost per qualified demo | Tracked | Your total programme spend divided by demos booked, reported every month. |
How reporting works
Weekly snapshot
- Requests sent and accepted
- Replies received and handled
- Calls booked this week
- Posts published and their reach
- Anything blocking us
Monthly review
- Every KPI against its range
- Which segments and messages performed
- What we are cutting and what we are scaling
- Pipeline value influenced to date
- The written plan for next month
Acceptance and reply rates depend on your market and offer as much as on execution. If a range is not being met, the monthly review says so and explains what changes.
How the other three lines are measured
Demos are the wrong yardstick for infrastructure and software work, so each line is judged on something it can actually control.
GTM engineering
Measured on data and timing rather than volume: how much of the target list is enriched and routable, how quickly a buying signal turns into an approach, and how clean the CRM stays.
- List coverage and match rate
- Signal-to-outreach time
- Duplicate and stale-record rate
- Reply rate lift versus the baseline
AI workflow automation
Measured on hours removed and errors avoided. We baseline how long a process takes before the build, then report against that number every month.
- Hours saved per month
- Manual touches removed
- Response and turnaround times
- Workflow success and failure rate
Custom software and AI products
Measured on delivery and stability. Scope agreed up front, progress shown in working software weekly, and quality tracked after release rather than declared at handover.
- Scope delivered against plan
- Release cadence
- Defects found after release
- Uptime and performance
Whatever the line, the measure is agreed in writing before work starts. If we cannot define how something will be judged, we say so rather than invent a metric.
See the numbers against your own pipeline.
Tell us your average deal size and close rate and we will show you what this volume of demos is worth to you, alongside a scoped proposal.