Cookie preferences

Manage your consent preferences by category. Necessary cookies are always active because the website cannot function properly without them. See our Privacy Policy

Necessary
Preference
Statistics
Marketing
Unclassified

This website uses cookies

We use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners who may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services.

See our Privacy Policy

The two sides of a build

A build that keeps the business brief and the technical reality in the same room

We do not start with modules and settings. We start with the marketing outcomes the platform needs to support, then design the Salesforce setup around them.

Business side

What you need your marketing to do

  • The customer journeys that matter: welcome, onboarding, retention, and reactivation.
  • A measurement framework agreed before a single setting is touched.
  • How your team actually works day to day, not how the org chart says it works.
  • The growth stage you are in now, not the business you might be in three years.

Technical side

What Salesforce needs to look like to run it

  • Data extensions, relationships, and segmentation logic, built for those journeys.
  • Content, automation, and personalisation, live in Content Builder, Journey Builder, and Automation Studio.
  • Integrations with Salesforce CRM and external data sources, handled in the same phase.
  • The right platform for the job: Marketing Cloud, MC Next, Data Cloud, or Agentforce.

How we build

Six phases. One accountable team.

We do not hand a spec to a build team and check back at go-live. Every phase is visible, and every phase has to earn the next one.

1

Discover

We define the journeys that matter and map every data source, system, and touchpoint needed to run them. Nothing assumed, everything documented before design starts.

2

Design

We design the data model and architecture that will power those journeys. Getting this right at the start prevents months of rework later.

3

Build

Content, journeys, and automation, built and configured, with personalisation and integrations handled in the same phase.

4

Test

Every journey is validated end to end, across devices and clients, before we activate anything.

5

Deploy

We activate the build, brief your team on how to run it, and get KPI dashboards live from day one.

6

Evolve

A launch is a starting point. We stay on to monitor, optimise, and expand the build as your marketing matures.

Who this is for

Three types of brief. One team that handles all of them.

New to Salesforce

Implementing Marketing Cloud, Data Cloud, or Agentforce for the first time, and want it built to last, not built to spec and left.

Migrating or expanding

Moving to MC Next, or adding Data Cloud to an existing setup, and need the transition planned properly, not bolted on.

Already live, not satisfied

Running on Salesforce but unsure whether the build still fits the job. A health check is where we start.

Why Growing Minds

A build you can market from

  • Designed around your use cases, not a generic template.
  • A data architecture that supports the journeys you actually want to run.
  • Full documentation and team briefing, so you are not dependent on one person knowing how it works.
  • KPI dashboards active from day one, and a team that stays involved after launch.