
How to find — and keep — product-market fit | Bob Moore (Co-founder and CEO at Crossbeam, ex-RJMetrics and Stitch Data)
Bob Moore is the co-founder and CEO at Crossbeam, a “LinkedIn for data” platform that helps companies find overlapping opportunities with their partners. Crossbeam has raised US$117M to date and recently acquired Reveal in 2024. Bob previously cofounded RJMetrics (now part of Adobe Commerce Cloud) and Stitch Data (acquired by Talend). He is also the author of Ecosystem-Led Growth.
Table of Contents
🚀 How did Bob Moore validate the idea for Crossbeam?
Founder-Market Fit Validation Strategy
Bob Moore took an unconventional approach to validating his third startup idea by focusing on founder-market fit before product-market fit. After selling his previous companies RJ Metrics and Stitch Data, he developed a systematic method for choosing his next venture.
The Idea Collection Process:
- Decade-Long Documentation - Maintained an Evernote file of every business idea he encountered while building his previous companies
- Comprehensive Catalog - Collected ideas from skunk works projects, unsolved problems, coffee conversations, and random inspirations
- Diverse Range - Ideas spanned from B2B SaaS to consumer businesses, even including escape room chains
The 2x2 Matrix Framework:
Bob used a founder-market fit pre-screening matrix with two key dimensions:
- Personal Interest: How much fun would I have doing this? How intellectually stimulating is the problem?
- Experience Match: What about my specific experience makes me predisposed to solving this problem?
Validation Through Founder Feedback:
- Narrowed Focus: Reduced 100+ ideas to 10-15 using the matrix framework
- Founder Interviews: Conducted 20-30 calls with founders at different company stages
- Unbiased Testing: Presented 3 business ideas equally without revealing preferences
- Clear Winner: Crossbeam consistently stood out in founder conversations
🎯 Why did Bob Moore choose founders over end users for idea validation?
Strategic Reasoning Behind Founder-Focused Validation
Bob Moore deliberately chose to validate his startup ideas with founders rather than potential end users or buyers, based on his experience with the ephemeral nature of product-market fit.
Trust and Conviction Factors:
- Higher Trust Level - Founders provide more honest, unbiased feedback than potential customers
- Long-term Perspective - Founders understand sustainable business models beyond immediate product-market fit
- Team Building Capability - Validation needs to support personal conviction for rallying teams and investors
The Product-Market Fit Challenge:
Bob learned from his previous companies that product-market fit is extremely ephemeral:
Common Ways Companies Lose Product-Market Fit:
- Market Movement - The market shifts while your product stays static
- Product Evolution - Adding features that push you out of your sweet spot
- Market Saturation - Reaching the ceiling of your addressable market (e.g., hitting $2M ARR and realizing that's the limit)
- Feature Creep - Trying to 10x growth by building the "next feature" that completely changes your value proposition
The Validation Trap:
Speaking only to target personas creates a "prison of your own making" where you become trapped building and selling only to those specific feedback providers, potentially limiting long-term scalability and vision.
📈 What is Bob Moore's entrepreneurial background before Crossbeam?
Three-Time SaaS Founder Journey
Bob Moore is a serial entrepreneur who built two successful data companies before founding Crossbeam, with each venture teaching him valuable lessons about product-market fit and market timing.
First Company - RJ Metrics (2008):
- Launch Timing: Started the day before Lehman Brothers collapsed in 2008
- Market Context: Built when "SaaS wasn't even SaaS yet"
- Product Focus: Analytics platform for e-commerce companies
- Outcome: Sold to Magento in 2016, later acquired by Adobe
Second Company - Stitch Data (2016):
- Product Focus: Data infrastructure company building cloud-based data pipelines
- Market Position: Early player in the modern data stack
- Technical Focus: Helped companies get data into their data warehouses
- Outcome: Sold to Talend in 2018
Key Learning Pattern:
Both companies achieved "base hit style outcomes" rather than IPO-scale success, which Bob attributes to varying levels of founder-market fit. Neither company reached the trajectory that Crossbeam is currently on.
The Transition Period:
After wrapping up Stitch, Bob experienced a 6-month "calm before the storm" period where he couldn't simply relax on a beach and instead dove into planning his next venture using his decade-long collection of business ideas.
💎 Summary from [0:30-7:58]
Essential Insights:
- Founder-Market Fit First - Bob Moore prioritized personal passion and experience alignment over immediate product-market fit when choosing his third startup
- Product-Market Fit is Ephemeral - Companies frequently lose product-market fit through market shifts, feature creep, or market saturation, making founder conviction crucial for long-term success
- Validation Strategy Matters - Speaking to founders rather than end users provides more honest feedback and prevents getting trapped in a narrow customer segment
Actionable Insights:
- Use a 2x2 matrix to evaluate startup ideas: personal interest/fun vs. relevant experience
- Document business ideas continuously over time to build a comprehensive opportunity pipeline
- Test ideas with fellow founders for unbiased feedback rather than potential customers during early validation
- Consider founder-market fit as a predictor of sustainable success beyond initial product-market fit
📚 References from [0:30-7:58]
People Mentioned:
- Brett Berson - Partner at First Round Capital, podcast host conducting the interview
- Bob Moore - Co-founder and CEO of Crossbeam, serial entrepreneur being interviewed
Companies & Products:
- Crossbeam - Bob's current company, a data-driven partner ecosystem platform
- RJ Metrics - Bob's first company, analytics platform for e-commerce (acquired by Magento/Adobe)
- Stitch Data - Bob's second company, data infrastructure platform (acquired by Talend)
- First Round Capital - Venture capital firm that helps startups like Notion, Roblox, Uber, and Square
- Magento - E-commerce platform that acquired RJ Metrics in 2016
- Adobe - Acquired Magento and RJ Metrics as part of Adobe Commerce Cloud
- Talend - Data integration company that acquired Stitch Data in 2018
- Notion - Productivity platform mentioned as First Round portfolio company
- Roblox - Gaming platform mentioned as First Round portfolio company
- Uber - Ride-sharing company mentioned as First Round portfolio company
- Square - Payment processing company mentioned as First Round portfolio company
Technologies & Tools:
- Evernote - Note-taking app Bob used to collect business ideas over a decade
- SaaS - Software as a Service model that wasn't fully established when Bob started RJ Metrics in 2008
Concepts & Frameworks:
- Founder-Market Fit - Bob's framework for evaluating personal alignment with business opportunities before pursuing them
- Product-Market Fit - The degree to which a product satisfies strong market demand, discussed as ephemeral and challenging to maintain
- Modern Data Stack - The contemporary approach to data infrastructure that Stitch Data helped pioneer
🎯 Why do founders make better early customers for validating startup ideas?
Founder Empathy and Market Understanding
Bob Moore discovered that founders possess unique qualities that make them exceptional early customers for idea validation:
Key Founder Advantages:
- Multi-persona empathy - Founders develop deep understanding across different user types and customer segments
- Market evolution insight - They grasp how markets change over time and what creates durable, versatile solutions
- Strategic thinking - They can evaluate ideas beyond immediate use cases to see broader potential
The Validation Approach:
- Question shift: Instead of asking "Would you buy this?" ask "Would you start this company?"
- Obstacle identification: "What challenges do you think you might encounter?"
- Scope expansion: Rather than narrowing ideas to specific personas, founders help broaden horizons of what's possible
Why This Works:
- Founders think at IPO scale rather than quick wins
- They provide feedback on long-term viability and market potential
- Their perspective helps entrepreneurs zoom out before zooming in on specifics
- They understand the full journey from concept to scale
🤝 How does presenting multiple ideas prevent biased feedback from investors and advisors?
The Optionality Trap Problem
Bob Moore identified a critical issue in founder-advisor dynamics that leads to non-optimal feedback:
The Bias Problem:
- Social politeness - Smart people want to be nice or assume the founder is smart
- Proxy dynamics - Advisors think "if this person is smart, their idea must be smart"
- Investor optionality - Investors preserve relationships by being overly positive
- FOMO effect - Fear of missing the founder's next big thing overrides honest feedback
The Multi-Idea Solution:
- Forces comparison - Advisors must choose between options rather than just validate one
- Creates criticism space - Easier to critique ideas when there are alternatives
- Reduces confrontation - Less personal attachment to any single concept
- Enables candid feedback - Removes the binary approve/disapprove dynamic
Founder Psychology Factor:
- Default optimism - Founders think "I could run that, sounds fun, therefore it's good"
- Forcing function - Comparison requires deeper analysis of "which one and why"
- Critical evaluation - Must justify choices rather than just pursue passion
📊 What was Bob Moore's retroactive AB testing idea from Stitch Data?
Data-Driven User Journey Optimization
Bob Moore developed an innovative approach to customer optimization using historical data analysis:
The Core Concept:
- Retroactive analysis - Instead of running traditional A/B tests, analyze existing data patterns
- Built-in variability - Leverage natural differences in user populations and behaviors
- Conversion correlation - Identify which user journeys lead to highest customer lifetime value
Data Sources Used:
- User behavior tracking - Snowplow analytics capturing every click and action
- Marketing funnel data - All upstream marketing touchpoints and sources
- Product usage patterns - First actions, pages visited, data sources connected
- Partner relationships - Existing customer relationships and integrations
Key Insights Discovered:
- Database preferences - MySQL users were 30% more likely to become paying customers than PostgreSQL users
- User journey optimization - Specific paths through the product correlated with higher conversion
- Content influence - Certain pieces of content led to better customer outcomes
- Source quality - Different acquisition channels produced varying customer lifetime values
Implementation Strategy:
- Route users through optimized journeys based on data insights
- Customize content and discovery funnels for different user types
- Present analytics in board-ready format showing clear business impact
- Use findings to inform product development and marketing strategies
🌐 How did Stitch Data create 700 landing pages with just 80 pieces of content?
Scalable SEO Content Strategy
Bob Moore's team at Stitch Data developed an ingenious content multiplication system:
The Mathematical Approach:
- Formula: A + B content pieces = A × B landing pages
- Stitch example: 10 destinations + 70 sources = 80 articles → 700 unique pages
- Domain strategy: Purchased domains like "to-redshift", "to-snowflake", "to-bigquery"
Technical Implementation:
- Dynamic page construction - Pages built in real-time when accessed
- Content management system - Automated content assembly for each combination
- Subdomain structure - Every data source got its own subdomain (e.g., mailchimp.do2redshift.com)
Page Content Structure:
- Source explanation - What the SaaS tool is and how its APIs work
- Destination details - Data warehouse specifications and data placement methods
- DIY option - Technical instructions for building custom data pipelines
- Easy solution - Simple Stitch signup for automated data flow
Business Impact:
- Enormous lead generation engine - Massive SEO footprint with minimal content creation
- Zapier comparison - Similar strategy to Zapier's successful SEO approach
- Scalable model - Exponential page growth with linear content investment
- Product idea potential - Could be productized as a platform for other companies
💎 Summary from [8:03-15:56]
Essential Insights:
- Founder validation advantage - Founders make superior early customers because they possess multi-persona empathy and understand market evolution at scale
- Multi-idea feedback strategy - Presenting multiple concepts prevents biased feedback from advisors and investors who otherwise preserve optionality
- Data-driven optimization - Retroactive AB testing using historical data can reveal powerful insights about user journeys and customer lifetime value
Actionable Insights:
- Ask founders "Would you start this company?" instead of "Would you buy this?" for deeper validation
- Present 2-3 ideas simultaneously to advisors to force comparative analysis and honest feedback
- Leverage existing user data to identify optimal customer acquisition and onboarding patterns
- Use mathematical content strategies (A + B = A × B pages) to scale SEO efforts exponentially
📚 References from [8:03-15:56]
Companies & Products:
- Stitch Data - Bob Moore's previous company that provided data integration services, acquired by Talend
- Crossbeam - Bob Moore's current company, described as "LinkedIn for data" platform
- Zapier - Referenced for their successful SEO strategy similar to Stitch's approach
- Slack - Example of successful pivot outcome mentioned in founder persistence discussion
- Twitter - Another example of successful company pivot referenced
Technologies & Tools:
- Amazon Redshift - Data warehouse platform mentioned as Stitch destination
- Google BigQuery - Google's data warehouse solution referenced
- Snowflake - Cloud data platform mentioned as integration destination
- Azure SQL Data Warehouse - Microsoft's data warehouse solution
- Snowplow - Analytics platform used for tracking user behavior
- MySQL - Database system mentioned in conversion analysis
- PostgreSQL - Database system compared to MySQL in user behavior study
SaaS Tools Referenced:
- Trello - Project management tool mentioned as data source
- HubSpot - CRM platform referenced as integration source
- Salesforce - CRM system mentioned as data source
- GitHub - Development platform referenced as data source
- MailChimp - Email marketing platform used in landing page example
🎯 How did Bob Moore validate Crossbeam's product-market fit before building?
Early Validation Strategy
Bob Moore discovered a powerful validation method when pitching his three startup ideas to 40+ founders. While other concepts like escape rooms generated polite interest ("oh that'd be so cool, see you later"), Crossbeam sparked immediate engagement and next steps.
Key Validation Signals:
- Active Referrals - People said "you should really talk to so-and-so because I know they've run into this problem"
- Waitlist Formation - Founders asked to be added to mailing lists for updates on when the product would be built
- Organic Virality - Partner managers from major companies reached out independently through word-of-mouth
The Intrinsic Viral Nature:
- Network Effect Requirement: Crossbeam functions as "LinkedIn for data" - users can't get value unless their partners also join
- Self-Propagating Growth: Users are naturally motivated to invite and convince their partners to join, independent of any company marketing efforts
- Pre-Product Virality: The viral loop started working before the product even existed, spreading through telephone chains and text messages
Product-Market Fit Recognition:
"Product Market fit just punches you in the face when you find it right and I think it was just very very clearly there from the idea stage with Cross Beam"
The validation was unmistakable - people weren't just interested, they were actively cultivating demand and creating organic distribution channels.
🔄 What does Bob Moore mean by getting into and out of product-market fit?
The Dynamic Nature of Markets
Bob Moore challenges the common founder misconception that markets are stationary targets. Most entrepreneurs think of product-market fit as a fixed destination where you iterate your product until it "clicks" with an unchanging market.
The Traditional (Flawed) Mental Model:
- Static Market Assumption - Treating the market like "a pole in the ground" - a fixed target
- Product-Only Iteration - Following the build-measure-learn cycle by only adjusting the product
- Arrow-Shooting Approach - Continuously shooting arrows (product iterations) at the stationary pole (market) until one hits
The Reality of Market Dynamics:
- Markets Move Constantly - Customer needs, competitive landscapes, and economic conditions shift continuously
- Timing Matters Enormously - RJMetrics launched right as Lehman Brothers collapsed, entering the Great Recession
- Fit Can Be Lost - Companies can achieve product-market fit and then lose it as markets evolve
- Multiple Transitions Possible - RJMetrics went from no fit → strong fit → lost fit again over several years
RJMetrics Case Study Timeline:
- 2008: Started without product-market fit during market crash
- Multi-year period: Achieved and sustained clear product-market fit
- Later years: Slipped out of fit as market conditions changed
This dynamic view requires founders to continuously monitor and adapt to market shifts, not just perfect their product once.
💪 How did RJMetrics survive the 2008 financial crisis as a startup?
Bootstrapping Through the Great Recession
When Bob Moore and Jake Stein quit their venture capital jobs at Insight Partners on Friday, September 2008, Lehman Brothers collapsed the very next Saturday. This timing forced them into an extended bootstrapping period that shaped their entire business approach.
Crisis Response Strategy:
- Geographic Arbitrage - Moved from expensive New York to Camden, New Jersey for lowest possible real estate costs
- Services-First Model - Built a services business with software wrapped around it to generate immediate revenue
- Self-Funded Growth - Grew entirely without external capital for three years
- Survival Metrics - Focused on generating enough revenue to pay for basic necessities like health insurance
The Bootstrapping Journey:
- Duration: Approximately 3 years of pure bootstrapping
- Growth Rate: Intentionally slow but sustainable growth
- Revenue Milestone: Reached $1M ARR profitably
- Team Building: Hired first dozen employees before raising capital
- Market Reality: VC contacts from Insight Partners proved "completely worthless" due to LP capital restrictions
Key Insight on Product-Market Fit:
During this extended period, Moore believes they didn't actually have true product-market fit. Instead, they had "hustle and patience" - the determination to build a sustainable business through pure execution rather than venture-backed scaling.
This experience taught them that survival and growth are possible even without perfect product-market fit, but it requires exceptional resourcefulness and long-term thinking.
📊 What was RJMetrics' early product and business model?
E-commerce Analytics for Non-Technical Marketers
RJMetrics solved a critical gap for e-commerce companies whose marketers needed advanced analytics but lacked dedicated data teams. The solution combined data infrastructure with user-friendly analytics interfaces.
Core Product Architecture:
- Data Connection - Connected directly to back-end databases (usually shopping cart systems)
- Data Warehousing - Migrated data into hosted MySQL databases optimized for analytics
- Automated Query Generation - Built software to automatically generate SQL queries based on business logic and data structure
- Dashboard Interface - Provided user-friendly dashboards for non-technical marketers
Key Analytics Capabilities:
- Cohort Analytics - Understanding customer behavior patterns over time
- Customer Lifetime Value - Calculating long-term customer worth
- Marketing ROI Analytics - Measuring campaign effectiveness
- Repeat Customer Analysis - Tracking repeat vs. new customer sales
- Purchase Pattern Analysis - Understanding what first purchases predict about future behavior
- Order Size Trends - Analyzing how order values change across multiple purchases
Target Market Focus:
- Primary Users: Marketers at e-commerce companies
- Key Value Proposition: Advanced analytics without requiring data teams
- Business Logic: Focus on repeat business optimization since new customer acquisition costs were so high
Modern Equivalent:
RJMetrics was essentially "Fivetran + Snowflake + DBT + Looker all together in one product" - though Moore admits they built "the crappiest version you can imagine" of each component to create the integrated solution.
🚀 How did RJMetrics alumni influence the modern data stack?
The RJMetrics Data Diaspora
The 2013 RJMetrics team became a breeding ground for the next generation of data infrastructure companies. The experience of building an integrated analytics platform taught the team valuable lessons about the individual components that would later become standalone businesses.
Notable Alumni Companies:
- DBT (Data Build Tool) - All three co-founders worked at RJMetrics
- Stitch Data - Founded by Bob Moore and Jake Stein, became early competitor to Fivetran
- Omni - Described as "the hot new" analytics company (referenced but cut off in transcript)
The Unbundling Pattern:
RJMetrics built integrated versions of what would later become the modern data stack:
- Data Ingestion (later Fivetran/Stitch)
- Data Warehousing (later Snowflake)
- Data Transformation (later DBT)
- Data Visualization (later Looker)
Strategic Insight:
The experience of building "the crappiest version" of each component in an integrated platform gave the team deep understanding of:
- Individual Component Needs - What each piece of the data stack should do well
- Integration Challenges - How these components need to work together
- Market Opportunities - Which components deserved to be standalone businesses
This pattern demonstrates how early integrated solutions often spawn the next generation of specialized, best-in-class tools as markets mature and demand more sophisticated solutions.
💎 Summary from [16:01-23:57]
Essential Insights:
- Product-Market Fit Validation - True PMF creates organic virality and waitlists before the product exists, not just polite interest
- Market Dynamics - Markets aren't stationary targets; companies can find, sustain, and lose product-market fit as conditions change
- Crisis Bootstrapping - Survival without venture funding is possible through geographic arbitrage, services-first models, and patient capital efficiency
Actionable Insights:
- Look for validation signals beyond enthusiasm: referrals, waitlist signups, and organic word-of-mouth spread
- Recognize that achieving product-market fit once doesn't guarantee permanent success - continuous market monitoring is essential
- Consider bootstrapping strategies during market downturns: location arbitrage, services wrapping, and profitability-first growth
- Integrated early solutions often spawn the next generation of specialized best-in-class tools
📚 References from [16:01-23:57]
People Mentioned:
- Jake Stein - Bob Moore's co-founder at RJMetrics and Stitch Data
- DBT Co-founders - All three worked at RJMetrics before founding DBT (Data Build Tool)
Companies & Products:
- Crossbeam - Bob's current company, described as "LinkedIn for data"
- Partner Base - Crossbeam's database of all partnerships between companies globally
- RJMetrics - Bob's previous company, now part of Adobe Commerce Cloud
- Stitch Data - Data integration platform co-founded by Bob, acquired by Talend
- Insight Partners - Venture capital firm where Bob and Jake worked 2006-2008
- Lehman Brothers - Investment bank that collapsed in September 2008
- Fivetran - Data integration platform, competitor to Stitch
- Snowflake - Cloud data warehouse platform
- DBT (Data Build Tool) - Data transformation tool founded by RJMetrics alumni
- Looker - Business intelligence platform, now part of Google Cloud
- Omni - Analytics company mentioned as emerging from RJMetrics diaspora
Technologies & Tools:
- Oculus Rift - VR headset mentioned in escape room startup concept
- MySQL - Database technology used in RJMetrics' early data warehouse
- SQL - Query language automated by RJMetrics for business users
Concepts & Frameworks:
- Order of N-squared SEO Strategy - Content multiplication technique for generating landing pages
- Build-Measure-Learn Cycle - Lean startup methodology for product iteration
- Cohort Analytics - Method for analyzing customer behavior patterns over time
- Customer Lifetime Value (CLV) - Metric for calculating long-term customer worth
🚀 What happened when RJMetrics finally found product-market fit in 2011?
The Explosive Growth Phase
After 3.5 years of grinding to reach $1M ARR, RJMetrics suddenly exploded into hypergrowth when the market shifted to meet their product.
The Breakthrough Moment:
- Market Timing Alignment - Subscription commerce emerged overnight as a business model
- Customer Acquisition Explosion - Landed all the hot internet brands of 2011 in a single year
- Venture Capital Interest - VCs came knocking, enabling rapid funding rounds
Notable Customers Acquired:
- E-commerce Giants: Fab.com (fastest-growing e-commerce company at the time)
- Groupon Wave Companies: All the major Groupon clones during the daily deals boom
- Direct-to-Consumer Brands: Warby Parker, Casper, Bonobos, Paper Post
- Subscription Commerce Leaders: Companies pioneering the subscription model
The Growth Trajectory:
- 2011: Seed round raised
- 2012: Series A completed
- 2013: Series B secured
- Revenue Scale: Went from struggling to reach $1M to explosive growth mode
The key insight: "We didn't cross the chasm, the chasm crossed us" - they stayed consistent while the market evolved to need their solution.
🎯 How did Bob Moore predict the data analytics market before it existed?
Early Market Vision and Positioning
Bob Moore's experience at a venture firm gave him unique insight into how successful businesses would use data, allowing RJMetrics to build for a future market.
The Venture Firm Advantage:
- Front-Row Seat to Innovation - Worked at a firm investing in the most successful e-commerce businesses
- Pattern Recognition - Saw early indicators of how data would fundamentally change business operations
- Market Timing Insight - Understood the gap between current capabilities and future needs
Key Investment Example:
- Fanatics Case Study: Invested when it was "Football Fanatics" - three guys in a Jacksonville strip mall
- Growth Trajectory: Witnessed transformation into a multi-billion dollar sports merchandise powerhouse
- Data Usage Patterns: Observed sophisticated data practices that would become mainstream
The Strategic Vision:
- Mission: Bring investor and smart entrepreneur data thinking to the masses
- Challenge: Market wasn't ready - companies were still figuring out basic sales tracking
- Timeline: Required 2-4 years for market education and readiness
- Execution: Maintained consistent "North Star" direction while market matured
The Patience Factor:
- Age Advantage: Being 23 with "all the time in the world"
- Persistence Strategy: Kept shooting arrows in the same direction
- Market Education: Continuously advocated for advanced analytics approach
⚡ Why did RJMetrics lose product-market fit after crushing it for three years?
The Modern Data Stack Revolution
RJMetrics fell out of product-market fit not due to execution failures, but because the market continued evolving beyond their bundled solution approach.
The Disruption Timeline:
- 2014-2015: Amazon Redshift becomes fastest-growing AWS product
- Cloud Data Warehouse Revolution: Fundamental shift in how companies store and access data
- Market Unbundling: Grand unbundling of previously integrated solutions
The Technical Wedge:
- Infrastructure Change: Companies adopted Amazon Redshift as their central data warehouse
- Data Flow Shift: All analytics data started flowing into centralized cloud warehouses
- Redundancy Problem: RJMetrics' embedded data warehouse became unnecessary duplication
Customer Decision Process:
- Cost Evaluation: "Why buy another redundant data warehouse embedded in a full-stack product?"
- Alternative Solutions: "Why not just buy a BI product and put it on top of our existing warehouse?"
- Preferred Vendors: Tableau and Looker became the go-to solutions
Revenue Impact Pattern:
- Growth Trajectory: 100% → 100% → 50% → 10% growth rates
- Revenue Scale: Still under $10M ARR when the 10% growth hit
- Churn Challenge: Decent new business but renewals were dying
- Customer Evolution: Existing customers needed bigger, more robust solutions
The Bundling vs. Unbundling Reality:
"There's only two ways to make money in software: bundling and unbundling" - Jim Barksdale quote that captured the market shift happening against their bundled approach.
🤔 What three strategic options did RJMetrics consider when they lost product-market fit?
Strategic Decision Framework
After 6-12 months of declining performance, RJMetrics leadership conducted a deep analysis and identified three potential paths forward.
Option 1: Double Down Strategy
- Approach: Raise Series C and continue pushing RJMetrics forward
- Capital Requirements: Significant additional funding needed
- Reality Check: Would be "uphill battle" with "very ugly terms"
- Market Forces: Fighting against clear market trends toward unbundling
- Feasibility: Technically possible but not realistic given market conditions
Option 2: Hard Pivot Strategy
- Approach: Take the best piece of RJMetrics technology and pivot completely
- Technology Focus: Identify newest, best technology that fits the modern market
- Human Cost: Lay off 70-80% of staff
- Financial Challenge: Recalibrate cap table weighed down with liquidation preferences
- Team Impact: Ask remaining team to "sign up for a lot" without intermediate returns
- Assessment: "Probably intellectually the right answer" but "very hard pill to swallow"
Option 3: Strategic Exit
- Approach: Sell the business as-is
- Asset Value: Decent revenue scale, good marquee customers, still growing
- Growth Profile: Growing asset, just not hypergrowth
- Market Position: Reasonable exit opportunity despite challenges
- Stakeholder Consideration: Create some returns rather than risk total loss
The Decision Framework:
- Market Analysis: Deep understanding of the modern data stack revolution
- Technology Assessment: Evaluation of which components had future value
- Financial Reality: Cap table and funding environment constraints
- Team Consideration: Impact on employees and their career trajectories
💎 Summary from [24:03-31:58]
Essential Insights:
- Product-Market Fit Timing - RJMetrics found explosive growth not by changing their product, but by staying consistent while the market evolved to need their solution
- Market Vision Advantage - Early exposure to successful businesses through venture investing provided crucial insight into future data needs before the market was ready
- Continuous Market Evolution - Product-market fit isn't permanent; the modern data stack revolution caused RJMetrics to lose fit after three successful years
Actionable Insights:
- Persistence Strategy: Sometimes the right approach is maintaining direction while waiting for market readiness, especially when you have runway and conviction
- Pattern Recognition: Working closely with successful businesses can provide early signals about future market needs and opportunities
- Strategic Optionality: When losing product-market fit, systematically evaluate all options: double down, pivot, or exit - each has distinct trade-offs and requirements
📚 References from [24:03-31:58]
People Mentioned:
- Chris Merrick - Founding CTO of Fivetran, previously CTO at RJMetrics
- Jim Barksdale - Former Netscape CEO, quoted on bundling vs. unbundling in software
Companies & Products:
- Fivetran - Data integration platform, founded by former RJMetrics CTO
- Fab.com - Fast-growing e-commerce company that was an RJMetrics customer
- Groupon - Daily deals platform that spawned many clones served by RJMetrics
- Warby Parker - Direct-to-consumer eyewear brand, RJMetrics customer
- Casper - Direct-to-consumer mattress company, RJMetrics customer
- Bonobos - Men's clothing brand, RJMetrics customer
- Fanatics - Sports merchandise company, originally Football Fanatics
- Amazon Redshift - Cloud data warehouse that disrupted RJMetrics' model
- Tableau - Business intelligence platform that competed with RJMetrics
- Looker - Business intelligence platform acquired by Google
Technologies & Tools:
- AWS (Amazon Web Services) - Cloud platform where Redshift became the fastest-growing product
- Modern Data Stack - Architecture approach that unbundled integrated analytics solutions
Concepts & Frameworks:
- Product-Market Fit Evolution - The concept that market fit can be gained and lost as markets continue evolving
- Bundling vs. Unbundling - Jim Barksdale's framework for software business models and market cycles
- Subscription Commerce - Business model that emerged and created demand for RJMetrics' analytics
🔄 How did RJMetrics execute a strategic pivot while preserving team jobs?
Strategic Multi-Path Approach
When facing declining growth from 100% to 10% and mounting churn problems, RJMetrics executed a sophisticated three-pronged strategy to gather data on potential exit paths:
The Three Simultaneous Paths:
- Product Pivot Development - Built RJMetrics Pipeline as a standalone data integration tool, carving out the data pipeline component from their existing platform
- Fundraising Attempts - Pitched Series C to Silicon Valley investors (unsuccessful due to declining metrics)
- Strategic Acquisition Discussions - Cultivated relationships with larger partner companies for potential acquisition
The Magento Acquisition Strategy:
- Initial Negotiation: First round fell apart due to valuation gaps that wouldn't return investor capital
- Renegotiation: Both parties became more reasonable on valuation after initial FOMO
- Creative Deal Structure: Negotiated to retain IP rights for RJMetrics Pipeline while selling the core business
Outcome Preservation:
- Team Protection: 70-80% of employees who would have been laid off in a pivot were acquired by Magento
- Economic Success: Generated investor returns and funded the next venture
- Strategic Continuity: Used acquisition proceeds to bankroll Stitch without raising additional capital
🚀 How did Stitch achieve in 19 months what RJMetrics took 8 years to build?
The Perfect Market Pivot
Stitch leveraged a fundamental shift in the data infrastructure landscape, transforming former competitors into strategic partners and lost deals into new opportunities.
Rapid Growth Mechanics:
- Revenue Acceleration: Reached nearly the same revenue as RJMetrics in 19 months vs. 8 years
- Market Timing: Capitalized on the modern data stack revolution with cloud-based data warehouses
- Competitive Advantage: Became essential middleware for companies using Looker, Redshift, and other analytics tools
The Competitive Inversion:
From Competitor to Partner:
- Looker Transformation: Former biggest competitor became biggest referral source
- Sales Rep Incentives: Looker sales reps needed Stitch to close deals by providing complete data for demos
- Ecosystem Value: Made competitor installations more valuable by enabling comprehensive data access
Customer Acquisition Strategy:
- Pipeline Conversion: Lost RJMetrics prospects became Stitch opportunities
- Problem-Solution Fit: Addressed the gap between analytics tools and data sources
- Engineering Relief: Eliminated need for custom scripts to move data from APIs to warehouses
Strategic Positioning:
- Middleware Excellence: Positioned as essential glue between data sources and analytics platforms
- Partnership Model: Enhanced rather than competed with existing data stack investments
- Market Validation: "If you can't beat them, join them" philosophy proved highly successful
🎯 What is the key to maintaining product-market fit as markets evolve?
The Critical Role of Intellectual Honesty
The most essential skill for founders navigating market changes is developing intellectual honesty—the ability to distinguish between noise and signal in business problems.
Core Framework for Market Awareness:
Signal vs. Noise Analysis:
- Persistent Problems: Distinguish between ongoing structural issues and market-driven changes
- Data Interpretation: Avoid contorting analytics to support preferred narratives
- Honest Assessment: Acknowledge when fundamental market shifts require strategic pivots
Warning Signs Recognition:
Multiple Simultaneous Breakdowns:
- Growth Deceleration: Rapid decline from strong growth rates
- Churn Deterioration: Existing retention problems becoming amplified
- Sales Efficiency Collapse: Previously profitable channels becoming uneconomical
The RJMetrics Case Study:
- Historical Blind Spots: Always had churn issues but rationalized them as "structural churn"
- Market Shift Impact: Modern data stack emergence made existing problems critical
- Analytical Trap: Being too data-driven led to narrative manipulation rather than honest assessment
Actionable Insights for Founders:
- Regular Honest Audits: Systematically evaluate which problems are getting worse vs. staying constant
- External Perspective: Seek input from advisors who aren't emotionally invested in current strategy
- Scenario Planning: Prepare multiple strategic options before problems become critical
- Market Monitoring: Track competitive landscape and technology shifts that could impact positioning
💎 Summary from [32:05-39:56]
Essential Insights:
- Multi-Path Strategy Execution - RJMetrics simultaneously pursued product pivot, fundraising, and acquisition to maximize optionality during crisis
- Creative Deal Structuring - Retained valuable IP (Pipeline) while selling core business, preserving team jobs and funding next venture
- Market Timing Mastery - Stitch achieved 19-month success by positioning as essential middleware in the modern data stack revolution
Actionable Insights:
- Execute parallel strategic paths when facing declining metrics rather than betting on single approach
- Structure acquisitions creatively to retain valuable assets while achieving economic outcomes for all stakeholders
- Develop intellectual honesty to distinguish between persistent structural problems and market-driven changes requiring pivots
📚 References from [32:05-39:56]
People Mentioned:
- Jake - Co-founder who participated in Series C fundraising attempts alongside Bob Moore
Companies & Products:
- Magento - E-commerce platform that acquired RJMetrics, later acquired by Adobe for $1.6 billion
- eBay - Former parent company of Magento before it spun out as independent private equity-backed company
- Adobe - Acquired Magento for $1.6 billion, incorporating RJMetrics into Adobe Commerce Cloud
- Looker - Business intelligence platform that transformed from RJMetrics competitor to Stitch's biggest referral source
- Redshift - Amazon's cloud data warehouse service frequently used with Stitch data pipeline
- Talend - Company that acquired Stitch after 19 months of operation
- MailChimp - Email marketing platform mentioned as example data source requiring integration
Technologies & Tools:
- RJMetrics Pipeline - Data integration product carved out from RJMetrics core platform, later became Stitch
- Stitch - Data pipeline company spun out from RJMetrics acquisition, focused on moving data from SaaS tools to warehouses
- APIs - Application Programming Interfaces used for automated data extraction from various SaaS platforms
Concepts & Frameworks:
- Modern Data Stack - Technology revolution in mid-2010s featuring cloud-based data warehouses and analytics tools
- Structural Churn - Customer attrition attributed to external factors like business closures and acquisitions rather than product issues
- Intellectual Honesty - Critical founder skill for distinguishing between noise and signal in business problems
🧠 What happens when founders dismiss market feedback as customer stupidity?
Intellectual Honesty in Product Development
The Pattern Recognition Problem:
- Customer Churn Rationalization - When customers left for Looker or moved analytics to engineering teams, the initial reaction was dismissing them as "dumb" rather than recognizing market shifts
- Competitive Blindness - Dismissing Amazon Redshift as non-competitive despite a TechCrunch reporter's persistent questions about the threat
- The Mirror Test - If everyone around you seems to be getting "dumber," you might be the one missing critical market signals
Key Warning Signs:
- Increased Dismissiveness: When your rate of dismissing people who "don't know as well" goes up
- Pattern Denial: Refusing to acknowledge repeated customer behavior patterns
- Expert Arrogance: Assuming deep industry knowledge makes you immune to blind spots
The Intellectual Honesty Check:
- Question your own assumptions when facing consistent pushback
- Look for patterns in customer departures rather than individual explanations
- Consider that persistent questions from outsiders might reveal important blind spots
- Balance conviction with openness to contradictory evidence
⚖️ How do entrepreneurs balance conviction with intellectual honesty?
The Entrepreneur's Dilemma
The Conviction Paradox:
- Suspending Disbelief: Entrepreneurship requires believing in a future state others can't see yet
- Pre-Product Market Fit: Many people won't "get it" until they actually experience the value
- The Flip Side: The same dismissiveness that helps push through early skepticism can blind you to real market changes
Finding the Right Balance:
- First Principles Conviction - Seek ideas where you have deep, foundational belief that can cut through "anomalous noise"
- Conscious Market Awareness - Unlike subconscious pattern recognition, deliberately study where markets are heading
- North Star Clarity - Having a clear vision helps distinguish between temporary noise and fundamental shifts
The Risk-Reward Trade-off:
- High Conviction Risk: If your North Star is wrong, you'll stick with a failing direction
- Low Conviction Risk: Without strong conviction, your company becomes "designed by committee" and caps upside potential
- The Sweet Spot: Strong conviction based on first principles analysis rather than just gut feeling
🏗️ How did Bob Moore bootstrap Crossbeam's initial development?
The Repeat Founder's Prototype Strategy
Self-Funding Approach:
- Personal Investment - Wrote a check into a bank account, created C Corp, and issued a SAFE note to himself
- Strategic Hiring - Brought in Buck Ryan from The Buck Codes Here, a former RJMetrics/Magento colleague who had started his own development shop
- Technical Validation - Focused on understanding the materiality of technical challenges and creating defensible technology
The Six-Week Sprint:
- Prototype Development: Built the most barebones version to test core concepts
- Technical Feasibility: Chose something hard enough to create a defensibility moat in the technology itself
- Rapid Execution: Leveraged existing relationships for quick, quality development
Immediate Next Steps:
- Customer Discovery: Started meeting with target personas (RevOps people initially)
- Geographic Strategy: Used Philadelphia's smaller startup ecosystem to meet with every company large enough to have RevOps functions
- Network Leverage: Expanded to New York using existing founder relationships from previous portfolio connections
🔄 What did Bob Moore learn from RevOps conversations about data flow?
Understanding the Technical Implementation Details
The RevOps Deep Dive:
- Data Structure Mechanics: How data is organized and what structural elements matter most to operations teams
- Full Cycle Data Flow: Understanding how data leaves CRM, gets enhanced or enriched, then needs to land back in CRM
- Value Enhancement Process: What happens to data between extraction and re-insertion that makes it more valuable
Technical Implementation Focus:
- API Access Requirements - Understanding integration capabilities and limitations
- Object Architecture - Mapping which data requires custom objects versus custom fields
- Implementation Minutia - Getting into the detailed mechanics that would determine product feasibility
Strategic Purpose:
- Product Validation: Ensuring the solution would actually work within existing tech stacks
- Technical Defensibility: Building something complex enough to create competitive moats
- Customer-Led Discovery: Using actual user workflows to guide product development rather than assumptions
💎 Summary from [40:02-47:56]
Essential Insights:
- Intellectual Honesty Check - When dismissiveness toward others increases, it's time to examine whether you're missing market signals rather than others being "dumb"
- Conviction vs. Flexibility Balance - Entrepreneurs need strong first-principles conviction to cut through noise, but must remain open to genuine market feedback
- Repeat Founder Advantages - Experience enables faster prototype development, better network leverage, and more strategic approach to early validation
Actionable Insights:
- Look for patterns in customer behavior rather than dismissing individual cases as outliers
- Build conviction based on first principles analysis, not just gut feeling or market consensus
- Use geographic and network advantages systematically for customer discovery
- Focus early technical development on creating defensible complexity while validating core assumptions
📚 References from [40:02-47:56]
People Mentioned:
- Jake - Bob's business partner/colleague at RJMetrics who he discussed the TechCrunch reporter situation with
- Buck Ryan - Former RJMetrics/Magento colleague who started The Buck Codes Here development shop and built Crossbeam's initial prototype
Companies & Products:
- Looker - Analytics platform that some RJMetrics customers churned to, indicating market shift toward engineering-controlled analytics
- Amazon Redshift - Data warehouse product that Bob initially dismissed as non-competitive but may have represented a significant market threat
- TechCrunch - Technology publication whose reporter persistently questioned Bob about Redshift competition
- The Buck Codes Here - Buck Ryan's development shop that built Crossbeam's initial prototype
- Magento - E-commerce platform where Bob and Buck previously worked together
Technologies & Tools:
- MySQL - Database technology that was part of RJMetrics' tech stack
- CRM Systems - Customer relationship management platforms central to the data flow discussions with RevOps teams
- API Access - Application programming interfaces crucial for data integration capabilities
Concepts & Frameworks:
- RevOps (Revenue Operations) - Business function focused on optimizing revenue processes across sales, marketing, and customer success
- Product-Market Fit - The degree to which a product satisfies strong market demand
- First Principles Thinking - Reasoning from fundamental truths rather than by analogy or assumption
🚀 How did Bob Moore build Crossbeam's first customer network?
Building the Initial Network Through Personal Connections
The Foundation Strategy:
- Leveraged existing relationships - Started with Stitch (his previous company) as the first customer
- Strategic partner selection - Brought on Looker as Stitch's biggest partner for the second spot
- Manual onboarding process - No website or automated systems, everything done personally
Early Customer Acquisition:
- Guru - Knowledge management software company led by Rick Nucci in Philadelphia
- Gainsight - Connected through Nick Meta from RJ Metrics days
- Sendoso - Gifting platform from the sales enablement universe
- Goal: Get each company to invite as many partners as possible onto the platform
The Viral Growth Pattern:
- Initial wave: Manually onboarded 5 companies
- First expansion: Those 5 companies led to 15 total
- Viral acceleration: 10 of those 15 invited 3 more each, reaching 30 companies
- Natural virality: This growth happened before any product optimization for viral loops
Why Personal Relationships Worked:
- Companies needed to evaluate security, RevOps, and technical feasibility
- Partnership teams consistently became the internal owners
- Early adopters were willing to experiment because of existing trust
💡 Why is social capital the ultimate product-market fit test for network businesses?
The Critical Difference from Traditional SaaS
Network Effects vs. Traditional SaaS:
- Traditional SaaS: Users operate in isolated silos, even in multi-tenant systems
- Network businesses: Users must expend social capital with other people to participate
- Higher stakes: Not just personal time and energy, but reputation with important business relationships
The Social Capital Test:
- Low-stakes favor: Friend pays $50/month to avoid awkward conversation
- High-stakes commitment: Asking important partners to use a new tool together
- Real validation: When someone risks their relationship with key business partners
Why This Test is More Reliable:
- Flipped cost-benefit ratio: Cost of awkward conversation now includes burning social capital
- Material business impact: Partners drive significant sales pipeline and customer retention
- Authentic validation: Beyond one degree of separation, virality has nothing to do with personal relationships
The Bluff-Calling Moment:
When Bob asked Rick Nucci to invite Zendesk (a publicly traded partner), it became a "show your cards" moment - Rick wouldn't risk a valuable business relationship just to be nice.
⚡ When did Bob Moore commit fully to building Crossbeam?
The Point of No Return Decision
High Conviction Timeline:
- July 2018: Raised $3.5M seed round before Stitch and Looker had even signed up
- Early validation: Had initial founder conversations and RevOps discussions
- Product development: Building the version that would actually work for enterprise needs
The Funding Round:
- Lead investors: First Round Capital and Uncork Capital co-led
- Supporting investors: Handful of investors from previous companies
- Strategic timing: Could have bootstrapped until end of year, but chose aggressive growth path
Why Full Commitment Made Sense:
- Three-year validation: Idea had been in Evernote file since 2015
- Pattern recognition: Experience from previous companies provided validation framework
- Market timing: Saw clear opportunity in the partnership space
- Capital intensity: Network effects businesses require significant upfront investment to solve cold start problem
Different Approach from RJ Metrics:
- Not lean startup: Didn't want to do classic "build, measure, learn" playbook
- Intentionally hard: Chose something difficult to get started (network effects)
- Venture-backed from start: Knew rapid scaling would be capital intensive
🎯 What was the minimum viable product for Crossbeam?
Discovering the Account Mapping Process
The Existing Manual Process:
- Industry standard: Companies already did "account mapping" before Crossbeam existed
- Email spreadsheets: Partners sent Excel files back and forth
- Participants: Partner teams, sales reps, and partner managers
- Content: Lists of customers, prospects, and open opportunities
The "Battleship" Strategy:
- Selective sharing: Instead of sharing all 500 opportunities, pick 17 strategic ones
- Market targeting: Choose accounts in the same market segment
- Protective approach: Don't give away "the Glengarry leads" (premium prospects)
- Strategic collaboration: Work with partners without revealing entire pipeline
Key Insight:
Companies were already solving this problem manually through spreadsheet exchanges - Crossbeam just needed to digitize and streamline this existing workflow rather than create something entirely new.
The Learning:
Bob realized people were already doing cross-referencing of customer and prospect lists, but it was inefficient and limited. The MVP just needed to make this existing process better, not invent a completely new behavior.
💎 Summary from [48:02-55:55]
Essential Insights:
- Network effects validation - Social capital expenditure is a more reliable product-market fit test than traditional metrics for network businesses
- Strategic bootstrapping - Leveraging existing relationships and companies can create authentic viral growth patterns before product optimization
- Commitment timing - High conviction can develop quickly when pattern recognition meets market opportunity, justifying aggressive funding and growth strategies
Actionable Insights:
- Use personal relationships strategically to build initial network density, but rely on product value for sustained growth
- Test network effects by asking early users to invite important business partners, not just casual connections
- Identify existing manual processes in your target market - the MVP might just be digitizing current workflows rather than creating new behaviors
📚 References from [48:02-55:55]
People Mentioned:
- Rick Nucci - CEO of Guru, early Crossbeam adopter and Philadelphia entrepreneur who provided generous time and suggestions
- Nick Meta - Connection from RJ Metrics days who helped get Gainsight onboard early
Companies & Products:
- Stitch - Bob's previous company, became the first company on Crossbeam platform
- Looker - Business intelligence platform, second company on Crossbeam as Stitch's biggest partner
- Guru - Knowledge management software company, early Crossbeam adopter
- Gainsight - Customer success platform that joined Crossbeam early
- Sendoso - Gifting and sending platform from sales enablement universe
- Zendesk - Customer service platform mentioned as Rick Nucci's publicly traded partner
Concepts & Frameworks:
- Account Mapping - Traditional manual process of cross-referencing customer/prospect lists between partner companies via spreadsheet exchanges
- Social Capital Test - Using willingness to risk important business relationships as validation for network effect products
- Atomic Networks - Building initial small networks of connected companies to create viral growth patterns
- Cold Start Problem - Challenge of getting initial users for network effects businesses before value becomes apparent
🔄 How did Crossbeam replace manual partner data sharing processes?
From Spreadsheets to Automated Data Sharing
The traditional partner data sharing process was fundamentally broken and inefficient:
The Old Manual Process Problems:
- Overwhelming incompleteness - Data was always extremely stale and impossible to act on
- Rare occurrence - Happened so infrequently that real-time changes couldn't be tracked
- Security nightmares - Huge compliance issues with sharing sensitive data
- Spreadsheet dependency - Even multi-billion dollar companies relied on Excel vlookup functions
Crossbeam's Initial Solution:
- Simple spreadsheet interface where both partners could connect data
- Two connection methods: Salesforce connector and CSV upload only
- Population segments: Prospects, opportunities, and customers as standard groupings
- Universal data mapping with Crossbeam sitting in the middle as intermediary
The Account Mapping Matrix:
- 3x3 grid system: Prospects/opportunities/customers on both axes
- Overlap counts only: Shows how many prospects are your partner's customers, etc.
- Privacy protection: Each side keeps non-overlapping data completely private
- Clickable insights: Click any box to see the actual overlapping records
At its core, it was essentially a collaborative spreadsheet where you could only see the rows that overlapped.
🚀 What made some Crossbeam customers explosive while others failed?
The Network Effect Success Pattern
Customer outcomes fell into two stark categories with a clear differentiator:
Dead on Arrival Customers:
- Random website visitors from funding announcements or organic discovery
- No existing connections - like joining LinkedIn when none of your contacts are there
- Single player mode problem - No value without network participation
- Unwilling to recruit - Lacked context or investment to bring partners onboard
Explosively Growing Customers:
- Invitation-based onboarding - Joined because a partner invited them
- Immediate value proposition - Email said "Company X wants to share data with you right now"
- Guided onboarding journey - Clear steps toward first data connection
- Viral expansion - Saw value and immediately invited other partners
The Invitation Advantage:
- Compelling entry point: "You're one step away from getting that data"
- Clear progression: Connect Salesforce → Define populations → Access data
- Instant gratification: Real value delivered immediately upon connection
- Natural expansion: Success led to inviting more partners organically
Strategic Pivot Required:
- Traditional marketing failed: Content marketing, ads, and outbound didn't work
- Fresh signups struggled: No connections meant no value realization
- Network effects essential: Success required existing users inviting new ones
- Viral mechanics focus: Product development centered on incentivizing invitations
Seven out of every 10 companies signed up because they were invited by someone already on the platform.
🤝 What is Crossbeam's "joint jam session" sales strategy?
Revolutionary Three-Way Demo Approach
Crossbeam pioneered a unique sales methodology that eliminated single-player mode entirely:
The Joint Jam Requirements:
- No solo demos: Refused to do product demonstrations with just one company
- Partner prerequisite: Required prospects to bring their biggest partner to calls
- Three-way setup: Crossbeam + Company A + Company B on every demo
- Live data connection: Got both companies signed up and connected during the call
The Process Flow:
- Initial contact: Prospect requests demo from website or referral
- Partner requirement: "Please bring your biggest partner to the demo"
- Live onboarding: Both companies connect data sources during call
- Immediate value: Bypass single-player mode to show real overlaps
- Atomic state achievement: Reach first valuable data sharing moment together
Why It Worked:
- Eliminated cold starts - No empty network experience for either party
- Instant value demonstration - Real data overlaps shown immediately
- Natural viral seeding - Created connected clusters from day one
- Reduced friction - Both parties committed simultaneously
Early-Stage Advantage:
- Simpler approvals: Seed and Series A companies had fewer bureaucratic hurdles
- Direct decision makers: Partnership managers could authorize Salesforce connections
- CSV fallback option: Could export and upload data if CRM connection wasn't immediate
- Pre-compliance era: GDPR and CCPA requirements were less stringent initially
This approach was essential because traditional B2B marketing tactics completely failed for a network-dependent product.
📈 How did Crossbeam achieve explosive network growth from 4 to 20,000 companies?
Viral Network Expansion Metrics
Crossbeam's growth trajectory demonstrated the power of network effects in B2B software:
Growth Timeline:
- September 2018: First customers onboarded
- End of 2018: 4 registered companies
- End of 2019: 300 companies (75x growth)
- End of 2020: 1,800 companies (6x growth)
- End of 2021: 5,800 companies (3.2x growth)
- End of 2022: 12,000 companies (2.1x growth)
- End of 2023: Over 20,000 companies (1.7x growth)
The Viral Coefficient:
- 70% invitation-driven: Seven out of every 10 companies joined via partner invitation
- Network effect rarity: Extremely uncommon for B2B software to achieve true network effects
- Compound growth: Each successful customer became a source of multiple new customers
Strategic Implications:
- Unique B2B model: Network effects are very rare in business software
- Durability question: Having every potential customer on platform vs. capturing economic value
- Pricing challenge: Huge network with low willingness to pay isn't valuable
- Long-term investment: Required venture capital for extended runway during growth phase
The Network Effect Paradox:
You need everyone on the platform for maximum value, but you also need to capture economic value to prove business viability. This created a fundamental tension around pricing strategy.
💰 Why was pricing a major challenge for Crossbeam's network model?
The Network Effect Pricing Dilemma
Pricing became a persistent challenge that haunted the business for years:
The Core Tension:
- Network value requires scale - Platform becomes more valuable with every participant
- Economic value capture needed - Must prove business viability through revenue
- Social capital spending - Users already investing effort to recruit partners
- Payment barrier risk - Charging everyone could kill network growth
The Albatross Effect:
- Four to five year struggle - Pricing remained a major obstacle throughout early growth
- Capital intensive necessity - Required venture funding specifically for long-term pricing flexibility
- Strategic patience required - Needed extended runway to solve the monetization puzzle
The Fundamental Question:
If you have a huge network but nobody's willing to pay anything, that's not really worth very much. But if everyone has to pay to participate, you might never build the network in the first place.
This pricing challenge exemplified why Crossbeam needed significant venture capital early - to maintain a long-term view while solving the network effect monetization problem.
💎 Summary from [56:01-1:03:56]
Essential Insights:
- Network effects transformation - Crossbeam replaced manual spreadsheet processes with automated data sharing, but success required invitation-based onboarding rather than traditional marketing
- Joint jam innovation - Three-way demos with prospect + partner eliminated single-player mode and created immediate value demonstration
- Viral growth achievement - Scaled from 4 to 20,000 companies with 70% invitation-driven signups, proving rare B2B network effects
Actionable Insights:
- Traditional B2B marketing fails for network-dependent products - focus on viral mechanics instead
- Invitation-based onboarding creates dramatically different user experiences than cold signups
- Network effect businesses require patient capital due to inherent pricing challenges between scale and monetization
📚 References from [56:01-1:03:56]
People Mentioned:
- Bob Moore - Crossbeam CEO discussing the company's network effect strategy and growth challenges
Companies & Products:
- Crossbeam - Partner data sharing platform that replaced manual spreadsheet processes
- RJMetrics - Bob's previous company (now part of Adobe Commerce Cloud) where traditional marketing worked
- Stitch Data - Another previous company where conventional growth tactics were effective
- Looker - Early large customer that was an anomaly in Crossbeam's typical customer base
- Salesforce - CRM platform used for data connections in Crossbeam's system
- LinkedIn - Social network used as analogy for network effect challenges
- Snowflake - Example of large enterprise company mentioned in contrast to early-stage customers
- Adobe - Large enterprise company mentioned alongside Snowflake
- Gain Sight - Customer success platform mentioned as early big customer through personal relationships
Technologies & Tools:
- Excel - Spreadsheet software with vlookup functions that Crossbeam aimed to replace
- CSV uploads - File format used as backup data connection method when CRM integration wasn't available
Concepts & Frameworks:
- Network Effects - Rare phenomenon in B2B software where platform value increases with each additional user
- Single Player Mode - Product state where user gets no value without other participants
- Joint Jam Session - Crossbeam's three-way demo methodology with prospect and their partner
- Account Mapping Matrix - 3x3 grid showing data overlaps between partner companies
- Viral Coefficient - 70% of signups came through partner invitations rather than direct marketing
- GDPR/CCPA - Data privacy regulations that became more prominent during Crossbeam's growth
🚀 How did Crossbeam build network effects without charging customers for 2.5 years?
Free-First Network Strategy
Crossbeam adopted an unconventional approach by treating their platform like open-source software rather than traditional SaaS, prioritizing network growth over immediate revenue.
Strategic Philosophy:
- LinkedIn for Data Model - Built ubiquity first to create extreme value through network effects
- Open Source Mentality - Focused on getting passionate contributors who would invest their own time and energy
- Community Development Investment - Large upfront investment period with minimal revenue focus
Revenue Approach During Growth Phase:
- Custom Negotiations - Every dollar was individually negotiated, not standardized pricing
- Design Partner Model - Charged $10K-20K to strategic partners for feature development collaboration
- No Traditional ARR - Openly stated "we don't have ARR, we just have R" in investor presentations
- Non-Recurring Revenue - Payments weren't guaranteed to be annual or recurring
Network Growth Results:
- 30,000 Contributors - Built massive network graph similar to open-source projects
- GitHub Stars Equivalent - Created passionate user base willing to contribute to product development
- Enterprise Readiness - Achieved ubiquity needed for material enterprise applications and PLG paths
Business Model Evolution:
The strategy mapped out a funding approach that mirrored open-source companies: significant community development investment upfront, followed by enterprise monetization once network effects reached critical mass.
🤝 Why did Crossbeam merge with competitor Reveal instead of competing?
Customer-Driven Market Consolidation
The merger between Crossbeam and Reveal was driven by customer frustration with a fragmented network that compromised the value proposition for both platforms.
The Competitive Landscape:
- Parallel Development - Both companies started within 6 months of each other with identical core missions
- Same Vision - Building connected company graphs for modern account mapping and ecosystem-led growth
- Geographic Split - Crossbeam strong in US/analytics vertical, Reveal strong in Europe/HR vertical
- Similar Funding - Crossbeam raised $100M from a16z, Reveal raised $50M from Insight Partners
The LinkedIn Analogy Problem:
Customers experienced a broken user experience similar to having two separate LinkedIn networks:
- Split Networks - Professional contacts divided between two platforms
- Compromised Value - Customers couldn't access their full network of potential partners
- Integration Confusion - RevOps teams reluctant to integrate two incompatible systems
- Investment Hesitation - Why buy Salesforce integration if only half your target companies are accessible?
Customer Pressure Points:
- Feature Requests - #1 requested feature across Crossbeam was Reveal integration
- Public Demand - LinkedIn threads and webinar chats constantly asking for merger
- Table Pounding - Customers actively demanding consolidation for better experience
- Market Dysfunction - Unlike typical competing software, network effects made fragmentation particularly painful
The Decision Framework:
Both founders realized neither company could achieve true potential with split networks, leading to an ego-aside, customer-first merger decision.
🌍 What made the Crossbeam-Reveal founder relationship work despite being competitors?
Authentic Connection Between Parallel Entrepreneurs
The successful merger was built on a foundation of genuine personal compatibility and shared values between the competing founders.
The Miami Meeting:
- Chance Encounter - Met at partnership leaders event 1.5 years before the deal
- Personal Connection - 15-minute conversation about being repeat founders with young kids
- Immediate Compatibility - Discovered they were essentially the same person in different markets
Shared Founder Profile:
- Geographic Mirrors - Simon as "French version" of Bob, Bob as "Philadelphia version" of Simon
- Family Situations - Both repeat founders with young children of similar ages
- Intellectual Honesty - Both obsessed with problem-solving rather than glamour or spoils
- Brain Stimulation - Motivated by interesting problem spaces rather than just financial outcomes
Values Alignment:
- Fundamental Compatibility - Shared core values that typically create CEO personality mismatches
- Professional Respect - Maintained "giant air gap" while building foundation for future dialogue
- Problem-First Approach - Both prioritized solving customer problems over competitive positioning
Strategic Foundation:
The personal relationship created the trust necessary to have difficult conversations about market consolidation, ultimately enabling both founders to "put egos aside and do what's right for the customer."
💎 Summary from [1:04:03-1:11:56]
Essential Insights:
- Network-First Strategy - Crossbeam treated their platform like open-source software, prioritizing ubiquity over immediate revenue for 2.5 years to build network effects
- Customer-Driven Consolidation - The Crossbeam-Reveal merger was driven by customer frustration with fragmented networks that compromised value propositions
- Founder Compatibility - Personal values alignment and authentic connection between competing founders enabled successful merger discussions
Actionable Insights:
- Consider open-source growth models for network effect businesses where ubiquity creates exponential value
- Listen to customer pain points about fragmented experiences, even when they challenge your competitive strategy
- Build genuine relationships with industry peers based on shared values rather than just competitive positioning
- Recognize when market dynamics (like network effects) make consolidation more valuable than competition
📚 References from [1:04:03-1:11:56]
People Mentioned:
- Simon Bouchez - Multi-time founder based in Paris, co-founder of Reveal (formerly ShareWork), previously sold company to SAP in HR Tech space
Companies & Products:
- Crossbeam - "LinkedIn for data" platform for partner ecosystem mapping and co-selling
- Reveal - European competitor to Crossbeam (formerly ShareWork), focused on partner ecosystem mapping
- Andreessen Horowitz - Lead investor in Crossbeam's $100M funding round during zero interest rate era
- Insight Partners - Lead investor in Reveal's $50M funding round, also Bob Moore's former employer
- SAP - Acquired Simon Bouchez's previous HR Tech company
- LinkedIn - Used as analogy for network effects and fragmented user experience problems
- Salesforce - Referenced for CRM integration challenges with split networks
Technologies & Tools:
- GitHub - Referenced as analogy for open-source contribution model and community building
- LinkedIn Sales Navigator - Used in analogy about choosing between fragmented network platforms
- LinkedIn Recruiter - Part of the fragmented platform choice analogy
Concepts & Frameworks:
- Network Effects - Core dynamic driving both companies' value propositions and merger rationale
- Ecosystem-Led Growth - Strategic approach both companies were enabling for their customers
- Open Source Software Model - Growth philosophy Crossbeam adopted instead of traditional SaaS metrics
- Zero Interest Rate Phenomenon (ZIRP) - Economic era that enabled both companies to raise significant capital pre-revenue
- Account Mapping - Traditional partner team function both platforms aimed to modernize
- Co-selling and Cross-selling Motions - Partner activities enabled by the connected company graphs
🤝 Why did Crossbeam CEO Bob Moore merge with French competitor Reveal?
Strategic Partnership Decision
Bob Moore and his team at Crossbeam faced a unique competitive situation with Reveal, a French company in the same space. Rather than continuing to compete destructively, they made the strategic decision to merge.
The Competitive Reality:
- Both companies had raised substantial capital, making neither likely to disappear
- Years of head-to-head competition weren't producing a clear winner
- The market dynamic was poor with two strong players splitting the opportunity
- Both teams realized they were potentially destroying each other through coexistence
The Merger Logic:
- Shared Vision Over Ego - Both founders prioritized building something bigger rather than having their name on top
- Network Effects - This particular business required network graph effects that benefited from consolidation
- Competitive Positioning - As smaller venture-backed companies, they needed to compete against big tech for budget
- Financial Strength - Both had 5+ years of runway, allowing for an equity-only deal with no cash exchange
Strategic Advantages:
- Extended Runway: Combined resources for long-term operation on a big problem
- Market Position: Better positioned to tackle revenue orchestration, data enrichment, and partnership technology tools
- Unified Approach: One cohesive platform to serve customers effectively
The deal was structured as an all-equity transaction, bringing both teams under one roof to create a stronger competitive position in the partnership technology space.
🇫🇷 What surprised Crossbeam CEO about working with the French Reveal team?
Cultural Expectations vs. Reality
Bob Moore shares his honest perspective on the cultural assumptions Americans often have about French business culture and how the reality completely contradicted those stereotypes.
American Stereotypes About French Business:
- Expectation of employees smoking cigarettes and taking long breaks
- Assumptions about month-long August vacations
- Concerns about difficulty in workforce management
- General skepticism about work ethic and productivity
The Surprising Reality:
Exceptional Work Ethic: The Reveal team demonstrated incredible dedication and smart work practices that matched or exceeded any team Bob had worked with in his previous companies.
High-Quality Talent: The French team built an incredible company and consistently performed at the highest levels, going "toe-to-toe" with top American talent.
Paris Startup Ecosystem Insights:
- Growing Energy: Paris has incredible startup ecosystem momentum
- Technical Talent: Large population of knowledge workers and technical professionals
- AI Leadership: France has a particularly strong AI ecosystem with significant investment activity
- Investment Interest: First Mark investor Matt Turk was involved with multiple French AI companies
Business Impact:
Bob now feels lucky to work with the French team and plans to continue investing in growing their Paris office. The cultural due diligence was impossible to conduct beforehand, requiring a leap of faith that paid off significantly.
🧠 Who had the biggest impact on Crossbeam CEO Bob Moore's thinking?
Jake Stein's Intellectual Honesty Lesson
Bob Moore credits his co-founder Jake Stein from RJ Metrics and Stitch Data as having the most significant impact on his approach to business and decision-making.
Jake Stein Background:
- Co-founder: RJ Metrics and Stitch Data with Bob Moore
- Current Role: CEO of Common Paper, treating legal documents like APIs
- Partnership Duration: Worked together for a decade despite being very different on almost every dimension
The Transformative Moment:
The Business Book Story: In the early days of RJ Metrics, Bob came into the office excited about a startup book he'd read over the weekend, full of Post-it notes and ideas to implement.
Jake's Critical Question: Instead of getting excited about the ideas, Jake asked: "What in that book did you not agree with?"
The Learning Impact:
- Intellectual Honesty - Learning to hold two conflicting thoughts simultaneously
- Critical Thinking - Not treating all advice as gospel just because it's published
- Contextual Application - Understanding that good advice for one situation may not apply to their specific business
- Balanced Perspective - Moving beyond blind optimism or pessimism
Evolution of Their Partnership:
- Initial Dynamic: Bob was the "yes man," Jake was the "no man" (the "Charlie Munger to Warren Buffett")
- Convergence: Over the decade, both learned to balance optimism with critical thinking
- Outcome: Both became capable of holding conflicting thoughts and making more nuanced decisions
This intellectual honesty framework became critical for Bob's ability to navigate the complexities of building multiple companies without "losing his mind."
💎 Summary from [1:12:02-1:18:24]
Essential Insights:
- Strategic Mergers Over Competition - Sometimes combining forces with a competitor creates more value than destructive competition, especially when both companies have strong funding and market position
- Cultural Assumptions vs. Reality - Stereotypes about international business cultures can be completely wrong; the French Reveal team exceeded all expectations with exceptional work ethic and talent
- Intellectual Honesty Framework - The ability to hold conflicting thoughts simultaneously and critically evaluate advice is crucial for effective leadership and decision-making
Actionable Insights:
- Consider merger opportunities when competition is destroying value for both parties and customers would benefit from consolidation
- Challenge cultural assumptions when evaluating international partnerships or acquisitions
- Develop critical thinking skills by actively questioning popular business advice and asking what you disagree with
- Build partnerships with people who complement your thinking style and challenge your assumptions
- Invest time in understanding international talent markets, particularly emerging tech hubs like Paris
📚 References from [1:12:02-1:18:24]
People Mentioned:
- Jake Stein - Co-founder of RJ Metrics and Stitch Data with Bob Moore, now CEO of Common Paper, had transformative impact on Bob's critical thinking approach
- Matt Turk - Investor from First Mark who was on boards of multiple French AI companies, highlighting France's strong AI ecosystem
Companies & Products:
- Common Paper - Jake Stein's current company treating legal documents like APIs and building next-generation technology for efficient legal agreements
- Reveal - French competitor that merged with Crossbeam in an all-equity deal
- First Mark - Investment firm with significant involvement in French AI companies
- RJ Metrics - Bob Moore and Jake Stein's first company together (now part of Adobe Commerce Cloud)
- Stitch Data - Second company co-founded by Bob Moore and Jake Stein (acquired by Talend)
Technologies & Tools:
- Revenue Orchestration Tools - Category of business software that Crossbeam competes against for budget
- Data Enrichment Tools - Technology solutions for enhancing business data quality and completeness
- Partnership Technology Tools - Software platforms designed to manage and optimize business partnerships
Concepts & Frameworks:
- Network Graph Effects - Business model advantage where value increases as more participants join the network, necessitating consolidation in this market
- Intellectual Honesty - Framework for holding conflicting thoughts simultaneously and critically evaluating business advice rather than accepting it as gospel
- Charlie Munger to Warren Buffett Dynamic - Partnership model where one person provides critical counterbalance to the other's optimism