Capability 02 · One source, every channel
Content and messaging infrastructure your campaigns run on.
We build your content model, CMS, asset library and localisation workflow, and set up email, SMS and WhatsApp so messages arrive. Change a price, claim or logo once and every channel updates.
Route: email, WhatsApp and push sent; SMS suppressed for lack of consent; the in-app banner queued for the next session.
Illustrative. Consent is checked per purpose and channel at the moment of sending.
What we build · 6 parts
Structured content, reused everywhere.
Content is stored as fields, so your website, emails, ads and AI assistants all draw on the same source.
-
Content model & headless CMS
Content types, structured fields and reusable blocks in a headless CMS, with versioning and preview.
Structured · reusable -
Digital asset management
One library for photography, video, logos and templates, with usage rights, licence expiry and market restrictions recorded on each asset.
Rights · metadata -
Localisation & translation pipeline
Machine translation with in-market human review, locale variants, right-to-left support and regional legal lines, built into publishing.
Locales · review -
Messaging infrastructure
Email, SMS and WhatsApp senders set up correctly: email authentication, IP warm-up, approved WhatsApp templates and the 24-hour service window respected.
Authentication · warm-up -
Channel component library
Email, landing page and message components on your brand tokens, tested for accessibility, dark mode and the email apps your audience uses.
Tokens · tested -
Editorial workflow & governance
Roles, review stages, legal and compliance sign-off, scheduled publishing and an audit trail of every change, in tools your team already uses.
Approvals · audit trail
How it works
From content model to delivered message.
Each message is assembled once, checked for consent on every channel and logged. The highlighted step is where this capability works.
- 01 · Source Content model Structured types and approved blocks, kept in a headless CMS.
- 02 · Assemble One message Rendered for each channel and language from the same source.
- 03 · Check Consent per channel Sent only on channels the person agreed to, for that purpose.
- 04 · Route Channel adapters Email, SMS, WhatsApp templates, push and in-app through one sending layer. Infrastructure
- 05 · Record Delivery log Sent, held, suppressed and failed messages recorded with the reason.
How it runs · 4 stages
Content model first, migration second.
We test the content model on your hardest pages and campaigns before any content moves into it. Timings shown are typical.
Stage 01 of 4Wk 01–04
Model
We audit your content and channels, then design the model: types, fields, relationships and reuse rules.
Produces
- Content audit
- Content model
- Governance plan
Stage 02 of 4Wk 04–10
Build
We configure the CMS and asset library, build components on your brand tokens, set workflows and permissions, then authenticate and warm up senders.
Produces
- CMS build
- Component library
- Sender set-up
Stage 03 of 4Wk 09–14
Migrate
We move content and assets with their mapping and rights data, add redirects and fix gaps on the way. Editors train on your own content.
Produces
- Migration
- Redirect map
- Editor training
Stage 04 of 4Wk 14–16
Operate
We hand over documentation with an owner for each content type, then review the model quarterly as channels are added.
Produces
- Documentation
- Ownership map
- Review cadence
Template coverage · what you will see
Template status for every message type and channel.
The registry shows your team which message types exist on each channel, in which languages and which still need approval.
| Message type | SMS | Push | In-app | ||
|---|---|---|---|---|---|
| Order confirmed | 4 of 4 (on track) | 4 of 4 (on track) | Approved (on track) | 4 of 4 (on track) | —not applicable |
| Delivery update | 4 of 4 (on track) | 4 of 4 (on track) | Pending review (needs attention) | 4 of 4 (on track) | 4 of 4 (on track) |
| Price drop alert | 3 of 4 (needs attention) | —not applicable | Rejected: wording (gap) | 4 of 4 (on track) | 4 of 4 (on track) |
| Account security | 4 of 4 (on track) | 4 of 4 (on track) | —not applicable | —not applicable | 4 of 4 (on track) |
What you get
Content models and adapters, documented for your team.
A content model, channel adapters and a delivery log in your accounts, with a runbook for adding channels.
| # | Deliverable | Format |
|---|---|---|
| 01 | Content model & type documentation | Schema · docs |
| 02 | Configured CMS & asset library | Platform build |
| 03 | Email, landing & message component library | Templates · tokens |
| 04 | Localisation workflow & glossary | Workflow · sheet |
| 05 | Sender authentication & deliverability set-up | DNS · report |
| 06 | Editorial workflow & permissions | Config · RACI |
| 07 | Migration mapping & redirect plan | Sheet |
What changes
Faster to publish, consistent everywhere.
Success means one source feeds every channel and language, and each send is recorded. These outcomes are aims, not guarantees.
-
01
One fact, one place
A price, claim or disclaimer changed once is correct in every channel that uses it.
-
02
Localisation stops being a project
New markets reuse the content model, glossary and review workflow already in place.
-
03
Messages that arrive
Authenticated senders, warmed-up IPs and clean lists help each campaign reach the inbox.
Hours from approved copy to live, per release. Shape only. Solid line: releases from shared content and channel adapters. Dashed line: the same work copied into each channel by hand.
Technologies we work with
Headless CMS to channel APIs, chosen for your team.
The content, search, messaging and hosting tools we build this infrastructure on. Listed as tools we work with; no partnership is implied.
- Contentful
- Sanity
- Strapi
- WordPress
- Webflow
- Figma
- Algolia
- Cloudflare
- Vercel
- n8n
- Twilio
Frameworks we build to
Accessibility, speed and consent built into every channel.
Every template and page is built to these frameworks. None of them is a certification we hold.
-
WCAG 2.2 AA — Web Content Accessibility Guidelines
Web Content Accessibility Guidelines
Emails, landing pages and in-app messages checked for contrast, alt text, reading order and keyboard use before approval.
-
Core Web Vitals — Loading, interactivity and visual stability
Loading, interactivity and visual stability
Landing pages held to LCP ≤ 2.5 s, INP ≤ 200 ms and CLS ≤ 0.1 at the 75th percentile of visits, with tracking tags audited for speed.
-
GDPR — General Data Protection Regulation (EU) 2016/679
General Data Protection Regulation (EU) 2016/679
Consent recorded per purpose and channel, tags held until consent (Consent Mode v2 for Google) and erasure requests sent to every connected tool.
-
DPDP Act 2023 — Digital Personal Data Protection Act, 2023
Digital Personal Data Protection Act, 2023
Notices and consent records for India-based customers, with withdrawal honoured in every journey and channel within the same working day.
-
ISO/IEC 27701 — Privacy information management systems
Privacy information management systems
A register of every marketing tool holding personal data, with its purpose, retention and processor terms, updated as tools are added.
Services & packages
Content and messaging services, from content model to inbox.
We set up the content, assets, localisation and messaging behind multi-channel marketing. Each service lists what is included, who it suits and a typical timeline.
- Categories
- 05
- Services
- 16
- Packages
- 04
How to buy
- 01Pick services. Enquire about one, or add several to a brief.
- 02Choose a package. A sprint, a fixed project or an ongoing team.
- 03Send the brief. We reply within one working day.
How we work with you
Ways to engage, from a question to an RFQ.
Ask a quick question, send a project brief or issue a formal RFQ. The lead for the work reads each one in full, and any services already in your brief go with it.
Or book a thirty-minute call-
01
For a first conversation, a press request or anything that does not need a scope yet.
You get A reply from a named lead
-
02Recommended
Goals, audiences, a budget band and timing, so our first reply can outline the work.
You get Options and a first scope after one call
-
03
Your documents, deadlines and the procurement and security rules the work must meet.
You get Receipt confirmed and a named bid lead
How it is priced
Each package shows its pricing model. Work starts once a written scope and quote are agreed.
Opens a project brief with this package chosen.
-
In your brief
- Typical length
- 4–12 weeks
- Pricing
- Fixed price
-
In your brief
- Typical length
- 3–9 months
- Pricing
- Fixed price per milestone
-
In your brief
- Typical length
- Ongoing · 6-month minimum
- Pricing
- Monthly fee
-
In your brief
- Typical length
- 1–3 weeks
- Pricing
- Fixed fee
Compare what each package includes
| Package | Every engagement includes | Best for |
|---|---|---|
| ProjectA defined scope, delivered for a fixed price. |
|
Work you can describe up front: an identity, a platform or a set of tools |
| MilestoneA larger build in phases you approve and pay for one at a time. |
|
Programmes too large for one contract, where you want control at each step |
| RetainerReserved monthly capacity to run, improve and extend what we built. |
|
Live brands and products that need a steady team without hiring one |
| SprintA short, fixed-scope engagement that answers one defined question. |
|
Discovery, a diagnostic, a prototype or a decision you need to make soon |
Questions
What teams ask about content infrastructure.
Anything else, ask us directly. A short call is usually quicker than a long email.
01Is this the same as building a website?
No. Websites & Apps, in Technology & Intelligence, builds the site or app. This builds the content and messaging set-up beneath it, which your site, emails, ads and AI assistants draw on. The two can be delivered together.
02Which CMS do you recommend?
The one your editors will use and your developers can build on. We work with Contentful, Sanity, Strapi, WordPress and Webflow. We choose by content model, localisation, workflow and total cost.
03Why does a content model matter for marketing?
Because content stored as structured fields can be reused. It can be assembled automatically into emails, ads and landing pages, given to AI tools with the right context and corrected in one edit. That is what keeps personalisation affordable.
04Can AI write directly into the CMS?
Yes, as a draft. AI writes against your content model and approved facts, and its drafts go through the same review as any other content. A named person approves everything before it is published.
05What about content rights and licences?
Each asset carries its usage rights, territory, channel and expiry as metadata. Assets past their licence are blocked from new campaigns and flagged where they are already in use.
Works best with
Related capabilities that run on this infrastructure.
Creative AI fills the content model; Automation decides when each message goes.
Tell us what you need built.
You will speak to a lead who would run the work, and get a straight answer on fit.
Three ways to start
Every engagement starts with a written scope and a quote agreed before work begins.
Choose one of the three ways above