Case study · Fintech · GTM engineering + data stack + RevOps hiring

Ramp case study: the GTM data stack behind 25% of new-business pipeline

JayOh helped Ramp hire its RevOps team and stand up a modern GTM data stack: Snowflake, dbt and Hightouch feeding enriched data into Salesforce, HubSpot and Outreach. The automated BDR and personalization engine built on top drove 25% of all new-business pipeline while cutting data platform costs 20%.

By Joe LaGrutta, Founder, JayOhUpdated October 2026
Case file · Ramp Results
Toggle view
New-business pipeline from the engine25%
Data platform cost−20%
Transformation speed+33%
RevOps leadershipSenior leader + 2
25%of new-business pipeline
−20%data platform cost
+33%transform speed
Figures as reported in JayOh’s case study materials. “Baseline” means the starting point the improvement is measured against.
ClientRamp
IndustryFintech
ServicesGTM engineering · Data stack · RevOps hiring · Automated BDR
TimelineMulti-phase
01 · Client type

Who was the client?

Ramp was growing faster than its revenue operations. The team needed RevOps leadership, and the data that reps and leadership acted on had to be consistent, fast and pushed into the tools sellers actually use.

ClientRamp
Client typeHigh-growth fintech scaling GTM headcount rapidly
Source systemsSalesforce, HubSpot, Zendesk, Outreach
EngagementRevOps team design and hiring, data stack, reverse ETL, automated BDR and personalization
02 · Problem

What problem were they solving?

Problem 1

No dedicated RevOps leadership yet

Biz Ops, leadership, sales and marketing needed someone to own revenue systems and processes as GTM headcount scaled.

Problem 2

Warehouse bottlenecks

The previous data warehouse struggled with concurrency, causing deadlocks and performance bottlenecks.

Problem 3

Inconsistent core metrics

Data from Salesforce, HubSpot, Zendesk and Outreach was transformed ad hoc, so the same metric could disagree across reports.

Problem 4

Reps doing manual research

Without enriched, scored data in the CRM and sequencer, sellers spent time on research and data entry instead of selling.

03 · System built

What system did JayOh build?

6 workstreams, in the order they matter. Each one closes a specific gap from the problem list above.

Stack
SnowflakedbtHightouchSalesforceHubSpotOutreachZendesk (source)Ad platforms

RevOps team design and hiring

Worked with Biz Ops, leadership, sales and marketing to define roles, wrote the job descriptions and ran sourcing, interviews and evaluation. Placed a senior RevOps leader plus two supporting hires.

Snowflake warehouse

Replaced the bottlenecked warehouse with Snowflake for near-unlimited concurrency, automated scaling and lower maintenance overhead.

dbt data models

Standardized transformations across Salesforce, HubSpot, Zendesk and Outreach data so core metrics were consistent everywhere.

Reverse ETL with Hightouch

Synced enriched, scored data back into Salesforce, HubSpot and Outreach so reps and marketers acted on the same insight.

Automated BDR engine

Enriched prospect data flowing into the CRM, automated multi-channel sequences, and signal-triggered follow-ups so nothing slipped.

Personalization engine

Custom audiences synced to ad platforms, CRM enrichment and automated workflows delivering tailored outreach across marketing and sales.

04 · Timeline

How long did it take? Multi-phase

The work ran in the four phases below. A start-to-finish duration wasn’t recorded in the case study, so we don’t quote one.

Phase 1

Define and hire

Roles scoped with leadership; senior RevOps leader and two supporting hires placed.

Phase 2

Rebuild the data layer

Snowflake warehouse and dbt models standardize metrics across source systems.

Phase 3

Activate

Hightouch reverse ETL pushes enriched data into Salesforce, HubSpot and Outreach; BDR motion automated.

Phase 4

Personalize and scale

Personalization engine and synced audiences drive new-business pipeline as GTM headcount grows.

05 · Numbers

What were the results, before and after?

Every figure below comes from JayOh’s documented case study for this engagement. Where the starting value wasn’t recorded as a number, the “Before” column describes the starting state instead.

MetricBeforeAfterHow it was measured
Share of new-business pipelineNo automated engine25%From the automated BDR + personalization engine
Data platform costBaseline−20%Budget freed for growth initiatives
Data transformation speedAd hoc transforms+33%Faster insight for sales and leadership
Company growth supported—200%+With a foundation for 10X GTM employee expansion
RevOps team placedNo dedicated leader1 senior leader + 2 hiresStrategic leadership plus execution
06 · Takeaways

What made it work?

The operator lessons we’d apply to any team facing the same problem.

01

Hire the owner, then build the system

Placing a senior RevOps leader early meant the stack had an owner who kept scaling it after the build.

02

Model once in the warehouse

dbt models ended the ad hoc transformations that made the same metric disagree between Salesforce, HubSpot and Outreach.

03

Data only creates pipeline when it reaches the rep

Reverse ETL into the CRM and sequencer is what turned a warehouse into 25% of new-business pipeline.

07 · Self-check

Is this your situation?

Five signs we saw at this client before the work started. Tick the ones that are true for you; the more you tick, the closer your fix looks like this system.

Rule of thumb: 1–2 signs is a contained fix, 3 is this pattern, 4–5 means the system needs rebuilding rather than patching.

Signs you need this system

Tick the statements that are true for your team.

08 · FAQ

Questions about this case study

What did JayOh build for Ramp?
Two things: the team and the system. JayOh scoped RevOps roles, ran the hiring process and placed a senior RevOps leader plus two supporting hires, and built a modern GTM data stack (Snowflake, dbt, Hightouch) feeding Salesforce, HubSpot and Outreach, with an automated BDR and personalization engine on top.
How did the data stack create pipeline?
Hightouch reverse ETL pushed enriched, scored data into Salesforce, HubSpot and Outreach, which powered automated sequences, signal-based follow-ups and synced ad audiences. That engine generated 25% of all new-business pipeline.
How did Ramp cut data platform costs by 20%?
By moving off a warehouse with concurrency bottlenecks to Snowflake’s managed, auto-scaling platform and standardizing transformations in dbt, which also made data transformation 33% faster.
Is this GTM engineering or RevOps?
Both. The hiring and process work is classic RevOps; the warehouse, models, reverse ETL and automated BDR engine are GTM engineering. See our guide to what GTM engineering is for the distinction.
Does a company need Ramp’s scale for this stack?
No, but it needs a reason: inconsistent metrics, manual rep research, or data that never reaches the CRM. Smaller teams often start with reverse ETL or enrichment into the CRM before a full warehouse build.
Next step

Want this system in your stack?

Bring your current setup to a 30-minute call. We’ll tell you which parts of this case apply, what we’d build first and what it would take.

  • Growth pods: a consultant plus developers, run in weekly sprints
  • 100+ engagements and 75+ CRM migrations since 2016
  • HubSpot Platinum Partner, Clay partner, Anthropic/Claude partner
  • Current plans on the pricing page