The expensive part of modern lifecycle marketing is no longer only the vendor. It is the habit of hand-building audiences, journeys, and touchpoints every time the business shifts priority.
The Problem: Scale Without Leverage
Most growing companies eventually face the same question: keep investing in a commercial journey platform, or rebuild around a more composable stack? Tools like Braze are excellent for single-branded, hard-coded journeys. That is a narrower strength than the market pitch usually admits.
As soon as you add real-time data, dynamic content, content blocks, multiple brands, or multiple categories, the system starts to break down. I have used Braze across my last two companies over the last six years. It cannot handle that kind of scale cleanly. The cost is not only licensing. It is the manual campaign construction, list assembly, QA, and channel coordination required to keep the platform upright as complexity rises.
That is the real fork. The decision is not whether Braze can ship a journey. It is whether your operating model can absorb new product lines, retention goals, and channel experiments without hiring more people for every new priority.
Where a Suite Still Fits
A lifecycle suite remains a rational choice when the work is still mostly single-brand and relatively static: a modest number of hard-coded flows, clear ownership, and enough operational bandwidth to maintain them by hand. If the company is still proving unit economics, commercial validation can outrank infrastructure redesign.
In that phase, Braze can be useful because it is strong at assembling and launching those hard-coded journeys. The friction is tolerable while the business is still discovering which messages, offers, and retention moments matter.
The suite becomes the wrong long-term answer once the same people are translating growing complexity into one-off campaigns inside a tool that resists real-time data, dynamic content systems, multi-brand rules, and category-scale variation. At that point the platform is not merely expensive. It is the bottleneck.
Manual Campaign Ops Is the New Legacy
Legacy used to mean an old ESP, a brittle ETL job, or a vendor that could not keep up. The new legacy is quieter: operators still build lists, stitch attributes, assemble content, and schedule touches as if every campaign were a custom project.
That process does not scale with business ambition. A company can add a new product line, enter a new retention problem, or launch a new channel and discover that the CRM organization is already fully occupied servicing last quarter’s journeys. The team then faces a false choice: ignore the new priority, or hire more people to keep pace.
The scalable alternative
Define audiences, goals, content, eligibility, and measurement as reusable units. Then use automation and model-assisted compilation to assemble the right treatment, instead of rebuilding each journey from scratch.
Focus Problems Make the Constraint Visible
Product surges expose this quickly. When one line of business becomes the company’s center of gravity—GLP-1 medications are a current example across digital health—the rest of the portfolio does not disappear. Existing retention programs, onboarding flows, support messaging, and adjacent product journeys still need care.
If the CRM model depends on people manually rebuilding journeys for whatever is loudest this quarter, the hot product line consumes capacity and other lines quietly degrade. That is not primarily a staffing failure. It is an infrastructure failure. Automation exists so a team can support new interests without restarting the org chart every time strategy changes.
The same pattern appears outside healthcare: a marketplace launches a new category, a retailer pushes a seasonal franchise, a SaaS company over-indexes on one expansion motion. The names change. The capacity trap does not.
What Composable Orchestration Changes
A composable approach separates the pieces that suites usually bind together:
- Data and eligibility live in governed warehouse models and contracts, not only inside the activation tool.
- Reverse ETL and syncs move curated audiences and attributes into channels without a custom engineering project for every request.
- Journey logic becomes modular: audience, goal, content, timing, and suppression can be reused across programs.
- Decisioning and optimization compile treatments with feedback loops instead of relying only on hand-authored campaign trees.
- Channels remain interchangeable. Email is still the primary commercial driver in many U.S. businesses; SMS and push matter; higher-cost channels such as direct mail need stronger testing infrastructure before they are treated as defaults.
This is the architecture I expand in The Perfect MarTech Stack and the migration path in Migrating From a Marketing Suite to a Composable Stack. The short version: keep the channel tools that earn their place, but stop letting one suite own every definition, decision, and deployment path.
Team Design: Builders That Scale Others
Headcount is not the success metric. Leverage is. A MarTech team should act as a builder and enabler for marketing, not as a ticket queue that recreates campaigns by hand. With the right automation, a relatively small technical group can support a much larger set of marketing priorities because the infrastructure absorbs volume.
That is why “hire more CRM operators” is often the wrong response to growth. If five people can operate a governed activation layer that marketers trust, that is usually better than fifteen people maintaining fragile journey trees that only the specialists understand. Exact numbers vary by company. The design principle does not: automation should remove the need to grow the team linearly with every new business interest.
For the organizational side of this model, see The Perfect MarTech Team.
Retention Before Aggressive Upsell
Across categories, CRM creates the most durable value when it protects the relationship the customer already has with the business: renewal reminders, lapse prevention, treatment or service completion, onboarding resolution, and timely support. Upsell and cross-sell still matter, but they sit on top of trust. When retention systems are underbuilt, growth messaging becomes noise.
A composable operating model helps here because retention logic can be defined once—eligibility, timing, quiet hours, suppressions, and success metrics—and reused as the product portfolio changes. That is harder when every program is a bespoke journey tree owned by whoever last touched the suite.
A Practical Decision Sequence
- Prove the commercial motion first. Do not rebuild infrastructure before the business knows which retention and revenue loops matter.
- Inventory the manual work. Identify which audiences, attributes, suppressions, and content assemblies are rebuilt repeatedly.
- Keep the suite only for the journeys it still handles well. Braze can remain a channel or delivery layer for simpler hard-coded flows inside a composable design.
- Move definitions upstream. Put identity, eligibility, and audience logic into governed data products that marketing and MarTech can both trust.
- Automate compilation, not judgment. Let systems assemble candidates; keep humans on strategy, creative quality, and risk.
- Measure capacity freed, not only campaigns shipped. Track how many new priorities the same team can support without adding headcount.
Tradeoffs
- Composable stacks require ownership. Without clear contracts and QA, modularity becomes fragmentation.
- Suites concentrate complexity inside one UI. That feels convenient early, then collapses when real-time data, dynamic content, content blocks, multiple brands, and multiple categories arrive together.
- Automation without governance creates confident mistakes. Eligibility, consent, and review still matter.
- Hot product lines can distort the roadmap. Protect shared infrastructure so one priority does not starve the rest of the portfolio.
Lessons
- Manual campaign construction is the legacy process to replace, even when the vendor is modern.
- Braze is strong for single-brand, hard-coded journeys and weak once real-time data, dynamic content, multi-brand rules, and category complexity accumulate.
- Automation is how MarTech supports new business interests without hiring in lockstep with strategy changes.
- Focus surges—whether GLP-1, a seasonal franchise, or a new category—are stress tests for operating leverage.
- Retention systems should be reusable infrastructure, not a queue of one-off journeys.
Related reading: Why Reverse ETL Is Quietly Replacing Traditional Marketing Data Pipelines, MarTech Data Contracts, and Governed AI Workflows for Marketing.