Personalisation beyond the first name

Content that changes because the person changed, across email, web and app, and tested on real results.

Let's talk

Relevance as the default, not the exception

Putting someone's name in a subject line is not personalisation. It is a mail merge with ambition.

  • Cross-channel consistency

    We make sure web, email, app and push tell one story instead of contradicting each other by a day.

    1. Web
    2. Email
    3. App
    4. Push
  • On-site personalisation

    We adapt content, banners and product blocks on your site based on behaviour, segment and lifecycle stage.

  • Dynamic content and recommendations

    We build blocks that assemble themselves per recipient, with recommendation logic that still looks right when the data is thin.

  • Personalisation governance

    We set rules for what gets personalised and for whom, including where the line sits between relevant and unsettling.

  • A/B testing and experimentation

    We test what changes behaviour, keep the winner, and write down why it won so the next test starts smarter.

  • Conversion rate optimisation

    We find where people drop out and fix the step, not the button colour.

    • Find the drop-off
    • Fix the step
    • Test the fix
    • Keep the winner

Core builds

Built for relevance. Designed to be tested.

Product recommendations that adapt

Recently viewed, bestsellers in a category, alternatives when something is out of stock, and what similar customers picked. We define which logic belongs in which moment, style it to look native, and build the fallback for customers you barely know yet.

What it includes

  • Recently viewed
  • Out-of-stock alternatives
  • Fallback logic

Behavioural content blocks

Reusable blocks that change per person and per language, managed centrally so an update lands everywhere at once. Your marketers add them to a campaign without a developer and without a new template.

What it includes

  • Per person
  • Per language
  • Managed centrally

A test-and-learn programme

Personalisation without measurement is decoration. We set up a testing rhythm, agree what counts as a win, and run it long enough to separate real lift from a good week.

What it includes

  • Testing rhythm
  • Holdout groups
  • Shared learnings

Deep platform expertise

Often, what you need is already in your automation platform. We use that first.

  • Bloomreach
  • Adobe
  • Klaviyo
  • Customer.io

Friendly asked questions

Got questions? We've got answers.

How much data do we need before personalisation is worth it?

Less than most teams assume. Two useful signals, what someone browsed and what they bought, already support recommendations, reactivation and content selection. The trap is waiting for a complete customer view before starting. We usually begin with one journey where the data is strongest, prove the lift, then widen it.

Where is the line between relevant and unsettling?

Roughly here: use what a customer would expect you to know from doing business with you, and be careful with anything they would be surprised you noticed. Referring to a product someone viewed is fine. Referring to how long they hesitated is not. We write these rules down at the start of a project so the decision is not made ad hoc by whoever builds the campaign.

Do we need a personalisation tool, or can our automation platform do it?

For email, your automation platform can usually do more than your team currently uses. Dynamic content, conditional blocks and behavioural triggers are standard. A dedicated tool earns its licence when you want on-site personalisation, product recommendations at scale, or experimentation across channels. We audit what you own before recommending anything new.

How do you measure whether personalisation works?

Against a holdout. A share of your audience keeps getting the generic version, and the difference between the two is the actual effect. Click-through alone will flatter you. We look at conversion, order value and repeat purchase, and we run tests long enough to survive a good week and a bad one.

Can you personalise the website and the emails with the same data?

That is the point, and it is where most setups break. Browsing on the site should change what the next email shows, and clicking in an email should change what the site shows on return. It needs a shared profile and a working connection between the two systems. We build that link, and we tell you early if your current stack cannot support it.

What could your data do today?

We'll show you what your current data supports, and what it takes to go further.

Let's talk