Function: Client success
AI Workflow for Post-Project Follow-Up
Deployment Brief
Start with a closeout checklist covering acceptance, final deliverables, open issues, feedback ask, archive, and 30-day follow-up task.
Related Field Report
- AI customer health scoring workflow: A field report on customer risk, retention signals, owner review, and measurable follow-up.
Quick Answer
An AI workflow for post-project follow-up prepares a closeout brief, open-issue list, feedback request, archive task, and future follow-up plan after delivery. It should separate final acceptance, support issues, testimonials, referrals, and expansion ideas so the client is not overwhelmed. A project or account owner reviews client-facing messages, unresolved issues, and any ask for proof, referral, or future work.
TL;DR
A project is not finished when the final file is sent. Closeout should protect the relationship, capture feedback, and create the next useful follow-up.
What is post-project follow-up?
Post-project follow-up is the structured closeout process that confirms completion, captures feedback, preserves project knowledge, and identifies appropriate next actions.
Who is this workflow for?
- Agencies, consultants, construction/service firms, SaaS implementers, freelancers, and professional service teams that deliver projects for clients.
- Teams where projects end abruptly and future work, referrals, or lessons learned get missed.
- Owners who want a clean closeout without sounding pushy.
What breaks in the manual process?
The manual process fails when delivery is treated as the finish line. Files are sent, the next project starts, feedback is forgotten, and nobody owns the follow-up conversation.
How does the AI-enabled process work?
The workflow reviews deliverables, acceptance, open issues, notes, invoice status, outcome evidence, and customer relationship context. It prepares closeout tasks and drafts the right follow-up sequence for review.
What does this look like in practice?
Example scenario: A website project is approved, but one analytics handoff item remains open. The workflow drafts a closeout note that confirms acceptance, keeps the handoff task internal, schedules a feedback request, and holds the testimonial ask until the open item is resolved.
What decision rules should govern this workflow?
- Confirm acceptance before asking for testimonials or referrals.
- Separate open support issues from proof or expansion asks.
- Archive final deliverables and decision records.
- Route client-facing follow-up to the account owner.
- Pause when payment, scope, or satisfaction is unresolved.
What are the implementation steps?
1. Trigger: A project deliverable is accepted, a project closes, final invoice is prepared, or a post-delivery follow-up window arrives. 2. Inputs collected: final deliverables, client acceptance status, open issues or support items, project results and notes, invoice or payment status, testimonial or referral eligibility, archive requirements, account owner review rules. 3. AI/system action: The system checks source evidence, prepares the proof or feedback output, and flags permission, claim, context, or owner-review requirements. 4. Human review point: The project or account owner reviews client satisfaction, unresolved issues, testimonial or referral timing, expansion language, and final acceptance. 5. Output delivered: project closeout brief, client follow-up draft, open-issue task list, feedback request, archive checklist, measurement event for closeout and future opportunity. 6. Measurement logged: Track closeouts completed, unresolved issues, feedback received, archives completed, testimonial/referral asks approved, follow-up tasks completed, and repeat work generated.
Required inputs
- final deliverables
- client acceptance status
- open issues or support items
- project results and notes
- invoice or payment status
- testimonial or referral eligibility
- archive requirements
- account owner review rules
Expected outputs
- project closeout brief
- client follow-up draft
- open-issue task list
- feedback request
- archive checklist
- measurement event for closeout and future opportunity
Human review point
The project or account owner reviews client satisfaction, unresolved issues, testimonial or referral timing, expansion language, and final acceptance.
Risks and stop rules
- client asked for proof before issues are resolved
- future work suggested before acceptance
- project knowledge not archived
- feedback and testimonial asks blended into one awkward message
Stop the workflow when permission is missing, claims are unsupported, customer issues are unresolved, sensitive details are involved, or the next action would create a public proof, customer ask, or relationship-sensitive message without approval.
Best first version
Use a closeout checklist with acceptance, final deliverables, open issues, feedback ask, archive, and 30-day follow-up task.
Advanced version
The advanced version adapts closeout by project type, satisfaction signal, payment status, renewal opportunity, testimonial eligibility, and future-work potential.
Related workflows
- AI Workflow for Client Reporting
- AI Workflow for Testimonial Request
- AI Workflow for Referral Request Timing
- AI Workflow for Case Study Candidate Selection
- AI Workflow for Account Value Recap
Measurement plan
Track closeouts completed, unresolved issues, feedback received, archives completed, testimonial/referral asks approved, follow-up tasks completed, and repeat work generated.
What not to automate
Do not automate testimonial asks, referral asks, expansion pitches, final acceptance claims, or payment-sensitive messages without owner review.
FAQ
What is post-project follow-up?
It is the structured process for confirming completion, capturing feedback, archiving project knowledge, and identifying next actions after delivery.
What can AI prepare?
AI can prepare the closeout brief, open issue list, feedback request, archive checklist, and follow-up tasks.
What should stay under human review?
Client-facing messages, unresolved issues, testimonial timing, referral requests, and future-work language should stay under owner review.
What is the simplest first version?
Use a closeout checklist with acceptance, deliverables, open issues, feedback ask, archive, and 30-day follow-up.
How should this workflow be measured?
Measure closeout completion, feedback received, issues resolved, archive completion, follow-up tasks, proof asks, and repeat work.