One owner moves the opportunity
Sales ops owns source, fit, next action, proposal state, and handoff notes for this path.
Win back opportunities
Scale Phase 22 Win Back Guide
Scale Phase 22 Win Back Guide for managing ZartsAlgo sales qualification, discovery, audits, proposals, scope, contracts, onboarding handoff, and win-back workflows at larger client volume.
Sales contract
What this opportunity path must protect.
Use this guide before scaling lead qualification, audits, proposals, contracts, onboarding handoff, or win-back campaigns.
Name the close risk
The main risk is building a proposal before fit, source, scope, and decision path are verified.
Separate promise from implementation notes
Internal caveats, provider limits, raw audit notes, and pricing assumptions stay internal until approved for client-safe language.
Track every opportunity event
At higher volume, every qualification, proposal, objection, approval, win, loss, and handoff needs owner, timestamp, stage, and next action.
Baseline controls
Checks that apply to every sales workflow.
- Confirm source, service fit, urgency, decision owner, contact path, budget signal, and next action.
- Create a task for every promised follow-up, proposal review, contract step, or onboarding handoff.
- Keep scope, exclusions, assumptions, integrations, timeline, and pricing separate.
- Attach every proposal to a lead, client, service, project, approval, and communication record where possible.
- Record sent date, viewed date, follow-up date, objection, probability, and decision deadline.
- Pause proposal work when audit evidence, scope, timeline, or decision path is not verified.
- Use client-safe summary language for audit findings, revenue proof, provider caveats, and launch blockers.
- Move won deals into project, portal, connector, reporting, and onboarding workflows before delivery starts.
- Track lost reason and reactivation window instead of deleting stale opportunities.
- Retest admin, portal, mobile, proposal links, and message copy after changes.
Topic checks
Specific checks for this opportunity path.
- Confirm source, service fit, urgency, decision owner, contact path, budget signal, and next action.
- Capture discovery notes, pain points, current lead flow, provider stack, and decision criteria.
- Use audit evidence before naming scope, price, timeline, or expected improvement.
- Separate included deliverables, excluded work, optional add-ons, assumptions, and dependencies.
- Route proposal, pricing, sensitive claims, and contract language through an approval step.
- Log proposal sent date, viewed date, follow-up task, objection, probability, and decision deadline.
- Pause follow-up when consent, timing, source context, or decision path is not valid.
- Move accepted deals into client, project, task, portal, connector, and reporting records.
- Record payment state, contract state, kickoff date, onboarding owner, and launch blockers.
Checkpoints
Turn the guide into a close-ready checklist.
Each checkpoint can become a field, task, approval gate, sales note, proposal rule, or onboarding requirement.
Sales checkpoint
Confirm source, service fit, urgency, decision owner, contact path, budget signal, and next action.
Sales checkpoint
Capture discovery notes, pain points, current lead flow, provider stack, and decision criteria.
Sales checkpoint
Use audit evidence before naming scope, price, timeline, or expected improvement.
Sales checkpoint
Separate included deliverables, excluded work, optional add-ons, assumptions, and dependencies.
Sales checkpoint
Route proposal, pricing, sensitive claims, and contract language through an approval step.
Sales checkpoint
Log proposal sent date, viewed date, follow-up task, objection, probability, and decision deadline.
Sales checkpoint
Pause follow-up when consent, timing, source context, or decision path is not valid.
Sales checkpoint
Move accepted deals into client, project, task, portal, connector, and reporting records.
Sales checkpoint
Record payment state, contract state, kickoff date, onboarding owner, and launch blockers.
Data hooks
Tables and runtime sources to connect later.
Public pages stay static; live opportunity state should be handled by admin, portal, approvals, and prepared database reads.
automation_runs
Connect this source through admin, proposal, approval, contract, or portal-safe handoff views.
connector_accounts
Connect this source through admin, proposal, approval, contract, or portal-safe handoff views.
portal_users
Connect this source through admin, proposal, approval, contract, or portal-safe handoff views.
proposal_line_items
Connect this source through admin, proposal, approval, contract, or portal-safe handoff views.
proposals
Connect this source through admin, proposal, approval, contract, or portal-safe handoff views.
contracts
Connect this source through admin, proposal, approval, contract, or portal-safe handoff views.
payments
Connect this source through admin, proposal, approval, contract, or portal-safe handoff views.
audit_trail
Connect this source through admin, proposal, approval, contract, or portal-safe handoff views.
Outputs
Make sales measurable and handoff-ready.
Useful sales operations show what was promised, what changed, what closed, and what delivery must inherit.
Qualified opportunity
This output should preserve source, owner, stage, due date, scope state, client-safe status, and next action.
Discovery notes
This output should preserve source, owner, stage, due date, scope state, client-safe status, and next action.
Audit proof
This output should preserve source, owner, stage, due date, scope state, client-safe status, and next action.
Proposal draft
This output should preserve source, owner, stage, due date, scope state, client-safe status, and next action.
Approval state
This output should preserve source, owner, stage, due date, scope state, client-safe status, and next action.
Contract handoff
This output should preserve source, owner, stage, due date, scope state, client-safe status, and next action.
Onboarding checklist
This output should preserve source, owner, stage, due date, scope state, client-safe status, and next action.
Won or lost reason
This output should preserve source, owner, stage, due date, scope state, client-safe status, and next action.