Technical Fit Assessments
Every SE leader knows the proof of value that should never have started. The signs were there in week one, but technical fit lived in one sales engineer's head, so nobody else could act on it. Opine scores fit against a rubric you write, from context the deal already carries, then measures it again against what the buying team rates while you prove it.
trusted by the world's
highest performing revenue teams
A fit call, and the evaluation that checks it
One deal, from the first reading in March to the pattern it turns out to be part of. Everything below happens to the same record.
Deployment model unconfirmed. Self-hosted is one of the two models we ship, and nothing on the record yet says which one they need.
Read from
- GongDiscovery · 27:04“Everything sits inside our own VPC. Data leaving our tenancy is a non-starter for us.”
- SalesforceDeployment model“Self-hosted, which is one of the two models we ship.”
- EmailPlatform team threadnew since Mar 4“On-call is ours, so alerting has to reach the rotation we already run.”
your rubric · four bands you wrote
The rubric your team wrote reads the deal from what is already on the record. It can't answer the deployment question yet, so it lands at Moderate and says exactly why.
A fit call, and the evaluation that checks it
One deal, from the first reading in March to the pattern it turns out to be part of. Everything below happens to the same record.
- Mar 4
The first read
The rubric your team wrote reads the deal from what is already on the record. It can't answer the deployment question yet, so it lands at Moderate and says exactly why.
Calderwick$94KModerate fitTechnical fitread Mar 4 · runs weekly, and on stage changeDeployment model unconfirmed. Self-hosted is one of the two models we ship, and nothing on the record yet says which one they need.
Read from
- GongDiscovery · 27:04“Everything sits inside our own VPC. Data leaving our tenancy is a non-starter for us.”
- SalesforceDeployment model“Self-hosted, which is one of the two models we ship.”
IdealGoodModeratePooryour rubric · four bands you wrote
First run. Nobody is staffed on it yet. - Mar 18
A call moves it
The evaluation re-runs on its schedule. One discovery call has confirmed self-hosted inside their own VPC, so the score moves to Good and the reasoning is rewritten to say what changed.
Calderwick$94KGood fitTechnical fitread Mar 18 · runs weekly, and on stage changeSelf-hosted inside their VPC, which we support, and the platform team is already the technical champion. Held at Good rather than Ideal because on-call alerting has to reach their existing rotation, and that integration is one we have shipped twice.
Read from
- GongDiscovery · 27:04“Everything sits inside our own VPC. Data leaving our tenancy is a non-starter for us.”
- SalesforceDeployment model“Self-hosted, which is one of the two models we ship.”
- EmailPlatform team threadnew since Mar 4“On-call is ours, so alerting has to reach the rotation we already run.”
IdealGoodModeratePooryour rubric · four bands you wrote
Re-run after the discovery call. Score changed, reasoning rewritten. - Week 1
Your team starts rating
The proof of value begins. Seven success criteria, each carrying a priority and a four-point rating, and your side of the scorecard fills in as the work lands.
Calderwick$94KGood fitSuccess criteriaYour teamCalderwick- SSO via Okta with SCIMMustMeetsawaiting
- Ingest 2TB a dayMustExceedsawaiting
- Alerts into on-callMustMeetsawaiting
- Deploys in their VPCMustMeetsawaiting
- Role-based accessNiceMeetsawaiting
- Audit log to SIEMNiceExceedsawaiting
- Custom dashboardsNiceMeetsawaiting
0 of 7 returned by L. Byrne - Week 4
Their ratings arrive
The buying team rates the same criteria through the portal, in their own time. Five match yours. Two don't, and one of those two is a Must-Have.
Calderwick$94KGood fitSuccess criteriaYour teamCalderwick- SSO via Okta with SCIMMustMeetsMeets
- Ingest 2TB a dayMustExceedsExceeds
- Alerts into on-callMustMeetsPartially Meets
- Deploys in their VPCMustMeetsMeets
- Role-based accessNiceMeetsMeets
- Audit log to SIEMNiceExceedsExceeds
- Custom dashboardsNiceMeetsDoes Not Meet
5 of 7 agree · 2 gaps, one of them a Must-Have - Week 6
The gap gets answered
Alerting reaches their on-call rotation and the buying team re-rates it. Six of seven now agree, and the one still open is a Nice-to-Have you carry into the readout knowing about.
Calderwick$94KGood fitSuccess criteriaYour teamCalderwick- SSO via Okta with SCIMMustMeetsMeets
- Ingest 2TB a dayMustExceedsExceeds
- Alerts into on-callMustMeetsMeets
- Deploys in their VPCMustMeetsMeets
- Role-based accessNiceMeetsMeets
- Audit log to SIEMNiceExceedsExceeds
- Custom dashboardsNiceMeetsDoes Not Meet
6 of 7 agree · alerts re-rated after Thursday's session - Across the book
The pattern behind it
That alerting criterion has been rated in twenty-four plans and averages 2.4. High usage with a low score is a capability gap, and it is the sharpest product feedback your team owns.
Calderwick$94KGood fitCriteria Metricsevery library criterion- Alerts route into the on-call rotation24 plans2.4capability gap
- Custom dashboards for the platform team19 plans2.2capability gap
- SSO via Okta with SCIM provisioning31 plans3.6strength
- Ingest 2TB a day without backpressure22 plans3.4steady
71%+9Technical win rate84%+5Tech win → closed wonThe same criterion, in every plan that used it
A fit score nobody can check is just an opinion
Scoring deals is the easy half. Most teams that have tried it have a spreadsheet where fit was guessed once, and nothing in that spreadsheet can say whether the guess was right, because the thing that would settle it lives in a different file: how the evaluation actually went, criterion by criterion, with the buyer's own ratings on it. In Opine both are properties of the same opportunity record, built from the same calls, notes, email, and CRM fields. So the question stops being what you scored a deal and becomes which of your fit calls held up, and the rubric turns into something you correct rather than something you defend.
Where your team's hours went stops being an argument
Four mechanisms, and each one exists to make a fit call something a leader can act on: the list, the argument, the second opinion, and the place the score lives.
Poor fit becomes a list with names on it
Filter the open pipeline by fit and the deals that would quietly take a quarter of your team's capacity are in front of you. Nothing is blocked and nothing disqualifies itself. The deals just stop being invisible.
A new score can wait for a person
Turn approval on and a run proposes rather than applies: the deal keeps the value it had until someone accepts the new one, with the reasoning and the call it read sitting right there. Leave it off where you trust the rubric, and the score just lands.
The buyer's rating sits beside yours
Buyers rate the criteria they own through the portal, on the same four-point scale. Two ratings on one criterion is the only honest way to learn that your Meets is their Partially Meets, and it surfaces in week two rather than at the readout.
Scoring without a CRM project
Fit starts as an Opine deal property, so your team can run it this quarter without touching a CRM schema. It rides the same field engine as everything else, which makes writing it back to a Salesforce or HubSpot field a governed option rather than a prerequisite.
One number, three people who have been arguing without it
Fit is the thing your team disagrees about most and writes down least. Here is what changes for each side of that argument.
- 01Your sales engineers
“trust me, this one's a waste of a month”
Poor fit, and here are the three lines it read
The case for passing is on the record before anyone is staffed, so an SE is agreeing with the deal rather than arguing against a rep's optimism from memory.
- 02Your account executives
“the SE has gone quiet on my deal”
One Must-Have short, and here is what closes it
A score with its reasoning attached is a conversation about what would have to change, not a refusal. And where the buying team rates a criterion lower than your team did, the rep sees it while there is still evaluation left.
- 03And you, on the capacity call
“we need more sales engineers”
Six poor-fit deals, and the criterion behind them
How much of the quarter sits in each fit band, which criteria your evaluations keep losing on, and whether technical wins are converting. The headcount conversation stops running on anecdote.
Asked in real demos
The questions SE leaders ask when technical fit stops being one person's judgment.
Have one we didn’t cover? Bring it to the demo →
CadenceDoes the AI score every opportunity on its own, or does a sales engineer have to run it?
Configured once, then automatic. You define what a good or poor technical fit means for your product, with your own bands and your own triggers, and Opine evaluates deals against that rubric on the schedule you set, on a stage change, or whenever someone asks for a fresh run. Each score arrives with its explanation and its history, and you can require human approval before it is applied.
GatingCan we require a fit assessment before a POV is allowed to start?
You can score fit early and triage on it. You can't block on it yet. Opine scores the deal against your rubric, writes it with the reasoning, and lets you filter the pipeline by it, so poor-fit deals are visible before a sales engineer is spent on one. An enforced gate that stops a plan from starting isn't supported today. It's a request we're actively considering, and we'd rather say so now than demo something that doesn't exist.
ScoringHow does success-criteria scoring actually work, and can the buyer score too?
Each criterion has a priority and a four-point rating, and buyer-side owners rate their own. Exceeds, Meets, Partially Meets, or Does Not Meet, weighted by whether the criterion is a Must-Have or a Nice-to-Have, computing the plan's overall score. Buyers rate the criteria assigned to them through the portal and can reset a rating, and their scores appear alongside yours per criterion rather than blended into a single number.
PatternsCan we see which criteria we consistently lose on across deals?
Yes. That's Criteria Metrics. Every library criterion is ranked by how many plans use it and how it scores. High usage with a low average score is a capability gap, and it is the sharpest product feedback a presales team owns. The Win/Loss report then tells you whether that pattern is costing you technical wins or the conversion after them.
vs. qualificationHow is this different from the qualification scoring we already run?
Different question, different bar. Qualification asks whether a deal is real: budget, authority, timing, the commercial bar. Technical fit asks whether your product suits what this buyer is actually trying to do, and then whether the evaluation proved it. A deal can be perfectly qualified and a poor technical fit, and that combination is where presales quarters go.
AccuracyWhat stops the score from being an AI guess?
It reads your rubric, not one of its own. The rubric is written by your team, and every reading cites what it was argued from: the call, the note, the email thread, the field. Scores keep their history, so you can see what moved one and when. Where you disagree with a reading, you change the rubric and the next run reflects it.
CRMIs the fit score a field in our CRM?
It starts as an Opine property. So you get scoring without a CRM schema project, and without waiting on whoever owns that backlog. Because it rides the same AI field engine as the rest of Opine, it can also fill a Salesforce or HubSpot field with governed write-back if you want it there, behind the same approvals.
Proven in the field
Technical sales teams run their evaluations on Opine, and report what happened to their technical win rates.
“Opine is the first tool that I’ve seen in my twenty years of sales that truly honors the SE craft. Now, I can do everything from deal management to capacity planning in Opine. It’s a dream.”
Clive Quinton
Manager of Solutions Engineering at Tailscale
