LLenny's Podcast
← All frameworks
EntrepreneurshipGustaf Alströmer (Y Combinator, Airbnb)

Value the Technical Co-Founder

Why engineering is the hard part, and how a non-technical founder should actually treat it

Difficulty
Moderate
Time to result
~months to results
Steps
3
Confidence
90%

Many non-technical founders treat engineering as a commodity — 'I have the idea, I just need someone to build it' — which fatally undervalues the hardest part of the company. Because a product is an infinite series of technical iterations, not a one-time spec-to-build handoff, you need a technical co-founder (or a founding-team-caliber engineer with real equity) who participates in decisions, not a contracting firm. If you can't recruit one, learn enough to build a prototype yourself.

Origin

Gustaf Alströmer's synthesis from screening and advising 600+ YC startups; includes his friend Paul's 'idea for a song' analogy.

Core principles

  • 01Engineering is the hard part; a product is infinite iterations, not a spec you hand off once
  • 02Offering an engineer a tiny equity share signals you don't value engineering
  • 03Most technical decisions and iterations require a founder who understands engineering to make them well
  • 04A contracting firm rarely builds a successful startup because they don't participate in the iteration loop

How to run it

  1. 1

    Reframe how you value engineering

    Stop treating the build as 'just make my idea real.' Recognize engineering as the genuinely hard, decision-heavy core of the company.

    Pro tip Check your equity split: offering 90/10 in your favor over the engineer signals you value the build at one-tenth of yourself.

    Watch out Undervaluing engineering in the split is a red flag that predicts you'll make bad technical decisions later.

  2. 2

    Recruit a real co-founder, not a contractor

    Ask the best technical people you know to start a company with you — many technical people want a business co-founder and have quietly hoped to be asked. Use co-founder matching if you don't know anyone.

    Pro tip Push through fear of rejection the same way you would with customers; some strong engineers are waiting to be asked.

    Watch out A hired contracting team won't join the iteration loop, so the product rarely becomes great.

  3. 3

    If you can't recruit, learn to build the prototype yourself

    Learn enough coding online to build a first prototype. You needn't be the best engineer — many founders stop coding after hiring three or four engineers — but you must understand engineering's value.

    Pro tip You're not locked in by what you studied at 18; learning to code at 25 is very doable.

In the wild

Calendly's founding-team engineering firm

Calendly had a Ukrainian dev team build the first product; they weren't co-founders by YC's 10% definition but functioned as the founding team, and even drove early growth by using and spreading Calendly within their own firm and network in Ukraine.

→ The engineering team functioned as founders with real ownership, and Calendly succeeded — the pattern that works when a non-technical founder deeply values engineering.

Common mistakes

Treating engineering as a commodity to spec out

Believing you just need someone to 'make' your idea undervalues the hardest part and leads to wrong technical decisions across the infinite iterations a product requires.

Hiring a contracting firm to build the whole thing

Contractors don't participate in the product iteration loop, so the startup rarely produces a great product; Gustaf can't recall a case where this worked.

Is it for you?

Best for

Non-technical would-be founders deciding how to get their product built

Not ideal for

Teams that already have a committed technical co-founder invested in the iteration loop

From the transcript

“I have an idea for a song I just need a musician to help me make it right”

34:30

“you applied to YC and you have 90 for yourself and 10 for the engineer”

35:00

“the engineering part is the really hard part and the first thing I would say is you need to learn how to Value the engineering…”

35:00

“it takes more than just sort of like writing a spec to build a product you can't actually expect yourself to a great product you…”

38:00

From the episode

Lessons from working with 600+ YC startups

Gustaf Alströmer (Y Combinator, Airbnb)

→