Never open with “so, what are you trying to do?”
You inherit the account and the knowledge stays behind: why they bought, what was proven, what got promised, what was waived to close on time. Opine hands you all of it on day one, because none of it was ever written for the handoff.
4.8/5Trusted by high-performing revenue teams
Making them repeat it reads as incompetence.
“Hit or miss. ‘Hey, I’m your post-sales. What is it you want to do?’”
A customer’s champion, on how handoffs go today
The buyer already explained all of it. The pain, the success criteria, the politics, the thing somebody promised them in June. They explained it to an engineer who has now moved on to the next deal.
So the knowledge dies at the boundary, and you rebuild it by asking the customer questions they have already answered. Which costs you the only thing you had on day one, which was their confidence.
A handoff document written from memory is only ever as good as the memory, and the memory has left the deal.
Everything below is dated before you owned it.
Nobody assembled this for you. It is what the evaluation produced while it was running, still attached to the account after the deal closed.
- Why they bought
Audit evidence took three weeks per customer request
Discovery call · 14 Mar
- What was proven
Six success criteria rated by their own team, four Exceeds
Evaluation plan · 2 May
- What was promised
SSO for their EU tenant, committed for Q1
Email thread · 19 Jun
- What was waived
Two criteria dropped to close on time, both still unmet
Evaluation plan · 28 Aug
- Who to call
Champion left in August. Their deputy ran the last two sessions
Calendar + CRM · 4 Sep
Two of these are liabilities, and finding them on day one rather than on a renewal call is the whole difference.
Nothing here was asked of the customer
This is not a customer success platform.
You probably already have one, and we are not asking you to move. Health scores, lifecycle stages and playbooks are somebody else’s job and they can keep it.
What none of those systems has is the technical truth of the account. Not the relationship, not the tickets: what the buyer said they needed, which criteria were actually proven, what got promised in an email in June, and what was quietly waived to close on time.
That layer is the one that makes your first ninety days credible. It is the layer we win.
The book remembers what nobody wrote down.
The dossier is what makes week one survivable. This is what makes the renewal winnable, and it is the part that compounds across a whole book of accounts.
- Criteria waived at close, still unmet
- Promises made in the evaluation, still open
- Contacts who have left, and who replaced them
T-90 and T-30 renewal wakes · plans from your own templates
Bring an account somebody handed you, and the questions you had to ask anyway.
Thirty minutes on a real inherited account. You leave knowing what the record would have told you on day one, and which of the awkward questions you'd never have needed to ask.
Adopted upstream, whole at the handoff.
Opine is the AI-ready context layer for revenue teams: it reads each call when it ends and keeps one current record per account, so the handoff arrives with the promises, proof and waivers already on it.
The questions post-sales teams ask us first.
What it replaces, what it refuses to replace, and where the account context comes from.
Have one we didn’t cover? Bring it to the demo →
limitsWe already have a customer success platform. Are you asking us to replace it?
No. We don't do health scores or playbooks. Your CS platform owns the customer lifecycle, the health scoring and the playbooks, and we're not trying to take that. What no CS platform has is the technical truth of the account: what the buyer actually said they needed, which criteria were proven, what got promised in an email in June, and what was quietly waived to close on time. That layer is ours, it's the layer that makes your first ninety days credible, and it sits alongside whatever you already run.
sourcesWhere does the account context actually come from?
The evaluation, as it happened. CRM deal and account data, Slack and Teams threads, call transcripts, calendar events, the evaluation plan and its success criteria, notes and documents. Nothing was written for the handoff, which is the point: it was written while the evaluation ran, so it doesn't depend on a departing engineer remembering to write it down.
trustHow do I know a line in the dossier is true?
Every claim cites its source. Hover any claim to preview the Slack message, transcript moment or CRM update behind it, and click through to the full conversation. If a claim can't be traced to a source it doesn't belong in the summary. That matters more here than anywhere else on the site, because you'll be repeating these lines to a customer who was in the room.
cadenceHow current is it? Is something watching the account?
On view, on a schedule, or on demand. A summary regenerates when you open it if it's gone stale, on an optional nightly schedule, and whenever you hit refresh. A material change on the account shortens that staleness window to a day, and anything older than a couple of days carries an indicator so you know what you're reading. There's no live per-event trigger, and we'd rather tell you the mechanism than imply something is watching.
riskWhat about the promises made during the sale that nobody wrote down?
If it was said on a call, it's on the record. Commitments made in calls and email threads are part of the account's context, and criteria that were rated but never met stay visible after close rather than disappearing with the deal. Inheriting the promises is unpleasant, and inheriting them on day one rather than on a renewal call is the whole difference.
workflowCan we run our renewal process in here, or is this read-only?
Plans, from your own templates. Post-sales and renewal plans run from your organization's templates, and customer asks can be logged as product requests carrying the revenue behind them. Customers run real post-sales programs on this. What it isn't is a ticketing system or a health-score engine, and we'd rather be clear about the boundary than have you find it in month two.
sourcesHow does AI improve the sales-to-post-sales handoff?
The handoff document writes itself from the deal. Everything the buyer said they needed, what was demonstrated, and what was waived to close is already on the deal's record with citations by the time it closes. Post-sales inherits that record instead of a recap written from memory, so the first ninety days start from what actually happened.