Sep 18, 2020 · 49m · mad
Fireside Chat: George Fraser (Founder & CEO, Fivetran) with Matt Turck (Partner, FirstMark)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In a Data Driven NYC fireside chat, FirstMark Partner Matt Turck interviews Fivetran Founder and CEO George Fraser about the evolution of the modern data stack, automated ELT pipelines, and Fivetran's journey to becoming a $1.2B enterprise data integration platform.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Matt holds 13.2% of the talking time here. How this is scored →
Matt as informed peer 2.0 Guest teaching 3.6 Guest disagreement 0.5 Matt pushing back 0.3
speaking balance: gold is Matt, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 28:08 Guest playfully rejects host's sarcastic jab at VCs
When Matt sarcastically jokes about VCs actually helping for once, George playfully counters that VCs are great and unfairly targeted on Twitter.
Hardest push from Matt ▶ 30:45 Host pushes back on marketing buyer technical awarenessMatt presses George on whether non-technical business buyers like CMOs actually understand complex data concepts like warehouses and connectors.
Biggest teaching moment ▶ 16:50 Guest contrasts legacy platforms with Fivetran's correctness guaranteeGeorge reframes the entire data integration sector, explaining that legacy tools left correctness responsibility to customers whereas Fivetran treats mismatches as engineering bugs.
Matt holds his own ▶ 35:11 Host demonstrates deep knowledge of Fivetran's funding historyMatt cites exact historical context, detailing Fivetran's multi-year struggle to find product-market fit before executing rapid, back-to-back funding rounds.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Matt as informed peer | Guest teaching | Guest disagreement | Matt pushing back | Why |
|---|---|---|---|---|---|---|
| Welcome and Overview of Fivetran | 2 | 3 | 1 | 1 | Matt introduces Fivetran with facts regarding valuation and funding history. George provides a polite, minor correction regarding Fivetran's headquarters being in Oakland rather than San Francisco before defining data warehouses. | |
| Analytics, Dashboards, and Post-Warehouse Workflows | 2 | 4 | 0 | 0 | Matt guides the architectural overview from post-warehouse analytics to ELT mechanics. George breaks down why cheap cloud compute makes extracting and loading normalized schemas better than legacy ETL optimization. | |
| Fivetran Connector Architecture and Automation Engineering | 2 | 4 | 0 | 0 | Matt inquires about connector volume and underlying automation polling mechanisms. George educates the host on Fivetran's internal API abstraction layer that standardizes connector development. | |
| API Engineering, Data Accuracy, and the Fivetran Protocol | 3 | 4 | 1 | 1 | Matt asks whether Fivetran works directly with source vendors or reverse engineers APIs independently. George explains how taking total responsibility for schema correctness differentiated Fivetran from legacy toolkit vendors. | |
| Multi-Cloud Environments and Cloud Warehouse Dominance | 3 | 4 | 0 | 0 | Matt asks about source environment diversity across on-prem and cloud. George details why cloud-native data warehouses possess inherent structural compute and storage advantages for analytical queries. | |
| Transformations and Strategic Bet on Open-Source dbt | 3 | 4 | 0 | 0 | Matt highlights Fivetran's transformation offering. George explains dimensional modeling and why Fivetran strategically aligned with the open-source dbt ecosystem developed by Fishtown Analytics. | |
| Powered by Fivetran and Vertical Data Integration | 2 | 3 | 2 | 1 | Matt asks about the Powered by Fivetran product announcement and jokingly quips about VCs actually being useful. George humorously defends VCs against Twitter criticism while explaining embedded vertical analytics. | |
| Go-To-Market Strategy and Enterprise Buyer Personas | 3 | 4 | 1 | 1 | Matt pushes on whether non-technical business buyers like CMOs actually comprehend data stack mechanics. George reframes Fivetran as the utility plumber that builds invisible infrastructure behind the scenes. | |
| Founding Journey, Co-Founder Trust, and Capital Growth | 4 | 3 | 0 | 0 | Matt demonstrates research into Fivetran's early history and compressed fundraising rounds. George shares personal stories regarding family ties with his co-founder and the dynamics of hypergrowth fundraising. | |
| Audience Q&A: Cloud Portability and Warehouse Competition | 0 | 3 | 1 | 0 | Jack reads audience questions regarding multi-cloud deployment and competition with native warehouse tools. George clarifies why data warehouse internal tools are basic building blocks while Fivetran handles complex SaaS APIs. | |
| Audience Q&A: Compliance, Privacy, and Master Data Management | 0 | 4 | 0 | 0 | Jack asks audience questions covering compliance and master data management. George defines MDM principles and explains why non-destructive ELT in the warehouse preserves raw historical data. | |
| Audience Q&A: Handling Schema Drift and Company Naming | 0 | 3 | 0 | 0 | Jack asks about schema drift handling and company naming origin. George explains metadata polling algorithms and recounts the story behind Fivetran's Fortran pun name. |
Statements from this episode (18)
Fraser: Cloud data warehouses render legacy tools like OLAP cubes obsolete
“The tools that you use to manage data and analyze data are actually getting simpler over the last 10 years. You don't need as many different things because a few tools, most importantly the data warehouse, Have gotten so much better over the last 10 years that…”
Fraser: Amazon Redshift was the first cheap, fast data warehouse
“Redshift was incredibly important because it was, it came out in 2013. It was in the AWS console. It wasn't the first really good fast data warehouse, but it was the first one that was cheap.”
Fraser: BI dashboards are the most common data warehouse use case
“In practice, the most common use of data warehouses is to support business intelligence dashboards.”
Fraser: Fivetran has customers running billing out of their data warehouse
“We have customers who run billing out of their data warehouse.”
Fraser: In-warehouse transformation compute is cheaper than data engineering time
“The additional cost of compute and storage to replicate the extra data, to do those steps, those transformation steps inside the warehouse Are so small now, you know, they're less than what it's going to cost you to pay your data engineer for a week to build y…”
Fraser: Syncing a single database can support an entire company
“You can make a whole company just out of syncing one database”
Fraser: Fivetran succeeded by guaranteeing data accuracy instead of selling toolkits
“And the really critical thing we did that laid the foundation for our eventual success was that we said that it was our responsibility to make the data match. Which is actually unusual in the field of data integration. Most data integration tools, they see the…”
Fraser: SaaS vendors sometimes alter their APIs specifically for Fivetran
“And then sometimes they actually change the APIs for us.”
Fraser: Fivetran is publishing standards for replication-friendly API design
“And we're working on we're working on publishing more about, like, what do you need to do to make an API that's friendly to replication for data warehousing? Whether it's by us or one of our competitors or just the customers building their own data pipelines, …”
Fraser: dbt has emerged as the standard for data warehouse transformations
“Over the last couple of years, this great tool called DBT, which is an open source community. It's also a product, and there's a company called Fishtown Analytics that's the primary sponsor of DBT, but it's really emerged as the way to orchestrate transformati…”
Fraser: Vertical data integration will be a major trend in tech
“I think there's going to be a huge wave of this over the next few years. I think this is a giant trend in the In the data technology space is vertical integration, both because there's just like a centralization of effort, but also because it allows you to acc…”
Fraser: VCs are Fivetran's top referral source for Powered by Fivetran
“Venture capitalists are our most effective source of referrals actually for the powered by Fivetran program, because they all have a lot of, they have a lot of portfolio companies that are building businesses that, that meet that description in one way or the …”
Fraser: Marketing data is often Fivetran's initial enterprise use case
“So marketing data is often like the initial use case for Fivetran at a large company.”
Fraser: Fear of public failure is an underrated motivator for founders
“Fear of failure is an underrated motivator, let me tell you. But when all of your relatives know that you've started this company and you see all these people every summer at the lake, you realize that you had better make it succeed or you are going to be hear…”
Fraser: Hypergrowth forces quicker venture rounds regardless of capital efficiency
“No matter how capital efficient you are, you end up the faster you grow, the sooner you need to raise again, unless you want to just sit there and have, you know, one month's payroll in the bank account, which I don't think you want to when you have a lot of e…”
Fraser: Building custom data pipelines works best for large, stable internal sources
“If the data source is really large, it's something that's just yours, so Fivetran's never going to build a connector to it, and it's relatively stable, like it's not constantly changing configuration, then you can build your own data pipeline using the tools p…”
Fraser: Post-load master data management in the warehouse is safely non-destructive
“And this is different than how it's historically been done, but the big advantage of Doing MDM and other similar things in this way is that it's non-destructive. So you still have the original data. If you make a mistake and you realize later, oh, I said these…”