How I Build Growth | Zulma Arria

HOW I BUILD GROWTH

Growth doesn't break from lack of activity.
It breaks in the architecture.

I read the system.
Then I build what it requires to compound.

WHERE I CREATE THE MOST VALUE

The mandate varies. The pattern doesn’t.

Four organizational conditions — the ones where the work I do creates the most impact and where I’m the right person for what the business needs next.

The infrastructure doesn’t exist and the business needs it now.

The organization has outgrown its current model — or never had one to begin with. Pipeline is generated through effort and heroics rather than through a system designed to produce it consistently. The demand infrastructure, the signal layer, the handoff architecture between marketing and sales — none of it is built in a way that scales or holds under pressure.

This is where I start with a blank canvas. I read the commercial system before I touch it — understanding where pipeline stalls, where signals don’t translate, and where execution loses ground in the seams between functions. Then I build what the business needs: audience intelligence, demand architecture, pipeline progression, and the operating model that connects them. While delivering results on the same timeline.

I’ve built this kind of infrastructure in environments where the model didn’t yet exist — and again later when the organization didn’t yet recognize the problem was architectural.

The system is active but it isn’t connected.

Marketing is running. Sales is selling. Channels are producing activity. But the connections between them — signal to action, engagement to pipeline, marketing output to sales trust — don’t hold. Each function is performing inside its own logic and the seams between them are where revenue is quietly lost.

Transformation here isn’t about replacing what works. It’s about diagnosing what’s fragmented, designing the connective architecture, and rebuilding the operating model around shared commercial outcomes rather than functional metrics. The hardest part isn’t the build — it’s doing it while the business keeps running and results are still expected every quarter.

I’ve run this in organizations where the transformation wasn’t visible until the system started compounding — and where the board conversation changed because the revenue story finally held.

The motion works here. It needs to work everywhere.

A program, a team, or a motion is producing results in one place — one region, one product line, one segment, one sales channel. The challenge isn’t proving it works. The challenge is making it travel without losing the precision that made it work in the first place.

Most scaling attempts fail because the original model lived in people’s heads rather than in a codified architecture. Rebuilding from scratch at every new site, market, or tier is expensive, slow, and produces inconsistent results. The alternative is designing the model to travel from the beginning — with the segmentation logic, the enablement infrastructure, the coaching and accountability frameworks, and the operating rhythms that hold across different geographies, cultures, and commercial contexts.

I’ve scaled motions from a single market to global deployment and from a pilot program to enterprise infrastructure — without the precision degrading as the coverage expanded.

The problem has a name. The opportunity behind it hasn’t yet.

Some of the most significant commercial results I’ve contributed to weren’t visible as opportunities when I arrived. They were visible as friction — a stalled pipeline, a broken handoff, a customer experience that wasn’t holding, a route to market that hadn’t been designed for the buyers it was supposed to reach. Some of the largest growth opportunities emerge when those operational problems are reframed as commercial design problems — not how to fix a process, but how to redesign the system around how buyers decide, how revenue progresses, and how the organization compounds rather than resets each cycle.

That reframe — from operational problem to commercial opportunity — is where I’ve done some of my most consequential work. Before the discipline existed. Before the category had a name. Before the playbook was written.

The patterns behind those opportunities became repeatable operating models — shaping how later teams scaled, measured, and executed the work.

HOW I WORK

Four things that are consistently true — regardless of the organization, the market, or the moment.

I SEE THE SYSTEM, NOT JUST THE FUNCTION.

When I look at a revenue marketing challenge, I’m reading the architecture behind it — where audience intelligence is structural or assumed, where demand creation is connected to pipeline progression or operating in isolation, where buyer progression is designed or left to chance.

That system view spans the full commercial arc — from the first moment of awareness through demand, pipeline, and closed revenue — and it changes what’s visible. A coverage gap isn’t a headcount problem — it’s a signal that the model wasn’t designed to scale. A pipeline shortfall isn’t a campaign problem — it’s a signal that the connective architecture between marketing and revenue needs to be rebuilt.

I design from that read — not from the surface symptom, but from the structural condition underneath it.

I DELIVER AND BUILD ON THE SAME TIMELINE.

In complex organizations, the luxury of choosing between near-term performance and longer-term capability rarely exists.

Growth leadership requires holding both simultaneously — delivering results the business needs now while building the infrastructure that makes the next cycle more precise and scalable.

Each phase funds the next. Neither waits for the other.

I THINK IN COMMERCIAL OUTCOMES.

Every program, every investment, every team priority runs through one question: does this advance the governing commercial outcome the business is accountable for — and does it build the capability to advance it further next cycle?

Pipeline contribution, conversion rates, revenue velocity, and return on marketing investment are not reporting metrics. They are the design criteria — defined by the business model, not by marketing convention. What doesn’t vary is the discipline of connecting every marketing decision to the commercial outcome leadership expects it to produce.

But commercial outcomes don’t begin at the dashboard. They begin with the buying committee — with what buyers need to build confidence, reduce uncertainty, and advance toward a decision.

I design demand programs around that progression. The measure isn’t activity generated. It’s whether the motion advanced buyers through the decision process — and whether that progression ultimately reached revenue.

I BUILD STRENGTH THROUGH TEAMS AND CULTURE.

High-performing teams don’t happen by accident. I build the conditions deliberately — creating clarity, developing people before they feel ready, and building a culture where experimentation, ownership, and shared accountability reinforce each other.

The best growth work expands what the organization can do next.

The Diagnostic

Before prescribing what needs to change, I identify where the revenue marketing model is no longer aligned to how buyers buy and revenue progresses.

I read the system before I work on it. Not to produce a findings report — but to understand where the foundation needs to hold, where it will break under the next level of ambition, and where the build needs to start. That read happens across five dimensions simultaneously.

Where revenue is being created

The organization has a story about where its revenue comes from. Pipeline reports, attribution models, and campaign dashboards tell that story. I read what's underneath it — which audiences are actually progressing to closed revenue, which motions are producing pipeline the business can forecast around, and where the gap exists between what marketing believes is working and what is actually driving commercial outcomes.

That gap is almost always where the first intervention lives. Not in the programs that are underperforming — in the assumptions about performance that haven't been tested against revenue reality.

Where the buying journey and the demand model diverge

Buying committees don't progress because campaigns launch. They progress because the right information reaches the right stakeholders at the moment they need it to reduce uncertainty and build collective confidence toward a decision. When the demand model is built around activity volume rather than buyer progression, the gap between marketing output and pipeline contribution widens — regardless of how much execution improves.

I read where the demand architecture is designed around what marketing can produce versus what buying committees need to advance. That divergence is where pipeline stalls, where sales loses trust in marketing-sourced accounts, and where the connective architecture between demand creation and closed revenue needs to be redesigned.

Where the system will break under the next level of ambition

Every revenue marketing system has a capacity ceiling — a point at which the current model stops holding. Sometimes it’s a coverage model that works at 25 accounts but can’t travel to 1,200. Sometimes it’s a demand program that works in one region but wasn’t designed to operate across markets, products, or buying motions simultaneously. Sometimes it’s a measurement model that produces accurate reporting at current scale but can’t support the prioritization decisions the next level of growth requires.

I read for that ceiling before the build begins. Not what’s breaking today — what will break when the mandate expands. Designing for the next level of ambition from the start is what separates infrastructure that compounds from infrastructure that has to be rebuilt each time the business grows.

Where the operating model is creating friction

Revenue marketing doesn’t operate inside one function. It operates across sales, product, customer success, and revenue operations — in a matrix where ownership is frequently shared, handoffs are rarely clean, and decisions that should be fast get slow because accountability isn’t clearly assigned.

I read where that friction lives before it surfaces as a program failure. Where handoffs break down and context doesn’t transfer. Where investment is spreading across too many motions because prioritization decisions aren’t being made. Where the organizational structure and the commercial strategy are no longer aligned. Surfacing that friction early determines whether the build holds under execution pressure — or quietly loses ground in the seams between functions.

Whether the team has the capability the build requires

The most precise revenue marketing architecture fails if the people running it aren’t capable of operating at the complexity it requires. I read the team the same way I read the system — understanding individual strengths, how people think under pressure, where capability gaps exist relative to what the build demands, and whether accountability is tied to outcomes or effort.

That read shapes everything: the development map, the team structure, the pace of the build, and the sequence in which capability is developed alongside the infrastructure being built. The goal isn’t to assess what’s missing. It’s to understand what the team needs to become — and to begin building that alongside the revenue system from day one.

THE FIRST 90 DAYS

How the build starts — and what shifts at each stage.

Days 1–30

Read, Align, and Establish Clarity

Objective: A shared commercial reality the organization can act from.

—Map where revenue is being created versus where the organization believes it is.
—Read where buying committees are and what they're encountering from marketing.
—Identify where the buying journey and the current demand model diverge.
—Clarify growth priorities and how success is defined at the executive level.
—Identify execution gaps — handoffs, ownership, and decisions not getting made.
—Read the team — strengths, gaps, and capability relative to what the build requires.
—Build early trust with sales — understand their pipeline reality and where forecast confidence is eroding.

Days 31–60

Prioritize, Build, and Create Momentum

Objective: Momentum that compounds beyond the moment that required it.

—Concentrate demand generation, ABM, and lifecycle around a prioritized ICP.
—Eliminate what's diluting focus and establish clean handoffs across functions.
—Build the signal layer, scoring model, and progression design that makes pipeline visibility actionable across teams.
—Design the demand environment buying committees encounter while reducing uncertainty.
—Introduce operating rhythms that strengthen coordination without adding overhead.
—Close capability or capacity gaps through development, adjustments, or hiring.
—Connect individual team ownership directly to pipeline and commercial outcomes.

Days 61–90

Reinforce, Develop, and Demonstrate Lift

Objective: Results that hold — and a team that keeps building on them.

—Reinforce programs showing traction and embed what makes them repeatable.
—Measure whether buying committees are advancing — not just whether pipeline grew.
—Strengthen signal integrity and attribution confidence across the commercial arc.
—Demonstrate measurable lift in buyer progression, velocity, or sales acceptance.
—Establish a stable execution baseline the organization can scale from. business needs
—Advance team development — expand scope and connect growth to commercial ambition.
—Codify what's working into playbooks so performance holds beyond the moment.

By Day 90: priorities are clear, early lift is visible, and the team has a development path — not just a task list. Sales has a marketing partner it can forecast around. That’s how executive confidence is earned — and how growth becomes something the business can plan around.

WHAT CHANGES

This is what the organization looks like when the system is working.

Pipeline builds and converts.

The right buyers enter the system qualified — because targeting reflects live buying behavior, not historical assumptions. Buying committees encounter a demand motion designed around their decision process — building confidence before sales enters the conversation. Pipeline advances because the progression architecture was built for it. What marketing builds upstream reaches revenue downstream.

Revenue growth becomes predictable and defensible.

The team measures and improves fast enough for each cycle to build on the last. CAC drops. Payback shortens. The connection between marketing investment and revenue outcomes is clear enough to defend at the board level. Growth stops depending on heroics — and starts depending on the system.

Sales and marketing operate as one revenue team.

Definitions align. Signals are actionable. Handoffs hold — with shared context, clear accountability, and pipeline both teams can see and act on simultaneously. Sales stops rebuilding what marketing already built. Marketing stops defending its contribution in language sales doesn’t recognize. The friction was structural. So is the fix.

The team grows stronger with every cycle.

Capability develops alongside the infrastructure being built. People operate at a scope beyond what they were asked for before. Accountability is tied to outcomes — and the team holds itself to that standard because they understand what winning looks like. Each cycle starts more capable than the last — not because the system demands it, but because the team was built to compound.

More predictable growth. Better conversion. Less internal friction. Stronger forecast confidence.

Growth becomes easier to scale because the commercial system is connected.

Each of these outcomes connects to a specific place where growth was breaking. The six dimensions identify where — and what it takes to build what’s missing.

Growth doesn't break from lack of activity. It breaks in the architecture.