Marketing Cloud developer staff augmentation for Brightline Media Group
Engagement summary
ForceFolks supplied a full-time Marketing Cloud developer to Brightline Media Group from 22 April to 6 September 2024. The developer built four production journeys in Brightline’s Marketing Cloud Engagement org. Brightline’s Head of Lifecycle Marketing owned the campaign calendar and approved each activation. Subscription analytics recorded trial-to-paid conversion rising from 21.4% to 25.5% across the matched 60-day windows.
Client and Engagement Facts
| Field | Engagement detail |
|---|---|
| Client | Brightline Media Group |
| Industry and client location | Media and digital subscriptions. London, UK. |
| Staffing arrangement | One full-time nearshore Marketing Cloud developer from 22 April to 6 September 2024. Five hours of daily overlap with the client in BST. |
| Salesforce scope | Marketing Cloud Engagement. Audience data from Sales Cloud and Salesforce Data Cloud (now Data 360). |
| Tools | Journey Builder, Marketing Cloud SQL, AMPscript, Jira and Bitbucket. |
| Client ownership | Lifecycle Marketing owned the calendar and activations. Marketing Operations reviewed the build and received the runbook. |
Why the Client Added Capacity
Brightline’s lifecycle team could design campaigns. It needed engineering capacity for the data extensions, SQL and AMPscript that would put those campaigns into production. The work had to fit Brightline’s own Marketing Cloud org and leave its two-person marketing operations team with documentation it could use to run future journeys.
Client corroboration
“ForceFolks sent a developer who wrote clean SQL, tested every suppression case we could think of, and left documentation our own team actually uses. We have launched two more journeys since without outside help.”
Role Contributions and Acceptance
| ForceFolks role | Work and outputs | Client review or acceptance |
|---|---|---|
| Marketing Cloud developer | Built six data extensions using SQL activities against Sales Cloud and Data Cloud inputs. Implemented AMPscript for dynamic content and preference handling. Shipped onboarding, trial expiry, win-back and payment-failure journeys with consent and suppression checks, then handed over the build documentation. | The Marketing Operations lead reviewed the build. The Head of Lifecycle Marketing approved each journey before activation. |
Outcomes and Evidence
| Measure | Baseline | Result | Window | Source |
|---|---|---|---|---|
| Trial-to-paid conversion | 21.4% | 25.5%, up 4.1 percentage points or 19% relative | First 60 days after launch versus prior 60 days | Brightline subscription analytics |
| Onboarding audience reconciliation | Manual reconciliation without automated checks | 2,114,000 records in, 2,113,982 sent, 18 suppressed with reasons | May 2024 | Journey Builder send record |
| Suppression coverage | No benchmark recorded | 24 of 24 scripted tests passed | June 2024 | Marketing Operations test log |
| Journey handover | No documented journeys in scope | Four journeys handed over with documentation | September 2024 | Client runbook repository |
| First accepted build | Start of assignment | Accepted after 11 business days | May 2024 | Client Jira ticket record |
Related roles and delivery services
Discuss the work your team needs
Share the Salesforce work, roles and client review responsibilities. ForceFolks will assess the staffing requirement against that scope.
Discuss your staffing requirement