Customer spotlight: [CUSTOMER NAME PLACEHOLDER]

Customer spotlight: [CUSTOMER NAME PLACEHOLDER]

A short feature on a Norma customer running a [PROGRAMME TYPE PLACEHOLDER, e.g. welcome kit, client gifting, event giveaway, uniform] programme. Published with the customer's permission; identifying details edited where the customer requested anonymisation.

This template post is the running format for the customer spotlight series. Real customer entries replace the placeholders as written permission lands.

At a glance

• Customer: [COMPANY NAME PLACEHOLDER]
• Sector: [SECTOR PLACEHOLDER, e.g. B2B SaaS, professional services, creative agency, hospitality]
• Size: [HEADCOUNT PLACEHOLDER]
• Programme shape: [WELCOME KITS / CLIENT GIFTS / EVENT DROPS / UNIFORM / MILESTONE]
• Recipients per quarter: [NUMBER PLACEHOLDER]
• Active since: [START DATE PLACEHOLDER]

The brief

[PLACEHOLDER PARAGRAPH 1: two to four sentences describing what the customer was trying to solve. The before state: how many suppliers, what was breaking, what the recipient experience was like.]

[PLACEHOLDER PARAGRAPH 2: two to four sentences describing the success criteria. The numbers the customer wanted to hit: cost per recipient, lead time, sustainability metrics, audit trail.]

How the programme works

The customer placed the first order with Norma in [MONTH YEAR PLACEHOLDER]. The kit was specified across [NUMBER PLACEHOLDER] items:

• [ITEM 1 PLACEHOLDER, e.g. Heavyweight cotton tee in brand sage, 180gsm GOTS certified.]
• [ITEM 2 PLACEHOLDER, e.g. Hardback A5 notebook with foil stamped logo.]
• [ITEM 3 PLACEHOLDER, e.g. Ceramic mug in matt black.]
• [ITEM 4 PLACEHOLDER, e.g. Letterpress welcome card, signed by the People Ops lead.]
• [ITEM 5 PLACEHOLDER, optional.]

The workspace is set up with [NUMBER PLACEHOLDER] members across [ROLES PLACEHOLDER, e.g. admin, approver, ordering member]. The approval rule routes orders over £[THRESHOLD PLACEHOLDER] to the approver, who sees the order in app and via Slack.

Net 30 invoicing is in place; the credit limit is £[LIMIT PLACEHOLDER]. The monthly invoice carries PO reference [PO FORMAT PLACEHOLDER] and lands within one working day of order completion.

[PLACEHOLDER PARAGRAPH: two to three sentences on how the orders trigger. New starter event from BambooHR? Manual upload from a CSV? A combination?]

What changed

[PLACEHOLDER PARAGRAPH 1: two to four sentences describing the operational change. How much ops time the People Ops or procurement lead now spends, against the prior state.]

[PLACEHOLDER PARAGRAPH 2: two to four sentences describing the recipient response. The on time arrival rate, the use rate at four weeks if measured, the sentiment in the pulse survey if run.]

In the customer's own words

[PLACEHOLDER PULL QUOTE 1: a direct quote from the customer, three to four sentences in their voice. The quote should describe the operational change and what it freed them up to do.]

[PLACEHOLDER SPEAKER ROLE], [PLACEHOLDER COMPANY NAME OR DESCRIPTOR]

[PLACEHOLDER PULL QUOTE 2: a direct quote from a recipient or a stakeholder outside the procurement function, two to three sentences. The quote should describe the recipient experience.]

[PLACEHOLDER SPEAKER ROLE]

The numbers

What is next

[PLACEHOLDER PARAGRAPH: two to three sentences on the customer's next move. Expanding the programme to a second cohort, adding a new SKU, rolling the workspace out to a regional office, etc.]

How to run a programme like this

Three takeaways for buyers considering a similar setup.

1. [TAKEAWAY 1 PLACEHOLDER, e.g. Lock the recipient list in one system before adding items to the kit. The list quality drives every downstream success metric.]
2. [TAKEAWAY 2 PLACEHOLDER, e.g. Size the kit at four items rather than six. The recipient noticed every item.]
3. [TAKEAWAY 3 PLACEHOLDER, e.g. Pick the apparel weight at the heavyweight threshold; it carries the brand signal further than any other item.]

For a working playbook on multi recipient dispatch, read the multi recipient swag drop playbook. For the broader catalogue of programme shapes Norma supports, see the customers page.

If you run a programme through Norma and would like to be featured in this series, write to hello@normamade.com. We share a draft for review before any spotlight publishes; identifying details are anonymised on request.

---

This is a template. Replace every [PLACEHOLDER] block with content sourced from a customer interview before publishing a real spotlight. Keep the brand voice constraints: no em dashes, no exclamations, no hype, specific numbers over abstract claims.

Editorial checklist for real spotlights

Before a customer spotlight publishes, the following lands:

• Written permission from the customer to publish the spotlight.
• Confirmation of whether the customer is named or anonymised.
• All numbers verified against the workspace data.
• Two direct quotes captured from the customer in writing.
• Draft shared with the customer for review at least five working days before publish.
• Hero image either sourced from the customer or commissioned with their agreement.
• Brand voice lint passes (no em dashes, no exclamations, no banned vocabulary).
• AI detector pass via Quillbot per HANDOFF section 22.3.
• Internal links to the relevant case study (if one exists) and the related blog playbook.
• Customer notified of publish date one working day before publish.