Customer story development

This playbook governs customer success story and case study production for an identified client milestone. One run evaluates a single nominated customer account, validates documented business outcomes against operational evidence, secures formal customer permission, and routes the approved narrative into your content management system or document repository. Operating boundaries require that the agent never publish directly to live public channels without human confirmation, never invent quantitative claims or quotations, and never contact a customer account when an active commercial sensitivity or unresolved support blocker is flagged.

• Extract the nominated customer account details, milestone trigger, and raw interview or survey submissions from the CRM or intake form. Verify that the customer account is in good standing and that contract terms permit advocacy participation. Cross-check initial intake claims against logged CRM implementation dates and benchmark statistics, highlighting any metric or timeline discrepancies for the authoring dossier.
• Information request. Present the account executive or customer success manager with the initial story brief, candidate metrics, and recorded interview excerpts. Request confirmation that the account relationship is currently stable for public advocacy outreach and ask for clarification on any unverified operational metrics. If the account owner indicates an ongoing renewal negotiation or unresolved support escalation, halt outreach and place the case on hold until the relationship blocker resolves.
• Assemble the structured customer story draft according to brand narrative guidelines, dividing the copy into client background, core operational bottleneck, implemented configuration, and measurable business impact. Attribute every direct quote to a specific recorded interview statement and link every quantitative claim to a verified milestone log. Prepare alternate copy blocks for both fully attributed and anonymized publication formats.
• Approval. Present the complete narrative draft, evidence citation table, and proposed permission form to the internal marketing lead. The marketing lead verifies narrative tone, alignment with current messaging strategy, and factual grounding against the evidence dossier. If the marketing lead requests editorial adjustments, revise the draft and resubmit; if the draft is approved, proceed to external customer review.
• Transmit the approved draft and attribution agreement to the designated customer stakeholder, specifying the exact quotes, quantitative claims, and logo assets requested for public release. Require formal written sign-off confirming the accuracy of all attributed statements and defining permitted distribution channels.
• Approval. Review the customer's returned sign-off and permission grant with the marketing editor. Verify whether the customer authorized full corporate attribution, restricted quote usage, required specific metric redactions, or mandated an anonymized company profile. If an anonymized profile is required, prepare the exact proposed pseudonym and scrubbed descriptive phrasing and obtain customer written sign-off on that specific anonymized version before moving forward. Once customer consent is validated, proceed to staging the draft.
• In a fictional scenario, an advocacy manager initiated a story run for Northwind Freight following their annual contract renewal. Intake notes from a post-implementation survey reported that Northwind achieved a 60% acceleration in warehouse dispatch. During evidence reconciliation, logged warehouse telemetry in the CRM showed dispatch cycle times decreased from 45 minutes to 27 minutes—a 40% improvement, while administrative filing time decreased by 60%. Rather than propagating the inflated 60% dispatch claim, the agent documented the distinction in the evidence table. When presented with the draft, the account owner confirmed the 40% figure with Northwind's logistics director. Northwind approved the revised copy with an authorized executive quote but withheld permission for vector logo display. The agent updated the publication payload to text attribution without logo assets, staged the draft in Webflow, and notified the marketing lead. After verifying the staged preview, the marketing lead authorized public release. The agent executed the publish action, verified the published Webflow live URL and item status via API read-back, and logged the confirmed placement.
• Stage the finalized case study draft, approved imagery, and authorized metadata in the designated destination, such as Webflow CMS, HubSpot blog staging, or a central Notion repository. Read back the staged record identifier and revision status from the destination platform to verify successful draft creation.
• Approval. Present the staged preview, read-back verification receipt, and verified customer consent record to the marketing lead for final publication authorization. The marketing lead inspects the live preview rendering, confirms the publication schedule, and chooses whether to execute immediate live publishing via API, assign an explicit manual publication handoff to a named webmaster with a scheduled release date, or hold the draft. If live publication is declined or indefinitely deferred, record the decision and move the case to Declined or unresolved.
• Exception. If the CMS API is unreachable, authentication fails, or required destination schema fields are missing during staging or live publication, log the exact error payload and retain the approved markdown artifact and customer sign-off records in the workspace. Notify the content operations lead with the payload for manual entry, keeping the case pending until manual placement confirmation is verified.
• Conclude the case only after verifying the approved live publication placement via API read-back or documenting an accepted handoff receipt with an accountable release owner and date, transitioning the board column to Outcome confirmed. If the customer explicitly declines participation, revokes quote approval, or fails to respond after scheduled follow-up periods, record the decision reason, archive the unreleased draft, and transition the board column to Declined or unresolved.