Deployment Brief
Start with a closeout checklist covering acceptance, final deliverables, open issues, feedback ask, archive, and 30-day follow-up task.
Difficulty
Low
Revenue impact
Medium
Operational impact
High
Risk level
Low
When it runs
Evidence in
What AI prepares
- project closeout brief
- client follow-up draft
- open-issue task list
- feedback request
- archive checklist
- measurement event for closeout and future opportunity
Decision rules
- 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.
Human approval point
What stays human
- Do not automate testimonial asks, referral asks, expansion pitches, final acceptance claims, or payment-sensitive messages without owner review.
Quality and stop gates
- Trigger is narrow and observable
- Required evidence is listed
- Human approval point is explicit
- Permission and proof claims are protected
- Measurement plan is defined
How it is measured
- Track closeouts completed, unresolved issues, feedback received, archives completed, testimonial/referral asks approved, follow-up tasks completed, and repeat work generated.
Systems involved
Workflow Dataset Record
Deployment evidence and duplicate boundary
This section is generated from the enriched workflow dataset. It is designed for pilot planning, not as validated outcome evidence.
Buyer Problem
Post-Project Follow-Up is weak when client success teams rely on scattered notes, incomplete fields, and informal judgment instead of a source-backed operating record. The problem is not a missing AI draft; it is the missing owner, evidence, exception status, and review path that decide whether the work can safely move forward.
Economic Logic
The value of Post-Project Follow-Up comes from reducing avoidable rework, misrouting, stalled decisions, and unsupported customer or revenue actions. The pilot should prove that required evidence is captured earlier, exceptions are reviewed by Client success lead, and the team can measure readiness without claiming validated outcome lift.
Baseline Metric
post_project_follow_up_review_ready_rate
Share of post-project follow-up records with source evidence, required business fields, named owner, human review status, exception outcome, and measurable follow-up result before the workflow is expanded.
Source system: CRM record store, workflow owner notes, pilot evidence log, exception review queue, HubSpot, risk review notes
Minimum Viable Pilot
- Duration
- 30 to 60 days
- Sample
- First 100 post-project follow-up records, or all records from one client success segment over 45 days
- Owner
- Client success lead
- Threshold
- At least 90% of sampled post-project follow-up records include source evidence, owner decision, and exception status; 100% of high-impact or customer-visible exceptions receive human review before action.
Unique Workflow Test
Audit 100 post-project follow-up records for source link, required fields, timestamp, owner, exception status, review decision, downstream action, and result. The test passes only when the workflow can separate approved action from blocked, low-confidence, or not-ready records.
Duplicate Guard
Keep post-project follow-up separate from adjacent client success workflows by requiring post_project_follow_up_review_ready_rate, the Client success lead review point, and the source boundary hubspot-customer-onboarding, hubspot-service-hub-onboarding, nist-ai-rmf. Adjacent pages may share data, but this record owns the sampled decision path and exception outcome.
Not Ready If
- Post-Project Follow-Up does not have stable source records, owner fields, or status fields to sample.
- No accountable client success owner can approve exceptions or customer-visible actions.
- The team cannot track timestamp, source, owner, exception, and outcome fields across the pilot sample.
Claim level: Pilot-shaped. Sources support workflow mechanics and pilot design unless field evidence is attached.
HubSpot Customer Onboarding Checklist
Customer onboarding should include kickoff, communication channels, milestones, expectations, training, support, and feedback loops.
HubSpot Service Hub Onboarding Plan
Service onboarding can include ticket imports, ticket pipelines, knowledge base setup, surveys, and support process configuration.
NIST AI Risk Management Framework
AI workflows should include risk mapping, measurement, governance, and accountable human oversight.
Keep moving
Where this workflow connects next
A useful AI build rarely lives on one page. Check the surrounding workflow, the decision rule, and the deployment path before you commit budget.
Workflow group
Customer Success
Compare the nearby workflows that usually break before or after this one.
OpenSales pillar
AI Sales Workflow Deployment
See how sales teams can use AI for pipeline briefs, meeting prep, follow-up, account plans, and stalled deals.
OpenDecision tool
Sample workflow audit
Use the audit format to pressure-test the trigger, evidence, owner, and metric.
OpenIndustry fit
Browse industries
See how this workflow changes by revenue model, buyer urgency, delivery risk, and customer handoff.
OpenService path
AI Workflow Implementation
Build the first version around a sales or revenue workflow that already has demand.
OpenSales review
Pressure-test this sales workflow
Bring the sales motion, the source evidence, and the number this workflow should move.
OpenTL;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?
- Trigger: A project deliverable is accepted, a project closes, final invoice is prepared, or a post-delivery follow-up window arrives.
- 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.
- AI/system action: The system checks source evidence, prepares the proof or feedback output, and flags permission, claim, context, or owner-review requirements.
- Human review point: The project or account owner reviews client satisfaction, unresolved issues, testimonial or referral timing, expansion language, and final acceptance.
- Output delivered: project closeout brief, client follow-up draft, open-issue task list, feedback request, archive checklist, measurement event for closeout and future opportunity.
- 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.
Related Workflow Group
AI Workflows for Customer Success
Compare this workflow against nearby operating problems before choosing the first build. The group shows what usually breaks together, what evidence is needed, and where review still matters.
View Workflow GroupFurther Reading
AI customer health scoring workflow
A field report on customer risk, retention signals, owner review, and measurable follow-up.