Marketing Automation

Make customer journeys work.

Design and implement campaigns and journeys that respond to customer and lead behaviour. I help teams build lifecycle and nurture programs, investigate unreliable automation, and keep campaign delivery dependable, starting with the tools they already use.

Tell me what you want to change

Build the journey your team needs next

Start with the customer experience and the reason for each message. Then connect the audience, timing, content and data needed to make that journey work.

Lifecycle and nurture programs

Build or improve B2B nurture and B2C lifecycle programs. Define who can enter, what happens next, and when someone should leave or stop receiving messages.

Campaigns and communications

Implement email, SMS, triggered and transactional communications within the agreed platform scope. Work through campaign configuration, personalization, connected data and the checks needed before launch.

Audiences, consent and preferences

Review segmentation, eligibility, exclusions and permission rules together. Check how customer behaviour and preference changes affect the next audience or journey decision.

Find why an existing journey is unreliable

A visible campaign issue can start in an audience rule, a data feed or a journey decision. I follow the relevant path, agree on the change and test the result across the systems involved.

Trace unexpected entry, timing, branching or exit behaviour.
Investigate missing events, conflicting identifiers and failed data handoffs.
Check old logic, data and timing that still affect messages after a platform change.
Review imports, exports, mappings, APIs and schedules where the journey depends on them.

Keep campaign delivery dependable

Get hands-on help with implementation work, campaign operations, administration or launch QA. One-off work and ongoing support are scoped separately, including support alongside an internal team or agency.

Testing and launch QA

Check audience counts, content, links, personalization, representative test cases and data handoffs before an agreed launch. Document the checks, expected behaviour and who owns the next step.

Journey care and troubleshooting

Maintain the relevant setup and investigate operational issues after a build or fix. Review changes with the people doing the work, so the implementation and its documentation remain useful.

Define a manageable piece of work

You do not need finished requirements to begin the conversation. If the cause is unclear, a separately scoped investigation may be the first step. We agree on deliverables, exclusions, cost, timing, testing and handover before implementation begins.

The customer journey or campaign you want to build or improve.
What happens today and what you want to happen instead.
The platform, data sources, channels and connections involved.
Timing, contributors, approvals and known dependencies.
Any documentation, walkthroughs or ongoing support you need.

Platforms

Hands-on platform work.

Oracle Responsys Implementation, administration and troubleshooting. See what you can hire me for and what helps scope the work.

Start with the change you need

You don’t need a finished brief.

Tell me what needs to work better and which journeys or campaigns are affected. A short outline is enough to identify what needs clarifying before the work can be priced. Do not send passwords, API keys, customer lists or data exports with your enquiry.

Talk to Rafael How Build · Fix · Run works