YC BATCH INTELLIGENCE REPORT
Signal extraction
Founder profiles
Pricing + early revenue
AI ↔ Cloud parallels
LP implications
How do you tell if a YC company is going to break out? Is it the leadership? Is it the execution strategy? Is it the pricing and product behavior? All of these questions are legitimate, and beforehand, no one really looked at what made those top YC alumni stand out.
At Lobster Capital, we have one thesis. There are indeed metrics to look at the early stages of companies that can determine if they will break out and become the unicorns they were always meant to be. We look at historical precedent to spot companies on Demo Day that have all the bells and whistles of a true breakout star.
This report is built around a simple question: What did the top YC alumni look like before the market agreed they were special?
We analyze 6–7 recent YC outcomes and reconstruct early signal patterns across traction shape, product behavior, founder profile, pricing posture, and distribution dynamics. The goal here is to find the signal amongst the noise, and with all the hype around tech and AI at the moment, there is quite a bit of noise to get lost in. So what are some things to look at in the nacent stages of YC companies? Let’s break it all down below
Executive summary
The most predictive early signals are not the easiest ones to measure; they are behavioral and structural:
- Wedge
- Learning velocity
- Pull intensity
- Distribution physics
- Compounding scope
Luckily, YC is a data goldmine because it compresses time. Hundreds of early-stage companies per batch, similar fundraising goals, and similar growth strategies. This makes it easier to compare the “early signals” and identify which indicators repeat when the outcome is exceptional. The report is organized around nine sections. First, we describe the Demo Day reality and why surface-level cues mislead.
Then we reconstruct the signal patterns for 6–7 companies and translate those into a practical investor framework: a short list of signals, a scoring rubric, and numeric datasets you can chart.
- A signal stack you can apply to current batches (especially AI).
- A 1–5 scoring rubric for learning velocity, pull intensity, urgency-to-pay, distribution leverage, and compounding scope.
- Template tables for reconstructing the early company state without requiring perfect historical metrics.
- Chart-ready datasets for a radar chart, stacked bars, and a “signal vs. surface” comparison graphic.
What the “Top ~2%” actually looked like at Demo Day
Investors always have 20/20 hindsight, and if you ask one, they would have told you that on demo day, XYZ company was definitely set to become a billion-dollar company for XYZ reason. They didn’t invest because their capital was tied up in other things, would have messed with their profile, blah, blah, blah.
But this is definitely not true; it’s a load of BS.
Across recent YC breakouts, the companies that later became multi-billion-dollar outcomes typically showed modest surface metrics and strong invisible signals. Even though on paper it might have seemed like your run-of-the-mill YC startup, underneath the hood, there were some consistent signals.
For this guide, we are analyzing 7 previous breakout stars from YC. The table below shows how these companies likely appeared at Demo Day based on publicly reconstructable early data, founder interviews, early customer behavior patterns, and additional metrics that we measure at Lobster Capital.
| Company | YC Batch | Likely Demo Day ARR | Early Users | What was visible | What was actually predictive |
|---|---|---|---|---|---|
| Deel | W19 | <$250k | Dozens of remote startups | Payroll tool for remote contractors | Extreme urgency to pay from founders facing legal risk |
| Supabase | S20 | ~$0 revenue | Thousands of GitHub stars, early adopters | Open-source Firebase alternative | Developer pull + infrastructure embed |
| Whatnot | W20 | <$500k GMV/month | Niche collector sellers | Live collectibles marketplace | High seller repeat rate and buyer engagement density |
| Jeeves | S20 | <$300k | LatAm startups | Corporate card for startups | Cross-border credit friction no incumbents solved |
| Rippling | W17 | <$1M | SMBs managing HR + IT | HR software | System-level workflow integration across departments |
| Hightouch | S19 | <$200k | Data teams | Reverse ETL tool | Warehouse-to-tool dependency is forming quickly |
| Instawork | S18 | <$150k | Local hospitality businesses | Staffing marketplace | Local density loops and repeat shift postings |
What these numbers tell us
At Demo Day, these companies did not show:
- Millions of dollars in revenues (Although ARR is indeed important)
- Large customer bases
- Polished narratives
- Obvious market dominance
They did show:
- Repeat user behavior in a tight wedge
- Clear budget owners and urgency
- Fast product iteration driven by real usage
- Early signs of distribution loops
- A wedge that could naturally expand into a platform
The companies by the numbers vs. where they are now
At the time they passed through YC, most of these companies looked like $10–20 million startups solving pretty narrow problems for small groups of users. The graph below tracks how those early, run-of-the-mill-looking companies compounded into multi-billion-dollar outcomes in just a few years.
This is the gap between how these companies looked at Demo Day and what they later became.
Reconstructing Demo Day
To reduce the 20/20 hindsight bias as mentioned above, each company is reconstructed using the same lens. Even when exact numbers are not available, the pattern can still be scored with consistency.
When you review YC outcomes backward, the same signals appear again and again:
- Companies with strong early pull reach Series A at 45% rates vs 33% for typical startups
- Companies that embed into workflows show 87% survival rates vs ~10% industry average
- Companies with repeatable distribution reach meaningful scale 2–3 years faster
- Companies with compounding scope grow from $50K ARR to $10M+ ARR in under 36 months
How to measure Demo Day
We take 5 categories that we feel are intrinsic to companies on Demo Day, which later become breakout stars. Below is what to look at when analyzing a YC demo day participant.
| Field | What to measure at Demo Day | Typical range in breakout YC companies | Why it predict breakout outcomes |
|---|---|---|---|
| Wedge | Specific ICP + painful job-to-be-done | 1 narrow buyer persona 1 core workflow Often <50 customers |
Breakouts begin with wedge clarity before expansion |
| Pull behavior | Repeat usage, workflow embed, urgency signals | Weekly or daily usage Retention >70% in first cohort Users asking for features |
Early pull is stronger than early revenue |
| Learning velocity | Shipping cadence and user-driven changes | Product updates weekly or faster Roadmap driven by real users, not vision decks |
Fast learners compound advantage quickly |
| Distribution lever | Community, integrations, compliance networks, density loops | 30–60% of early users from word-of-mouth, community, or integrations | Distribution explains later scale |
| Compounding scope | Clear path from wedge → platform → higher ACV | Obvious adjacent workflows within 6–12 months ACV expansion potential 3–10× |
Outliers require compounding, not linear growth |
Why did we choose these 5 fields?
Because when you map them against historical YC outcomes, they are the precursors to the only thing that matters: Becoming one of the 6% of companies that drive 90% of portfolio returns.
Applying the template to recent breakout YC companies
Now that we have our template, let’s backtrack to see
Deel – Global payroll and compliance
| Field | Early state reconstruction |
|---|---|
| Wedge | Startups are hiring remote contractors across borders and struggling with legal payroll compliance |
| Pull behavior | Founders urgently needed a way to pay international talent without breaking local laws |
| Learning velocity | Rapid iteration across jurisdictions as users surfaced country-specific compliance issues |
| Distribution lever | Startup networks, remote work communities, and founder word-of-mouth |
| Compounding scope | From contractor payments to full payroll, HR, compliance, and enterprise workforce infrastructure |
At the time, this likely looked like a tool for a small subset of remote startups.
- Within 24 months, Deel reached a $1B+ valuation.
- Within 5 years, it crossed $12B.
- Today, it operates in 150+ countries.
The wedge was on the narrower end, but the compounding opportunity was huge. There was real pent-up demand all over the world waiting for a platform to solve the international contractor issue.
Supabase — Backend-as-a-Service
| Field | Early state reconstruction |
|---|---|
| Wedge | Developers who wanted an open-source alternative to Firebase |
| Pull behavior | Developers are integrating it directly into live side projects and prototypes |
| Learning velocity | Constant shipping based on developer feedback in public forums and GitHub |
| Distribution lever | Open-source community and developer evangelism |
| Compounding scope | From database tooling to a full backend stack used in production systems |
This looked like an open-source developer project.
- Within 5 years, Supabase reached a $5B valuation.
- Its GitHub community grew to 60,000+ stars, a stronger early signal than revenue.
- Thousands of production apps were running on it before most investors noticed.
Subscribership and community intensity were the metrics. Not ARR.
Whatnot — Live shopping marketplace
| Field | Early state reconstruction |
|---|---|
| Wedge | Collectors selling niche items through live video streams |
| Pull behavior | Sellers repeatedly returning because buyers were active and engaged in real time |
| Learning velocity | Rapid feature changes to improve live selling mechanics and trust |
| Distribution lever | Community density within collector categories |
| Compounding scope | From collectibles to broader live commerce categories |
This looked like a collectibles streaming app.
- Within 12 months, it crossed $1B valuation.
- GMV scaled into the hundreds of millions before the model was widely understood.
- Engagement per session exceeded traditional e-commerce benchmarks by 5–8x.
Density, not category size, was the signal.
Jeeves — Corporate spend and finance
| Field | Early state reconstruction |
|---|---|
| Wedge | Startups operating internationally without a proper credit infrastructure |
| Pull behavior | Founders urgently need cross-border corporate cards |
| Learning velocity | Fast adaptation to financial and regulatory constraints across countries |
| Distribution lever | Startup founder networks and CFO communities |
| Compounding scope | From cards to a full financial management platform |
Within 24 months, Jeeves reached a $2.1B valuation.
It solved cross-border financial friction in 20+ countries while incumbents stayed domestic.
The wedge was geography and the compounding was infrastructure.
Rippling — HR and IT platform
| Field | Early state reconstruction |
|---|---|
| Wedge | Companies struggling to manage employees across HR and IT systems |
| Pull behavior | Teams using it daily because onboarding and device management were painful |
| Learning velocity | Constant expansion of integrations and automation flows |
| Distribution lever | HR operators recommending it to other HR operators |
| Compounding scope | From payroll to a full workforce operating system |
This looked like HR software.
Today, Rippling is valued at $13B+ and manages workforce infrastructure for 10,000+ companies.
Its early signal was daily operational dependency, not revenue.
Integration depth, not feature set, was the predictor.
Hightouch — Enterprise data sync
| Field | Early state reconstruction |
|---|---|
| Wedge | Data teams wanting warehouse data usable inside business tools |
| Pull behavior | Data teams repeatedly using it to power marketing and sales tools |
| Learning velocity | Rapid expansion of connectors based on user needs |
| Distribution lever | Data community and integration ecosystem |
| Compounding scope | From sync tool to central data activation layer |
Within 3 years, Hightouch reached a $1.2B valuation.
It became embedded in the modern data stack of hundreds of growth teams before most investors understood reverse ETL.
The easy embedding is a classic example of a distribution lever being utilized ot the max.
Instawork — Workforce marketplace
| Field | Early state reconstruction |
|---|---|
| Wedge | Hospitality businesses need reliable hourly workers on short notice |
| Pull behavior | Businesses repeatedly post shifts because workers showed up reliably |
| Learning velocity | Iteration around reliability, trust, and worker matching |
| Distribution lever | Local density loops in cities |
| Compounding scope | From hospitality staffing to a multi-industry labor marketplace |
This looked like a local staffing tool.
By 2021, Instawork reached ~$760M valuation, approaching unicorn territory.
It expanded across multiple industries while maintaining density economics in each city.
Local reliability was the missed signal, that at a local level, the demand for this would be astronomical.
Section 2: The obvious vs. the invisible
Most investors are fluent in legible signals, as they are easy to explain, and easy to raise money on the back of. Revenue today, logo screenshots, pipeline counts, and a tidy story fit neatly into that frame. It’s the building blocks for 99% of seed investment that goes into early-stage companies today, whether they be in Shenzhen or Silicon Valley. However, the more predictive signals don’t necessarily scream out loud; they are more behavioral, and thus harder to both track and summarize.
This is why two investors can watch the same Demo Day pitch and walk away with opposite conclusions. One sees a small business with unclear upside. The other sees a wedge that will compound into a platform, because they are paying attention to the layer beneath what is immediately visible.
So, what exactly are the cues? Both obvious and much more subtle/invisible?
| Obvious (often misleading) cues | Invisible (often predictive) cues | How it shows up in practice |
|---|---|---|
| Low revenue | High urgency to pay | Customers ask for pricing; compliance or operational pain forces purchase behavior. |
| Messy narrative | Wedge clarity | Even if the pitch is rough, the first buyer and job-to-be-done are sharply defined. |
| No “big logos” | Pull intensity | Small set of users behave as if the product is already mission-critical. |
| “Crowded market” | Distribution physics | The company has a repeatable route to users that competitors can’t easily copy. |
| “Boring category” | Compounding scope | The “boring” workflow expands into adjacent workflows, higher ACV, and platform lock-in. |
If your evaluation framework can’t capture invisible signals, it will reliably miss outliers or enter only after the best terms are gone.
Section 3: The early metrics
We are calling this section metrics as opposed to KPIS, as KPIS are usually associated with more mature businesses. YC companies on Demo Day are far from stable, and here are the metrics that REALLY MATTERED.
Companies like Deel, Supabase, Rippling, and Whatnot did not look inevitable at Demo Day. Deel was solving payroll for remote startups. Supabase was an open-source Firebase alternative. Rippling was HR software. Whatnot was a collectibles streaming platform. Yet within 1–5 years, each crossed $1B+ valuation.
The difference was not visible scale. It was the early presence of signals that consistently predict breakout outcomes.
1) Wedge
Across YC breakout companies, the wedge is usually where the first real signal appears. A strong wedge means the product solves a painful problem for a very specific customer, and that pain is strong enough that people are willing to adopt early. When the wedge is clear, customers often pay before pricing is fully optimized because the problem already sits inside a real workflow with a budget attached.
Jeeves is a good example. The company focused on startups operating across borders that lacked proper financial infrastructure, which is a very specific and painful situation. Because the wedge was so clear, early customers were willing to adopt and pay even while the product was still developing, and the company reached a roughly $2.1B valuation within about two years.
Hightouch showed a similar pattern. Data teams needed warehouse data available inside operational tools, and that workflow already mattered to the business. Even though the product started as infrastructure software, the clarity of the wedge created early adoption and revenue, which helped the company reach about a $1.2B valuation within three years.
Early observation: A narrow customer, a painful workflow, and clear budget ownership.
YC pattern: Strong wedges consistently appear before large revenue numbers.
Why it predicts: Wedge clarity creates the foundation for expansion into larger platforms over time.
2) Pull intensity (not vanity traction)
Pull intensity, in layman’s terms, is how desirable your product is. If it’s desirable, it will naturally pull people into its orbit, and the better the product or solution, the more intense this “pull” is. Among all YC breakouts, pull was obvious, even before ARR.
Two examples of this can be found in Deel and Whatnot.
Deel initially served startups hiring international contractors, which is a pretty narrow edge, to be honest. However, due to the rise of remote work and digital products, the pull was incredibly strong. Within 24 months, Deel crossed $1B valuation and later scaled to $12B+. Whatnot showed similar patterns. Due to its attachment to collectible communities, which are religiously committed to the cause, their early engagement and pull intensity were off the charts. Within roughly 12–18 months, Whatnot crossed the unicorn threshold.
Deel’s pull intensity was based on a real problem that needed urgent solving, and Whatnots pull intensity was based on the commitment of the community.
- Early observation: Repeat usage user desire,e and high retention within a narrow segment.
- YC pattern: Breakout companies often showed strong pull inside small wedges long before broad adoption.
- Why it predicts: Pull becomes the foundation for compounding distribution and pricing power.
3) Learning velocity
Learning velocity is the rate at which an organization can move from reality to product development. Founders are able to generate learning velocity as they iterate on their product/ service through various methods (e.g., customer feedback, internal experimentation). Solid learning velocity was evident across all breakout sessions from YC during DEMO DAY.
A prime example of this is Supabase; at the time, it had reached tens of thousands of developers with its GitHub community. At the time, the traction was real, but the monetization was lagging behind. How was Supabase going to start making money? This rapid iteration cycle enabled the founding team to quickly pivot from what was initially being developed as a database wedge into a full backend platform and achieve a valuation of approximately $5 billion.
Rippling is another great case of learning in action. Before becoming a $13B+ company, its early advantage was not scale but speed of integration and expansion. The product rapidly absorbed adjacent workflows, increasing embed depth inside organizations.
- Early observation: Weekly shipping cadence, rapid iteration, clear product convergence.
- YC pattern: Breakout YC companies often compress product learning cycles into weeks rather than months.
- Why it predicts: Learning compounds. A team learning 2x faster can build a structural advantage within 12–24 months.
4) Distribution physics
Distribution physics determines whether adoption becomes repeatable. In all of the YC breakout examples, it was rare that distribution relied on paid acquisition to get started.
Supabase has grown primarily through its open source distribution mechanism. Deel grew through the startup network and remote hiring community. Instawork grew through loops of local marketplace density. Rippling has grown primarily by embedding its operations into the workflows of HR departments.
The above distribution mechanisms have created compounding adoption patterns. Once a company’s adoption has been embedded into the workflow, it will grow without an equivalent increase in sales effort.
- Early observation: Referrals, community pull, integrations, workflow embed.
- YC pattern: Breakout companies showed repeatable acquisition loops before scale.
- Why it predicts: Repeatable distribution is a prerequisite for venture-scale outcomes.
5) Compounding scope
Compounding scope refers to the ability of a single application (or a small set of applications) that initially addresses a narrow need to ultimately grow into a much broader platform.
Rippling has expanded its payroll capabilities to become a full-fledged Workforce Infrastructure Platform.
Deel has grown beyond merely paying contractors to become a Global Human Resources and Compliance Solution.
Supabase has evolved from being a database tooling platform to being a complete Backend Infrastructure Platform.
As these applications have expanded their offerings, each application’s revenue opportunity with existing customers has also expanded significantly. These applications are no longer simple tools but rather the foundational layers of the platforms upon which other applications can be built.
- Early observation: Clear adjacent workflows and natural platform expansion paths.
- YC pattern: Breakout YC companies consistently expanded from narrow wedges.
- Why it predicts: Compounding scope is what enables power-law outcomes.
What YC outcomes reveal about early metrics
| What investors focused on | What YC breakouts actually showed | Outcome correlation |
|---|---|---|
| Early ARR scale | Strong pull and workflow embedded in a narrow wedge | Faster expansion into large markets |
| Market size theory | Immediate wedge dominance | Platform expansion and category leadership |
| Polished pitch narratives | High learning velocity and behavioral pull | Faster progression to $1B+ valuation |
These signals appeared consistently across YC companies that later reached billion-dollar outcomes. They were visible early, even when revenue and valuation were still small.
Section 4: Founder profiles that correlate with breakout outcomes
In startups, the founders are extremely important; just ask Elon Musk. The question for every VC investor is, how can you really tell if the founders are legitimate, or if they are going to fold under pressure? The answer lies in measuring the character and behavior of founders. In YC, good founders are usually high-speed decision makers, truth-seeking, and have both an instinct and an insatiable appetite for distribution.
- Fast compounding is common. In our “years to ~$1B” dataset, multiple companies reached unicorn territory in 1–3 years (Whatnot: 1; Deel: 2; Jeeves: 2; Hightouch: 3; Instawork: 4; Supabase: 5).
- This speed is not luck. The repeat pattern is founders who move faster than the market’s ability to react.
Pattern 1: High-speed decisions with fast correction
When companies are starting out, particularly those using new technology, decisions and corrections need to be made at hyper speed. Usually, founders need to run multiple iterations of products constantly, correct them instantaneously, and then move on to the next one. This is an important metric when comparing companies at YC: how much are they iterating and correcting?
Pattern 2: Truth-seeking over storytelling
The tech world really doesn’t go for salesy as much as they do accuracy. That’s one of the biggest differences between Silicon Valley and Wall Street. Too much swarmy salesman schtick will be seen right through by experienced VCs; the most important facet is accuracy. A good story to tell is how many things you got wrong and how fast you corrected them. That honesty might be more important than any slick presentation.
Pattern 3: Distribution instinct
Early on in their journey, breakout founders discover how their users will ultimately find them. It’s not about marketing and flashy advertising; it’s about finding a repeatable path to get there. That can be a community, integration with other applications, regulatory compliance issues, market trends, or any other way to become part of someone’s daily routine, the holy grail of Business SaaS.
How these founder patterns show up in our case set (with numeric anchors)
| Company | Founded / YC batch | Founders (YC listing) | Numeric anchor | Founder pattern it exemplifies |
|---|---|---|---|---|
| Deel | 2018 / W19 | Alex Bouaziz, Shuo Wang | ~2 years to ~$1B | Tempo + truth-seeking (compliance reality forces fast correction) |
| Supabase | 2020 / S20 | Paul Copplestone, Ant Wilson | ~5 years to unicorn-range | Distribution instinct (community pull) + high shipping tempo |
| Whatnot | 2019 / W20 | Grant LaFontaine, Logan Head | ~1 year to ~$1B | Distribution instinct (marketplace liquidity loops) + rapid correction |
| Jeeves | 2020 / W21 | Andrés García-Amaya, Nicolas Rojas, Miguel Armaza | ~2 years to unicorn-range | Domain edge (cross-border finance reality) + truth-seeking |
| Hightouch | 2018 / W19 | Kashish Gupta, Tejas Manohar | ~3 years to unicorn-range | Domain edge + distribution via integration ecosystems |
| Instawork | 2015 / S15 | Sumir Meghani, Rahul Mehta | ~4 years to unicorn-region | Comfort with ambiguity + operational tempo (marketplace density is earned) |
Other YC examples that started small and became massive
| Company | Founded / YC batch | Why it matters here |
|---|---|---|
| DoorDash | 2013 / S13 | Operational wedge + local density loops (a “messy” early category that compounds) |
| Dropbox | 2008 / S07 | Product pull + distribution simplicity (default choice behavior can start before revenue looks huge) |
Section 5: The “boring” companies that later did extremely well
Venture is fundamentally biased toward excitement for an investor, but some of the greatest results come from workflows that are boring at demo day (compliance, infrastructure, data plumbing, and operational marketplaces) and win as they have a budget for the buyer, are already a part of the buyers’ process, and have an opportunity for organic growth based on the structure of the business.
In this report’s case set, the “boring” wedge often becomes a compounding engine. One simple way to see it is the time-compression:
- Deel: ~2 years to ~$1B+ valuation
- Hightouch: ~3 years to ~$1B+ valuation
- Instawork: ~4 years to unicorn-region
These are not “slow grind” outcomes. The wedge compounds faster than the pitch looks.
Section 6: Pricing, ARR, and what the first 12 months really look like
In year one, there are many who tell you that ARR doesn’t matter, but it does. An early solid and growing ARR is where you can really see if the founders have their stuff together and if everything is stable. That being said, it’s just as important to have a condensed thesis on why this business will succeed. Who the buyer is, what is a “must have” job that the product solves, what reliability standard does the buyer require, and what the first “wedge” of the product will look like in the real world. Pricing is one of the fastest ways to find out the truth about how a product is viewed by a customer vs. priricing which forces a buyer to make a decision based on the available money.
Most early companies fall into one of three monetization shapes. Each shape implies a different “first-year scorecard”:
- Workflow charge early (compliance/ops): pricing conversations happen in weeks, not years.
- Usage-led (dev tools): monetization follows intense usage, often after product trust is earned.
- Take-rate (marketplaces): the early goal is repeat behavior and liquidity, not maximizing take.
Common early pricing postures and what they usually signal
| Pricing posture | What it usually looks like early | Signal | Company examples in this report |
|---|---|---|---|
| Charge early (workflow) | Invoice-based, service-assisted onboarding, clear buyer | Urgency-to-pay + budget owner clarity | Deel, Jeeves |
| Usage-led (dev tools) | Community adoption first, monetization later via usage intensity | Infrastructure embed and compounding reach | Supabase |
| Take-rate / marketplace | Economics tied to GMV; early focus on density and repeat sellers | Liquidity flywheel + operational discipline | Whatnot, Instawork |
The first 12 months: what “good” looks like (by category)
The first year often looks “small” even for later winners. What matters is the repeatable proof inside a wedge: Reliability, usage intensity, and a path to expansion. Use the framework below to keep the evaluation numerical and comparable across companies.
| Category | Month 1–3 (proof) | Month 4–8 (repeatability) | Month 9–12 (expansion) |
|---|---|---|---|
| Compliance / ops | Workflow works end-to-end; reference customers exist | Onboarding standardizes; adjacent compliance needs appear | Repeatable sales motion; ACV expansion begins |
| Dev tools | Community pull; “default choice” emerges in one use case | Integrations + reliability; monetization experiments start | Usage-led revenue begins compounding |
| Marketplace | Repeat sellers; conversion mechanics proven | Density in one vertical; friction drops | Expand categories/regions once the loop works |
Section 7: What today’s AI YC companies share with 2010 cloud companies
Platform changes lead to the same mispricings over and over again: The first companies are evaluated using the metrics of the last YC event, or the previous era. In 2010, many cloud companies were offering products that they defined as “tools” or “wrappers”. Investors at the time didn’t recognize that this was a powerhouse technology that became the building blocks for all tech.
| 2010 cloud pattern | 2025 AI pattern | Interpretation |
|---|---|---|
| Tooling emerges before platforms | AI tooling emerges before AI-native platforms | Early winners often look “small” because they are primitives |
| APIs looked thin but became foundational | Wrappers can become infrastructure if embedded in workflows | Workflow embed can be defensibility |
| Boring infra produced massive outcomes | AI evals, data, compliance, orchestration can produce massive outcomes | Boring often hides compounding economics |
Section 8: The signal stack (Repeating signals)
After reconstructing the case studies, we can reduce the noise to a short list. This is the “signal stack”: indicators that show up repeatedly across the top outcomes. This is a solid method to make early-stage evaluation comparable and scorable.
The signal stack (One last time, so you always remember!
- Wedge clarity
- Learning velocity
- Pull intensity
- Distribution leverage
- Compounding scope
Example: Scoring Deel with our system
At the YC stage, Deel looked like a niche payroll tool for startups hiring contractors overseas. On the surface, the market looked narrow. But the underlying signals were strong.
Here is how we might have scored it in retrospect.
Wedge clarity: 5/5
Deel was extremely focused from the start. The customer was founders hiring international contractors, and the pain point was legal payroll compliance across borders. There was no confusion about the use case. If a company needed to pay someone overseas without breaking laws, Deel solved that exact problem.
Learning velocity: 4/5
The product learned at a rapid pace because each new country added new edge cases and compliance issues for the team to address. Customers reported their experience directly to the team, resulting in changes and improvements to the product. The only reason we don’t give this a perfect score is that international regulation inherently creates delays in how quickly some features can be iterated upon vs. straight-up software.
Pull intensity: 5/5
There was a high level of pull from customers. Founders had an urgent need to pay contractors without risking compliance; therefore, they were more likely to purchase a solution such as Deel before it had reached maturity.
Distribution leverage: 4/5
Growth spread through founder communities, startup networks, and word of mouth rather than heavy marketing. When one startup solved payroll problems with Deel, others heard about it quickly. The score is slightly below perfect because the company still needed sales effort as it expanded into larger markets.
Compounding scope: 5/5
From day one, the potential for Deel’s expansion path was well-defined. Once Deel handles contractor payments, the logical next steps would be payroll, compliance, HR tools, and workforce management, etc. This progression would allow Deel to take its narrow initial focus on contractor payments and expand it into a comprehensive global employment platform.
Total signal score: 23/25
© 2026 Lobster Capital. All rights reserved. This report is for informational purposes only and does not constitute investment advice.
Leave a Reply