Projects and achievements
What we build, how each piece of work is documented, and the results we can stand behind with evidence.
Client projects
We publish a client project only with the client's written permission and with outcomes we can measure. Until those write-ups are approved, the blueprints below show how we approach each kind of work.
Delivery blueprints
Reference architectures for problems we are asked to solve. Each is labelled illustrative: it shows a design, not a named client's results.
Abandoned Cart Recovery Blueprint
Reference architecture for cart recovery with Marketing Cloud: data flow, journey design, consent, testing and measurement.
- Business problem
- Architecture
- Example data extension: Cart_Items
- Entry event
Agentforce Service Agent With Human Handoff Blueprint
How we would design a customer-facing Agentforce service agent that answers from approved knowledge and escalates to a human with full context.
- Business problem
- Architecture
- Components and responsibilities
- Data model
Order-to-Cash Integration With MuleSoft Blueprint
How we would connect Salesforce and an ERP with MuleSoft so orders, invoices and payment status move reliably, with errors that people can see and fix.
- Business problem
- Architecture
- Components and responsibilities
- Data model
Welcome and Onboarding Lifecycle Journey
How to design a welcome and onboarding journey that reacts to what new customers do, from entry rules and branching to consent, testing and honest measurement.
- The business problem
- Architecture and data flow
- Journey design
- Data model and consent
Unified Customer Profile with Data Cloud
A step-by-step reference design for unifying CRM, commerce and marketing data into one customer profile in Data Cloud, with match rules, consent and testing.
- The business problem
- Architecture and data flow
- Example match rule design
- Designing the rules
Consent Synchronisation Across CRM and Marketing
How to keep opt-outs and subscription preferences consistent across Salesforce CRM and marketing platforms, so an unsubscribe in one place is honoured everywhere.
- The business problem
- Where consent typically lives
- Target architecture
- Data flow for a single opt-out
B2B Lead Nurturing with Account Engagement
A reference design for B2B nurture programmes in Account Engagement (formerly Pardot), from track design and scoring to a clean, measurable hand-off to sales.
- The business problem
- Nurture tracks
- Programme design in Engagement Studio
- Scoring, grading and the hand-off
CRM to Marketing Cloud Data Synchronisation
How to move Salesforce CRM data into Marketing Cloud Engagement reliably, with the right subscriber key, synchronised data extensions, SQL staging and monitoring.
- The business problem
- Integration options
- Architecture and data flow
- Data model and consent
Activating Data Cloud Segments in Journeys
A reference design for turning Data Cloud segments into Journey Builder audiences, covering identifiers, activation, staging, journey entry, consent and testing.
- The business problem
- Architecture and data flow
- Identifiers: get this right first
- Why stage instead of entering directly?
Self-Service Preference Center
A reference design for a preference centre that lets people choose topics and frequency instead of unsubscribing from everything, built on CloudPages and AMPscript.
- The business problem
- Preference model
- Architecture and page flow
- Security
Re-engagement and Win-back Programme
How to define inactivity, bring lapsed subscribers and customers back with a focused journey, and retire the ones who will not return, without hurting deliverability.
- The business problem
- Segment definitions (example)
- Journey design
- Finding inactive subscribers with SQL
Event Registration and Reminder Journey
A reference design for registration confirmations, timed reminders and attended or missed follow-ups for webinars and in-person events, using Journey Builder.
- The business problem
- Architecture and data flow
- Journey design
- Message schedule (example)
Lead Routing and Assignment Automation
A reference design for routing every new lead to the right owner quickly and predictably in Salesforce, with clear rules, follow-up SLAs and the reports to prove it work…
- The business problem
- Example routing matrix
- Architecture
- Data flow for a new lead
Service Case Notification Journeys
How to keep customers informed as a service case moves from open to resolved, without notification storms, leaked internal statuses or marketing creeping in.
- The business problem
- Choosing where messages are sent from
- Architecture components
- How a notification moves through the system
Loyalty Tier Lifecycle Messaging
A reference design for messaging members as they move between loyalty tiers, from upgrade welcomes to fair, well-timed downgrade warnings.
- The business problem
- The tier lifecycle
- Data flow
- Detecting tier changes
Migrating from a Legacy ESP to Marketing Cloud
A phased reference plan for moving email from an older platform to Marketing Cloud Engagement without losing unsubscribes, reputation or history.
- The business problem
- Mapping legacy concepts to Marketing Cloud Engagement
- Migration phases
- Data model and consent
Transactional Email via API
A reference design for sending order confirmations, password resets and account alerts from your own systems through Marketing Cloud Engagement's APIs.
- The business problem
- Choosing the API pattern
- Architecture and data flow
- The send request
Field Service Scheduling and Mobile Workforce Blueprint
How we would structure work orders, scheduling, mobile technicians and van stock on Salesforce Field Service and Operations.
- Business problem
- Architecture
- Components and responsibilities
- Data model
B2B Reorder Portal With Commerce and Experience Cloud
How we would build a self-service reorder portal for distributors using B2B Commerce, an Experience Cloud LWR site and an ERP integration.
- Business problem
- Architecture
- Components and responsibilities
- Data model
Financial Services Cloud Advisor Workspace Blueprint
How we would design an advisor workspace on Financial Services Cloud that brings households, holdings, consent and service requests into one view.
- Business problem
- Architecture
- Components and responsibilities
- Data model
CPQ to Revenue Cloud Advanced Migration Plan
A phased, illustrative plan for moving from Salesforce CPQ to Revenue Cloud Advanced without disrupting quoting, contracts or renewals.
- Business problem
- Architecture
- Current and target components
- Data model
What every project write-up covers
Business context
The problem, who owns it and how success will be measured.
Constraints and requirements
Existing systems, data, consent and deadlines.
Solution design
Architecture, data model and the trade-offs we chose.
Build and integration
Products used, configuration and custom code.
Testing and security
Test evidence, access model and release plan.
Measured outcomes
Only results we can evidence, with how they were measured.
Tell us what you are trying to fix.
Share your Salesforce setup, goals and constraints. A practitioner reads every message and replies with questions, first thoughts or an honest view of whether you need outside help at all.
Talk to a Salesforce Expert