Dana Oshiro - General Partner at Heavybit
Heavybit has backed dev-tool founders since Netlify, LaunchDarkly, Snyk and Circle were 2-10 person teams. Dana Oshiro's read on what those companies had in common early on: a small, believable side door into a much bigger idea.
Dana Oshiro is a General Partner at Heavybit, a VC that invests exclusively in developer-first startups and has run an accelerator for dev-tool founders since 2013.
We get into the idea of 'one sharp thing' — a small, addressable entry point into a bigger vision, illustrated by Heroku's one-click deploy and Stripe's easy API — why founders who go to meetups and actually listen outperform ones who don't, why dev-tool companies that lead a 'movement' have an edge, and how Heavybit actually works with founders once it's invested.
The Q&A below is experimental — extracted from the episode transcript with AI. If you spot a mistake, let us know at jack@scalingdevtools.com.
What is Heavybit, and how far back do the investments go?
Heavybit is a VC that invests exclusively in developer-first startups, and it started life in 2013 as an accelerator for dev-tool founders. We've backed companies like Netlify, LaunchDarkly, Snyk and Circle back when they were two-to-ten person teams, well before any of those names were established the way they are now.
You talk about founders finding 'one sharp thing.' What does that actually mean?
It's finding an addressable chunk of a much bigger opportunity — a side door into the vision rather than trying to sell the whole vision on day one. Heroku's actual wedge was one-click deploy: a genuinely small, concrete thing to build and to explain, that also happened to be the leading edge of a much bigger platform. Stripe's wedge was an API and documentation that were simply easier to use than anyone else's at the time. Neither company pitched 'we're going to be the future of cloud infrastructure' or 'the future of payments' out of the gate — they picked something narrow enough to actually deliver and let people feel the bigger idea through that narrow thing.
How do you tell the difference between a real 'sharp thing' and something too small to matter?
You have to think big and small at the same time. It's worth asking, concretely: are five people seriously going to be able to support a company migrating off Datadog? At a place like Facebook you had a huge amount of internal support, people and systems, that founders can quietly forget isn't there once they're a five-person startup selling to an enterprise. The sharp thing has to be genuinely deliverable by the team you actually have, not the team you wish you had.
You mentioned watching a founder pack up right after a demo instead of sticking around to talk to people. What's the lesson there?
Stepping up as a founder is hard, and there's a real fear of hitting up the people you respect — it's much easier to do your demo, feel like you did the job, and leave. But the best founders build for themselves first, and they push through that fear because they know the value is in the room afterward, not just on stage. It's a real question whether founders get better at putting themselves out there over time, or whether it's closer to a fixed trait, but the ones who do get better tend to be the ones who treat it as a skill to practice rather than something to avoid.
Why is in-person, live feedback so much more valuable than feedback from posting online?
In-person critics tend to be higher intent, and you can actually interrogate them — ask a follow-up question, push back, understand what's really behind the complaint. Anonymous feedback, like a flame war online, doesn't give you any of that; you just get the complaint with no way to dig into it. Edith Harbaugh, co-founder of LaunchDarkly, actually used structured founder feedback sessions partly as a way to practice public speaking — putting herself in front of a room repeatedly until it stopped being uncomfortable, while also getting the benefit of direct, interrogable feedback each time.
What do you mean by dev-tool companies 'leading a movement'?
Some of the best-performing dev-tool companies got there by leading a best-practices-driven movement rather than just selling a product feature by feature. Heroku had the 12-factor app. Netlify had Jamstack. DevOps as a term was coined by Jesse Robbins and Adam Jacobs at the Velocity conference, and observability was popularized largely by Honeycomb. In each case the company didn't just describe its product, it described a better way of working, and the product became the natural way to actually practice that better way of working.
Is there a risk in trying to control a movement you've started?
Yes — the instinct to control it too tightly usually backfires. A movement spreads because other people pick it up and make it their own, extend it, argue about it, apply it to problems you didn't anticipate. If you try to gatekeep who gets to use the term or how, you choke off exactly the organic spread that made it valuable in the first place. It's also fine, and often smart, to join into other movements that are already happening rather than needing to originate your own from scratch.
How important is founder-market fit compared to the founder simply being frustrated by a problem?
Frustration with a problem is common — plenty of people are frustrated by the same things. What matters more is founder-market fit: whether this specific founder has some real, earned advantage in this market, whether that's domain expertise, credibility with the buyer, or a genuine head start on understanding the problem. Frustration gets you to an idea; founder-market fit is what gives you a real shot at building the company around it.
How does the fundraising path typically start for the founders you back?
It usually starts with angels and friends and family, using a SAFE or a convertible note, with checks in the ten-to-fifty-thousand-dollar range. From there, founders move into a seed round, which for the companies we see is typically one-and-a-half to five million dollars. That earliest money is less about the amount and more about proving someone outside your own head believes the idea is worth backing.
How does Heavybit actually work with founders once it's invested?
We strongly prefer warm introductions rather than cold inbound. Once we're working with a company we do bi-weekly meetings, and when we're leading a round we'll take a board seat. We think about these relationships on an eight-to-ten year horizon, not a quarter-to-quarter one, so the cadence and the depth of involvement reflect that — it's closer to a long partnership than a transaction.
You mentioned helping technical founders get comfortable with content and marketing. Why does that matter so much for dev-tool companies specifically?
A lot of technical founders are genuinely uncomfortable with anything that feels like self-promotion once they've taken venture money — there's an internal resistance to 'doing a capitalism,' as I'd put it. But once you've taken outside capital, being visible, writing, speaking, explaining your thinking publicly, is part of the job now, not an optional extra. Helping founders get past that discomfort and actually show up in public is a real, recurring part of the work.
What's the one thing you'd want founders to take away from all of this?
I love the people that you're building for. If you actually hold onto that — really care about the people on the other end of the product — you're going to do a better job, and you're going to do right by them. Everything else, the positioning, the movement, the fundraising, sits downstream of that.