Building the Product

When my technical hire and I disagree on the tech stack, whose call is it?

A starting point

Default to the developer on how it is built, because that is their craft and living with their own choices keeps them accountable, but you get to set the constraints that matter to the business: speed to ship, hiring pool for that stack, and cost. Push back hard on any choice that optimizes for the developer's resume or curiosity over your need to launch. If they cannot explain the tradeoff in terms of your goals, that is the real signal, not the stack itself.

Go deeper

Hand-picked from around the web, each with a note on why it earns your time.

3 resources 3 link-checked Listen Read

Listen

🎧 Podcast
✓ Link checked Free Beginner

Why we picked it Frameworks are useful, but sometimes you just want to hear how real founding teams actually got through a hard disagreement. This show interviews founding teams about their toughest conversations, communication breakdowns, and how they made decisions when they did not agree. It is a reminder that the stack fight is usually a trust-and-clarity problem, not a technical one, and that other teams have found their way through it.

How I Met My Co-Founder

On Apple Podcasts by Annie Garofalo Episodes ~30 to 60 min

  • Real founding teams talk candidly about navigating conflict and reaching decisions when they disagreed, which is more instructive than any abstract rule.
  • Co-founder conflict is a leading reason startups fail, so building a way to disagree and still commit matters as much as any single stack choice.
  • Hearing how others handled it gives you concrete language and moves to bring to your own disagreement instead of guessing.
Listen on Apple Podcasts podcasts.apple.com →

Read

✍️ Essay
✓ Link checked Free Intermediate

Why we picked it When you and your technical hire are arguing about the stack, this essay reframes the whole fight: the goal is not the best or newest tool, it is shipping a product and keeping the company alive. McKinley's idea that every team has only about three innovation tokens gives you a shared, honest test to settle most stack disagreements before they turn personal. It is the closest thing to a neutral referee both sides can respect.

Choose Boring Technology

From mcfunley.com by Dan McKinley ~20 min read

  • Every team gets about three innovation tokens, so spend novelty only where it is core to the product, not on the database or the framework.
  • Prefer well understood technology, because its failure modes are documented and the long-term cost of keeping things running dwarfs any early convenience.
  • Adopting new tech should require a real conversation about the problem it solves, not one person's preference, which is exactly the frame a founder and hire need.
Open mcfunley.com →
📄 Article
✓ Link checked Free Beginner

Why we picked it This piece is useful because it separates the question of who owns the tech stack from job titles and points it at the real thing: a cofounder shares core technical decisions as a partner, while a hire executes a roadmap the company has aligned on. If you are not technical, it is honest that ceding all product direction lets a senior hire fill the vacuum with their own roadmap, which is often what the stack fight is really about. Read it as a way to name the relationship, then decide the call.

Technical Cofounder vs CTO Hire: What to Do If You Are Non-Technical

From platvix.com by Platvix ~10 min read

  • A technical cofounder co-owns core technical and product decisions, while a CTO or engineering hire executes a direction the company sets, so the answer to whose call it is depends on which relationship you actually have.
  • A non-technical founder still needs to own product direction, or a senior technical person will set the roadmap by default.
  • A fractional or advisory technical voice can help you choose a stack with guidance, instead of ceding the decision entirely or overruling from ignorance.
Open platvix.com →

People also ask

I'm non-technical, do I actually need a technical co-founder? If you're building a technology product for the long haul, yes: agencies and freelancers are a stopgap, not a foundation, and YC's data shows teams... Beginner 3 resources → How do I actually find a technical co-founder? Treat it like sales, not luck: build a pipeline, expect many nos, and follow up. Go where builders are, hackathons, dev communities, open-source, s... Intermediate 2 resources → Should I hire an agency or a freelancer to build my MVP? Fine for a throwaway prototype or a validation build, risky as the backbone of a product company, you'll own code you can't change and depend on pe... Intermediate 2 resources → How do I hire good engineers in India when everyone's competing for the same talent? Lean hard on your network, alumni, ex-colleagues, referrals, because job portals alone won't surface the best people in India's talent war. Sell th... Intermediate 2 resources → How do I evaluate a developer's skill if I can't code? Skip trivia and whiteboard puzzles; give them a small, paid, job-representative task and see how they think, communicate, and ship. Ask them to wal... Intermediate 2 resources → What equity should I offer a technical co-founder vs. an early engineer? A true co-founder who joins early and shares the risk is usually a near-equal partner, think tens of percent, always with vesting, not an employee ... Advanced 2 resources →