Framework
Minimum Effective Dose (Operations)
Build and do the least amount legally and operationally required to make a system functional. Bureaucrats over-build because every additional process justifies headcount and grant spend. Lean founders strip everything that is not legally required or genuinely operationally necessary. The goal is not cutting corners — it is refusing to rebuild complexity that only exists because someone was incentivized to create it.
How it works
- 1Study the actual legal requirements. Many processes that 'have always been done this way' have no legal basis — they exist because they justified someone's job.
- 2Canonical example: apprenticeship certificates that included the project name required reissuance every time an apprentice moved projects. No legal requirement for the project name. Remove it; eliminate an entire recurring task.
- 3Bureaucratic systems are built by people incentivized to maximize process, not minimize it. Reverse-engineering those incentives reveals which processes can be safely eliminated.
- 4Minimum effective dose in product means one core feature described in five words. Minimum effective dose in operations means the fewest steps that keep the system legally compliant and functionally running.
- 5This is the operational counterpart to the Eliminate Before You Hire framework: first eliminate unnecessary tasks, then determine whether what remains requires a person or can be systematized.
Hear it on the podcast
He Built a $1M SaaS AloneListen to the episodeMore from this episode
Eliminate Before You HireWhen operational complexity makes you feel like you need to hire someone, the correct order of operations is: first try to eliminate the task entirely — does it even need to exist? Second, fix it with a focused project or sprint. Third, and only if both fail, find a person. The instinct to hire is a reasonable response to overwhelm, but it skips the harder and more valuable question of whether the thing causing the overwhelm needs to exist at all.Market Timing via Legislative MandateThere is a critical difference between a law that creates an incentive (nice to have) and a law that creates a mandate (must do). When legislation requires businesses to do something they have no existing solution for, you are not competing for mindshare or convincing anyone they have a problem — you are standing on the other side of a requirement. This is a fundamentally different and far more favorable demand environment than ordinary market development.
Get the next framework first
One email a week with the frameworks, tools, and founder stories from the podcast. Free.
More frameworks for Operations & Scaling
The Founder's FourAt MVP/pre-PMF stage, founders should only do four things: marketing, sales, customer conversations, and fundraising. Anything else is not value. A founder at this stage is at a developmental milestone — and these four activities are the only ones where their presence creates leverage that no one else can replicate. Technical execution is delegated; everything else is a distraction or a delegation failure.The Amundsen Preparation StandardBefore undertaking a high-risk venture, systematically think through every failure mode and build contingencies for each. The explorer who returns safely is rarely the boldest — they are the most prepared.Provisional-as-Priority StakeThe provisional patent application is the most underused tool in the founder's legal stack. Under the America Invents Act, the US runs first-to-file: whoever reaches the patent office first wins priority, regardless of who invented first. A provisional costs $65 for a micro-entity, requires no formal claims, and grants 12 months of patent-pending status. The gap between 700K non-provisional applications and only 170K provisionals per year is a market failure — not a founder behavior problem. The gatekeeper was always attorney economics, not founder willingness.Three-Track IP StrategyOphir's framework for choosing between the three available IP protection vehicles based on the nature of the invention, competitive environment, and operational realities. Patent, trade secret, and defensive publication each solve a different problem — and the wrong choice can leave you either over-exposed or locked into disclosure requirements that hurt more than they help.Transparent Cost-Plus EOR ModelAlways show clients exactly what goes to the employee versus what goes to the service provider. Opaque pricing creates incentives to compress employee compensation - transparent pricing aligns everyone around fair wages and prevents exploitative reverse tendering.The Founder Operating SystemUse the same platform for your user-facing product and your internal tooling — then eventually let it run operations.