Hours are worthless. Replace them with this.
with Ali Hassan, Wednesday
Hours are worthless. Replace them with this.
Show Notes
Ali Hassan is the co-founder of Wednesday, a product engineering agency that has worked with 10% of India's unicorns - most of them since their Series A. Wednesday doesn't charge by the hour. It charges per sprint, using what Ali calls the Adaptive Engineering Framework: a combination of pirate metrics, rapid iteration, and relentless customer validation designed to help founders go from MVP to product-market fit without burning through their runway on the wrong thing.
The quote that anchors this conversation - "AI makes hours worthless" - is not a provocative claim about the future. It is a description of what Wednesday has already observed: three people doing what six used to do, at three times the output per sprint. The unit of value has changed, and the implications run through everything from how you price services to how you build a team to what a founder should be doing with their time.
Sprint Zero: Validate Before You Build
Before writing a line of code, Wednesday does a Sprint Zero: an audit of where the company actually is, not where the founder believes it is. The audit looks at pirate metrics - retention, referral, revenue - and specifically tries to identify whether the numbers the founder is reporting are real signals or vanity metrics. Signups, views, app downloads, press mentions that cause a spike: none of these predict whether anyone will pay.
Sprint Zero also forces the founder to make their assumptions explicit. Almost every founder arrives with a three-month roadmap and near-total confidence. Ali's team drills down on each item: why do you want to build this? What specific business metric will it move - activation, retention, referral, revenue? In almost every case, the founder doesn't have data to support the prioritization; they have conviction. The Sprint Zero process converts that conviction into a 1–1.5 month validated roadmap that the team can actually build against - and is confident enough to build against.
The Founder's Four: What You Should Actually Be Doing
Ali's most direct piece of advice for pre-PMF founders: there are exactly four things you should be spending time on - marketing, sales, customer conversations, and fundraising. A founder at the MVP stage is like a child at a developmental milestone. There are specific things that only that person can do at that moment, and everything else is either a distraction or a delegation failure.
The corollary is pointed: if an engineering-background founder is still doing day-to-day product work after they have a functioning MVP, they are spending their most leveraged hours on the lowest-leverage activity available to them at that stage. Wednesday has to push founders away from the keyboard and into customer conversations. The founders who find PMF are the ones focused relentlessly on who they serve and what that person actually needs - not on the technical elegance of how it gets built.
Retention Benchmarks: The Numbers That Tell You If You're Headed the Right Way
Ali offers specific, actionable retention benchmarks as early kill-or-continue signals. For B2C products: 50% day-one retention, 25% at day seven, 10–15% at day thirty. For B2B products: 20–30% constant retention through the first thirty days. These are not guarantees - they are indicators. Getting these numbers right suggests you are headed in the right direction. Missing them suggests the product or the audience needs to change before more sprints are justified.
Every company Wednesday has worked with that eventually succeeded started as something materially different from what it became. B2C products became marketplaces. Health assistants became online pharmacies. The companies that made it were the ones that treated the shape of the solution as open to change - because the founder was focused on the customer's demand, not on protecting the original thesis.
Taste, Judgment, and the Era of Outcome-Based Pricing
One of the more philosophical threads in this conversation is Ali's argument about taste. In an era of abundance - where execution is cheap and becoming cheaper - the scarce thing is judgment: the ability to look at a situation and know what matters. Judgment is built through deep, repeated experience in a domain. Taste is judgment made legible.
The conversation touches on Musashi's principle that if you find the way deeply in one thing, you see the way broadly in all things. Ali agrees without hesitation: his number-one litmus test for hiring is whether he can delegate a full area of responsibility and not worry about it - and that has never been possible with someone who hasn't spent roughly a decade in that domain. Experience produces taste, taste produces judgment, and judgment is what clients are actually paying for when they buy an outcome.
This is also why Wednesday moved away from hourly billing toward per-sprint pricing and why Ali believes pricing is moving toward pure outcomes: effort is increasingly abundant, and abundance depresses value. What remains scarce is the wisdom to know what to build - and that is worth paying for at a premium, regardless of how many hours it took to deliver.
The X-Men Model: Small Teams of Hyper-Specialists
Ali's vision for the future of teams is specific and counterintuitive relative to conventional startup advice. Conventional wisdom says surround yourself with generalists who can adapt. Ali says the opposite: hire specialists. The generalist role belongs to the founders and co-founding team - that is who is supposed to be running experiments, trying things, figuring out what sticks. When you need something done well, you bring in the person who has dedicated themselves to that area.
His projection for what teams will look like: small, with insane mutual trust, each person owning their pillar completely. No cap on revenue. Two roles he has already seen emerge from this shift: the GTM Engineer (go-to-market thinking combined with engineering execution) and the Forward Deployment Engineer. Roles that didn't exist two years ago. His prediction: all engineers become prompt engineers; designers absorb product responsibilities; product managers absorb marketing. One pod - prompt product engineer, product designer, product marketer - does what three separate functions used to do, and does more of it.
- Sprint Zero - Before building, audit pirate metrics, surface vanity metrics, force the founder to validate every roadmap assumption with data, and produce a 1–1.5 month validated roadmap. The outcome of Sprint Zero is a direction you can trust - not code. See Frameworks.
- The Founder's Four - At MVP/pre-PMF stage, founders should only do four things: marketing, sales, customer conversations, and fundraising. Anything else is not value. Technical execution is delegated. Engineering-background founders who keep doing product work after MVP have a delegation failure, not a workload problem. See Frameworks.
- Specialist-First Hiring - Hire specialists, not generalists, especially in early stage. The generalist role belongs to the founders. Use focused specialists to run fast, high-signal experiments - it is faster and more informative than building a team of generalists trying to figure out what sticks across every function. See Frameworks.
- Wednesday - Ali's product engineering agency. Works with seed/Series A founders (MVP to PMF) and Series B founders (parallel products). Charges per sprint using the Adaptive Engineering Framework. 10% of India's unicorns are clients. See the Tools page for details.
- Claude Code - Wednesday uses Claude Code as a core part of their development workflow. Ali cites it as a driver of the 3-person-does-what-6-did productivity shift, with quality checks in markdown files and test case requirements baked into their Claude Code setup. See the Tools page for details.
- Pirate Metrics (AARRR) - The Acquisition, Activation, Retention, Referral, Revenue framework for measuring product health at each stage of the user journey. Named for the acronym sounding like a pirate. Ali focuses primarily on Retention, Referral, and Revenue as the metrics that distinguish real traction from vanity spikes. See Glossary.
- Sprint Zero - The discovery and validation phase conducted before sprint 1 (building begins). Produces a validated roadmap rather than code. Includes a pirate metrics audit, assumption validation, customer interview analysis, and identification of the founder's existing distribution strengths. See Glossary.
- Vanity Metrics - Metrics that feel positive but don't predict revenue, retention, or business health: signups, app downloads, views, press mentions that cause a spike. The danger of vanity metrics is that they can sustain founder confidence through a PR cycle while actual product-market fit is absent. See Glossary.
- Customer Pull - The signal that users are actively seeking out and recommending your product rather than being pushed toward it through marketing or sales. Ali's target signal: sprint-on-sprint, are customers pulling the product out of your hands and telling five other people to use it? The presence of pull is the leading indicator of PMF. See Glossary.
- Outcome-Based Pricing - A pricing model in which value is exchanged for results delivered - a business metric moved, a goal achieved - rather than hours worked or features shipped. Ali's view: we are moving toward a world where people will only pay for outcomes. Effort is increasingly abundant; judgment and results are the scarce inputs. See Glossary.
- Pre-PMF Stage - The phase between having an MVP and achieving product-market fit. Characterized by high uncertainty about what to build, active customer discovery, and rapid iteration. During this phase, technical excellence is not needed - what's needed is the fastest path to understanding what customers will pull and pay for. See Glossary.
- GTM Engineer - A role that emerged around 2024 combining go-to-market thinking with engineering execution. Focused on driving distribution and adoption through technical means - integrations, automation, growth infrastructure - rather than pure product development. Ali cites this alongside Forward Deployment Engineer as evidence that org charts are already changing faster than conventional hiring frameworks assume. See Glossary.
What is Sprint Zero and why does it come before building?
Sprint Zero is the discovery and validation phase that happens before sprint 1 - before a line of code is written. The team audits pirate metrics (retention, referral, revenue), identifies whether the founder is tracking real signals or vanity metrics, maps their existing distribution strengths, and forces every roadmap item to answer the same question: what business outcome will this move, and what data supports that? Almost every founder arrives with a three-month roadmap and total conviction. Sprint Zero converts that conviction into a 1–1.5 month validated direction that the team can actually build against. The outcome of Sprint Zero is not code. It is clarity.
What are the retention benchmarks that indicate a product is headed in the right direction?
For B2C: 50% day-one retention, 25% at day seven, 10–15% at day thirty. For B2B: 20–30% constant retention through the first thirty days. These are indicators, not guarantees - getting these numbers right suggests you're pointed in the right direction; missing them suggests something about the product or the audience needs to change before committing more sprints. Ali also watches time to value closely: how quickly does a new user reach the core promise of the product? The longer that takes, the more friction exists before retention can even be measured.
What are the Founder's Four and why does everything else not count?
Marketing, sales, customer conversations, and fundraising. At the MVP/pre-PMF stage, a founder is at a developmental milestone - like a child - and the only things that create leverage at that moment are the four activities that no one else can do as well. Anything else is a delegation failure. Engineering-background founders are the hardest to redirect because writing code is the most comfortable and immediate thing available to them - and Wednesday has to actively push them away from it. The founders who find PMF are focused on who they serve and what that person pulls, not on building features nobody asked for.
Why should you hire specialists instead of generalists in the early stage?
The generalist role - run experiments, figure out what sticks, try different things - belongs to the founders. That is their job. When you hire for execution, you want someone who has dedicated themselves to that area, built taste for it, and can own their pillar without needing supervision. A generalist in a specialist's seat produces mediocre experiments and ambiguous results. A specialist runs a clean, fast, high-signal test and either validates or eliminates the assumption. Ali's litmus test for any hire: can he delegate full responsibility for an area and not worry about it? It has never been possible with someone who hasn't spent close to a decade in that domain.
What does 'taste' mean in a business context, and why will people pay for it?
Taste is judgment made visible. It's the ability to look at a product, a decision, or a market and know what matters - what's worth doing and what isn't. Taste is built through deep, repeated experience: seeing 60 products fail over three years doesn't just tell you what not to do, it gives you pattern recognition that amounts to context. Musashi's principle applies: if you find the way deeply in one thing, you see the way broadly in all things. In an era of abundance where execution is cheap, judgment is the scarce input - and people will pay a premium for it, even when it's packaged as an outcome rather than expertise.
How has AI changed Wednesday's ability to deliver, and what does that mean for pricing?
A project that previously required six people Wednesday can now do with three, at three times the output per sprint - and at a lower price per sprint to the client. Claude Code is central to this: quality checks baked into markdown files, consistent programming patterns, automated test case generation. The implication for pricing is structural: if hours are worthless, charging for hours is dishonest. The real value Wednesday delivers is judgment - knowing what to build, identifying the right ICP, forcing the founder to validate assumptions. That is worth paying for as an outcome, not as a time-and-materials invoice. Ali believes all professional services and most SaaS is moving toward this model.