guidesContent Creation

Guide: Content Creation

Drafts, decks, emails, and proposals — branded to your company, ready to send.

Set Up Your Brand Once

In Dashboard → Settings → Branding, upload:

  • Logo (SVG)
  • Primary brand color
  • Font preferences
  • Optional: a PDF letterhead template

Once registered, every doc Chief generates uses these.

Drafting an Email

Chief, draft a polite follow-up email to the Acme thread.
We had a call last Tuesday, sent the proposal Wednesday,
and haven't heard back. Tone: friendly but direct, under
80 words. Don't sign off — I'll do that.

Chief replies with the draft inline. Iterate:

Make it shorter and don't mention the proposal explicitly.

Generating a Branded PDF

Chief, write a one-page proposal for the Acme deal:

- Problem they're trying to solve: workflow visibility for ops
- Our solution: a custom dashboard built in App Factory
- Investment: $25k one-time, $2k/mo retainer
- Timeline: 3 weeks to MVP

Export as a branded PDF.

Chief drafts, formats with your brand, and uploads the PDF to the thread. Iterate by saying “Make the timeline section more detailed” and Chief rebuilds and re-uploads.

Decks

Chief, build me a 5-slide deck for the Acme kickoff:
1. Goals
2. Scope
3. Timeline
4. Team
5. Next steps

Use our brand. Output as Google Slides and DM me the link.

Chief creates a Google Slides deck (using your Drive integration), applies brand colors, and shares the link.

Long-Form Content

For docs longer than a couple pages — RFPs, technical specs, internal handbooks — drop in source material first:

[uploads notes-from-customer-calls.txt]
[uploads competitor-analysis.pdf]

Chief, using these inputs, write a 3-page positioning doc
explaining why we win on workflow customization. Output as
a branded DOCX so the team can edit.

Chief reads both inputs, synthesizes, and produces the doc.

Tone Memory

Chief learns your voice over time. The first few drafts will feel slightly off — correct them. “Drop the exclamation points,” “Use ‘we’ not ‘I,’” “Don’t open with a question.” Each correction is saved and applied to future drafts.

Pitfalls

  • No brand registered → Chief uses defaults. Set up branding in Settings before relying on consistent output.
  • Too vague → bland draft. The more constraints you give (length, tone, audience, what to include and exclude), the better the first draft.
  • Don’t paste sensitive data without checking. If your draft contains customer PII, decide whether you want it in Chief’s thread context (it’ll be retained per your retention settings).
Code ReviewCustom Integrations