From a client brief to a proposal you can approve
A new request arrives with a rough brief, an ambitious deadline, and a few unanswered questions. Give it a clear path from intake to a response you are ready to stand behind.
This example chooses a human checkpoint for commercial commitments. Other stages can use automatic checks, and you can configure a different level of autonomy.
The situation
You run a small agency. A prospect asks for a product launch campaign: a landing page, three emails, and social posts, ready in four weeks. Their budget, target audience, and approval process are missing. You need a useful first response without quietly committing your team to a scope or date.
Start with one ticket
Review the attached client brief. Summarize the requested deliverables and deadline, list the information we still need, and draft a response proposing the next conversation. Keep confirmed facts separate from assumptions. Do not invent a price or promise a delivery date.
Paste the request or attach the brief to the ticket. Add your service descriptions, qualification checklist, and approved response examples to the project workspace.
A workflow to configure
- Qualification: an agent extracts the requested work, known constraints, and unanswered questions. The ticket keeps a link to the source brief.
- Response draft: a writing step uses that summary and your approved service information to prepare a reply and a provisional scope outline.
- Chosen human checkpoint: in this example, an owner decision step holds the draft for you. Confirm the interpretation, remove unsupported commitments, and approve it or request corrections. An automatic checking step can handle repeatable qualification rules before this checkpoint.
What you get
- A short qualification brief covering deliverables, constraints, and missing inputs.
- A focused question list: budget range, audience, available assets, and who approves the work.
- A draft reply that acknowledges the request and proposes a next step.
What to check before approving
Every requested deliverable should trace back to the brief. Unknowns should remain explicit. Pricing, availability, and commitments need your confirmation. Send the approved response through your usual email or CRM; this workflow does not assume an inbox integration.
The practical result: a client request reaches you as a structured decision and a draft to review. Feedback stays with the ticket for the next revision.