Sales Process Enforcement
Your methodology lives in MEDDPICC fields, an exit-criteria doc, and one person's head. Opine turns it into a skill your agents apply to every deal, so the process holds without anyone chasing reps for updates.
trusted by the world's
highest performing revenue teams
How Sales Process Enforcement works
Write the process once. The agents apply it to every deal and show their work.
- 01 · Playbook
Your process becomes a skill
Author it in plain markdown, or import the playbook you already have. Opine follows the open SKILL.md standard.
- 02 · Scope
You choose where it applies
Skills are opt-in per agent and per chat surface. Nothing runs anywhere you didn't turn it on.
- 03 · The check
Every deal gets the same read
The agent works the deal against your criteria: calls, threads, fields, and the technical record.
- 04 · The nudge
The gap lands with its owner
In Slack or on the deal record, naming what's missing and drafting the next step. Writes wait for approval.
A ticked box isn't proof
Your CRM can require the field. It can't tell you whether discovery actually happened, whether the criteria were agreed with the buyer, or whether the champion has changed since. Opine reads conversations, fields, and the technical sale in one record per opportunity, and structures every deal summary around your methodology, so a gap shows up as a gap. The agent judges the work rather than the checkbox. It enforces by watching the deals, not the reps.
The process holds itself
Your best reps already run the playbook from memory. Skills are how the rest of the team runs it too, on every deal, without a manager in the middle. Time in stage and technical win rates show it's holding.
One playbook, every deal
Discovery questions, battlecards, POV runbooks. Authored once, shared across the org, used by every agent that needs them.
Gaps surface when the stage moves
When an exit criterion is missing, the agent names it and tells the owner. Nobody finds out in the pipeline review.
It does the step, not just the reminder
A deal enters your POV stage and the agent drafts the kickoff plan in the deal's channel. Where the context is enough, it fills the field and attaches the source. You approve.
Your methodology, your rules
Keep a skill private, give the team edit access, or share it org-wide. Turn it on per agent, and hold any write for sign-off.
Asked in real demos
The questions that come up when technical sales teams put their process into Opine.
Have one we didn’t cover? Bring it to the demo →
vs. required fieldsOur CRM already blocks a stage change until the fields are filled. Do we still need this?
Your gate fires once. The check runs every day. A required field is tested at the moment someone moves the stage, and any keystroke satisfies it. The skill runs against every open deal, again each time a new call or thread lands, and it never blocks the stage. Keep your required fields. The agent judges what's behind them.
OwnershipCan our sales engineers write their own playbooks, or is that locked down?
Both, by design. Skills are governed by resource grants: view, edit, or manage. Let every SE author skills, or keep editing with a few owners while everyone else uses them.
AuthoringHow do you create one? In Claude I just say “create a skill file for me.”
Same idea here. Skills follow the same SKILL.md standard Claude uses, and the editor includes an Edit-with-AI assistant that drafts and refactors skill files conversationally, with staged saves. You can also import an existing skill as a zip.
PortabilityWe've already built skills in Claude. Do they carry over?
They import as-is. Opine follows the open agentskills.io format, so a skill built for Claude imports as a zip and exports the same way. Nothing to rebuild, and no passing skill files around over GitHub.
StructureShould we build one big process skill or several small ones?
Fewer, well-bounded skills work better. Related instruction files usually belong in a single bundle with their references alongside. If a job needs four documents, they probably belong inside one skill rather than four fragmentary ones.
ScaleA playbook one person wrote is becoming load-bearing. How do we make it production-grade?
Share it, then enable it. Grant the team edit or view access, then turn it on for the agents that should use it. Skills are org-level resources rather than personal files, so nothing has to be rebuilt to graduate from one person's workflow to the team's.
Proven in the field
Technical sales teams run their pipeline on Opine. The results are public.
“I’ve used countless presales tools over the years, and I can confirm that not a single one comes close to what Opine is doing. Because of their platform, win rates are up, SEs are more efficient, and leadership has access to never-before-seen pipeline intelligence. It’s amazing.”
Shaun Dolan
Director of Solutions Engineering at Orca Security
