# TeamTalk: email signature, 90-second demo script, one-pager copy

Three ready-to-use pieces. Everything here is traceable to `pages/product.html`, `pages/pricing.html`, `pages/sales-kit.html`, `docs/gtm/research-commercial.md` and `docs/gtm/research-competitors.md`. Nothing is invented.

**TeamTalk has no customers yet.** There are no testimonials, logos, results or awards in this file, and you must not add any until you have a real one in writing. Where a quote would normally sit, there is a marked placeholder.

Brand: teal `#00C3D0` for the single accent. Charcoal `#0f0f0f` for text. Grey `#8a8a8a` for compliance furniture.

---

## Part 1: Email signature block

### 1.1 Why the compliance furniture is there

You are sending cold email to UK companies. Every outbound message needs your company legal name, registered number, registered office, a link to your privacy notice (UK GDPR Article 14, because the recipient did not give you their data) and an opt-out line. PECR fines run up to £8.7m or 2% of turnover. Source: `pages/sales-kit.html`, "Outreach that gets replies", legal note.

Email companies only (Ltd, PLC, LLP). Sole traders and ordinary partnerships need consent first.

### 1.2 Rules for this signature

1. **No images that will be blocked.** Most corporate mail clients block remote images by default, so the signature must read perfectly with every image off. The logo is optional decoration, never the only place your name appears. If in doubt, ship the text-only version.
2. **No quotes.** No inspirational line, no mission statement, no "sent from my phone".
3. **Under 8 visible lines.** Count them. Name, title, company, contact, link. That is it.
4. **One link.** `team-comms.com` and nothing else in the visible block. The privacy notice link in the grey compliance line is a legal requirement, not a marketing link, so it does not count against this rule. Do not add LinkedIn, a calendar link, a Twitter handle or a booking widget.
5. **No confidentiality boilerplate.** It has no legal effect on a cold email and it doubles the length.
6. **Keep the compliance furniture small and grey.** 10px, `#8a8a8a`. It needs to be present and readable, not prominent.
7. **One accent colour only**, the teal rule above the compliance line. Text is charcoal.
8. **Plain-text version is the default for cold outreach.** Sales-kit rule: plain text, one idea, no attachments on the first touch.

### 1.3 Plain-text version (use this for cold outreach)

```
Jake Hughes | [TITLE]
TeamTalk
[PHONE] | [EMAIL]
team-comms.com

[COMPANY LEGAL NAME], registered in England and Wales no. [COMPANY NUMBER].
Registered office: [REGISTERED OFFICE].
How we handle your data: team-comms.com/privacy
Reply STOP or "no thanks" and I will not contact you again.
```

### 1.4 HTML version

Tables only, no flexbox, no web fonts, inline styles, safe in Outlook 2016 and later. The only remote asset is the logo, and the block reads correctly with it blocked.

```html
<table cellpadding="0" cellspacing="0" border="0" style="border-collapse:collapse;font-family:Arial,Helvetica,sans-serif;font-size:14px;line-height:20px;color:#0f0f0f;">
  <tr>
    <td style="padding:0 14px 0 0;vertical-align:top;">
      <img src="[LOGO URL]" width="44" height="44" alt="TeamTalk" style="display:block;border:0;outline:none;text-decoration:none;width:44px;height:44px;" />
    </td>
    <td style="vertical-align:top;">
      <table cellpadding="0" cellspacing="0" border="0" style="border-collapse:collapse;">
        <tr>
          <td style="font-family:Arial,Helvetica,sans-serif;font-size:14px;line-height:20px;color:#0f0f0f;font-weight:bold;">
            Jake Hughes
          </td>
        </tr>
        <tr>
          <td style="font-family:Arial,Helvetica,sans-serif;font-size:13px;line-height:19px;color:#0f0f0f;">
            [TITLE], TeamTalk
          </td>
        </tr>
        <tr>
          <td style="font-family:Arial,Helvetica,sans-serif;font-size:13px;line-height:19px;color:#0f0f0f;">
            <a href="tel:[PHONE]" style="color:#0f0f0f;text-decoration:none;">[PHONE]</a>
            &nbsp;&middot;&nbsp;
            <a href="mailto:[EMAIL]" style="color:#0f0f0f;text-decoration:none;">[EMAIL]</a>
          </td>
        </tr>
        <tr>
          <td style="font-family:Arial,Helvetica,sans-serif;font-size:13px;line-height:19px;">
            <a href="https://team-comms.com" style="color:#00C3D0;text-decoration:none;font-weight:bold;">team-comms.com</a>
          </td>
        </tr>
        <tr>
          <td style="padding:9px 0 0 0;">
            <table cellpadding="0" cellspacing="0" border="0" width="260" style="border-collapse:collapse;width:260px;">
              <tr><td height="2" bgcolor="#00C3D0" style="height:2px;line-height:2px;font-size:2px;">&nbsp;</td></tr>
            </table>
          </td>
        </tr>
        <tr>
          <td style="padding:7px 0 0 0;font-family:Arial,Helvetica,sans-serif;font-size:10px;line-height:14px;color:#8a8a8a;">
            [COMPANY LEGAL NAME], registered in England and Wales no. [COMPANY NUMBER]. Registered office: [REGISTERED OFFICE].<br />
            <a href="https://team-comms.com/privacy" style="color:#8a8a8a;text-decoration:underline;">How we handle your data</a>. Reply STOP and I will not contact you again.
          </td>
        </tr>
      </table>
    </td>
  </tr>
</table>
```

Notes for whoever installs it:

- `alt="TeamTalk"` matters. With images blocked, Outlook shows the alt text, so the brand name still appears.
- Fixed `width` and `height` attributes on the `img` tag as well as in the style, because Outlook ignores CSS sizing on images.
- The teal rule is a one-cell table with a `bgcolor`, not a `border-top` and not an `hr`. Outlook renders those inconsistently.
- No `<div>` layout, no flexbox, no `<style>` block. Outlook strips or mangles all three.
- If your mail client mangles it anyway, ship the plain-text version. It is not worth an hour.

### 1.5 Reply signature (every message after the first)

Two lines. Use this once a thread is running, because the full block on message four looks like automation.

```
Jake Hughes | TeamTalk | [PHONE]
team-comms.com
```

HTML version of the same:

```html
<table cellpadding="0" cellspacing="0" border="0" style="border-collapse:collapse;font-family:Arial,Helvetica,sans-serif;font-size:13px;line-height:19px;color:#0f0f0f;">
  <tr><td>Jake Hughes &nbsp;&middot;&nbsp; TeamTalk &nbsp;&middot;&nbsp; <a href="tel:[PHONE]" style="color:#0f0f0f;text-decoration:none;">[PHONE]</a></td></tr>
  <tr><td><a href="https://team-comms.com" style="color:#00C3D0;text-decoration:none;">team-comms.com</a></td></tr>
</table>
```

The full signature, with the company details and the opt-out, must appear on the **first** message in every new thread. After that the reply signature is fine.

---

## Part 2: The 90-second demo video script, screen by screen

This is the 30-minute demo compressed. Same order, same story: get on, publish, land, confirm, prove, report back.

**Spoken word count: 221 words.** At a steady, unhurried pace that is about 90 seconds of narration. The end card holds silent for a few seconds after the last line, so the finished file runs to roughly 1:36.

### 2.1 The script

| Time | On screen | What you say | Note to the person recording |
|---|---|---|---|
| 0:00 | The printed join card on a wall or a welfare-unit door, QR code visible. A hand brings a real phone up and the camera recognises the code. | "This is the join card. It goes on the wall by the welfare unit. A worker scans the QR code with their own phone camera. Nothing to download, no app store." | Real phone, real card, real hand. Shoot it in one take. Show the camera recognising the code, not a cut to a loaded page. Landscape, phone held steady, daylight. |
| 0:12 | Phone screen: the number field, thumb typing, the SMS code arriving as a banner, the feed loading. Then the browser share sheet and "Add to Home Screen", ending on the TeamTalk icon on the home screen. | "He types his phone number. A code arrives by text. He's in. Then he adds it to his home screen, and it behaves like any other app, including notifications." | Use a real number that will actually receive the code. Do not speed-ramp the SMS wait; if it takes four seconds, cut on the code arriving. The home-screen icon shot is the one that kills the "another app to install" objection, so hold it for a full second. |
| 0:25 | Desktop: the manager's compose screen. The notice being typed, the must-read toggle switched on, the Publish button clicked. | "Meanwhile the site manager writes a must-read notice. The traffic-management route has changed: the north gate is closed from Monday. He ticks must-read and publishes." | Type the notice live, do not paste it. Never show a real company name, real site name or a real person's face on screen. Frame tight on the compose box so no menus or navigation are in shot. |
| 0:38 | Cut to the phone, locked. The push notification appears on the lock screen. Unlock, the notice is on screen in Polish. | "It lands on the phone straight away. On the lock screen, and in Polish, because that is the language this worker chose when he signed up. Nobody translated it by hand." | The lock-screen push is the money shot. Get it in one continuous take from the publish click if you can, two cameras if not. Do not fake the notification. |
| 0:50 | Thumb scrolling the notice to the bottom. The Confirm button appears. The tap. The state changes to confirmed with a timestamp. | "He reads to the end. The Confirm button only appears once the whole notice has been on screen. He taps it. That's the record." | Scroll at a readable speed. Let the viewer see that the button was not there at the top and is there at the bottom. That single detail is the product. |
| 1:00 | Desktop: the reach report. Confirmed and not-confirmed counts, then the toggle to the chase list, and the list shortening. | "Back in the office: who has confirmed, who hasn't. Switch to the chase list and everyone who has confirmed disappears. What's left is your morning's phone calls." | Have at least eight test workers with a realistic mix, so the list visibly shortens. All names must be obviously fictional. No cursor wandering: know exactly where the toggle is. |
| 1:12 | The printable per-person record, then the print preview or the PDF, then a glimpse of the CSV export. | "And per person: what they were sent, the language they read it in, and the time they confirmed. Print it or export the lot to CSV." | Show the paper-shaped page. Buyers who have ever handed a folder to an inspector recognise it instantly. One second on the CSV is enough. |
| 1:22 | Phone: the report screen. Photo taken, one sentence typed, location picked, Send. Cut to the desktop: the report arriving in English. | "It goes the other way too. A photo, a sentence, where it is. Sent, and it arrives in English." | Photograph something plausible and anonymous: a trailing cable, a blocked fire exit, a spill. Nothing identifiable, nobody's face. |
| 1:30 | End card: the line, the wordmark, the phone number and team-comms.com on a plain background. | "Every notice, every language, with a record. TeamTalk. team-comms.com." | Hold the card silent for four seconds after the last word so the number can be read and screenshotted. Phone number large. |

### 2.2 Shot list

Eleven shots. Nothing else.

1. Join card on a wall, wide enough to read the QR code.
2. Phone raised to the card, camera recognising the code (real phone, real hand).
3. Phone screen: number field, thumb typing.
4. Phone screen: SMS code banner, then the feed.
5. Phone screen: Add to Home Screen, ending on the icon.
6. Desktop: compose box, must-read toggle, Publish.
7. Phone, locked: push notification on the lock screen.
8. Phone: the notice in Polish, scrolled to the end, Confirm tapped.
9. Desktop: reach report, then the chase list.
10. Desktop: per-person record, print preview, one second of CSV.
11. Phone: hazard report sent, then the desktop showing it in English. End card.

### 2.3 Captions must be burned in

Most of this will be watched with the sound off, on a phone, in a car park or between meetings. Two consequences:

- **Burn the captions into the video file.** Do not rely on a platform's auto-captions or on an uploaded SRT. On LinkedIn, in an email preview and in a WhatsApp forward, only burned-in text is guaranteed to appear.
- **Write the captions to be readable standing alone.** They are the script, tidied, not a transcript with every "and" in it.
- Bottom third, large, high contrast, off-white on a dark plate. Never over the part of the phone screen the viewer needs to read.
- The video must make sense muted from start to finish. Watch it once on silent before you send it to anybody.

### 2.4 Set up the demo tenant before you record

From `pages/sales-kit.html`, "The 30-minute demo", set up before the call. The same setup applies here, with the customer-specific parts made generic because this video goes to everyone.

- A tenant with its own colours, logo and app icon. For the video use TeamTalk's own branding, not a prospect's.
- At least two test workers with Polish and Romanian set as their language, plus enough others (eight or more) that the reach report and chase list look like a real site.
- Every test name obviously fictional. No real people, no real companies, no real site names, no real addresses.
- One must-read notice drafted and ready to publish, in the manager's own words, typed live on camera.
- One hazard report already in the system with a photo, so you can show the translated arrival without waiting.
- A printed join card with a QR code that actually resolves.
- A real phone with a real number that will receive the SMS code, and push notifications switched on and already granted, added to the home screen.
- Charge the phone, turn on Do Not Disturb for everything except TeamTalk, and clear the home screen of anything personal.

### 2.5 Do not do this

- **No full feature tour.** Nine shots, one story. Groups, direct messages, drafts, scheduling and video captions are all real and all stay out. Every extra feature is a reason to think it is complicated.
- **No menus.** Not one navigation bar, sidebar or hamburger in shot if you can crop it out.
- **No settings screens.** Nobody buys because of a settings screen.
- **No cursor hunting.** Rehearse until you can hit every control without looking for it. A wandering cursor reads as "this is fiddly".
- **No simulator, no mockup, no screen-recorded phone frame.** A real phone in a real hand, filmed. The whole proposition is that this works on the phone the worker already owns, so the video has to show that phone.
- **No stock footage of hard hats.** No music bed with a build.
- **No named customer, no logo, no testimonial, no statistic on the end card.** You do not have one yet.
- **No claims the product cannot make.** No SSO, no HR integration, no offline posting, no app store listing.

---

## Part 3: One-pager copy, two flavours

One A4 PDF. Three screenshots: join card, translated post, reach report. Five bullets. Pricing. Phone number. That is all.

The generic title is **"Every notice, every language, with a record."** Each flavour below replaces it with its own headline. Everything is labelled so it can be dropped straight into a layout.

---

### (a) Caterer flavour

For contract catering and hospitality. Buyer: operations director or head of food safety. Trigger: allergen changes, supplier recalls, hygiene notices, shift changes, policy updates, kitchens spread across client sites.

**HEADLINE** (52 characters)
Every allergen change, every kitchen, with a record.

**SUBHEAD** (106 characters)
Notices reach every team member in their own language, on their own phone, with a record of who confirmed.

**OPENING PARAGRAPH** (45 words)
Your kitchens sit on other people's sites. When an allergen changes or a supplier recalls a batch, you need it read in every kitchen that day, by people whose first language may not be English. TeamTalk sends it, translates it, and shows you who confirmed.

**FIVE BULLETS**
1. Post once and every team member reads it in their own language. Translation happens automatically on publish, including video captions.
2. Mark a notice must-read and the Confirm tap only appears once the whole notice has been on screen.
3. See who has confirmed and who has not. The chase list hides everyone who has, leaving your phone calls.
4. Print a per-person record or export to CSV, with the language read and the time confirmed.
5. New starters join by scanning a QR code on a join card. Phone number and a text code, no email.

**SCREENSHOT CAPTIONS**
1. Join card: "The join card. Scan, enter a phone number, you are in."
2. Translated post: "The allergen notice, on the phone, in the reader's own language."
3. Reach report: "The reach report: who confirmed, who has not, ready to chase."

**WHAT IT IS NOT**
It is not a rota, a training record or a food safety management system, and machine translation is good for notices but not for legal wording without a human check.

**PRICING BLOCK**
Company plan: unlimited kitchens, priced in bands by enrolled workers. £550 a month up to 250 workers, £950 for 251-500, £1,600 for 501-1,000, £2,600 for 1,001-2,000. Eight kitchens and around 300 people is £950 a month, £11,400 for the year. Everything is included on every band: translation into any language, video with captions, confirmed reach, chase lists, exports, hazard reporting, join cards, unlimited managers. The only metered item is SMS delivery of posts at 8p a message, and push is the default, so most customers never pay it. All prices ex VAT, 12-month term, implementation £0. We re-band at renewal only, never mid-term.

Start with the 60-day pilot: £2,500 + VAT, fixed. Up to 3 sites and 250 enrolled workers, 100% credited against year one, and refunded if the first two success criteria are missed.

**PROOF AND COMPLIANCE LINE**
Regulation 10 of the Management of Health and Safety at Work Regulations 1999 requires information to be comprehensible, which is hard to argue for an English-only notice read by a Romanian kitchen porter, and TeamTalk leaves you a dated, per-person record showing the allergen change or recall was read, in the language it was read in.

**[CUSTOMER QUOTE PLACEHOLDER]**
> Leave this block empty in the layout, sized for roughly 25 words plus an attribution line reading "Name, job title, company".
>
> **Do not write a quote here.** TeamTalk has no customers yet. Fabricating a quote, even a plausible one, is the fastest way to lose a food safety buyer permanently and it is a misrepresentation.
>
> Fill it when, and only when, a real pilot customer has given you a sentence in writing and has agreed in writing that you may print it with their name and company. The sales kit tells you when to ask: at signature, alongside the request for two introductions. The pricing rules allow up to 20% off in year one for a named, quotable reference, in writing, expiring at renewal.
>
> Until then, leave the space blank or let the layout close up. Do not fill it with a stock photo, a made-up statistic, an award badge or a "trusted by" logo strip.

**CALL TO ACTION AND CONTACT**
See a recall notice land in a kitchen, in the reader's own language, and be confirmed. 25 minutes on a real phone, and I will tell you honestly if it is not useful.
Jake Hughes, [PHONE], [EMAIL], team-comms.com

**WORDS TO AVOID WITH THIS BUYER**
Avoid: toolbox talk, operative, gang, site induction, CDM, employee engagement, intranet, social feed, culture, wellbeing, employee experience, platform.

**SOURCES FOR THIS FLAVOUR** (for your own checking, not for the printed page)
Product claims: `pages/product.html`. Prices and pilot: `pages/pricing.html`. Buyer, trigger and one-pager spec: `pages/product.html` "Who it is for" and `pages/sales-kit.html` "The one-pager". MHSWR 1999 reg 10 and the "comprehensible" wording: `research-commercial.md` section 3.3, citing [legislation.gov.uk/uksi/1999/3242/regulation/10/made](https://www.legislation.gov.uk/uksi/1999/3242/regulation/10/made).

---

### (b) Housebuilder flavour

For housebuilders and main contractors. Buyer: head of HSEQ or the regional construction director. Trigger: toolbox talk records, site rule changes, CDM briefings, subcontracted multilingual crews.

**HEADLINE** (50 characters)
Every toolbox talk, every language, with a record.

**SUBHEAD** (114 characters)
Site notices reach every operative in their own language, subcontractors included, with a record of who confirmed.

**OPENING PARAGRAPH** (40 words)
A toolbox talk in English, signed on a sheet, is thin evidence when much of the gang reads Polish or Romanian. TeamTalk puts the notice on every operative's phone in their own language and records who confirmed it, subcontractors included.

**FIVE BULLETS**
1. Every operative reads the notice in their own language. Posts translate automatically on publish, including video captions.
2. Must-read notices need a confirmation tap, offered only after the whole notice has been on screen.
3. The reach report shows who confirmed and who has not. The chase list hides everyone who has.
4. A printable per-person record shows the notice, the language read and the confirmation time. CSV export too.
5. Subcontractors join in one break by scanning the QR join card. Leavers are locked out on their leaving date.

**SCREENSHOT CAPTIONS**
1. Join card: "The join card. Scan it, enter a number, you are on."
2. Translated post: "The site notice on a phone, in Polish, sent in English."
3. Reach report: "The reach report: confirmed, not confirmed, and the chase list."

**WHAT IT IS NOT**
It is not a rota, an induction or competence system, a RAMS tool or document control, and machine translation is good for notices but not for legal wording without a human check.

**PRICING BLOCK**
£180 per site per month on an annual plan. That is everyone on the site, up to 100 enrolled workers, however many languages, with the records: £2,160 a site for the year. Above 100 enrolled workers on a site, £1.60 per worker per month. Monthly billing is 15% more. Everything is included: translation into any language, video with captions, confirmed reach, chase lists, exports, hazard reporting, join cards, unlimited managers. The only metered item is SMS delivery of posts at 8p a message, and push is the default, so most customers never pay it. All prices ex VAT, 12-month term, implementation £0. For a whole region, the Company plan is unlimited sites from £550 a month, banded by enrolled workers up to £2,600 for 1,001-2,000.

Start with the 60-day pilot: £2,500 + VAT, fixed. Up to 3 sites and 250 enrolled workers, 100% credited against year one, and refunded if the first two success criteria are missed.

**PROOF AND COMPLIANCE LINE**
Regulation 15(8) of CDM 2015 puts the duty to give workers appropriate instructions and information on every contractor on site, not only the principal contractor, and section 40 of the Health and Safety at Work etc. Act 1974 reverses the burden of proof, so it is your job to show you did enough, which is exactly what a per-person, timestamped, language-stamped confirmation record is.

**[CUSTOMER QUOTE PLACEHOLDER]**
> Leave this block empty in the layout, sized for roughly 25 words plus an attribution line reading "Name, job title, company".
>
> **Do not write a quote here.** TeamTalk has no customers yet. An HSEQ director will check, and a fabricated quote ends the relationship and creates a real legal problem.
>
> Fill it when, and only when, a real pilot customer has given you a sentence in writing and has agreed in writing that you may print it with their name and company. Ask at signature, alongside the request for two introductions. The pricing rules allow up to 20% off in year one for a named, quotable reference, in writing, expiring at renewal. The best quote to ask for is about the chase list or the export, not about how nice the app looks.
>
> Until then, leave the space blank or let the layout close up. Do not fill it with a stock photo, a made-up statistic, an award badge or a "trusted by" logo strip.

**CALL TO ACTION AND CONTACT**
See a site notice land on a phone in Polish and be confirmed, with the record printed. 25 minutes on a real phone, and I will tell you honestly if it is not useful.
Jake Hughes, [PHONE], [EMAIL], team-comms.com

**WORDS TO AVOID WITH THIS BUYER**
Avoid: kitchen, colleague, staff, employee engagement, intranet, social feed, culture, wellbeing, comms platform, employee experience, digital transformation.

**SOURCES FOR THIS FLAVOUR** (for your own checking, not for the printed page)
Product claims: `pages/product.html`. Prices and pilot: `pages/pricing.html`. Buyer, trigger and one-pager spec: `pages/product.html` "Who it is for" and `pages/sales-kit.html` "The one-pager". CDM 2015 reg 15(8), HSWA 1974 s.40 and the reversed burden: `research-commercial.md` section 3.3, citing [legislation.gov.uk/uksi/2015/51/regulation/15/made](https://www.legislation.gov.uk/uksi/2015/51/regulation/15/made) and [legislation.gov.uk/ukpga/1974/37/section/40](https://www.legislation.gov.uk/ukpga/1974/37/section/40). The opening paragraph deliberately carries no figure, because the sector average should not be asserted of one customer's gang. If you want a figure on the page, the citable one is the University of Reading / RICS 2026 finding of non-English-speaking operatives averaging 34% of the workforce and reaching 75% (`research-competitors.md` section 2.16); quote it as a sector figure with the publisher and year beside it, never as a claim about the reader's own site.

---

## What you must fill in before using this

**Email signature (Part 1)**
- `Jake Hughes` in the full signature, the reply signature and both one-pager contact lines.
- `[TITLE]`, for example Founder, or Managing Director.
- `[PHONE]`, in full including the country code in the `tel:` link, for example `tel:+447700900123`.
- `[EMAIL]`, in the visible text and in the `mailto:` link.
- `[LOGO URL]`, an absolute HTTPS URL to a square PNG at 88x88 pixels for retina, displayed at 44x44. Host it somewhere permanent. If you have no logo file yet, delete the whole first `<td>` containing the image and the signature still works.
- `[COMPANY LEGAL NAME]`, exactly as registered at Companies House.
- `[COMPANY NUMBER]`, the Companies House registration number.
- `[REGISTERED OFFICE]`, the full registered address including postcode.
- The privacy notice must actually exist and be live at `team-comms.com/privacy` before you send a single cold email. Both signature versions link to it.
- Decide and write down what happens when somebody replies STOP, and keep the suppression list. The opt-out line is a promise, not decoration.
- Confirm you are emailing companies only (Ltd, PLC, LLP).

**Demo video (Part 2)**
- The demo tenant, set up per section 2.4, with fictional names throughout.
- A real phone with a working number, push granted, TeamTalk added to the home screen.
- A printed join card whose QR code actually resolves.
- The exact wording of the must-read notice you will type on camera. Keep it generic. No real company, site, person or address.
- An anonymous photo for the hazard report.
- The end card: wordmark, `[PHONE]`, team-comms.com.
- Burned-in captions, written from the script and checked muted.

**One-pager (Part 3)**
- Which flavour you are sending. Never send both to the same person.
- The three screenshots, taken from the demo tenant with fictional names, matching the captions.
- `Jake Hughes`, `[PHONE]`, `[EMAIL]` on the contact line.
- `[CUSTOMER QUOTE PLACEHOLDER]`: leave empty until you have a real, written, name-approved quote from a real customer. There is nothing to fill in today.
- Check the prices against `pages/pricing.html` on the day you print. If the price list has moved, this file has not.
- Confirm the "what it is not" line still matches the product: no SSO, no SCIM, no HR integrations, no app store listing, no offline posting, machine translation only.

**One more thing to watch**
The cold email templates in `pages/sales-kit.html` contain the placeholder `[reference]`, as in "Live with [reference] in the South East". You have no reference. Delete that sentence from the templates. Do not fill it in.