CRM & SALES OPERATIONS
One Reliable
Commercial Record.
From active lead through outcome and handoff.
Commercial activity can happen across email, meetings, spreadsheets, forms and CRM records while the pipeline still fails to explain what is true now.
Map Your Sales Operationtrue now?Evidence before state.
Visible exceptions. Accepted handoff.
A conceptual operating model, not a CRM product.
Batisha Labs designs CRM and sales-operations systems around record authority, accountable ownership, evidence-backed stages, controlled next actions and accepted handoffs—so the operating view reflects the commercial state instead of simply collecting activity.
Control before tools.01 / Commercial fragmentation
The activity happened. The pipeline still cannot explain it.
Identity, ownership, stage, evidence and next action can live in different places. The team has motion, but no dependable operating view.
Identity splits
Contact details, messages, notes and spreadsheets disagree. Duplicates accumulate; the team reconstructs which buyer record is current.
The conversation moves
The buyer advances, stalls or changes direction. The recorded stage stays behind; ownership changes without an accepted transfer.
Follow-up lives in memory
A call happened. The purpose and next action never reach the shared record. Only one person remembers the open obligation.
The labels stay active
Work stops, but opportunities remain open. Reporting shows a full pipeline without the evidence management needs to trust it.
Activity without reliable commercial state.
02 / One current record
Can the business answer these five questions from one governed record?
Five controls.
- Identity
- One buyer identity, a defined source of truth, and verified facts across dependent views.
- Ownership
- A named person or function, responsible for moving, resolving or reviewing the present obligation.
- State
- The buyer event, decision or verified fact that justifies the stage—not a completed task.
- Continuation
- Meaningful history plus an owned action, purpose, due condition, context and completion evidence.
- Exceptions
- Uncertainty stays visible with an accountable recovery path. Reporting reflects the record, not optimistic labels.
- 01 / Identity
Who is the buyer and which record is authoritative?
One buyer identity, a defined source of truth, and verified facts across dependent views.
- 02 / Ownership
Who owns the opportunity now?
A named person or function, responsible for moving, resolving or reviewing the present obligation.
- 03 / State
What commercial state is actually supported?
The buyer event, decision or verified fact that justifies the stage—not a completed task.
- 04 / Continuation
What happened last, and what must happen next?
Meaningful history plus an owned action, purpose, due condition, context and completion evidence.
- 05 / Exceptions
What is stale, overdue, duplicated or unresolved?
Uncertainty stays visible with an accountable recovery path. Reporting reflects the record, not optimistic labels.
03 / Ownership + stage governance
Ownership is responsibility. Stage is a business condition.
A named owner is accountable for moving, resolving or reviewing the current opportunity—not merely appearing beside it.
Ownership carries an obligation.
Record the expected action, purpose, due condition, required context, review condition and completion evidence. Quiet, blocked, disputed and overdue opportunities need an explicit owner review.
Stage carries a condition.
Pipeline management depends on entry conditions, supporting buyer evidence, an accountable owner, expected movement and a stale condition.
If evidence disappears, time makes the state stale, ownership changes or fit changes: move forward, move back, close, recycle or enter owned exception review.
- 01Entry condition
- 02Supporting evidence
- 03Accountable owner
- 04Expected movement
- 05Stale condition
Owns the open obligation until acceptance.
Transfer request → current state + open context + next expected action → receiving acceptance → responsibility transfer.
Accepts the current state, context and next action.
Notification or reassignment alone does not transfer responsibility.
04 / Pipeline discipline
Activity ≠ Commercial State
Events can inform the record. They do not prove the buyer’s state. Retain what happened without letting a completed task invent progression.
Activity remains recorded in both paths.
Check the commercial condition before changing state.
The activity cannot bypass evidence. Sending alone does not change the stage.
Buyer confirmation of review supports this condition, subject to the defined stage rule.
No buyer evidence: retain the event and hold the commercial state.
Sending is recorded activity. Review requires supporting buyer evidence.
A completed meeting does not establish a real decision process or a decision date.
A message does not establish buyer engagement, accountable ownership or credible continuation.
05 / Controlled continuation
No active opportunity should depend only on memory.
A reminder answers when. A controlled follow-up system also answers why, who, under what condition, with what context, what closes it and what happens if it is missed.
One next action. Six requirements.
- Owner
- Accountable for completion
- Purpose
- Why the action exists now
- Due condition
- The time or event that makes it actionable
- Required context
- What the owner needs before acting
- Completion evidence
- What closes the action
- Exception path
- What happens when it cannot complete
Missing or overdue next action is a visible exception. A record of the past alone is incomplete.
Follow-up follows conditions.
Scheduled
Time condition → follow-up dueA known date or interval creates a reviewable action.
Event-driven
Buyer event → next actionA response, state change or missing input creates the task.
Stalled review
No valid movement → owned reviewAge, silence or absent evidence forces explicit review.
Recycle / re-engage
Not active → future condition → re-entry reviewReturn to attention deliberately, without pretending the opportunity stayed active.
06 / Reconciled outcomes
Closed is a business state. Not just a button.
Won, lost and recycle are distinct, legitimate reconciled states. Each resolves the active pipeline while preserving the context that matters.
Won
Commercial acceptance is recorded. The receiving operation has accepted context and an owner for the next handoff.
Lost
Remove from active pipeline. Retain final context, the real loss reason when known, and a deliberate re-engagement decision. Unknown is better than fabricated certainty.
Recycle
Not active now. Record the reason, future review condition, re-entry condition and responsibility where required.
Delivery should not have to reconstruct what sales already knew.
Carry buyer identity, agreed scope, commitments, decision context, stakeholders, constraints and the next operational action. Notification is not handoff: the receiving operation must accept the context before responsibility transfers.
07 / Exception + recovery
Do not hide the conflict. Return it to one valid state.
Commercial exceptions preserve history, expose uncertainty and establish an owned recovery path. They do not disappear because the systems exchanged data successfully.
Seven exception classes
- Duplicate record
- Preserve both histories. Assign review, merge only verified facts and retire the duplicate deliberately.
- Owner missing
- Stop invisible routing. Assign responsibility and define the next expected action.
- Stale / invalid stage
- Expose the evidence mismatch. Review and return the record to a justified state.
- Next action absent
- Assign review. Record the continuation, or deliberately close or recycle the opportunity.
- Follow-up overdue
- Keep the miss visible. Assign recovery and decide whether to act, reschedule, close or recycle.
- System conflict
- Preserve both values. Reconcile through the defined record-authority path.
- Handoff failed
- Keep the sending owner accountable until the receiving owner accepts, resolves or explicitly reassigns the handoff.
Recovery / An ordered governance path
Preserve
History + evidence
Expose
Conflict + uncertainty
Assign
Recovery owner
Reconcile
One justified state
Act
Defined next action
Confirm
Outcome visible
Owner known. Next action known. Outcome visible.
System A: Proposal. System B: Negotiation. A completed sync does not resolve the disagreement. Preserve both values → expose conflict → authorized evidence review → reconcile → confirm one justified state.
08 / Automation + AI + human authority
Execute known movement. Assist with context. Keep commercial judgment explicit.
09 / Capability composition
The sales operation decides what gets built.
CRM process design and CRM workflow automation follow the operating problem. Fix the current CRM, restructure pipeline, clean records, connect systems or migrate platforms only when justified.
- 01Commercial control first.
- 02Record + ownership second.
- 03Pipeline + next action third.
- 04Architecture fourth.
- 05Tools last.
One capability or a deliberate combination.
CRM, forms, email, automation, AI assistance, reporting, integrations, notifications and handoff tooling may contribute. The commercial architecture decides which pieces belong.
Broader digital operationsUseful data. Explicit boundaries.
Collect only what supports identity, ownership, commercial state, next action, handoff, reporting and necessary decision context. Keep passwords, API keys, OAuth tokens, cookies, session tokens, payment-card information, recovery codes, credentials and private client secrets out of ordinary CRM or form intake.
10 / Delivery method
Map the commercial flow before choosing the machinery.
Observe the live flow, define record authority and human authority, architect the state model, validate exceptions and hand over a maintainable system.
- 01
Observe
Records · actors · activity
- 02
Define
Authority · ownership · state
- 03
Architect
Actions · follow-up · interfaces
- 04
Validate
Normal path · conflicts · recovery
- 05
Hand over
Visibility · control · maintenance
Begin with the current commercial flow
Bring the current pipeline.
We’ll map where commercial control breaks.
Show us where buyer records live, how ownership changes, what stages are meant to represent, how next actions and follow-up work, where duplicates appear, where systems disagree and where handoffs fail.
You do not need to design the solution first.
Map Your Sales OperationStart with a written description of the flow. Keep sensitive records and credentials out of the brief.
General enquiry