11plays led
27plays they also work on
14systems in the stack
2/4practices they lead plays in
The systems in the plays Kylee leads, in the order data moves through them. Lime marks the ones that come up most; the number is how many open roles ask for each.
Gong36
Vasco
SlackFrom LeanScale's case studies. Play leads are whoever has spent the most delivery time on that kind of work.
5 steps
Deciding which system owns the MQL, and making the number defensible
A lead count marketing reports on
Lead routing and speed to lead
+1
6 steps
From an empty CRM to enrichment, territories and a live lead-routing engine
Full account base enriched
Attribution
5 steps
Rebuilding a channel taxonomy and the MQL workflows that were never firing
Channel taxonomy rebuilt
GTM lifecycle
6 steps
Rebuilding a sales lifecycle on real conversion data, and enforcing it with stage gates
Stage gating live in production
Lead routing and speed to lead
+1
7 steps
Rebuilding inbound lead and account routing in native CRM flows, then migrating it back
Routing survived a tool outage and a tool return
Attribution
5 steps
Rebuilding lifecycle and attribution under a high-volume self-serve funnel
~800k contacts re-lifecycled
Attribution
6 steps
Replacing weekly manual dashboard clean-up with nightly correction flows
Manual dashboard clean-up retired
Executive reporting
6 steps
Retiring the spreadsheet: computing marketing's sourced and influenced share natively
Sourced and influenced shares now compute natively
Lead routing and speed to lead
+1
7 steps
Splitting systems delay from human delay: a working-hours speed-to-lead SLA
A one-hour SLA that actually runs
Lead routing and speed to lead
7 steps
Two years of holding an inbound routing chain together: scheduler, routing engine and two synced CRMs
Routing behaviour became explainable
Attribution
+2
6 steps
When a picklist rename silently broke a dozen pipeline reports
12 silently-broken reports found and fixed
