WORKED EXAMPLE · FICTIONAL DETAILS
A consultant’s quote approval workflow
A quote follow-up should help establish the next decision. It should not assume that a viewed proposal was accepted or that silence commits the client to a scope, amount or start date.
Record the version and decision requested
For a fictional independent consultant, a proposal shared on 3 November 2026 offers a defined research scope. Record the project label, proposal version and what you asked the client to decide. An internal target to start work on 12 November is your plan unless the client explicitly agrees to it.
Choose a contact date with context
If the client says they will review on 7 November, record that promise and plan a later check-in. If no review date was discussed, ask when a check-in would be useful. Keep the quote’s actual validity date separate from your next contact date; do not manufacture urgency or change the agreed terms in a reminder.
Move the record only after a real update
A request for clarification belongs in the record as a question or dependency. A revised scope needs a new explicit decision; it is not a completed approval. When the client declines or pauses, record that outcome rather than repeatedly prompting them as though a decision is still due.
Keep it single-user and reviewable
PakkaFollow’s reviewed workflow is a personal workspace, not a shared sales CRM, electronic-signature service or legal proof of acceptance. It helps keep recorded dates and the next step together. Account access and payments remain gated by the planned public subscription release.
Editable message examples
Check names, dates, amounts and permissions. Send through your usual channel only when you choose.
Quote decision
Hi Jordan, following up on the research proposal shared on 3 November. Are there any scope questions I can clarify before you decide?
A paused project
Thanks for the update. I’ll mark the proposal as paused. If your timing changes, please let me know and we can review the scope again.