FS-DOC-01Operations
Launch Plan
Client Onboarding & Engagement Letters
Audience
Practice Manager / Process Owner
Process
Client Onboarding & Engagement Letters
Build option
Standard (recommended)
01What you're launching
This launch covers the end-to-end automation of client onboarding at [YourCompany.com]. Today, every step from drafting the engagement letter to setting the client up in Karbon is done by hand. The process takes up to 3 weeks, costs around $16,400 a year in staff time, and loses roughly 7 hours every week to avoidable manual work. After this build, three agents handle the repetitive work. A person only steps in to review anything that requires judgement or compliance sign-off. The result is a client who goes from yes to ready-to-work in 4 days, not 3 weeks.
Step
Current owner
Time today
After automation
Status
Draft Engagement Letter
Practice Manager
40 min
Automated by Engagement Letter Agent
Automated
Send For Signature
Practice Manager
20 min
Automated by Engagement Letter Agent
Automated
Run ID And AML Checks
Practice Manager
45 min
Auto-run; unclear cases flagged to person
Human review if needed
Request Client Documents
Onboarding Admin
35 min
Automated by Document Collection Agent
Automated
Set Up In Systems
Onboarding Admin
50 min
Automated by Onboarding Setup Agent
Automated
Confirm Ready To Work
Practice Manager
20 min
Automated notification to team
Automated
Volume: approximately 15 new clients per month. The trigger is a client being marked won in the CRM. Sensitive compliance steps stay with a person by design and are never removed from human oversight.
02Before build starts
The items below must be confirmed before the builder can start. Delays in access or decisions here will push back the go-live date. The Practice Manager is responsible for completing or delegating each item.
Confirm the build option : Standard build is recommended. Agree with your builder before any work begins.
Identify the process owner : One named person at [YourCompany.com] must be available to answer questions and approve outputs throughout the build.
Provide admin access to Karbon : The builder needs an admin-level Karbon account to configure client creation and workflow steps.
Provide access to PandaDoc : Admin or API access is required to configure engagement letter templates and signature workflows.
Confirm the Gmail account for document requests : Provide the sending address and confirm it can be connected via OAuth. A shared inbox is preferred.
Confirm FullSpec Automation credentials : The orchestration environment must be provisioned before build week 1 begins.
Provide a sample engagement letter template : Share the current Google Docs template so the builder can map fields for automated population.
Confirm the CRM trigger field : Identify exactly which CRM field or status change signals a client is won. This is the automation trigger.
Agree on ID and AML check escalation rules : Define what conditions cause the system to pause and flag a case to the Practice Manager rather than proceed automatically.
Confirm who receives the ready notification : Decide which team members are notified when a client is confirmed ready to work.
Agree on document request reminder timing : Set the number of days between automatic reminders and a maximum reminder count before manual escalation.
Review and confirm tooling costs : FullSpec Automation: $165/month. PandaDoc: $25/month. Karbon and Gmail carry no additional monthly cost for this build.
Launch PlanPage 1 of 3
FS-DOC-01Operations
03Build phases
The Standard build runs over 4 weeks. Each phase has a clear output that must be confirmed before the next phase begins. The Practice Manager should allow 1 to 2 hours per phase for review and approval.
1Foundation and integrations
Week 1: Provision the environment and connect all tools
- FullSpec Automation environment provisioned and configured.
- Karbon connected with secure authentication and tested.
- PandaDoc connected; engagement letter template imported and field-mapped.
- Gmail account connected via OAuth; sending permissions confirmed.
- CRM trigger tested: a won client record fires the automation correctly.
- Milestone: All integrations live and passing connection tests. Owner signs off before Phase 2 begins.
2Agent builds and unit testing
Weeks 2 to 3: Build and test each agent in sequence
- Engagement Letter Agent built: pulls client details, populates template, sends via PandaDoc for signature. Tested against 3 sample clients.
- Document Collection Agent built: sends document and ID request email, fires reminders on schedule, tracks outstanding items. Tested for reminder cadence and completion detection.
- Onboarding Setup Agent built: creates client record in Karbon, applies correct job templates, sends ready notification. Tested against a sandbox Karbon environment.
- Compliance escalation path tested: cases that do not clear ID and AML checks are correctly paused and flagged to the Practice Manager.
- Milestone: Each agent tested in isolation and producing expected outputs. Owner reviews a sample run of each agent before Phase 3 begins.
3End-to-end QA and go-live
Week 4: Full regression, stakeholder sign-off, and launch
- Full end-to-end run completed using a real or near-real client record.
- Practice Manager and Onboarding Admin review outputs at each handoff point.
- Edge cases tested: unsigned letter after 7 days, missing documents, failed AML check.
- Monitoring and alerting confirmed: the team receives a notification if any step stalls.
- Go-live checklist completed (see Section 04).
- Automation set live. A short tuning period of 1 to 2 weeks runs against real data before the process is considered fully stable.
- Milestone: Stakeholder sign-off obtained. Automation running on live clients.
04Go-live checklist
Complete every item below before switching the automation on for live clients. If any item cannot be checked off, the launch should be held until it is resolved.
All tool connections tested and passing : Karbon, PandaDoc, Gmail, and FullSpec Automation all returning successful test calls.
Engagement letter template producing correct output : Client name, service scope, fee, and date all populate correctly from the CRM record.
PandaDoc signature request delivered to a test email address : Confirm the recipient receives the email and the signing experience works end to end.
Document request email reviewed and approved by Practice Manager : Tone, content, and requested document list signed off before go-live.
Reminder schedule confirmed and tested : At least one reminder fires at the correct interval in the test environment.
AML escalation path tested : A flagged case correctly pauses the automation and notifies the Practice Manager without proceeding to system setup.
Karbon client record created correctly in test : All required fields populated; correct job template applied; no duplicate records created.
Ready notification sent to correct team members : All named recipients receive the notification. Content is accurate.
Monitoring alerts configured : The team is notified if the automation stalls for more than 24 hours at any step.
Rollback plan agreed : If the automation produces an error on a live client, the team knows the manual fallback steps and who to contact.
Process owner has confirmed go-live approval : Practice Manager has reviewed the end-to-end test run and given written or verbal sign-off.
Launch PlanPage 2 of 3
FS-DOC-01Operations
05Your role vs your builder's role
This table clarifies who is responsible for what during the build and after go-live. Neither party can complete their work without the other holding up their side.
Task
Your role ([YourCompany.com])
Builder's role
Provide tool access and credentials
Owner action required
Receives and stores securely
Supply engagement letter template
Owner action required
Maps fields and configures agent
Define escalation and compliance rules
Owner decision required
Builds logic to the agreed rules
Review and approve agent outputs during build
Owner review required
Prepares test outputs for review
Confirm go-live sign-off
Owner sign-off required
Presents end-to-end test results
Build and configure all three agents
Not required
Builder responsibility
Connect and authenticate all tools
Provides credentials
Builder responsibility
Write and run test cases
Spot-checks outputs
Builder responsibility
Monitor automation post go-live (first 2 weeks)
Reports anomalies
Responds and resolves
Train staff on new process
Owner action required
Provides process summary
Adjust reminder timing or thresholds after go-live
Requests changes
Implements on request
Handle compliance review of flagged cases
Owner action required
Not in scope
Sensitive steps, including compliance review and final client approval, stay with the Practice Manager by design. The builder configures the automation to pause and hand off correctly; it does not make compliance decisions.
06What success looks like
The table below sets out the target outcomes at week 1, month 1, and month 3 after go-live. These are the benchmarks to track against the current state. All figures are based on approximately 15 new clients per month at the agreed hourly rate of $45.
Metric
Before automation
Week 1 target
Month 1 target
Month 3 target
Time to client ready
3 weeks
Under 1 week
4 days consistently
4 days or less
Hours spent per client on onboarding admin
7 hrs/client
Reduced, tuning in progress
2 hrs/client
2 hrs/client or less
Steps completed without omission
Occasional gaps
All steps tracked
100% tracked
100% tracked
Weekly hours saved
Baseline: 0
3 to 4 hrs/week
5 hrs/week
5 hrs/week
Annual staff cost for this process
$16,400
Reduction beginning
On track to $4,700
$4,700 annual rate
Client satisfaction (relative change)
Baseline
Early feedback collected
+10% vs baseline
+22% vs baseline
A tuning period of 1 to 2 weeks after go-live is normal. Week 1 targets reflect a system that is live but still being calibrated. Month 1 targets assume the tuning period is complete and the automation is running stably on real clients.
Next step: complete the pre-build checklist in Section 02, confirm the build option with your chosen builder, and agree a start date. The Standard build runs 3 to 4 weeks from the point all access and decisions in Section 02 are in place.
Launch PlanPage 3 of 3