ChiefOSby ConversintStart free
Menu
← Back to the library
Sales and customer relationships

Sales collateral storyline

Create, rewrite, audit, regenerate, publish, and maintain Conversint offering brochures and seller briefs as repeatable collateral. Use whenever the user asks for a brochure, PDF brief, sales deck-style PDF, marketing collateral, buyer-facing offer document, downloadable resource, case-study/proof page, website resource PDF, or says a brochure design/copy is weak, ugly, off-brand, overlapping, too AI-written, or not ready for clients. This skill coordinates copywriting, PDF generation, visual QA, Google Drive updates, website resource updates, ROI proof, and marketing learning-loop capture.

Works with the context you provideVersion 2.0.0Historical revision

# Offering Brochure

Use this skill to turn a Conversint offering, campaign, service module, or growth priority into polished buyer-facing brochure collateral that can be stored in chiefOS, Google Drive, and the Conversint website.

This is not a generic PDF-writing skill. It owns the full loop: offer context, copy, proof, design, PDF generation, visual audit, website resource update, Drive refresh, commit, and learning capture.

Related Skills

Use these skills with this workflow when relevant:

  • `/copywriting` for headlines, page copy, CTA language, and AI/dead-phrase review.
  • `/pdf` for PDF generation, text extraction, page rendering, and layout inspection.
  • `/marketing-roi` for proof standards, ROI claims, case-study evidence, and attribution caveats.
  • `/marketing-learning-loop` for storing what the brochure is testing and what buyer response teaches.
  • `/content-strategy` for deciding what supporting content or buyer assets the brochure should point to.
  • `/campaign-planner` when the brochure is part of a larger campaign.
  • `/gdrive` only when the user explicitly asks to update or upload Drive files.
  • Higgsfield/image-generation skills when the brochure needs original people-forward imagery or branded visual assets; use `references/image-generation-routing.md` so Codex `image_gen` or the current runtime's image tool can backstop static imagery when Higgsfield is unavailable.

Required Context Load

Before writing or editing:

1. Read Conversint brand and voice context: - `references/conversint-brand.md` - `references/org/identity.md` - `references/org/positioning.md` - `references/org/anti-patterns.md` - `references/marketing-message-governance.md` - `research-thought-leadership/conversint-messaging-optimization/active-message-catalog.md` when the brochure tests or adapts a message - `references/client-deliverable-standards.md` § 3 - `references/output-paths.md` 2. Read this skill's references: - `references/page-arc.md` - `references/design-qa.md` - `references/publishing-checklist.md` - `../../../references/image-generation-routing.md` when generating or editing imagery 3. If the brochure is tied to an active project, read `references/active-projects.md` and the relevant `/project-manager` ledger. 4. If the brochure uses prior results, case studies, or ROI claims, use `/marketing-roi` standards. Do not invent numbers. 5. If the brochure updates a website resource, inspect the existing website repo/component/generator before editing. 6. If the brochure supports a sales conversation, read `references/sales-playbook.md`. If it is built around a specific buyer pain or campaign, read the relevant evidence in `references/org/value-signals.md`. 7. Before a maintained brochure generator is treated as release-ready, run `scripts/python scripts/validate-marketing-messaging.py --consumer <generator-path>`. Add `--publish` before publishing any brochure that lists Conversint services.

Output Locations

Default source path for internal Conversint offering brochures:

```text research-thought-leadership/<offering-slug>/ ```

Expected files:

```text research-thought-leadership/<offering-slug>/README.md research-thought-leadership/<offering-slug>/scripts/generate-<offering-slug>-brief.mjs research-thought-leadership/<offering-slug>/assets/ ```

Generated PDFs are local build artifacts and Drive/share artifacts, not Git artifacts. The latest shareable PDF lives in Google Drive; the latest maintainable source lives in Git as the generator, README, structured data, and assets. Rebuild the local PDF from the generator when editing or publishing, then update the existing Drive file in place.

On the first Drive upload, record the returned Drive file ID and URL in the brochure's `README.md`. On every later refresh, use that recorded ID with `/gdrive --update-id` so the same Drive file, link, sharing settings, and comments are preserved. Create a second Drive PDF only when the user explicitly asks for a separate edition.

If the brochure is also a public website download, mirror the generated PDF into the website repository's resource path and update the download/link component there.

Intake

Resolve these from the conversation, files, meeting notes, or active project context before asking:

  • Offering or campaign name.
  • Who the brochure is for.
  • What decision the reader should make next.
  • Where the brochure will be stored or used: chiefOS only, Google Drive, website, sales email, client handoff, or all.
  • Whether this is Conversint selling itself, a client-facing deliverable for a named client, or internal enablement.
  • Required team names and public-facing roles.
  • Proof sources available: prior projects, case studies, stats, ROI models, customer examples, testimonials, completed work, or response data.
  • Whether an existing Drive file should be updated in place.
  • Whether an existing website resource must stay on the same URL.

If the brochure is for Conversint selling itself to a prospect, do not make the prospect the subject of the brochure. Tailor the offer to the prospect's likely work without making the copy feel like a client-specific proposal.

Workflow

1. Build The Story Before The PDF

Use `references/page-arc.md`.

Write the page-by-page story first. The brochure should read as one argument, not disconnected slides. Each page should answer the prior page about:

  1. The buyer's reason to care.
  2. The problem and belief behind the offer.
  3. The concrete work the buyer can expect.
  4. The work or result delivered.
  5. How progress will be assessed.
  6. The available evidence.
  7. The people involved.
  8. The next decision or conversation.

These are planning prompts, not headings or copy to reproduce. Derive every buyer-facing heading and sentence from the offer, available buyer evidence, and the required core context.

Do not promote internal planning labels into buyer-facing headings or copy. Derive that language from the required core positioning, buyer evidence, and offer-specific context.

2. Draft Copy With Buyer Language

Use `/copywriting` and the required core context.

The skill must not prescribe customer-facing phrasing or maintain a local phrase list. Use the approved positioning, brand, and anti-pattern sources as the authority, then adapt the language to the buyer and offer at hand. Make the buyer want the outcome before naming the mechanism.

3. Design With Real Visual QA In Mind

Use `references/design-qa.md`.

For brochure design:

  • Use people-forward visual assets when the offer involves consulting, collaboration, or execution.
  • Use real or generated bitmap imagery, not decorative SVG filler.
  • Make images reveal the product, team, work, buyer state, or evidence. Avoid purely atmospheric or badly cropped media.
  • Keep text blocks stable. Do not rely on optimistic text length.
  • For every card, callout, pill, or button, size the container from measured text height plus explicit top and bottom padding. Do not eyeball card heights from prior copy.
  • Pills and buttons must center text optically on the vertical axis. Do not use a raw magic `y + 8` or `y + 9` offset. Measure the text height for the actual font/size, calculate the label Y position from `(pillHeight - textHeight) / 2`, then apply a small named optical correction only if the rendered all-caps label still reads high or low. Render-inspect it.
  • Any Conversint-owned contact action or visible Conversint URL in a marketing PDF should link to `https://conversint.ai/contact` by default. Use the homepage only when the user explicitly asks for a homepage link or the context is informational rather than action-oriented.
  • Do not let repeated proof/result cards each invent their own internal layout. Use a consistent metric column, content column, vertical grouping, and accent treatment so the section reads as one designed grid.
  • Multi-step process callouts need a coherent row system: consistent row heights, centered number markers, aligned text baselines, and dividers that support rather than compete with the content.
  • Control hero line breaks when the intended read is clear. A technically valid automatic wrap is not enough if the headline reads better as a deliberate two-line or three-line composition.
  • Avoid white-background logo assets on tinted or dark surfaces. Use a transparent logo asset, or a transparent icon plus text treatment, when the background is not white.
  • Avoid cards inside cards.
  • Avoid pill labels that only look centered in code. Render and inspect them at full page scale and zoomed crop.
  • Avoid cramped page layouts. More pages are better than overlapping copy.

4. Generate The Artifact

Prefer a deterministic generator script in `scripts/` when the brochure must be maintained and regenerated.

Rules:

  • Keep source copy and layout in the generator or structured data.
  • Use stable page dimensions and explicit text widths.
  • Before finalizing a grid/card page, verify each card has enough bottom padding after wrapped body text. If any body text lands within 12px of the card border or appears clipped in render, increase card height, reduce copy, or split the page.
  • Brochure generators must fail loudly when text does not fit. Card helpers should measure label, heading, and body text with the actual font/size/width and throw an error when the final line would fall inside the bottom padding. Do not allow silent overflow.
  • Reusable layout helpers should return or enforce the actual height they used. Do not scatter fixed card heights throughout a script without a fit check.
  • Use helper functions for text, images, pills, cards, and page chrome.
  • Centralize URLs such as contact-page CTAs in named constants. Do not leave duplicated link targets across cover, footer, and final-page CTA elements.
  • If using generated images, store final assets under the brochure's `assets/` directory.
  • Record the image provider/tool and fallback reason when the preferred generator was unavailable.
  • If the same brochure appears in the website repo, keep the chiefOS generator and website generator aligned or document the relationship in `README.md`.

5. Audit Before Saying It Is Ready

Run the quality gates in `references/design-qa.md`:

  • Render every PDF page to images.
  • Inspect every page visually.
  • Run text extraction and phrase scans.
  • Inspect the PDF link annotations after regeneration and confirm visible CTA/click targets resolve to the intended URLs. For Conversint marketing PDFs, `conversint.ai` and contact CTAs normally resolve to `https://conversint.ai/contact`.
  • Check page count, metadata, and download path.
  • Check the website build when the website is touched.
  • Check Drive by downloading the updated file when Drive is touched.

Do not claim the PDF is ready until the rendered artifact has been inspected, not only generated.

6. Publish And Preserve Links

Use `references/publishing-checklist.md`.

When updating a known Google Drive PDF, update the existing file in place rather than creating a duplicate. When updating a website resource, preserve the public URL unless the user asks for a new link.

If the brochure has no Drive file yet, upload it once, record the returned ID and URL in its `README.md`, and use that ID for every later update.

Generated PDF files are gitignored in chiefOS. Do not commit regenerated PDFs to chiefOS. The standard flow is:

  1. Pull or inspect the existing Drive PDF when you need the latest published artifact.
  2. Pull or inspect Git for the latest generator/source.
  3. Rebuild the local PDF from the generator.
  4. Update the existing Drive PDF in place.
  5. Commit and push the generator/source changes only.

7. Capture Learning

Every brochure should have a learning purpose:

  • What buyer hypothesis is it testing?
  • What source or channel will distribute it?
  • What response will count as signal?
  • What tracking is needed?
  • What result would cause continue, stop, or change?

For live campaigns or client work, route this to `/marketing-learning-loop`. For ROI claims or proof packs, route to `/marketing-roi`.

Final Response

Report:

  • What changed.
  • Where the source and generated files live.
  • Whether Drive was updated and whether the link changed.
  • Whether the website resource was updated.
  • Verification performed.
  • Commits pushed.
  • Any remaining unrelated working-tree changes left untouched.