New Client Onboarding Checklist

Everything you need to spin up a new email builder from the template.

1

Gather Client Assets

Collect these from the client before starting:

2

Copy the Template

  1. Copy the entire _template folder.
  2. Rename the copy to your client name, e.g.:
    _template/CoastGuard/coastguard-builder/
  3. Your folder structure should look like:
    AI Email Builder/
    ├── OCC/                    ← existing
    ├── CoastGuard/             ← new client
    │   └── coastguard-builder/
    │       ├── CLIENT_CONFIG.js
    │       ├── index.html
    │       ├── help/
    │       ├── drop-google-doc-html-here/
    │       └── _do-not-edit/
    └── _template/              ← stays untouched
3

Fill in CLIENT_CONFIG.js

Open CLIENT_CONFIG.js and replace every CHANGE_ME value. Every field is documented with inline comments.

Claude Code Shortcut

Upload the client’s Google Doc HTML + brand assets to Claude and say:

“Here is a new client’s email copy document and their brand info: [colors, fonts, signers, merge field syntax]. Fill in CLIENT_CONFIG.js for me.”

Claude can detect signer names, greeting patterns, language, and segment structure directly from reading the email copy.

Key sections to fill in:

  1. IdentityorgName, orgNameFr, appTitle
  2. Brand ColorscolorPrimary, colorAccent, etc.
  3. TypographyfontFamily
  4. Merge FieldsfirstName, bodySlot, yearToken
  5. UTM Columns — match to the client’s spreadsheet headers
  6. Signatures — add each signer with detect pattern, name, title, image URLs
  7. Language Detection — French markers (or empty array for English-only)
  8. Button Style — CTA button appearance
4

Paste the Stationery Wrapper

  1. Open index.html in a text editor.
  2. Scroll to the very bottom — find the block:
    <!-- PASTE YOUR CLIENT'S STATIONERY WRAPPER HTML BELOW -->
    <script type="text/html" id="stationery-wrapper">
      ...placeholder HTML here...
    </script>
  3. Replace everything between <script type="text/html"> and </script> with the client’s full stationery wrapper HTML.
  4. Make sure the wrapper contains the body slot merge field (e.g., [[S63:3]]) matching what you set in CLIENT_CONFIG.mergeFields.bodySlot.
Also save a copy of the wrapper in _do-not-edit/email-assets/stationery_wrapper.html as a backup reference.
The wrapper must be embedded in the <script type="text/html"> tag (not loaded via fetch) so it works when opening index.html directly from the filesystem (file:// protocol).
5

Test the Builder

  1. Double-click index.html to open it in Chrome.
  2. Verify the header shows the correct client name.
  3. Verify the brand colors are applied (header bar, buttons, active states).
  4. Drop in the client’s Google Doc HTML and click Generate Emails.
  5. Check:
    • All emails are detected and listed in the sidebar
    • Segments are discovered correctly from color-coded keys
    • Subject lines and preview text are extracted
    • Signatures are detected (correct signer type shown in metadata card)
    • Links have UTM URLs (or {need UTM} placeholders if no spreadsheet)
    • Bold text preserved, underlined text converted to links
    • Merge fields replaced (e.g., [First Name] → platform merge code)
  6. Click Preview — verify the email renders inside the stationery wrapper with correct branding, footer, and social icons.
  7. Click Copy HTML and paste into the email platform to verify it looks correct end-to-end.
6

Optional: Customize Help Page

The help page (help/index.html) ships with generic language. Optionally update: