Lead intake
Website requests arrive by email, but no one owns first reply timing, follow-up due dates, or close reasons.
Scope lead intake workflowLead quality resource
Workflow bottleneck examples.
Clear requests describe the workflow, current tool, owner, and success metric. These examples help turn a vague note into a fixed-scope revenue workflow build that can be reviewed without guessing.
Useful request shape
Describe the stuck handoff, not the tool you want first.
Quote follow-up
Quotes are sent from email, then there is no review date, quote owner, revision status, or stale-quote queue.
Scope quote follow-up workflowInvoice/payment
Accepted work moves to invoicing, but payment evidence, owner review, and delivery-start approval are tracked manually.
Scope invoice handoff workflowDelivery handoff
After payment or approval, customer inputs, access boundaries, delivery owner, and completion proof are not in one queue.
Scope delivery handoff workflowBefore sending
Include enough detail for owner review.
A good workflow note is specific enough to prepare a draft scope, but it should not include passwords, wallet seeds, private keys, customer secrets, or payment credentials.
- Where the request or handoff starts
- Which tool or spreadsheet exists today
- Who owns the next action
- What status, due date, or evidence is missing
- What result proves the workflow is working