Automate Coaching Proposal Creation and Delivery
Nour
Founder, Coachful
Automate coaching proposal creation and delivery by reusing approved service content, assembling confirmed factual fields and assigning a human release owner. Keep the generated document, its delivery, the agreement, payment and service access as distinct states. A faster draft is not useful if it gives the wrong person a promise nobody approved.
This guide uses an original four-part workflow, an eight-field source map and a complete fictional case. Existing Word mail merge handles document assembly; Coachful holds separate service and agreement drafts. The buyer ultimately declines the suitable scope, so the process closes without a signature, charge or client-access grant.
Choose what the automation actually does
Begin with one repeatable service and a clear document owner. Separate stable paragraphs from variable facts such as participant, buyer, currency and version. Decide which source can establish each fact and which changes require a fresh review. Do not generate a personal diagnosis or a business outcome from an ambiguous discovery note.
Microsoft’s current Word guidance describes using a data source and merge fields, previewing results and reviewing individual merged documents. In the approach here, an existing desktop Word template assembles factual fields. The service paragraphs are original, already reviewed content selected before the merge. The merge does not validate authority, decide suitability or check every commercial implication.
The coach uses Mailings to prepare the letter and connect its intended data source, inserts the factual merge fields, then checks Preview Results. Edit Individual Documents supports reviewing the assembled text. Release and the actual recipient check remain separate. A saved merge document can retain its data-source connection, so check the intended source again before reusing it.
This is document assembly in the chosen office tool, not a claim that Coachful supplies a corporate proposal-merging engine. A PDF or document format does not establish that the recipient received, read or accepted it. Do not interpret an open signal or a successful send request as an authorized decision.
1. Collect only the facts needed for the draft
Confirm the service question, buyer, participant, proposed recipient and appropriate information audience. Keep a typed signer’s name separate from verified authority. A sponsor may ask for a proposal without being the participant or the person who can sign on behalf of the contracting entity.
Record the source, date and status of the information. Label an unresolved field rather than filling it from another client’s record. The ICO’s accuracy guidance addresses factual accuracy and clear source and status information. It is currently under review following UK legislative changes; apply the appropriate current rules to the actual engagement.
Limit the information used. A proposal rarely needs private coaching notes or a health history to identify a service and its boundaries. The FTC’s business security guidance supports necessary-data collection, restricted access and fictitious information for training. Those principles inform the synthetic checks below; the guide is not a certification of this workflow’s compliance.
2. Assemble a complete service, not just a personalized greeting
Use approved content for purpose, included work, limits, price basis and the next decision. State exclusions that matter to the buyer. A named leader, a sponsor and a contracting entity have different roles; a mail merge should not silently treat all three as the same person.
Check the delivery capacity behind the service block. Count preparation, response writing, review and closure, as well as live meetings. The coaching proposal template guide develops the document itself. Here, the focus is how verified content reaches the correct version and recipient.
Use clear instructions and persistent field labels. W3C’s Form Instructions guidance distinguishes labels from placeholder text and explains required, optional and format instructions. A blank currency or unexplained date should be visible to the reviewer; it should not be disguised by polished prose.
3. Approve the actual version before releasing it
Name a release owner who checks fit, factual fields, service counts, arithmetic, terms and recipient. Administrative staff can prepare the document without owning every business decision. Record what was checked and what remains a condition before contracting or payment.
A draft may be approved for the buyer’s review while still containing explicit unresolved entry conditions. Label that purpose. Do not use a checkout link or an invitation to sign as a substitute for resolving the contracting party, suitability, information sharing or applicable tax treatment.
Keep an initial error and its correction traceable. Correcting the source matters when later merges use it again. Editing only one generated file can leave the same error ready to recur. Confirm the corrected mapping with the relevant test records before moving back to a real proposal.
4. Hand off using evidence for each state
The proposal’s next step must identify the actual acceptance route and decision owner. If the buyer requests a different participant count, scope or reporting arrangement, return to review. Do not treat an affirmative comment about one paragraph as agreement to every remaining condition.
Signature and money are separate. Stripe’s Setup Intents documentation explains that setting up a payment method for future use creates no charge. A saved method therefore does not establish a settled payment. Follow the actual payment event and permissions if a later accepted engagement uses that route.
Account, entitlement and delivery readiness also need their own checks. A participant’s name on the proposal does not create an account, enroll them in a cohort or give them session credits. Keep the workflow stopped when a prerequisite fails, and assign an owner to close it rather than leaving automated follow-ups running indefinitely.
Build an eight-field source and review map
| Field | Source and status | Review owner |
|---|---|---|
| Buyer and contracting entity | Confirmed buyer brief; signing authority remains separately checked | Coach or contract owner |
| Participant | Confirmed intended person, with fit not assumed from the sponsor’s request | Coach |
| Purpose | Approved discovery summary, with assumptions explicitly labeled | Coach |
| Service and exclusions | Current reviewed service block and actual capacity calculation | Delivery owner |
| Price, currency and tax status | Approved service fee and currency; unresolved tax assessment shown as a blocker | Commercial owner |
| Term and availability | Proposed dates, staffed periods and booking conditions | Delivery owner |
| Information audience | Proposed reporting categories and the participant’s actual answer | Coach |
| Version and delivery recipient | Proposal register and a separately confirmed recipient | Release owner |
The map is original guidance, not a claim that every field is a native feature in every application. Implement it in the tools actually used. An external document source can coexist with a service platform without assuming an integration that has not been configured and checked.
Define the service before testing the assembly
The fictional case takes place on 3–21 March 2042, in UTC. Shirin is the coach and release owner. Devon is an authorized administrator working on the external proposal source and template. Lea is the buyer contact and Bo the proposed participant. Devon’s work does not assume unrestricted access to a coaching workspace or private client content. The existing buyer brief allocates Bo 20 paid minutes for optional fit review and reading the outcome; it does not authorize coaching participation.
On 3 March Shirin spends 30 minutes reading the existing buyer brief and preparing a one-leader service block and capacity estimate. The proposed term is 12 weeks, 5 May through 27 July 2042 inclusive, or 84 days. It has not started.
The service includes six 60-minute private meetings, a 45-minute kickoff and a 45-minute review: 450 live minutes. Eight ten-minute meeting-preparation allowances add 80; two twenty-minute document reviews add 40; twelve ten-minute question reviews add 120; setup and closure add 60. Total planned supplier work is 750 minutes against 840 reserved, leaving 90.
The question allowance is one concise question per week. The proposed twelve Monday receipt cutoffs run from 5 May through 21 July at 12:00 UTC, with a response by Wednesday at 17:00. At or after a cutoff, the next weekly window applies; after the final cutoff, no additional question window is included. Each ten-minute allowance includes reading and returning the answer. The proposal does not call this unlimited support.
The proposed service fee is USD 4,800. Applicable tax determination, participant fit, information sharing and contracting details remain unresolved entry conditions before acceptance or checkout. No fee is charged in this case, and the capacity estimate is not a profit calculation or a promised outcome.
Use synthetic checks that can genuinely fail
Devon spends 60 minutes on 3 March preparing the source map and the original Word template. Stable service paragraphs remain reviewed text; merge fields populate the factual parts. On 4 March Devon spends 30 minutes generating three synthetic records, and Shirin spends 15 reviewing the outputs.
| Synthetic record | Initial review | Required correction |
|---|---|---|
| A: complete intended record | Passes the declared factual and recipient checks | Retain as a regression check |
| B: missing currency | Fails; an amount without its currency reaches the generated draft | Correct the source requirement and release check |
| C: stale recipient mapping | Fails; the output points to a previous synthetic recipient | Correct mapping and verify the actual release recipient separately |
The reviewer blocks B and C. Word has not automatically recognized the commercial or recipient error. None of the synthetic outputs is externally delivered. On 5 March Devon spends 20 minutes correcting the source and mapping, and Shirin spends ten approving those changes.
On 6 March they rerun all three records: Devon uses 30 minutes and Shirin 15. All three pass the declared checks. Record A is actually retested, not assumed unaffected. This is the fictional team’s limited document rehearsal, not an author-performed customer UI test or a guarantee that every future proposal will be correct.
Keep the native service and agreement drafts separate
On 7 March Shirin spends 20 minutes checking separate Coachful Offer and agreement drafts. Both remain held. No Offer is published, agreement activated or recipient copy issued. The external mail merge does not create those records automatically.
If using an Offer template, check the actual session defaults. The released builder can prefill session-access settings and a session type from the coach’s library. Verify the promised inclusion, correct type and quantity in What they get; the template’s title is not proof of the entitlement. Enter and check the real price and currency separately.
For this proposed service, the six private sessions would use the intended 60-minute type. The kickoff and review are separately organized staff-arranged 45-minute meetings, not an assumed second set of automatic credits. They must be fulfilled as stated if an engagement is later accepted. In this case no sessions are booked or granted.
Coachful is our #1 recommendation for organizing the authorized service and agreement handoff behind this workflow. This is an editorial recommendation about that use, not a measured software ranking or a claim that it supplies the Word merge. Explore Coachful’s features alongside the actual document system.
Deliver a review version and obtain the real answers
On 10 March Devon spends 15 minutes reading the confirmed source and assembling proposal P1. Shirin spends 20 reviewing and manually sending it to Lea through the confirmed business email route. It is expressly a review version with the entry conditions still open, not an instruction to pay or a representation that Bo has agreed.
Its central service paragraph states:
P1 review proposal: “This proposal concerns one leader over twelve weeks, with six private meetings, a kickoff, a review and the stated bounded document and question allowances. The service fee is USD 4,800; applicable tax and contracting details require confirmation before acceptance or payment. Participant fit and reporting arrangements are not yet agreed. Please review the scope and identify any requirement that differs. Receipt does not create an agreement, account or service entitlement.”
Lea spends ten minutes on 11 March reading and replying that she wants two leaders and access to all session notes. Shirin spends ten on 12 March reading that response and sending Bo a bounded question about the proposed information audience. No private session notes exist in this case.
Bo spends ten minutes on 13 March reading and replying: “I do not agree to unrestricted session-note sharing. I would consider a private one-leader service with clearly agreed progress categories, but I am not agreeing to coaching or a reporting arrangement through this reply.” The employer has allocated these brief fit-review minutes; participation in coaching remains a separate choice.
On 14 March Shirin spends ten minutes reading Bo’s answer, revising the P2 source information and sending it to Devon. This is combined reading and revision, not ten pure editing minutes. Devon uses ten on 17 March to read, update the fields and assemble P2. Shirin spends ten checking and sending it to Lea.
P2 corrected position: “The available proposal remains for one leader. Bo has declined unrestricted session-note access. Any sponsor reporting would be limited to categories explicitly agreed with the participant; full private notes are excluded. Participant fit, applicable tax and contracting details still require confirmation. We cannot describe the requested two-leader service or unrestricted reporting as included. Please confirm whether the stated one-leader scope meets your need.”
Close an incompatible proposal without starting the next steps
Lea spends ten minutes on 18 March reading P2 and replying that she requires two leaders and unrestricted notes and cannot accept the stated service. Shirin spends five reading that answer. She does not silently change Bo’s answer, promise a second participant or send an agreement to make the sale easier.
On 19 March Shirin spends ten minutes sending Lea, Bo and Devon this closure:
Completed closure: “The proposal is closed without an engagement. The requested participant count and reporting access are not compatible with the stated service and Bo’s answer. No agreement has been issued, payment collected, account granted or service booked. The service and agreement drafts remain inactive. Please do not interpret either review proposal as acceptance or permission to share private content. Any future proposal needs a new scope and appropriate participant and buyer agreements.”
Lea, Bo and Devon each spend five minutes reading it on 20 March. No additional acknowledgment is claimed. The final register records each applicable state:
| State | Actual case evidence |
|---|---|
| Draft | P2 assembled and reviewed, with unresolved entry conditions explicit |
| Proposal delivery | Lea’s actual replies demonstrate receipt of P1 and P2 |
| Agreement | No recipient copy issued; inactive draft retained after decline |
| Payment | No method collected, charge, receipt or invoice |
| Account and access | No client account created or entitlement granted by this workflow |
| Service readiness | No booking or delivery started; proposal closed |
This is a finite business outcome, not a failed automation waiting for a retry. Further signing, payment or invitation messages are not scheduled from the closed proposal. A buyer’s refusal belongs in the record; it should not be overwritten by a generic completed-pipeline status.
Understand agreement versions and delivery records before a later handoff
In a future compatible engagement, deliberate agreement sharing creates recipient-specific copies. An existing client route and an external recipient route are different. Issuing a standalone agreement to a new person does not itself establish a client account, corporate signing authority or payment.
When active agreement wording changes, signed copies retain their signed text. Eligible pending unsigned copies can move to a new version when Update unsigned copies is selected; that option is on by default. Customized recipient copies and the other excluded copy types are not silently rewritten. Review the relevant new-signature or amendment route when changing terms for someone who already signed.
Agreement issuance, invitation email status and signature completion remain separate. An uncertain email is a reason to inspect the existing record before creating another copy. Do not generalize one native retry safeguard to every external merge, email or billing tool. See the intake-to-portal guide for the separate service-access handoff.
Handle an uncertain delivery without restarting the deal
If a later proposal delivery is uncertain, identify the exact file, version, intended recipient, channel and attempt time before retrying. Check the relevant delivery record and, when appropriate, ask the recipient through an authorized route. Do not interpret an uncertain send response as permission to create a fresh agreement, payment request or account.
Reuse the approved version only if its source facts and purpose remain current. A changed participant, price or reporting requirement sends it back to review. Record the new version and what it replaces; do not conceal an earlier error by renaming the old file as though it had always contained the correction.
In this case Lea’s actual replies resolve proposal receipt, while her final answer resolves suitability of the offer for her requirement. There is no failed-delivery retry to perform after the decline. The distinction prevents a technically successful resend from becoming unwanted continuation of a closed sales process.
Count setup, review and recipient work
| Person | Actual active minutes | Used / reserved |
|---|---|---|
| Shirin | Brief and service block 30; initial tests reviewed 15; fixes approved 10; full retest reviewed 15; native drafts checked 20; P1 reviewed and sent 20; buyer answer read and Bo question 10; Bo answer read, P2 source revised and sent 10; P2 reviewed and sent 10; buyer refusal read 5; closure sent 10; case audit 10 | 165 / 180 |
| Devon | Source and merge setup 60; initial fixtures 30; fixes 20; full retest 30; P1 assembly 15; P2 update and assembly 10; closure read 5 | 170 / 200 |
| Lea | P1 read and reply 10; P2 read and reply 10; closure read 5 | 25 / 35 |
| Bo | Fit question read and reply 10; closure read 5 | 15 / 20 |
The bounded setup-and-proposal project uses 375 person-minutes against 435 reserved, leaving 60. Shirin’s final ten-minute audit on 21 March includes reading the register and actual responses and recording the outcome. The uncommissioned 750 delivery minutes are not added as actual service work or treated as revenue.
The evidence is three initial synthetic outputs with two failures, all three passing a full retest, and one real proposal ending in a decline. It does not establish an average time saving, conversion improvement or reduced cost across twelve monthly proposals. Measure comparable complete cycles before making those claims, including maintenance and exception work.
Frequently asked questions
What should be automated first?
Start with confirmed factual fields and reviewed service content. Then define the release owner and failure route. Keep semantic judgments and actual recipient checks visible rather than assuming the merge validates them.
Must every proposal have three tiers?
No. Offer genuine alternatives only when they meet different needs and are deliverable. A single clear scope can be more useful than three artificial prices.
Does a signed agreement establish payment or access?
No. Check the actual configured payment and service steps. Signature, a saved method, collected money, account creation and entitlement are separate facts.
What should happen after the buyer declines?
Record and communicate the close, stop inappropriate follow-ups and preserve the correct version history. Do not create a charge, agreement copy or participant account simply because the earlier draft was complete.
