Mike Dauber

Snapshot

General Partner, Amplify Partners (joined 2014, helped build the firm). Based Menlo Park, CA. B2B-exclusive, technical-founder investor — “virtually always with some core IP innovation at the center of the company”; invests in cloud/devops, cyber, and AI/ML. Co-runs Amplify with founder Sunil Dhaliwal (his former Battery Ventures boss). LinkedIn · Amplify bio

Background

Verified career arc (firm bio + LinkedIn + GlobeNewswire, ≥2 sources):

• Hardware engineer at a semiconductor startup, ~2001–2003 (started as an engineer; “the core lesson I learned as an engineer — everything is about tradeoffs. You get nothing for free.”). ^[extracted]
• ~5 years across product, sales, solutions engineering, and marketing roles (operating background, not just technical). ^[single-source firm bio]
• Battery Ventures — joined 2008, ~6+ years; led early-stage enterprise infrastructure & applications investing on the West Coast. GlobeNewswire 2014 (Self-deprecating origin story he’s repeated: he “became a VC in 2008 / joined Battery because he thought it would help him find a better job at a startup” — then grew “envious of founders” and wanted to build something himself.)
• Amplify Partners — joined 2014 as General Partner to help his “good friend (and old boss) Sunil Dhaliwal build Amplify”; present. Amplify bio

Education: B.S.E., Electrical Engineering, University of Michigan (Ann Arbor); MBA, The Wharton School (University of Pennsylvania). ✅ (firm bio + multiple profiles)

Investing

• Thesis / focus: B2B only, with “core IP innovation at the center.” Cloud/infrastructure, devops, cybersecurity, AI/ML, data, developer tools. Seeks founders “deeply steeped in their domain, [who] feel like they’ve got something to prove and are borderline obsessed with their idea.” First-check, hands-on. Amplify bio
• Vertical-AI playbook (his current public thesis — high-leverage for init): in “Boring is sexy: the anatomy of a good vertical AI startup” (Apr 2026) he lays out a four-part playbook: (1) be boring — biggest opportunities are in the least “sexy” markets; (2) own the first mile — control the first customer interaction / the “front door”; (3) build a proprietary data asset the big AI labs can’t replicate (capture the “how”/operational logic, not just the “what”); (4) become a system of action — own a workflow and replace the static “system of record” (Salesforce/ServiceNow/Workday) with a dynamic, decision-making “system of action.” amplifypartners.com
• Notable investments / board-relevant (current): Chainguard (led the $5.0M seed, Dec 2021), Temporal, Avoca (deal partner), Archera, DataLane, Gremlin, Maze, Scribe, SiMa.ai, Enlitic (early vertical-AI bet, 2014). Exits: Cmd (→Elastic), Determined (→HPE), StackRox (→Red Hat), Platfora (→Workday), RelateIQ (→Salesforce), Splunk. Amplify bio · Chainguard post
• Recent (2025–26) deals: led Arito AI’s $6Mseed\ast \ast (May2026,agenticanalyticsforfinance;quotedinannouncement);\ast \ast co-ledDatologyA{I}^{\prime }s$11.65M seed with Sarah Catanzaro; participated in Subtle Computing ($6Mseed)andGradium($70M). TechBullion · firm/founder posts.
• Style: lead-heavy at seed, small initial checks then back through rounds (Amplify house style); chases non-consensus / outlier companies (Origins podcast). Check authority / IC threshold not public — as a co-leading GP at a partnership, treat any specific unilateral-check number as a hypothesis, not fact. ^[ambiguous]

Public voice

• The AI Engineering Report (Amplify’s flagship annual report). Dauber is closely associated with it / authors-sponsors it; the 2025 edition was written by Barr Yaron (edited by Justin Gage) and surveyed hundreds of AI engineers. Headline findings: ~80% say LLMs work well at work, but <20% say the same about agents (a maturity gap); <10% have no plans to use agents; most production agents have write access with a human in the loop, ~13% act fully autonomously; evaluation/evals + monitoring is the #1 most painful part of AI engineering; LangChain dominates frameworks; ~65% use a dedicated vector DB, ~70% use RAG, ~41% fine-tune; “audio is next”; open/closed model convergence. 2025 report · StartupHub recap w/ Barr Yaron ⚠️ Note: task framed the report as “his” annual report — Dauber is the public face/champion, but the 2025 byline is Barr Yaron’s. ^[ambiguous]
• Essays: “Boring is sexy / anatomy of a good vertical AI startup” (2026), “Our investment in Chainguard” (2021), “Second Wave DevOps / System Initiative” (2023), and other Amplify blog posts. He writes in the firm’s operator/think-tank voice.
• Podcasts: SaaStr #139 — “Why Hiring Sales People Is Like Being Thirsty, Why You Have to Separate Between Customers and Money & Why Time Kills More Companies Than Dollars” (2017). Origins (Notation/Sapphire) — “Backing Outliers in Venture” with Sunil Dhaliwal (firm strategy: building for outliers, shaping technical founders into leaders, backing non-consensus companies). Stanford Law VCS conference speaker. SaaStr 139 · Origins
• Handles: X/Twitter @dauber · LinkedIn /in/dauber (he says: “I respond to LinkedIn messages…eventually. There are faster ways to reach me/my team.” — consistent with the CRM note that his notifications are silenced).

Capital efficiency / runway — his on-the-record stance (directly relevant to our disagreement)

This is the crux of the live disagreement (Mike: 18–24mo runway; init: 3–4yr). What’s documented:

• SaaStr #139 framing is the strongest signal: “Time Kills More Companies Than Dollars,” “You have to separate between customers and money,” and sales-hiring “is like being thirsty” (don’t over-drink/over-hire ahead of signal). The throughline: danger is moving too slowly / losing time and focus, and confusing money with real customer traction — not raising “too little.” ⚠️ This is from the episode title + summary; the full nuance is in the audio (not transcribed here). ^[single-source]/^[needs-verification: listen to episode for exact quotes]
• Build-fast, capital-efficient, first-check culture at Amplify (small initial checks; help founders find product before scaling spend) reinforces a moderate-runway, milestone-driven posture over a big war-chest. ^[inferred]
• ⚠️ No public statement found of Dauber prescribing a specific “18–24 months” number — that figure comes from the CRM (the live conversation), not from his published writing. Don’t cite it as a published stance. ^[ambiguous]

Personal & interests (rapport)

All public, from the official Amplify bio + interviews (no minors’ details, no addresses):

• Grew up near Washington, D.C. ✅ [Amplify bio]
• Married, three children; family dog — a Goldendoodle named Molly. (Mention the dog, not the kids.) [Amplify bio]
• Die-hard DC sports fan. Enjoys travel and the outdoors. [Amplify bio]
• Comedy taste: Seinfeld and 90s comedy — a genuine rapport hook (a well-placed Seinfeld reference will land). [Amplify bio]
• Engineer’s worldview: “everything is about tradeoffs. You get nothing for free.” He frames investing as practicing what he preached — he “grew envious of founders” and wanted to build something that mattered, which is why he helped build Amplify rather than just write checks. [Amplify bio]
• Loyalty signal: he frames Sunil Dhaliwal as “good friend (and old boss)” and has built a 17+ year relationship from Battery → Amplify. He values long, durable partnerships.

Fundraise Relationship (init.inc)

• Status: Mike was very bullish on init and is a warm, direct contact into Amplify; passed this round (5/27, door open — see log). The open issue was raise size (Mike: 18–24mo runway; init: 3–4yr). ⚠️ Conflict-adjacency: he is also the deal partner on Avoca (services-economy AI; competitor-adjacent, different buyer).
• Conversation log (newest first, from CRM):
  • 2026-05-27 — Meeting (Sazzad + Mike + David Beyer). RESULT: PASS. Mike said no — “I don’t think this is it for me… I just think you got to find a different path in.” Door explicitly left open (“I enjoy these debates, I’m a big fan of yours… keep me posted”). Status flips: Follow Up Phase → Passed (intellectual partnership warm).
    • Mike’s pass reasoning (verbatim-ish, in order of weight):
      1. Crowded market — “there’s so many dynamics going into a space that already has a bunch of disruptive players who are well-funded, as well as a bunch of legacy players. It’s just a tough pincher move to squeeze through and build a big business.” He sees IT-ITSM getting ~50 startups crashing in.
      2. Channel + CAC problem, not technology — “I don’t doubt your technical acumen. The challenge on these is channels. It’s channels and just the cost of customer acquisition.”
      3. “Side door” preference — “I think you need to be one click out of the main view of everybody. Like if you’re in that main view, you’re just going to get too many startups that just drop right on top of you. They make the cost of sales higher.” IT = “going at the front door.”
      4. Implicit competitive bar — points to coding + customer service as already-attacked-but-real disruptions; says historically ITSM hasn’t been the biggest market either.
    • Mike’s structural suggestion (notable; unsolicited): “If you’re going to go after — if you’re not for MSPs — I almost wonder if you have to front as an MSP… You may be in a better spot to just start up an MSP or two or like I don’t know if this becomes a rollup.” → that’s structurally the Treeline / Thrive MSP-rollup model (already a vector in [[synthesis/cap-table-patterns-across-startup-competitors]]’s PE-MSP-rollup section).
    • Sazzad’s pushback (held the position): (a) the AI-native services play is structurally different from the ITSM-software play that’s getting crowded; (b) “to crack service it’s an AI problem with distribution” and the team can solve the AI side better than anyone; (c) services budget = $6inservicesforevery$1 in SaaS (the volume argument); (d) “willing to hypothesis-test in the market” (humility hedge); (e) acknowledged the NDR risk on small-co ICP.
    • Mike’s reply to the hypothesis-test framing: “there may be a path here. But it just feels like there are so many open areas right now… For me, I’d rather just go somewhere where there’s as fewer people today that I have to compete with.” Translation: even with a real angle, the friction of being in the obvious lane is the structural objection.
    • What Mike’s reaction revealed: he was processing init as ITSM-software more than AI-native services. The services framing is meaningfully different (Pass-2 confirmed both Sequoia/a16z back services-as-software directly), but it didn’t land enough to reset his frame in this meeting.
    • Re-touch posture: door open, intellectual-partnership warm. Walk + sounding-board offered + accepted. NOT Lost (different shape from Accel/Kerry firm-wide thesis-no; different shape from FF structural late-stage-only). Status: passed-this-round.
  • Since 5/7 — SILENT until 5/27 meeting. No reply, no next meeting scheduled until today’s meeting. Mike’s notifications are silenced (he openly says “faster ways to reach me/my team” than LinkedIn).
  • ~5/7 — Sazzad replied with a runway-for-hires framing (runway = ability to make the hires that compress time-to-milestones).
  • 5/7 — Mike replied warmly: “1000%. So few people get this!” and shared a founder example. ⚠️ The founder example is ^[inferred] to be Avoca/Apurva Shrivastava — Avoca launched publicly that exact week (Dauber’s “Boring is sexy” Avoca post ~Apr 27–May 4; founders’ $125M Seed→Series B announcement named “Mike Dauber and Grace Ge from Amplify”), and Apurva’s immigrant-household / answering-the-phones origin is a momentum/capital-efficiency exemplar in Mike’s own portfolio. Not confirmed as the specific example he sent — verify before relying.
  • 5/6 — Sazzad texted a momentum-over-runway message.
  • 5/5 — Sazzad texted a thank-you.
  • Mon 5/4, 1pm — In-person meeting. Great convo; Mike very bullish. OPEN DISAGREEMENT on raise size: Mike wants 18–24mo runway; init wants 3–4yr.
• Mutual connections / warm path: intro = Sazzad direct. Contact channels: CRM has dauber@amplifypartners.com ⚠️ his firm bio lists mike@amplifypartners.com (both plausible). He’s at 800 Menlo Ave, Menlo Park. He explicitly invites going through his team rather than him directly. Sunil Dhaliwal is a second channel into the firm. ⚠️ LinkedIn/X are effectively dead channels for re-engagement (silenced notifications).
• Live stage: in the CRM.

Cross-check vs existing wiki

• No prior “Dauber” mention anywhere in the vault before this page (grep clean) — this is net-new.
• ⚠️ He is the Amplify partner behind Avoca, which the wiki already tracks as an investor relationship on entities/avoca.md and in synthesis/research-avoca-ai.md (“YC/Amplify/Nexus backing”). This page adds the partner-level attribution (Dauber + Grace Ge) and the conflict-adjacency context. Agreement on the underlying Amplify↔Avoca fact; no contradictions.
• Email discrepancy flagged above (dauber@ per CRM vs mike@ per firm bio).

Related

Amplify Partners · Avoca (his portfolio company; competitor-adjacent) · research-avoca-ai