Name what an account did — usage measured against the entitlement it actually holds — and let the motive stay unnamed, then hand the signal to the growth manager who qualifies it.
A signal is raised, and the usage under it travels with it rather than being summarised away.
02
Usage crosses a line, and the line it crossed is named beside the entitlement record it came from.
Reason
03
A signal says what was observed, and it stops there instead of guessing at why anyone did it.
04
Usage climbs on retries, and the signal says so rather than reading a failing job as appetite.
05
An entitlement record is old, and the signal carries the day it was read instead of implying it is live.
Decide
06
A signal is raised on a trial, and the terms the customer was actually given are carried beside it.
07
Usage lands under a subsidiary, and the signal names the legal entity it was measured on.
Out
08
A signal cannot be attributed to anyone, and that is written up as a gap rather than assigned to a team.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
Watching entitlement against use, raising the signal and showing the unknowns belong to the agent. Deciding an account is ready to buy belongs to a named growth manager, who qualifies it and owns that call.
Example workflow
One signal, usage to qualification
AgentHuman
1Usage and entitlement receivedProduct telemetry, seat and API records, entitlement terms, order forms and billing history
2Entitlement fixed and datedThe limits the contract sets, the limits the system enforces and the day each record was read
3Signal raisedThe observation, the usage under it, the entitlement it was measured against and confidence
4Controls appliedEntitlement checks, retry checks, attribution checks and signal confidence
No human action required
Stages 1 to 4 run unaided, and no customer is approached at any of them — the agent is observing, and the growth manager lane opens at the entitlement gate.
5DecisionSplits at the entitlement gate
Entitlement current
Goes to the named growth manager to qualify.
Anything stale
Adds a senior growth read first.
Growth manager review
The signal is held with its usage, the entitlement it was measured against and what it cannot say.
Accept · Annotate · Send to senior review
Accepted — by the named growth manager▼
6Account and expansion records updatedOnly where write access and records policy allow it
7Outcome evaluatedEntitlement accuracy, attribution quality, manager corrections and what review found
Corrections
Each growth manager correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Qualifying a signal as an opportunity.
Pricing anything an account might buy.
Contacting a customer about their usage.
Deciding an account is ready to buy more.
Automation boundaryAgent acts unaided
✓Raise the signal and carry the usage under it.
✓Separate usage that came from retries from usage that came from people.
✓Mark the day each entitlement record was read.
✓State plainly what the signal cannot say about why usage moved.
No customer is approached except by a named growth manager, inside the agreed boundaries.
Judging why usage actually moved.
Telling a seller an account will expand.
Choosing which limit an account is sold up to.
Changes to the thresholds, terms or entitlements.
Example output
One expansion signal, annotated
This serves a growth team who may have to explain to an account team why a signal was raised at all; below is one signal exactly as the agent leaves it.
Expansion signal · single accountIllustrative example
Account
Recorded as
Usage
Evidence of record
Confidence
Held for
Mid-market, seat-based plan
Raised, entitlement dated
Usage carried
Entitlement read 3 August 2026
Held unqualified
The named growth manager
As receivedTaken from the usage recorded and the entitlement it was measured on, and it concludes nothing beyond that.
What the record holdsSeat recordsAPI call volumeEntitlement terms
Why no approach hereCalling a signal an opportunity is a judgement the manager makes.
ActionAcceptAnnotateSend to senior review
What the score decidesBelow the configured threshold a signal gets a senior read before the manager sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every signalFrom the usage under it
03Evidence
Where the entitlement comes from
An ancillary-offer agent in travel and hospitality presents an offer to a guest at the point of sale. This raises a signal for an internal team and presents nothing to anyone.
01Approved path
Usage is not intent
An account near a limit may be buying more, leaving, hearing from its own procurement team or refactoring what it built, and the usage reads alike in all four.
02Human review
What was checked, and not found
Checked and not found: no statute or published standard governs when a vendor may read its own telemetry for commercial ends, so there is no external rule to point at and this page claims none.
04Build an evidence trail
The signal, the usage under it and the manager who qualified it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Product telemetryPendo · Amplitude · Snowplow Seat activity and API call volume
Entitlement and billingZuora · Chargebee · Stripe Plan limits and overage terms
CRM and account recordsSalesforce · HubSpot · Gainsight Contract terms and account tiering
Agent
Expansion signal detection
Reads the usage Raises the signal Holds for the manager
Support and ticketingZendesk · Statuspage · Jira Throttling errors and limit complaints
A product-level qualification figure can read clean while accounts driven by API use carry most of the corrections. Nestack reports the correction rate by product line, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Accounts with API-driven use
8.6%
3.7×
Review
Multi-entitlement estates
6.1%
2.6×
Review
Accounts inside a trial
3.8%
1.6×
Watch
Established single-plan accounts
2.1%
0.9×
Normal
Bar: correction-rate lift vs. single-plan-account baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a scripted seat ceiling costs
The loop shuts when the signal raised on nothing is a standing case. That suite is what the next signal qualified is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on accounts with API-driven use.
02Diagnose
The team that hit the seat ceiling because one person wrote a script against the API is worked backwards until one cause is left standing.
03Improve
A change goes out numbered, and the signals that forced it travel with it.
04Verify
Nothing ships while one signal case remains red.
05Learn
The case is kept, and the qualification rules are amended in that same commit.
Learn → DetectThe return edge. The next signal raised is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, signal detection, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Entitlement-inventory and automation-boundary work.
02Telemetry, entitlement and billing sources.
03Usage-to-entitlement and threshold-source mapping.
04Usage ingestion and entitlement checks.
05Entitlement, threshold and account binding.
06Attribution scoring and review routing.
07Growth manager review workflow.
08Entitlement-system integration.
09Signal and qualification cases.
10Guardrails and qualification controls.
11Signal-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne product line, one quarterProductionProduction growth workflowAdvancedMultiple products / regions
Introduced at Pilot
Signal detection to your entitlements✓✓✓
Named growth manager release✓✓✓
Entitlement-and-usage baseline✓✓✓
Introduced at Production
Reporting by product—✓✓
Manager review workflow in your systems—✓✓
Approved write-back—✓✓
Entitlement-system integration—✓✓
Introduced at Advanced
Multi-entitlement rule sets——✓
Cross-product signal packs——✓
Large account estates——✓
Multi-entitlement signal controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, entitlement volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your live accounts and the entitlement each holds→Usage capture and entitlement checksWeek 1
02Representative accounts, including ones that churned→Entitlement binding, threshold logic and the signal baselineWeek 2
03Your expansion cadence and the managers it names→Entitlement mapping, threshold review and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Telemetry, entitlement and billing source assessment, then integration setupWeek 2
05Signals you would not want qualified→Qualification cases and the evaluation runWeek 4
06What no signal may promise→Attribution scoring, review routing, guardrails and release controlsWeek 3
07A named growth manager who qualifies it→Release to the named growth manager, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Six weeks measured out rather than six columns ruled; the fifth doubles up because the work does.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Entitlement discovery, threshold review and the automation boundaryW2Source integration and the entitlement-and-usage baselineW3Signal detection, attribution logic and release controlsW4Evaluation suite, signal cases and the qualification runW5Growth-platform integration, pilot signals and targeted correctionsW6One expansion quarter run under the growth lead, then Agent Care handover
Reading the bandA bar covers only the weeks its own work is named for, and week five carries two by design.
At the end of W6When the signal record validates, Agent Care assumes the agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Customer Success AI agent
Build an expansion signal agent around the ceiling your last account hit without telling anyone.
Show us one product line and the entitlement each account on it holds. Which of them sits near a limit nobody has told them about — and if nobody can answer that today, the limit is being watched by you and not by them. A signal that names a motive comes back as a finding.
