Sent
The proposal has a sent date, buyer role, internal owner, decision path, and expected response window.
- Sent date
- Buyer role
- Owner
Proof Asset
Show the follow-up path
A proposal workflow should make the next action obvious after send. The useful view is not a pretty pipeline. It is a simple path showing owner, buyer input, risk, review date, and what happens next.
Direct answer
A proposal workflow should start after send
The workflow should show who owns the proposal, what the buyer still needs to provide, which internal review is required, why the deal is at risk, and what action happens next.
Waiting on input
The team can see which specs, site facts, drawings, budget confirmation, or procurement details are missing.
- Specs
- Site facts
- Budget
Action due
The next step is visible: follow up, escalate, revise, schedule review, wait, or close the loop.
- Follow up
- Escalate
- Review
Workflow diagram
Keep the path simple enough to run weekly
This is the practical sequence a team can inspect during the plan. Each step should have an owner and a clear reason for moving forward.
1. Proposal sent
Record what was sent, who received it, what assumptions were included, and what response date matters.
- Scope
- Assumptions
- Response date
2. Buyer input check
Confirm whether the buyer owes technical details, site inputs, commercial approval, procurement steps, or stakeholder feedback.
- Inputs
- Approval
- Feedback
3. Risk review
Flag the reason a proposal may stall: no owner, no response, missing input, plan change, budget concern, or decision delay.
- Risk reason
- Owner
- Deadline
4. Next action
Assign the action that keeps the opportunity honest: follow up, revise, escalate, schedule review, wait, or close the loop.
- Action
- Date
- Outcome
Review rhythm
The weekly view should show exceptions
Leadership should not review every proposal line by line. The workflow should surface proposals that are late, unclear, ownerless, or valuable enough to deserve attention.
Late response
The expected buyer response date has passed and the next owner action is not complete.
- Response date
- Owner action
- Escalation
Missing input
The proposal cannot move because the buyer, partner, estimator, or specialist still owes context.
- Input owner
- Missing item
- Due date
High-value risk
The opportunity is valuable enough that proposal risk should be visible to leadership before it goes stale.
- Value
- Risk
- Leadership review
Related paths
Connect the workflow to the operating system
The diagram is useful when it ties back to CRM stages, dashboard fields, and the proposal follow-up system the team actually runs.
Proposal system
Use this guide when the workflow needs a practical follow-up operating model.
- Owner
- Input
- Risk
CRM stage map
Use this when proposal status needs clearer stages and exit criteria in the CRM.
- Stage
- Owner
- Action
Pipeline dashboard
Use this when workflow exceptions should appear in the weekly leadership view.
- Risk
- Status
- Next action
AI system fit
What AI can run here
For proposal workflow, the useful AI system is not a generic chatbot. It is an operating layer that reads project or buyer context, prepares the next owner action, flags missing information, and keeps follow-up visible. The team still owns technical judgment, pricing, plan, proposal language, and customer commitments.
Inputs to bring
Bring the source material already used to judge the opportunity: CRM fields, RFQs, forms, call notes, proposal status, files, source pages, buyer role, owner, due date, and missing facts.
- CRM and forms
- RFQ or proposal context
- Owner and due date
Useful AI work
AI can summarize inquiries, classify readiness, draft missing-info requests, prepare handoff notes, update operating views, and surface stale follow-up before opportunities drift.
- Summaries
- Readiness classification
- Follow-up prep
Human gate
A person approves technical fit, engineering assumptions, pricing, legal terms, customer promises, sensitive language, and whether the opportunity deserves specialist time.
- Technical approval
- Pricing and plan
- Customer promise
Next pages
Keep the diagnosis connected
Technical buyers often need more than one page before they trust the recommendation. These links connect the specific problem to the larger AI System Plan path.
Technical AI Systems
Use the hub when the team needs the full view of project context, specialist handoff, proposal follow-up, and pipeline visibility.
- Hub
- Use cases
- Technical fit
Run the scorecard
Use the AI Infrastructure Scorecard when the page points to a repeatable project context or qualified-demand problem.
- Inputs
- Build decision
- Next step
Conversion Skills
Use Conversion Skills to see the public method behind prompts, tools, review gates, handoffs, and repeatable AI work.
- Skills
- Tools
- Review
Next step
Find the gap first
Start with the repeated work, the source material, and the business result. Then choose strategy, an agent, or a custom AI system.
Choose the AI path