Published 23 October 2026
START WITH THE GAPS IN THE BUYING JOURNEY
Trials sign up and never get worked. PQLs sit in a dashboard nobody opens. SDR cost per meeting climbs while reply rates fall, and expansion signals surface only at renewal.
This guide describes the workflow design published in Xiilio’s industry playbook. It is not a case study or a claim of achieved results. Access, permissions and the connected systems determine what can be deployed.
- Trial signups and PQLs are never worked because nobody owns the queue
- SDR cost per meeting rises while reply rates fall
- Pipeline reviews rely on rep optimism rather than engagement evidence
- Expansion and churn signals surface at renewal, when it is already too late
MAP THE HANDOVERS BEFORE ADDING AUTOMATION
Write down the decision at each stage, who owns it and what information the next person needs. Qualification is not a substitute for a regulated or commercial decision.
- Problem aware: A team feels the pain, searches, reads comparisons and asks peers.
- Evaluation: Trial or demo. Multiple stakeholders join; the champion builds an internal case.
- Business case: Security review, procurement, budget owner. The champion needs material to sell internally.
- Close and expand: Signature, onboarding, then seat and usage expansion driven by adoption.
TRIAL TO MEETING
Agree these steps with the owning team, test the handovers and review exceptions before enabling the workflow.
- Trial signup creates a CRM record with enrichment from NOVA
- Activation events tracked; inactive trials get an enablement nudge, active trials a value message
- Second qualifying user or key feature activation triggers a meeting offer
- ARIA books directly into the AE calendar
- Outcome written back so activation-to-meeting rate is measurable
STALLED OPPORTUNITY RECOVERY
Agree these steps with the owning team, test the handovers and review exceptions before enabling the workflow.
- CORTEX flags deals with no meaningful engagement for a set period
- Champion-side signals checked: usage drop, job change, new stakeholder
- HERALD runs a re-engagement touch with a reason relevant to the flag
- No response after the sequence returns the deal for a human decision
EXPANSION SIGNAL
Agree these steps with the owning team, test the handovers and review exceptions before enabling the workflow.
- Usage crosses a threshold you define, or a new department appears in the product
- CORTEX raises an expansion alert with the evidence attached
- Account owner approves the play
- HERALD or the AE runs it; result attributed to the signal
CONNECT THE EXISTING STACK, WITH EXPLICIT BOUNDARIES
No rip-and-replace is the starting point. Confirm API availability, permissions, record mapping and failure handling with the system owner. Product names in the playbook describe systems commonly used in this sector; they do not imply a partnership or a prebuilt connector for every installation.
- HubSpot or Salesforce
- Product analytics or event stream
- Stripe or billing
- Slack or Teams for alerts
- Google Ads, LinkedIn Ads and GA4
- Calendar and meeting tooling
KEEP THE APPROVAL GATES VISIBLE
Automation should stop at the boundaries agreed with your team. Record escalations and approval decisions alongside the workflow activity.
- ICP definition and target list signed off before outbound
- Sequence copy approved and version-controlled
- Any pricing or contractual statement requires a human
- Enterprise-tier accounts can be set to per-send approval
MEASURE OUTCOMES, NOT ACTIVITY ALONE
Agree the baseline, reporting period and source of each metric before launch. Reconcile CRM outcomes with your own records; do not treat a modelled return or an advertising dashboard as independently audited revenue.
- Qualified pipeline created per month
- Trial or PQL to meeting rate
- Meeting to opportunity rate
- Customer acquisition cost and payback
- Net revenue retention and expansion pipeline