The problem: Personalization required engineering support

When Drew Price joined as VP of Growth Marketing, the team was sending generic batch emails through Zoho Campaigns during filing season. No segmentation, no personalization, no experiments.

Every data field needed for a campaign had to go through engineering first: Jira ticket, sprint queue, reverse ETL sync, then waiting for everything to propagate before anything could go out.

In practice, that meant weeks of lag between a marketing idea and an actual send.

BryteBridge was planning to expand from a handful of states to all 50. That workflow made it impossible.

Drew had seen the same trap at Grammarly, where a 15-20 person lifecycle team still needed three parties, the data team, a reverse ETL provider, and engineering, to get a single field into a subject line.

The Sortment: Connecting Sortment to their stack

Sortment connected directly to BryteBridge's Snowflake instance without any pipelines or reverse ETL.

Marketing got read-only access to the tables engineering already built and maintained. No risk of touching source data, no extra infrastructure to manage. It required 2 hours of engineering time at the very start, then nothing.

"I'm able to create audiences directly, without the need for a once-a-day or once-a-week pipeline, or reverse ETL, or whatever buzzword you want to use. None of that is nearly as efficient, or creates that sense of ownership over the data." - Drew Price, VP of Growth (SMB), BryteBridge Group

Drew stopped waiting on other teams. He started shipping the same day as the idea.

Use Cases: All your data, AI assistant and an all-in-one platform

1. Personalization with custom attributes

BryteBridge's compliance model depends on urgency.

A subject line reading "46 days left to file your annual report" converts better than a generic reminder. Calculating that field across millions of records used to mean weeks of back-and-forth with the data team, if you could get it prioritized at all.

With Sortment, Drew creates derived fields himself in under five minutes.

1. Describe what you need in plain language to the AI assistant

2. Review the generated SQL and a sample of output records to verify accuracy

3. Publish, the field is live in subject lines and audience conditions immediately

He has done this more than ten times in his first six weeks. Each time, a new personalization dimension, live the same day.

2. AI Assistant for all your needs

Sortment’s AI assistant sits inside the campaign workflow.

Marketers can use it to pressure-test audience logic, generate subject line variants, create new fields, or answer business questions without pulling in analysts or data teams.

For example, when the team needed to decide whether one unsubscribe should suppress an entire business entity, they could compare order impact against unsubscribe risk directly inside Sortment.

The point is simple: strategy, analysis, content, and execution happen in the same place.

3. Zero coordination overhead among your apps

Most lifecycle teams work across too many tools.

• Data requests in Jira

• Campaign tasks in Asana

• Approvals in Slack

• Audience logic in the ESP

• Analysis somewhere else.

Sortment brings that work into one operating layer.

A marketer can build audiences, create derived traits, write content, review logic, test, and launch without waiting on multiple handoffs.

That means fewer delays, less context loss, and faster execution.

What Changes When Execution Stops Being the Constraint?

The visible result is higher campaign output. The deeper shift is how lifecycle teams work.

In the old model, every new idea created a queue: data request, field sync, analyst support, QA, approval, launch.

With Sortment, a marketer can move from idea to audience to personalized campaign in the same session.

That changes the pace of experimentation. Instead of launching a few major programs per quarter, teams can test multiple campaign ideas in parallel.

The constraint moves from execution bandwidth to quality of strategy.

Frequently Asked Questions

How much engineering is needed to set up Sortment with Snowflake?
Engineering provides read-only Snowflake access once. After setup, marketers can build audiences, create fields, and launch campaigns inside Sortment without recurring engineering support.

Can marketers create custom fields without SQL?
Yes. They describe the field in plain language, review the generated SQL and sample output, then publish it for use in campaigns.

What does a typical campaign cycle look like?
Idea, audience creation, dynamic content, test send, launch. In many cases, the full cycle can happen in under an hour.

Does Sortment replace journey-based automation?
Sortment supports recurring automations and targeted campaigns. The shift is toward running more focused campaigns in parallel instead of maintaining large, complex journeys as the default.

Who gets the most out of Sortment?
Lifecycle and growth marketers who think in activation, retention, upgrades, renewals, and revenue, not just send volume.

What resources does Sortment reduce dependency on?
Data engineering, analytics, campaign operations, and project coordination. It gives marketers more direct control over data, logic, and execution.

Does this only work with Snowflake?
Sortment’s direct warehouse integration is built around Snowflake today. Other warehouse setups should be evaluated based on the implementation path.