Give the role a reliable starting point.
Share proposal versions, follow-up intervals, and who can answer scope or price questions.
Proposal follow-up
Proposal follow-up
Keep issued proposals and customer questions visible after the estimator has completed the offer.
Book a free consultationScope, access, and coverage are agreed with your team.
The day-to-day work
A clear queue. A useful handoff.
Define the recurring work and the evidence your team needs to review it. These building blocks become a role-specific operating plan.
- Confirm proposal delivery
- Send scheduled reminders
- Collect questions
- Record acceptance evidence
What comes back to your team
Work you can see and review.
Proposal follow-up queue
A working record with source references, current status, and the person responsible for the next step.
Question log
A focused view of missing inputs, unanswered questions, and items that need your decision.
Sales handoff
A dated handoff that distinguishes completed work from pending review and unresolved exceptions.
Put the role into practice
From the first brief to the final check.
A practical handoff
A customer asks about a different material. The assistant routes the request to the estimator and follows up after a revised offer is approved.
Illustrative workflow, not a client case study.Check the work before closing the loop.
Link responses to the current proposal and distinguish verbal interest from documented acceptance.
Your systems, your permissions
Fit the role to your environment.
Tool familiarity is considered when defining the role. Your team approves every platform, access level, and source of truth.
JobNimbusAccuLynxEmailYour proposal software
Platform names describe possible working environments, not endorsements or a promise of certification.
Inside the responsibility
What proposal follow-up looks like in practice.
Keep issued proposals and customer questions visible after the estimator has completed the offer. The scope below connects each recurring responsibility to its source information and a checkable working record. Your team confirms the exact steps, templates, and approval limits before work starts.
Confirm proposal delivery
Begin with the latest request and its approved source record. Check that the necessary information is present, identify the owner, and clarify conflicting details before making an update.
Working output: Proposal follow-up queue. Include the source reference, current status, and next owner when an item remains open.
Send scheduled reminders
Use the agreed template or checklist to carry out this task. Record what was checked and the date of the action so another team member can understand the current position.
Working output: Question log. Include the source reference, current status, and next owner when an item remains open.
Collect questions
Keep this work connected to the wider queue. Note dependencies and unanswered questions, and use the agreed escalation route when the next step requires a decision.
Working output: Sales handoff. Include the source reference, current status, and next owner when an item remains open.
Record acceptance evidence
Complete the task only when its agreed checks have passed. If an input is missing or an approval is pending, keep that status visible rather than treating the item as finished.
Working output: Proposal follow-up queue. Include the source reference, current status, and next owner when an item remains open.
A handoff you can act on
Keep ready work separate from unresolved work.
A customer asks about a different material. The assistant routes the request to the estimator and follows up after a revised offer is approved.
Ready for review
The agreed task is complete and the supporting information is available in your approved system. Attach or link the relevant record and identify any final reviewer before closing the item.
Review against: Link responses to the current proposal and distinguish verbal interest from documented acceptance.
Waiting on an input
Name the missing information, where it was requested, and who is expected to supply it. Keep a follow-up date visible. An unanswered request should not disappear into a completed-work total.
Starting requirements: Share proposal versions, follow-up intervals, and who can answer scope or price questions.
Needs your decision
Summarize the exception and the information already checked. Ask a specific question and route it to the authorized person. Keep the original source intact while the decision is pending.
Approval boundary: Pricing, material selection, contract terms, and warranties remain with authorized staff.
Set the role up well
Agree what good work means before the first handoff.
Access and examples
Provide individual, approved access to the systems used for this responsibility. Share a completed example, an incomplete example, the relevant template, and a named reviewer. Sensitive working records belong in those systems, not in a public inquiry form.
Possible working environments include JobNimbus, AccuLynx, Email, Your proposal software. Tool access and familiarity are confirmed as part of the role brief.
Review and workload measures
Agree which measures are useful for this queue: completed items, items awaiting an input, age of unresolved work, and corrections requested by the reviewer. Review these together with actual examples; volume alone does not establish that work is accurate.
Set response expectations from your operating needs. Coverage, turnaround targets, and the amount of work assigned are agreed separately rather than assumed from the service name.
Before you start
A few useful questions.
What should we prepare for proposal follow-up?
Share proposal versions, follow-up intervals, and who can answer scope or price questions.
How will we know what is complete?
Link responses to the current proposal and distinguish verbal interest from documented acceptance.
Which decisions remain with us?
Pricing, material selection, contract terms, and warranties remain with authorized staff.
Can the role work in our existing tools?
We scope the role around your approved systems, including environments such as JobNimbus, AccuLynx, Email. Access, training, and the final tool requirements are confirmed before the role begins.
Related support
Connect the work around this role.
Roofing lead intake
Roofing lead intake
Capture incoming project inquiries in a record your estimator can use.
Explore the service ↗
Inspection scheduling
Inspection scheduling
Coordinate estimator appointments and site access around the availability your team provides.
Explore the service ↗
Customer project updates
Customer project updates
Maintain thoughtful customer communication using the milestones your production team confirms.
Explore the service ↗
Project document organization
Project document organization
Bring estimates, approved changes, site records, and correspondence into a usable project file.
Explore the service ↗A role shaped around your operationStart with the work
Start with the work
you want to hand over.
Tell us where the queue slows down. We’ll discuss the scope, tools, coverage, and review points that belong in your support role.
Book a free consultation
Define the role before making a commitment.