NELC × Marketing Cloud Next

What is actually built

Everything below is real and in the SDO org now — this page is a crib sheet, not the demo.

Emails

1 master template + 6 emails

Built as content blocks, not HTML. The September newsletter is 57 separate blocks — headings, paragraphs, buttons, dividers, sections, columns and the logo image — every one selectable and editable in the WYSIWYG. Zero raw-HTML blocks.

Master Template · Resident Newsletter · Bins & Recycling · Ward Alert · Grimsby 2028 Campaign · Business Bulletin · Emergency Alert

Brand

NELC logo as a CMS asset

The real logo is uploaded into the NELC Demo CMS workspace as a managed image asset and referenced by every email. Replace that one asset and all seven emails update — no re-editing, no external hotlinking.

Data

5 council fields on Contact

Ward, Comms Topic Interests (multi-select), Preferred Channel (incl. WhatsApp), Resident Portal Registered, Bin Collection Day — the things a council comms team actually filters and personalises on.

Audience

30 residents · 16-strong audience

30 dummy residents across all NELC wards (Grimsby, Cleethorpes, Immingham, Waltham, Wolds…), with a populated Campaign audience of the 16 who opted in to regeneration or culture updates, plus three saved list views.

Where to find it

Asset	Where
The seven emails + logo asset	NELC Demo CMS workspace
Audience (16 residents)	Campaign: NELC — Grimsby 2028 & Regeneration Interest
Residents & council fields	Contacts → list views NELC — All Demo Residents, NELC — Regeneration & Culture Interest, NELC — Coastal Wards (Flood Alert)

Tone of voice

Copy is written from NELC's own news output, not generic council filler — the unitary-authority confirmation for 2028, the Service 3 and 4 bus timing changes, the Yarborough Road works, the homelessness strategy consultation, the Grimsby 2028 Town of Culture bid, the Lincs Inspire "Move Together" roundup and the procurement changes opening contracts to local SMEs. Plain, warm, practical, specific to the borough.

Suggested running order

About 15 minutes hands-on, then 10 on where it goes. Let them drive the editor if they will.

Open the September newsletter in the editor. Click a headline. Click a paragraph. Drag a story block above another. The point lands in ten seconds: this is their comms officer's job, not a developer ticket. — 3 min
Click the logo. Show it is a managed brand asset in the CMS, shared by every email. Swap it once, it changes everywhere. — 1 min
Show the master template. This is the base the other six came from — the pattern their team clones each month rather than starting from a blank page. — 2 min
Flick through the variety. Same template, six very different jobs: monthly newsletter, a service change (bins), a ward-targeted works alert, a campaign (Grimsby 2028), a business bulletin, and a red-banner emergency flood alert. One platform, the whole spread of council comms. — 3 min
Open a resident record. Ward, topic interests, preferred channel, bin day, portal registration — sitting on the Contact in their existing CRM, not in a separate broadcast tool. — 2 min
Show the audience. The 16-resident campaign audience and the coastal-wards list view. Then build a segment live — see the note below; doing it in front of them is a stronger moment than a pre-built one. — 4 min
Land the strategic point. Move to the positioning below. — 10 min

Read before you demo — two honest caveats.

Delete the earlier drafts first. The workspace also holds an earlier build of the same seven emails plus a spare logo asset — they reference an external logo URL that will not render in the editor. Multi-select and delete everything except the ten records below, then only the working set remains. About twenty seconds in the CMS UI.

Keep — record ID	Name
`20YKY000007OB3a2AG`	NELC Logo (the one every email points at)
`20YKY000007OB3k2AG`	NELC — 00 Master Template
`20YKY000007OB3p2AG`	NELC — 01 Resident Newsletter — September 2026
`20YKY000007OB3u2AG`	NELC — 02 Bins and Recycling — Collection Day Change
`20YKY000007OB3z2AG`	NELC — 03 Ward Alert — Yarborough Road Works
`20YKY000007OB442AG`	NELC — 04 Campaign — Grimsby 2028 Town of Culture
`20YKY000007OB492AG`	NELC — 05 Business Bulletin — Local Procurement
`20YKY000007OB4E2AW`	NELC — 06 Emergency Alert — Coastal Flood Warning

Quick check if in doubt: open an email and click the logo — on the keepers it resolves to the CMS asset, on the stale ones it is an HTML block with a broken image.

The Data Cloud segment is not pre-built. The 30 residents were created today and Data Cloud had not yet ingested them, so a pre-built segment would have shown zero members on screen. The populated Campaign audience is the safe thing to show. If you want the segment itself, build it live: Data Cloud → Segments → New, segment on Individual, filter on Campaign membership = NELC — Grimsby 2028 & Regeneration Interest. Check ingestion has run before you rely on a count.

The strategic conversation

The newsletter is the wedge, not the point. NELC already runs Salesforce as their core CRM — Marketing Cloud Next sits natively on that same Data Cloud and Customer 360 foundation. The resident profile, portal activity and case history are already there. When a resident opens or clicks one of these newsletters, that behaviour lands on their master profile, where the front-line service teams can see it too. That is the difference between a comms platform and a send tool.

Dimension	Gov.Notify / Gov.Delivery	MC Engagement	Marketing Cloud Next
Primary function	Basic transactional push notifications	Rules- and journey-based marketing	Data-driven, AI-native engagement
CRM & data	None — an isolated send tool	Requires connector syncs	Native to the Salesforce org they already run
Team autonomy	High manual effort, no flexibility	Heavy reliance on a partner to build and maintain	Designed for in-house configuration and self-service
AI & content intelligence	None	Limited / add-on	Native content scoring and automated segmentation
Channel growth	Web, email, SMS only	Extra integration required	Extends into WhatsApp and emergency alerts

The line to land

Gov.Notify solves today's basic send problem. MC Engagement solves campaign automation but creates long-term partner dependency. Marketing Cloud Next gives NELC an in-house foundation — it solves newsletters today, natively delivers the Content Quality Score they have asked for instead of stitching GA and SEMrush together, and opens the door to WhatsApp tomorrow. Run by their own ten-person team, with AI built in rather than bolted on.

Points worth having ready

Content Quality Score. They asked for it by name. Today it is Google Data Studio plus SEMrush, stitched by hand, with no unified view of content performance. Native scoring is a headline reason to prefer Next over both alternatives.
Scale sanity-check. 180k residents, 70k on the portal, 5–10k newsletters a year, 30+ social channels, a ten-person team. This is not a volume problem — it is a fragmentation problem. That framing suits Next and does not suit Gov.Notify.
The £2k/year intranet news app. Small money, but it is another point solution in a stack that already has too many. Worth naming as an example of the pattern.
The "safe government standard" objection. Meet it directly: Gov.Notify is genuinely safe for sending. It is send-only — no CRM tie-in, no unified resident profile, no native AI, no channel extensibility. It solves the narrow problem well and the wider one not at all.

Phasing

Phase 1

Migrate

Move the core council newsletters off the legacy tooling and Gov.Notify. Exactly what the build in this demo represents.

Phase 2

Enable

Team onboarding and skill transfer, plus native Content Quality Score setup. The point at which the partner steps back.

Phase 3

Extend

WhatsApp and service-triggered comms — SEND, Discover, Health & Care, crisis and outbreak comms — on the same platform, no re-platforming.

Commercials — indicative

Be straight about the shape of the numbers rather than vague. These are indicative list positions to frame the conversation, not a quote.

Option	Indicative list	What it gives NELC
MC Next — Growth	~$1,500 / org / month ≈ £14–15k a year	Multi-channel journeys, forms and landing pages, campaigns, core automation. SMS and WhatsApp are add-ons. Covers Phase 1 comfortably.
MC Next — Advanced	~$3,250 / org / month ≈ £31–33k a year	Everything in Growth plus AI scoring (the Content Quality Score ask), path experimentation and unified conversational messaging. The edition that matches what they have described wanting.
Gov.Notify / Gov.Delivery	Low / near-zero licence	Cheapest line item, and the true cost sits elsewhere: manual effort across a ten-person team, no resident profile, and a re-platform when WhatsApp becomes a requirement.

Marketing Cloud Next is priced per org, not per user — so the ten-person team is not a cost multiplier. Figures are US list converted roughly; confirm against the current UK price book before anything goes in writing.

The commercial framing

Reduced licence cost brings the implementation cost down toward zero for NELC. That is the offer, and it is deliberate — not a throwaway line.

It also answers the thing they have actually asked for: a partner who sets them up, transfers the skills and then steps back, rather than one they pay for every campaign forever. The value is in Phase 2 — getting their own team genuinely self-sufficient — not in an annuity on campaign builds. The demo backs this up: everything on screen was built to be edited by a comms officer, which is why it is content blocks and not HTML.

If they ask

"Can our team really edit these?" Open the editor and hand over the mouse. Every element is a block. That is the whole answer.
"What about WhatsApp?" Preferred Channel is already on the resident record in this demo, with WhatsApp as a value. The data model is ready before the channel is switched on.
"How do we target one ward?" Show the Coastal Wards list view against the emergency flood alert email. Ward is a field on the resident, so the audience is a filter, not a data project.
"Does engagement come back to us?" Yes — opens and clicks land on the resident profile in the same org as their case history. That is the native-CRM argument in one sentence.

Internal demo companion — SAMA Consulting. Contains no real resident data; all 30 contacts are dummy records on @example.com addresses. Built in an SDO/trial org.