Your team adopts it because it takes the boring work away.
Every tool you’ve rolled out asked your engineers to feed it, and the ones that stuck gave more than they took. Opine reads the calls, the threads and the calendar your team already generates, so the CRM updates, the handoff docs and the meeting briefs stop being anybody’s morning.
4.8/5Trusted by high-performing revenue teams
You bought it. Now eight people have to use it.
“The problem I want to solve for is how do we get all of the tacit account knowledge that we’re accumulating in very light-touch ways to be equivalently light to update Opine from those data.”
A presales leader, in a customer Slack channel
Your credibility is staked on a rollout you may not have designed. The budget is spent, the political capital is spent, and every week the team isn’t actually using the thing, the bet looks worse.
It’s never about the software. It’s that every system your engineers have been handed asked them to stop selling and go type something, and the calendar those eight people are already drowning in doesn’t have room.
So the only rollout that’s ever worked is the one where using it is less work than not using it.
Connect the calendar. Read the week.
Nobody fills in a timesheet. Hours land in four categories from the meetings themselves, benchmarked against your team’s own average rather than a target somebody invented. Connect the calendar, set your labels once, and that is the whole setup.
| Engineer | Hours | Where the week went | vs team |
|---|---|---|---|
| Priya RamanAMER East | 35h | +7h | |
| Marcus BellAMER East | 23h | -5h | |
| Dana WhitfieldAMER West | 36h | +8h | |
| Tom IversonAMER West | 21h | -7h | |
| Sofia MarchettiEMEA | 29h | +1h | |
| Ade OkonkwoEMEA | 26h | -2h | |
| Hana SatoAPJ | 35h | +7h | |
| Wei ZhangAPJ | 17h | -11h |
“Is this a stopwatch on my people?”
There’s no utilization score.
Hours by category, measured against your team's own average. No target, no percentage, and no threshold alert when somebody crosses a line. None of that exists in the product.
“Can someone game it by blocking their calendar?”
It reads the meetings, not the status.
Categories come from the meetings themselves. Hours anyone logs by hand stay their own labeled category, so automated and self-reported never blend silently.
“Who can open this?”
Managers and admins. Not the team.
Per-user CRM visibility applies on top, so nobody sees a deal they couldn't already see. An engineer can’t look up a teammate's week at all.
The part that runs on its own is the reading, which is the part nobody wants to do.
Manager and admin only · calendar integration required
A coaching view, not a stopwatch.
You want to know who’s drowning. You don’t want a number that tells eight people they’re being timed. Pick a role and see exactly what it can open.
The team they run, at the altitude that makes a coaching conversation possible.
- Team activity, hours by categoryExternal, internal, prep, other
- Each engineer's week, in detailDeals, meeting timeline, labels
- Demand for specialistsRequested, staffed, and unstaffed
Hours come from the meetings themselves, not from anyone filling in a timesheet. Manually logged time stays its own labeled category, so automated and self-reported never blend silently.
The conversation changes shape
“I think you’re overloaded” is a judgment about a person. “Your external hours doubled and your prep went to zero” is a fact about a week, and it’s the one your engineer can actually do something with.
There’s no score to defend
No utilization percentage, no capacity target, and no alert that fires when somebody crosses a line. Those things don’t exist in the product, which is the most durable form of a promise not to build a stopwatch.
Your existing permissions hold
Per-user CRM visibility applies on top of every view, so nobody sees a deal they couldn’t already see. The field-level security you built stays exactly as you built it.
You’ve always seen supply. You’ve never seen demand. Like this.
You know what your team did, because it happened. You’ve never had a record of what was asked of them, because the asks went to a channel and were answered by whoever replied first.
- Halden SystemsSecurity reviewA. Okonkwo
- Verity HealthData residency reviewH. Sato
- Northwind LogisticsArchitecture deep diveD. Whitfield
- Orbit FreightPerformance testM. Bell
- Corstone BankCompliance questionnaireP. Raman
- Delmar HealthMigration planningS. Marchetti
- Jarvis AerospaceArchitecture deep diveT. Iverson
- Stanmore TelecomCustom integration scopingW. Zhang
- Halden SystemsMigration planningD. Whitfield
- Kestrel EnergySecurity review34d
- Braddock SteelScale and sizing review33d
- Halden SystemsCompliance questionnaire31d
- Eastvale EnergyArchitecture deep dive30d
- Milbourne UtilitiesSecurity review29d
- Redhill TransitMigration planning28d
- Kestrel EnergyArchitecture deep dive27d
- Norbury InsuranceCompliance questionnaire26d
- Selby AviationSecurity review25d
- Verity HealthCompliance questionnaire24d
- Aldworth MediaCustom integration scoping23d
- Northwind LogisticsPerformance test22d
- Pinegrove RetailSecurity review21d
- Elmridge PharmaData residency review21d
- Halden SystemsPerformance test20d
- Trentham FoodsPOV support19d
- Fairhaven CreditSecurity review18d
- Orbit FreightCompliance questionnaire18d
- Glenmoor TextilesRFP technical response17d
- Kestrel EnergyPOV support16d
- Redhill TransitPerformance test15d
- Yardley DevicesArchitecture deep dive15d
- Corstone BankSecurity review14d
- Ilford WaterCompliance questionnaire13d
- Eastvale EnergyCompliance questionnaire12d
- Kelmscott LegalData residency review12d
- Halden SystemsRFP technical response11d
- Selby AviationMigration planning10d
- Jarvis AerospaceScale and sizing review9d
- Newlyn PortsSecurity review9d
- Verity HealthPOV support8d
- Alderfield GrocersPerformance test8d
- Stanmore TelecomPOV support7d
- Havelock MiningArchitecture deep dive6d
- Northwind LogisticsPOV support6d
- Pinegrove RetailCustom integration scoping5d
- Delmar HealthData residency review5d
- Penrose AnalyticsCustom integration scoping4d
- Orbit FreightMigration planning3d
- Kestrel EnergyData residency review3d
- Quintrell LabsScale and sizing review2d
Every headcount case you’ve ever made was built from the half of this you could see. Requests staffed is a supply number wearing a demand number’s clothes, and it’s the reason those conversations go the way they do.
You get asked in January. Every deal answered on the day it closed.
Every deal that closes writes its own report a few minutes later, from the calls, the evaluation record and the buyer’s own words. The quarter’s analysis reads all of them together and names what they have in common.
The pilot started before anyone wrote down what would end it
6 of 16 losses · $1.32M · 3 regions
In all six, a new requirement arrived after the technical win
- Corvale RoboticsAMER WestReport written 14 Jul
- Ashmere GridEMEAReport written 29 Jul
- Sandpiper RetailAMER EastReport written 18 Aug
- Holloway MaterialsEMEAReport written 3 Sep
- Perrin FoodsAMER EastReport written 19 Sep
- Mariner Bay UtilitiesAMER WestReport written 26 Sep
- 14 OctQuarterly business review
- 6 NovPipeline review with your CRO
- 22 JanNext year’s headcount plan
You answer all three from a report that was finished before the first of them.
Read one of these deals and you get a reason. Read six and you get a cause. Nobody used the same words, which is why a closed-lost picklist could never find this.
This isn’t six deals going wrong. It’s one evaluation habit, running the same way in three regions. A habit is a thing you can coach.
The step all six skipped is the one your best engineer never skips.
“Those six weren’t six different problems. They were one evaluation habit, in three regions.”
From the quarter’s cross-deal report
“We declined SE support on 14 opportunities worth $4.2M in pipeline, because we ran out of capacity.”
How leaders frame the headcount ask
Neither sentence needs a week of prep.
Make the best version the default version.
You don’t scale an SE org by hiring. You scale it when the way your best engineer runs an evaluation is the way the whole team runs one, without you standing over anybody’s shoulder.
Skills
Your winning POV, made executable.
The discovery framework, the qualification bar, the way your best engineer runs an evaluation. Written once, and every agent can opt into it, so the standard holds without you standing over anybody’s shoulder.
Open SKILL.md format, so what you build here leaves the same way it came in.
- 1Business driver named
- 2Technical criteria agreed
- 3Success owner identified
- 4Exit criteria written
Written once. Every agent can opt in.
- Business driver named
- Technical criteria agreed
- Success owner identified
- Exit criteria written
- Business driver named
- Technical criteria agreed
- Success owner identified
- Exit criteria written
- Business driver named
- Technical criteria agreed
- Success owner identified
- Exit criteria written
Describe the job, read the run log
Say what you want done in plain English and an assistant drafts the instructions and picks the triggers. Then you read what set it off, what it touched, what it held for a person, and what it cost.
Runssandboxed · survive a deploy · full run log
Break it on your data first
Run an agent against a dataset and watch where its judgment goes wrong before a live deal finds out. Costs are prepaid per run, so there's no overage bill waiting at the end of the month.
Creditsprepaid · per-run cost · auto-refresh
Works in both directions
Query your team's pipeline from inside Claude or Cursor over OAuth, scoped to what that person is allowed to see. Opine is a client too, so the agents you build can call the servers your org already connects.
AuthOAuth · no static tokens · authored agents save disabled
Reporting runs as Opine SQL, read-only and scoped to whoever asked, and it’s the same engine behind the dashboards. Teams who would rather skip the UI export against the schema catalog and join Opine with their CRM in the warehouse. Read the Agents docs
Bring your best evaluation. Leave with the standard.
One evaluation your best engineer ran, opened up on the call: the criteria they insist on, where they make the buyer commit, and the exit bar they hold. It leaves as a Skill the whole team runs from, instead of a habit only they have.
Four people get something. Only one of them has to defend the headcount.
Your engineers never open a settings page. The case you take into that conversation builds itself while they work.
Halden Systems: three open technical risks
Written before the call, from the last four
They walk in prepared without preparing. That’s why they keep using it.
Security specialist staffed: Ade Okonkwo
Matched on skills, with the reason recorded.
A request with an owner, instead of a channel with a question in it.
68%
Across 46 closed evaluations this quarter.
The answer to “what are we getting for this”, ready before they ask.
Evidence, not a feeling you’ve had since February.
Every SE hour returns more.
Opine is the AI-ready context layer for presales and sales engineering: it reads the calls and documents your team already produces and keeps one current record per deal, with the SE hours and the technical win on it.
The questions SE leaders ask us first.
What it measures, who can see it, and what it does when your team is already at capacity.
Have one we didn’t cover? Bring it to the demo →
capacityCan I see utilization against a 40-hour week? Who's at 70% and who's at 40%?
Hours and deltas, not a percentage. You get total activity hours per engineer, with per-person averages and a delta against the team average, and most leaders read utilization off that against their own capacity target. To be precise about the limit: it's an hours view rather than a single "% utilised" gauge, and capacity-threshold alerts aren't supported today. If you need a number that fires when someone crosses a line, that isn't in the product yet.
dataWhere does the data come from? Can't someone game it by blocking their calendar?
It reads the meetings, not the status. Hours are captured and categorised automatically from the calendar integration, based on the meetings themselves rather than on anybody's self-reported status. Manually logged hours show as their own labeled category, so automated and self-reported time never blend silently.
visibilityWho gets to see this? We don't want it in front of the wrong people.
Managers and admins, and per-user CRM visibility on top. The view is gated to manager and admin roles and requires a calendar integration. Per-user CRM visibility applies as well, so nobody sees a deal they couldn't already see. Individual contributors don't browse each other's utilization, and it stays out of general view.
adoptionMy engineers won't maintain another system. Does this depend on them changing?
No. That's the design constraint. The briefs, the CRM fields and the deal summaries are drawn from things that already happen: the calls, the email threads and the calendar on the deal. Your team keeps selling and the record catches up on its own. Every rollout that's failed at your company failed because it needed somebody to type more.
routingCan a manager stay in the approval loop on staffing without becoming the bottleneck?
Assignment Owner mode. The decision sits with an owner who can accept the system-proposed candidate in one click or override it with a recorded reason, and Auto Assign exists for request types that don't need a human gate. One thing we don't support today: a primary approver plus a CC'd group who can self-assign.
routingDoes routing know who's actually free?
Skills yes, working hours no. A skill catalog, per-member assignments with proficiency, and required skills on each request drive candidate scoring. Availability is handled through proposed time slots with time zones. Automatic working-hours-aware assignment isn't supported today, though it's a request we're considering.
routingWe usually have several engineers on one deal. How does assignment handle that?
Requests are per-need, not per-deal. A deal can carry several requests, each with its own assignee, and the deal's team reflects everyone staffed. The deal's Team Requests tab shows the full staffing picture in one place.
reportingCan we see effort per deal? I want to know if we're over-investing relative to deal size.
Per engineer, and across the portfolio. Click any engineer for their open deals with stats and their meeting timeline. Opine SQL answers the portfolio versions: hours invested per closed-won deal, per-person deal-versus-internal splits, and time spent on deals you lost.
platformWhat does AI deal intelligence do for a sales engineering team?
It turns the team's work into evidence. Every call your sales engineers join is read when it ends, and the technical criteria, POV progress and activity hours land on the deal's record with citations. The team stops writing summaries by hand, and you get the technical win measured in hours and outcomes you can stand behind at headcount time.