Automated Activity Tracking
You can't run a team on a spreadsheet of what people think they did last month. The fix that makes it worse is a timesheet. Opine reads the calendars your sales engineers already keep, links every meeting to the deal it was for, and labels it with rules you can see fire.
trusted by the world's
highest performing revenue teams
Nobody on your team writes any of this down
Every event on a connected calendar, attached to the deal it was for, labeled by a rule someone on your team wrote, and readable as a week by the time you ask for it.
Opine reads every event on your team's connected Google and Microsoft calendars and links it to the deal it was for. There is no approval step, because a vetting workflow would rebuild the clerical work you are removing.
Nobody on your team writes any of this down
Every event on a connected calendar, attached to the deal it was for, labeled by a rule someone on your team wrote, and readable as a week by the time you ask for it.
- 01 · The capture
Nothing stands in front of it
Opine reads every event on your team's connected Google and Microsoft calendars and links it to the deal it was for. There is no approval step, because a vetting workflow would rebuild the clerical work you are removing.
Google Calendar3 accounts
Microsoft Outlook2 accounts61 events this week · nothing to approve - 02 · The rule
The label comes from a word you chose
Labels are keyword rules on event titles, scoped by event type. “intro” resolves to Discovery because someone on your team decided it should, and every labeled event shows the keyword that fired.
Calloway · intro callRule“intro”→DiscoveryScoped to customer-facing events · edited by you, not inferred - 03 · The deal
The hour lands on the opportunity
Activity attaches to the deal record rather than to a calendar, so it rolls up the way pipeline does. Transcripts from Gong, Zoom, Clari, and Chorus merge into the same timeline for teams that use them.
Harborline$480K · POV In-progressMon 11:00Architecture reviewTechnical Deep DiveMon 15:00Prep for ThursdayDeal PrepTue 13:00SSO + SCIM sessionNo rule matchedThu 10:30Exec walkthroughCustomer Demo - 04 · The read
A week nobody had to reconstruct
External against internal, by person, by deal, by label, over any date range, saved as a view for the report you run every month. The only entries anyone typed are the ones that were never on a calendar.
Hours by label · this weekTechnical Deep Dive3hPOC2.25hWorkshop2hDiscovery1.25hCustomer Demo1h
A model could guess what that meeting was. You couldn't check it.
Any model can read a transcript and decide a session was a technical deep dive. That holds up right until the number lands in a headcount conversation and somebody asks how you know. Opine labels from keyword rules your team wrote, scoped to the event types you chose, and every event carries the word that matched and who last edited that rule. The context layer does its work underneath that: capture off the calendar, the link to the right opportunity, and the merge with whatever your team records. What a demo is stays your team's call, which is the part you can actually defend.
Visibility your team doesn't pay for
Presales time only becomes an argument once it is on the record. These four are what get it there without anyone maintaining it.
Capture with nothing in front of it
Every event on a connected Google or Microsoft calendar, linked to the deal it was for. No approval queue, no tagging step, and no habit for anyone to build.
Labels you wrote, and can watch fire
Keyword rules on event titles, scoped by event type. Every labeled event shows the word that matched, so a scheme that is wrong is a scheme you can fix rather than a black box you argue with.
Hours that belong to a deal
Activity attaches to the opportunity rather than to a calendar, and recordings from Gong, Zoom, Clari, or Chorus merge into the same timeline.
The report is already written
External against internal, by person, by deal, by label, over any range. Save the combination as a view and stop rebuilding it the night before.
What changes when nobody is asked to log anything
Three people have a stake in where the technical hours went. Only one of them is usually asked to write it down.
Nothing is asked of them
No timesheet, no tagging step, no Friday reminder. They keep their calendars the way they already do and the record fills in behind them. The one thing left is the work that was never on a calendar, like a site visit, and that takes about ten seconds to add.
The deal shows its own history
Whoever opens the opportunity sees every technical session that has happened on it, in order, with the recording attached where there is one. Nobody has to ask what happened on Tuesday, and a handoff stops depending on who was in the room.
You stop paying for the data twice
The trade is real and you have probably made it before: you can have the utilization numbers, or you can have a team that isn't doing clerical work, but not both. Capture off the calendar removes the trade. What you tune is the label scheme, once, and it sharpens as your team's naming conventions surface.
Asked in real demos
What comes up once a team stops filling in where its time went and starts reading it off the calendar.
Have one we didn’t cover? Bring it to the demo →
AccuracyHow accurate is the labeling, and what happens when something is mislabeled?
Capture is fully automatic. Labeling gets sharper the more you tune it. Labels are transparent keyword rules rather than a model's judgment, so you can see exactly why an event was categorized and refine the rules as your team's naming conventions surface. Most teams tune their scheme during onboarding and we help with that. Individual events take a manually applied label wherever no rule fits.
ApprovalIs the labeling automatic, or do our SEs have to review and approve every activity?
Automatic, and there is no approval queue by design. A vetting workflow would rebuild the clerical work you are removing, so events are captured and categorized from the calendar with nothing in front of them. Manual logging exists only for activity that was never on a calendar in the first place, like a site visit or an ad-hoc phone call.
SetupHow do we set this up to recognize demos, discovery, and deep dives?
Define the labels once in Activity settings. Each label carries the keywords that trigger it and an optional event-type scope, so a rule can be limited to customer-facing events. From then on, matching calendar events are labeled automatically, and you can add manual-only labels for categories no keyword can catch.
Off-calendarPlenty of our work never hits a calendar. What happens to that?
Log it in a few seconds, and it stays marked as logged. A quick Activity entry takes a duration preset and a label, and structured deal updates come in from Slack. Manually logged time never blends into the automatically captured time: it stays its own category everywhere it is reported, so nobody has to guess which numbers came from where.
RecordersWe don't allow call recorders. Does this still work?
Yes. Capture is calendar-first. Recordings from Gong, Chorus, Clari, and Zoom merge into the same timeline for the teams that use them, but they enrich the record rather than produce it. We have security-sensitive customers running activity tracking with no call recorder at all, and still logging nothing by hand.
ReportingCan we report utilization to leadership without spreadsheets?
Yes, with one honest caveat about the denominator. Total time by person over any date range, split external against internal, broken down by deal and by label, with saved views for the recurring report. Opine doesn't express utilization as a percentage of a forty-hour week, because that would push sales engineers into logging non-customer-facing time just to fill the denominator. Most teams index on external hours instead.
vs. surveillanceIs this a surveillance tool? My team will push back on it.
It reads meetings, not people. What gets captured is calendar events and who was on them, for a date range you choose. There is no keystroke tracking, no screen time, no idle monitoring, and nothing for a sales engineer to fill in. In practice the people it helps first are the ones who have been saying they're stretched and had nothing to point at.
Three teams, one record nobody filled in
The same mechanism, arrived at from three directions: a quarterly review, a mid-evaluation departure, and a team that had already refused to log its time.
Four proofs of value are running at once, and in the QBR the VP is asked which of them the quarter's technical hours actually went to. Reconstructing an answer means five people going back through their calendars.
SSO + SCIM session · Customer Meeting · no rule matched. Labeled Technical Deep Dive by hand, and the keyword added to the rule.
The quarter is already attributed by deal and by label, so the answer is a saved view. The handful of events the rules missed show up as gaps rather than as quietly wrong numbers.
A sales engineer leaves mid-evaluation and the account team inherits three deals whose entire technical history lived in one person's calendar and one person's memory.
Discovery, an admin workshop, two deep dives, and a stand-up every Tuesday. Four carry Gong recordings.
Whoever picks the deal up reads six weeks of technical history in order, with the recordings where they exist. The handoff takes an afternoon instead of a fortnight.
Leadership wants time tracking. The team has been through it at another company, knows exactly what a daily logging habit costs, and has already said they won't do it twice.
7 labels · 14 keywords · scoped to customer-facing events. Nothing to fill in per event, and no approval queue.
Capture starts the day the calendars are connected and asks nothing of the team. The only work is tuning the label scheme, which one person does once and sharpens as naming conventions surface.
Proven in the field
Technical sales teams run their activity record on Opine. The results are public.
“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
