The design exists. Nothing is built.
Implementation, migration delivery and ongoing campaign operations across customer engagement platforms. Where the operating model has already been decided, whether by an internal team, a vendor blueprint or a previous engagement, Saiga builds against it.
The Problem
The platform went live. The operating layer did not.
Implementation usually stops at go-live. What remains is a working system with no structure underneath it. Campaigns are assembled by hand each cycle, there are no reusable components, quality assurance depends on whoever remembers, and the team learned the tool without learning the model.
The platform then runs at a fraction of what was licensed, and nobody can say precisely why.
The pattern is consistent:
events not instrumented, so the journeys the platform was bought for cannot be built
segmentation logic that exists in one person's head and leaves when they do
templates rebuilt from scratch every campaign
approval and quality assurance that are habits rather than processes
capability paid for at contract and never configured
This is not a strategy problem. The strategy is usually fine. It is a delivery problem, and it is fixed by building the layer that was skipped.
What we deliver
Discovery and scoping
A short, paid scoping phase before any build commitment. We map what exists, what is broken, what done looks like, and who signs off. Output is a scoped delivery proposal with defined acceptance criteria.
From £4,000.
Implementation
Integration and event schema design. Data model and attribute structure. Channel configuration across email, push, in-app and SMS. A reusable template and component library. A documented quality assurance and approval framework. Team handover with written operating conventions.
Typically six to twelve weeks. Scoped and priced from the discovery.
Migration delivery
Moving off a legacy platform: inventory, consent and suppression mapping, rebuild, parallel running and cutover.
Onboarding
Guided setup and capability transfer for teams new to a platform, or inheriting one that nobody documented.
First campaigns built alongside your team. Documented naming and structural conventions. Role-based training. A written operating guide that survives the person who wrote it.
Priced to team size and scope.
Campaign operations
Ongoing build, quality assurance and deployment as a monthly service, run to a documented standard rather than to whoever is available that week.
Scope is agreed at the outset and reviewed quarterly. Volume, channels and platforms are set in the engagement, not assumed.
Monthly, priced by the number of delivery days. Minimum three months. Starts after a delivery engagement or a short onboarding review.
Platforms
Braze
Liquid, Connected Content, Currents, cross-channel orchestration across email, push, in-app and SMS. Delivered at enterprise scale across multiple markets with local compliance and consent requirements.
Salesforce Marketing Cloud
AMPscript, Journey Builder, Email Studio, Automation Studio. Implementation, optimisation, and migration both onto and off the platform. Includes regulatory and servicing communications at volume, where every customer has to be reached inside a defined window with an audit trail behind it.
Also worked with Dotdigital, Eloqua, HubSpot, Klaviyo and Mailchimp.
Platforms are added when a client relationship justifies it, not to lengthen this page.
Why Saiga
Built where the consequences were real.
Nine years operating CRM and lifecycle platforms from the inside, across financial services, media and professional membership.
The formative work was regulatory: delivering customer communications within a court-ordered UK retail bank migration, where letters had to be right, approved and sent ahead of a fixed legal deadline.
Before that, lifecycle messaging built and deployed in Braze and Salesforce Marketing Cloud across 24 EMEA markets for Disney+, and five years running email operations as a central shared service for a professional membership body of 150,000 members and 20,000 students.
That background sets the standard applied here: approval workflows that hold under scrutiny, quality assurance that catches problems before customers do, and documentation that survives the person who wrote it.
It applies whether the client is regulated or not. The discipline is the same. Only the stakes vary.