People
A name matched once. Never retyped.
Every deal, meeting and task in StratOps eventually points at a person. This page is about how that person gets into the record, and about the one thing StratOps flatly refuses to guess.
What actually happens when you say a name
You mention someone in passing — a first name, a company, half a sentence. StratOps checks whether that person is already in the record. If they are, the name matches to the existing contact instead of creating a second one next to it. If they aren't, a new contact gets created from what you said.
If the name could plausibly be two different people you already know, neither one gets picked for you. Both are named back to you, and you say which one. Guessing wrong here isn't a small mistake — it silently splits one person's history in half.
Contacts are the one thing with no undo at all.
Every other capture — a meeting, a time entry, a decision — can be pulled back if you catch the mistake immediately, one step, no further. A contact write has none of that. There is no version history, no trash, nothing to restore. That isn't an oversight; it's the direct consequence of the merge logic above. If a wrongly-matched contact could be undone after the fact, undoing it would have to somehow un-merge whatever got attached to the wrong person in between — a deal, a meeting, a task. There's no clean way to do that, so the system refuses the ambiguous case up front instead of promising a fix after the fact it can't actually deliver.
0
Undo steps on a contact write
1
Step back, for everything else you capture
- MeetingsEvery call logged against this person, in order.
- DealsWhatever pipeline is open with them, and its stage history.
- TasksWhat you still owe them, and what you already sent.
- DecisionsCalls made that named them as the reason or the context.
A contact is a join point, not a card.
There's no separate "profile" you fill out. A contact accumulates whatever gets said about them across every other kind of record — a meeting note, a deal stage, a task due date — and every one of those rows is scoped to the same account the contact belongs to, so a name from one workspace can't quietly end up attached to another's data. That scoping is enforced at the database level, not by a rule a tool author has to remember to apply.
This is not the contacts screen. There isn't one.
StratOps has no dashboard, and that includes a browsable list of every person in the record. You don't scroll a directory to find someone — you say their name, or ask a question that would surface them, in the conversation you're already having. Editing a contact happens the same way: by saying the correction, not by clicking into a record and typing over a field.