Inside Guide: what it watches, when it acts, and who approves
Guide (PrescientIQ’s trial conversion agent) monitors in-product events, flags the trial accounts that stall before their key value event, and prepares a personalized activation sequence at the stall moment. Every sequence is held for a named person’s approval before it sends. The trigger is the account’s behavior, not the calendar, and the intervention happens while the trial is still open.
In a product-led motion the most expensive moment is one nobody is watching. A trial signs up, gets partway toward the thing it came for, and stops. The product dashboard records the stall. The lifecycle tool keeps sending day-three and day-seven emails on schedule. The growth manager finds out at the end of the trial, in an exit survey or a conversion report, when the account has already decided. We described the pattern from the buyer’s side in why PLG funnels leak before the aha moment. Guide is built for that moment.
This is what it does, who it is for, where it runs, how the approval gate works, and when it is the wrong thing to buy.
What, who, where, how, and when
A digital worker that watches every trial account’s in-product behavior, identifies the ones that stall before their value event, and prepares a personalized activation sequence at that moment for a named person to approve. Not a lifecycle drip, and not a dashboard that reports the stall after the trial has ended.
Growth and product-led sales leaders at mid-market SaaS companies with a free trial or freemium motion, the RevOps leader who owns the CRM it writes to, and the people who will review the queue.
Against Salesforce or HubSpot, reading product event data for trial accounts, under your brand. The scope is published rather than discovered during implementation.
A trial’s events are compared with the expected path to the value event. When an account diverges, Guide flags the stall, prepares a sequence grounded in what that account did and did not do, stores the reasoning with it, and holds it in the approval queue. Only an approved message is delivered, and the decision is recorded.
When you know what the value event is and can see trials missing it, when the window to act is days and the people who would act are full, and when someone will own the approval queue. Not before the value event is defined, and not as a substitute for fixing a broken onboarding path.
The value event, and why the stall is the unit of work
Every trial has a moment where the user first gets what they came for: a data source connected, a teammate invited, a first report run, a first workflow completed. Product teams call it the value event or the activation milestone. Everything before it is a path, and most trial loss happens on that path, not after it.
A stall is a divergence from that path: an account that signed up on Monday, completed step two on Tuesday, and has not logged in since. On a chart it is a flat line. To Guide it is the unit of work. The agent compares each trial’s events with the expected path, flags the divergence as it happens, and prepares the sequence that fits what that account did and did not do. An account that stalled before connecting data gets a different sequence from one that connected data and never invited anyone.
How the approval gate works
Each prepared sequence arrives in the queue with the stall signal that produced it and the reasoning behind the angle. The reviewer, usually whoever owns trial conversion, decides whether the reason holds: approve, edit, or reject. An edit is captured as feedback. Only an approved message is delivered, and the decision is written to the ledger with the approver behind it.
Your team sets the governance mode for each class of action:
Human-in-the-loop (HITL). The action is drafted and held. It does not execute until a named person on your team approves it.
Human-on-the-loop (HOTL). The action executes under a standing policy your team sets. A named person supervises and keeps intervention, override, and revocation authority.
Your team chooses the mode for each action class, based on its risk tolerance, and can change it at any time.
Every action, in either mode, is recorded to the audit ledger with its rationale, before-and-after state, and the approver or policy behind it.
Every action class starts in human-in-the-loop until your team changes it.
In practice, teams raise the ceiling first on internal actions such as scoring a trial or writing a stall flag to the CRM, because an error there lands inside the company and is reversible from the ledger. Customer-facing sends stay held for a named person’s approval. Each agent runs under its own least-privilege identity, enforced by permissions and not by prompt instructions. Entitlements can be listed, and an agent can be revoked without disabling a person.
Key value propositions
Acts at the stall, not at the exit survey
Trial loss is visible in the product dashboard and usually acted on after the trial ends. Guide moves the intervention to the moment the account diverges from the activation path, while the trial is still open.
Grounded in the account’s own behavior
The sequence is written against what this account did and did not do, with the stall signal stored alongside the draft. The reviewer approves a documented reason, not a template with a merge field.
Held for a named approver
No customer-facing message leaves without a person on your team approving it. The queue is the control, and the control is enforced in the architecture rather than written into a prompt.
Recorded end to end
Every action, in either mode, is recorded to the audit ledger with its rationale, before-and-after state, and the approver or policy behind it. A trial that converted, or did not, can be traced back to what was sent, why, and who approved it.
One fee, all four agents
Guide is one of four specialist agents on the Revenue Accelerator platform fee, with Scout, Herald, and Steward, under one coordinator, Marshal. Adding reviewers does not change the fee.
What MatrixLabX targets, and how it is labeled
One figure is registered for this agent, and it is scoped on purpose. It applies to the trials Guide intervenes on before a stall, not to a funnel as a whole, and it is a target modeled against current baselines rather than a measured result at your company.
Figures labeled as targets are modeled against current human and copilot baselines. They are not guarantees. Every engagement begins with a free Autonomous Audit Report — a P&L projection built on your own data — and targets are validated against your environment before any commitment.
Where is your trial funnel actually leaking?
“Trials do not convert” resolves to one of four different problems with four different fixes, and only one of them is the case Guide is built for. This routes you to the right starting point.
What is actually happening to your trials?
What it does not do
It does not send without a named person’s approval. It does not fix onboarding: a broken path to value produces more stalls, and Guide will report them, but the repair belongs to the product team. It does not find the account; that is Scout, and the outreach that brought the trial in is Herald. And it does not handle what happens after conversion, which is Steward.
Where the data runs
PrescientIQ is hosted and operated by MatrixLabX on Google Cloud. SOC 2, ISO 27001, and PCI DSS attestations are held by Google Cloud, which operates the underlying infrastructure. They are not MatrixLabX certifications. MatrixLabX application-layer SOC 2 is in progress.
What it costs
Guide ships as one line of the full Revenue Accelerator platform fee. On our pricing page it is listed as “Guide · Trial Activation Specialist,” alongside Scout (prospecting), Herald (outbound), and Steward (expansion), under one published rate:
| Component | Investment | Billing frequency |
|---|---|---|
| Annual platform feeEnvironment provisioning on Google Cloud, per-agent IAM, audit-ledger setup, and context ingestion from your CRM — plus four cooperating agents (Scout, Herald, Guide, and Steward), their coordinator Marshal, the approval queue and standing-policy controls, and the immutable audit ledger, and the monthly execution volume a typical mid-market deployment runs. One fee, from signature, every year.Target — modeled: live in 21 days or less$165,000/year is the complete platform fee. There is no separate implementation charge and no different first-year number — deployment work is included from signature, not billed as a distinct line. Scope beyond a typical deployment — additional bundles, sustained higher volume — is quoted at your AAR before anything is signed. | $165,000/yr | Billed monthly at $13,750/mo against an annual commitment |
Frequently Asked Questions
- What does Guide actually do?
- Guide is PrescientIQ’s trial activation specialist. It monitors in-product events for every trial account, identifies the accounts that stall before reaching their key value event, and prepares a personalized activation sequence at that moment. Each sequence is held in the approval queue until a named person on your team approves, edits, or rejects it.
- Does Guide send messages to trial users automatically?
- No. Every customer-facing message Guide prepares is held for a named person’s approval before it goes out, and every send is recorded to the audit ledger with the approver behind it. Internal actions such as scoring a trial or writing a stall flag to the CRM can run under a standing policy your team sets.
- What is a value event, and why does the stall matter?
- A value event is the in-product moment where a trial user first gets the outcome they signed up for, such as connecting a data source, inviting a teammate, or completing a first workflow. Most trial loss happens before that moment. A stall is the gap between the expected path and what the account is actually doing, and it is only useful if someone acts while the trial is still open.
- What data does Guide need?
- Product event data for trial accounts, a CRM record for each trial in Salesforce or HubSpot, and a definition of the value event and the expected path to it. If the value event is not defined, the first implementation step is defining it with your product and growth teams, not deploying the agent.
- How is this different from a lifecycle email tool?
- A lifecycle tool sends the same sequence to everyone on a fixed schedule from signup. Guide acts on the specific account’s behavior at the specific moment it diverges from the activation path, prepares a sequence grounded in what that account did and did not do, and holds it for a person. The trigger is the stall, not the calendar.
- What result does MatrixLabX target for trial conversion?
- The registered target is a +38% lift in trial-to-paid conversion, scoped to trials that Guide intervenes on before a stall. It is a target modeled against current baselines, not a guarantee, and every engagement begins with a free Autonomous Audit Report that models the figure on your own trial data before any commitment.
- Who reviews the activation sequences?
- Usually whoever owns trial conversion: a growth manager, a product-led sales rep, or an account executive in a sales-assisted motion. Review is approve, edit, or reject on a queue, with the stall signal and the reasoning attached to each draft, so the reviewer is judging whether the reason holds rather than rewriting copy.
- What does Guide not do?
- It does not fix onboarding. If the product path to value is broken, Guide surfaces more stalls faster, which is useful diagnostic data but not a conversion fix. It does not send without approval, it does not find the account in the first place, and it does not handle post-sale expansion, which is Steward’s job.
Related Reading
- Inside Steward (the stage after this one)
- Inside Herald (the stage before this one)
- Buyer Intelligence vs. Decision Intelligence Across the SaaS Buying Cycle
- The 2027 RevOps Survival Blueprint
- Human-in-the-Loop vs. Human-on-the-Loop: Setting the Autonomy Ceiling for Each Revenue Action
- PrescientIQ for SaaS
Notes on this post
Product statements match the current public copy on the pricing and Revenue Accelerator pages. The one figure on this page renders from the site’s governed claims register with its proof class and scope shown; no funnel-wide conversion figure is stated. The quotation is George Schildge’s, in a form he supplied for this series. No comparison is made with any named product.
See where your own execution effort is going
The Autonomous Audit Report models where your team's execution capacity is currently spent, what your configuration is actually paying for, and what the governed alternative looks like on your own data — before any commitment.
Get your free AAR benchmark