Discover Jack Canter's principles for building an enduring company. Learn how to combine bootstrapping wisdom, quality-first culture, and high-agency teams t...
Build a Company to Run Forever: Jack Canter's Vision for Sustainable Business Success
Key Takeaways
- Eat glass principle: Doing things the right way even when economically illogical creates lasting competitive advantage
- High agency hiring: Seek team members who take full ownership and refuse victim mentality in problem-solving
- Long-term building: Patient 4.5-year development cycles outperform quick launches when product complexity demands it
- Quality drives costs down: Toyota Production System proves that prioritizing quality automatically reduces operational expenses
- Incremental scope reduction: Breaking work into demo-day-sized chunks makes complex products manageable and prevents cascading failures
- Margins matter deeply: Sustainable businesses require defensible economics, not just fast growth metrics
- Written culture: Decision records and documentation scale judgment across growing teams far better than verbal transmission
From Car Parts to Healthcare: Understanding the Art of Starting Right
When Jack Canter bought his first car—a 1995 Chevy Caprice—he never imagined it would launch a business that would eventually teach him lessons applicable to building Stedi, the programmable healthcare clearing house. That journey began not with a revolutionary idea, but with curiosity. A 16-year-old Canter created a fake business card to attend a SEMA aftermarket auto show, walking booth to booth asking about parts that would fit his rare vehicle. When one vendor mentioned he needed a $2,500 minimum order, Canter did the math: that meant 25 sets of components, enough to outfit 25 cars.
He put the purchase on a credit card, packaged the parts into kits, and listed them on the Impala SS forum. He sold 24 additional kits. That moment—when he discovered the power of wholesale versus direct-to-consumer—taught him something fundamental about business that would shape his thinking for decades: capital constraints, if managed correctly, can become your greatest teacher.
Over thirteen years, Canter grew this auto parts business into something substantial by focusing on customer feedback. When people complained that original equipment used metal-on-metal ball joints while modern replacements switched to plastic, he listened. When images on competitors' websites looked like scanned photocopies from decades-old catalogs despite representing billions in market cap, he recognized an opportunity. By applying basic manufacturing principles to e-commerce, providing excellent photography, clear descriptions, and world-class customer support, the business achieved software-level margins in a physical products category—something investors told him was impossible.
But after more than a decade of bootstrapped growth, Canter realized he'd hit an important ceiling. The constraint that had originally forced discipline and excellence—limited capital—had become a limitation. He'd raised his first venture round and suddenly faced a different challenge entirely: how good was he, really? With capital no longer the limiting factor, Canter confronted questions about his own ability to recruit, build products, and execute at scale. This realization drove a crucial insight: venture capital's greatest value isn't money; it's the removal of capital as an excuse for underperformance.
The EDI Problem: Where Manufacturing Wisdom Meets Software Reality
When Canter needed to automate his auto parts business's transaction processing, he discovered EDI—Electronic Data Interchange. Developed in the 1960s for railroad communication, popularized by Walmart in the 1980s, and adopted across supply chains when Amazon came online in the 1990s, EDI represented a decades-old standard that still powered global commerce. Yet every EDI platform he evaluated promised seamless integration while delivering 90-day implementations that dragged into 18-month nightmares.
The experience crystallized a pattern. Teams would promise integration "pre-built with" major retailers. In reality, "pre-built" meant "we've done this once before." Implementation required months of coordination where the software company waited for retailer responses, where unexpected complexity emerged constantly, where systems calcified and teams became trapped in evolutionary dead ends.
Canter's hypothesis was straightforward: if existing EDI platforms were so painful, perhaps the dozens of obvious things they weren't doing represented genuine opportunity. He wasn't talking about revolutionary technology or cutting-edge innovation. He was talking about basic execution—the things that manufacturers learned decades ago but somehow never made it into software.
This led to Stedi's founding, but not before Canter made a crucial decision about his own fundraising approach. Having observed founders struggle with venture investors, he identified patterns: they promised things they couldn't deliver, gave up control too early, or surrounded themselves with investors they didn't trust. Canter inverted these problems. He would tell investors good news only after it happened, and bad news as soon as possible. He would never give up board control. He would raise capital but structure it such that relationships felt like partnerships, not subordination.
When Stedi launched publicly in March 2023, nobody knew the company would immediately face the most extreme form of product-market fit imaginable. Change Healthcare, the dominant clearing house processing the majority of U.S. healthcare transactions, suffered a catastrophic cyber attack and went offline for 60 days. Stedi's drop-in replacement APIs meant healthcare providers could migrate instantly, avoiding financial collapse. Three weeks in, Canter was taking calls from desperate CEOs and CTOs every fifteen minutes, fielding pleas from organizations processing hundreds of millions in pending claims.
That viral moment—while extreme and unsustainable—revealed something fundamental about genuine product-market fit. It wasn't about hype or rapid user acquisition. It was about customers buying the product despite all the things it didn't do. It was about deals closing anyway. It was about urgency so acute that technical rough edges became irrelevant. After Change Healthcare came back online, Canter faced a different challenge: building sustainable, repeatable growth that didn't depend on competitors experiencing catastrophic failures.
Why Building Slow Sometimes Wins: The Case for Patient Product Development
The conventional wisdom in software says you should ship fast, get user feedback, and iterate rapidly. Canter doesn't entirely disagree—but he doesn't entirely agree, either. The tension matters because it reveals something important about how different businesses work.
When Canter's team first began building Stedi, they attempted to create a universal interface for all EDI transactions. After six months, they realized they were building something impossible. The problem space contained hundreds of transaction types, dozens of compliance variants, and unlimited dimensional combinations. No single interface could accommodate everything without becoming incomprehensibly complex.
The answer wasn't to simplify the vision but to rethink the architecture entirely. Instead of asking "How do we build one interface that does everything?" they asked "What are the fundamental building blocks we can expose?" The answer was eight core APIs that could be combined like genetic components. One API converted EDI format to JSON and back. Another mapped one JSON format to another. A third enabled rapid SFTP setup. These components seemed simple until you realized they could be recombined to build virtually anything—the equivalent of discovering DNA's structure and realizing you could now construct different organisms from the same elements.
This architectural insight required patience. It meant continuing to build for an existing major customer rather than the public market. It meant being willing to spend millions refining work that customers saw but the broader market didn't yet know existed. It meant accepting that the 4.5-year period before any public launch represented a kind of "failure" by startup metrics, yet was actually the prerequisite for everything that came after.
The key difference between this "slow build" approach and simply building the wrong thing for five years comes down to one factor: customer validation. Canter wasn't building in a vacuum. Every decision got tested against a real business that depended on it working. This wasn't two founders in a garage arguing about abstractions—it was engineers supporting a customer's actual operations, with real money depending on whether the system worked.
This approach teaches several lessons that contradict startup orthodoxy. First, there are categories of problems where shipping an inadequate solution creates more damage than not shipping at all. Second, sometimes the path to rapid scaling requires upfront patience that others won't tolerate. Third, accumulation effects matter more than anyone admits—getting thousands of tiny details right creates an emergent property that simple solutions never achieve.
The Manufacturing Playbook: Cost Reduction Through Quality
Canter credits discount retail companies like Aldi, Trader Joe's, Costco, and Walmart with teaching him more about business than any software category. This might seem strange until you realize these companies operate in an environment with no margin for error and no way to hide operational inefficiency through high markups. When margins are 2-3%, every detail matters. When overhead is baked into your model, you can't obscure it.
The software industry, by contrast, benefits from fat margins. A SaaS business with 70% gross margins can hide enormous operational waste. This created a dangerous pattern Canter observed repeatedly: venture-backed software companies achieving hypergrowth metrics but with such poor unit economics that they could never reach profitability. Growth at any cost works until the cost becomes unavoidable.
The lesson from Toyota Production System—frequently misunderstood—is that cost reduction isn't the primary goal. The primary goal is quality improvement. When you obsess over reducing defects, improving reliability, and eliminating waste, cost reduction naturally follows. But the reverse isn't true. Cutting costs while sacrificing quality doesn't work because you end up fixing problems repeatedly, paying far more in aggregate than you ever saved.
This philosophy manifests at Stedi in specific ways. The company doesn't have different support programs for customers paying seven figures annually versus those paying $500 monthly. Everyone receives the same hyper-responsive support. This seems economically irrational until you realize that it creates a quality signal that attracts the right customers, eliminates the friction of tiered support programs, and makes the business simpler to operate. The "inefficiency" produces better outcomes than the "optimal" approach.
Canter's principle of "eating glass"—doing things the right way even when economically illogical—operationalizes this philosophy. Some decisions around code quality, security updates, and architectural decisions aren't negotiable. You don't debate whether to apply security patches or maintain dependencies. You do these things because they're right, and you accept that the time investment might not show up as directly attributable revenue.
The flip side reveals another insight: not everything is a principle. Canter distinguishes between principles and preferences. A principle is something you do regardless of circumstances. Integrity, honesty, quality, and doing right by customers—these are principles. Preferences are things you'd like to do when circumstances make them reasonable. For years, Canter preferred not to build a sales function until the product was genuinely excellent. When the business required it, he built a sales team, and it became crucial. The preference was subordinate to the business reality.
High-Agency Hiring: Finding People Who Own the Outcome
The most underrated hiring criterion might be something Canter calls "desire to work"—what others might describe as work ethic, ambition, or ownership mentality. The difference between someone who treats work as a job and someone who becomes obsessed with problems rarely shows up on a resume. It shows up in how they talk about previous failures, whether they blame circumstances or their own decisions, and whether they seem constrained by their current environment or complacent within it.
Canter looks for "caged animals who need to be unleashed"—people who've accomplished things not because their environment was perfect, but despite significant constraints. These are the people whose skills and intelligence get blocked by organizational limitations, not by their own capabilities. The distinction matters because hiring ambitious people into constrained environments creates friction, while hiring ambitious people into the right environment creates momentum.
The challenge in screening for this trait is that people naturally tell you what they think you want to hear, especially in job interviews. When you ask someone about work-life balance, they know what answer sounds good. They'll say they believe in working smart not hard, that they're happy to go above and beyond during crises, and that balance is important to them. Then later, when decisions need to be made, you discover that work-life balance actually was their top priority—and you selected them partly because they told you what you wanted to hear, not because they were actually excited about high-impact work.
Canter's insight is to stop trying to read between the lines and instead listen carefully to what people actually communicate about themselves. Most problems with hiring don't stem from people lying—they stem from founders not believing what people tell them. Someone's priorities are usually evident in how they talk about their career. Rather than trying to detect hidden motivations, Canter focuses on whether the person's stated priorities align with the role's requirements.
Beyond motivation, Canter emphasizes hiring individual contributors and pushing back against the conventional wisdom that flatter organizations don't scale. For years, Stedi operated without formal engineering managers. Team leads spent 90% of their time coding and 10% managing. This worked until scaling required doubling the engineering team, at which point additional management layers became necessary simply for context distribution and on-call rotation complexity.
But adding managers didn't mean abandoning the principle of high-agency ownership. It meant finding managers who embodied the same philosophy—people who could scale judgment and decision-making rather than consolidate it. This required explicit mechanisms like decision records—written documents that captured scope, context, the actual decision, action items, and notable comments. These records became the way Stedi transmitted judgment at scale, teaching new people the reasoning behind decisions rather than just the decisions themselves.
The Detail Problem: Why Reality Is More Complex Than Plans
One of Canter's favorite essays is "Reality Has a Surprising Amount of Detail" by John Salvatiera. The core insight is that almost everything is vastly more complex than you expect until you try to actually do it. Most people have ridden bicycles thousands of times but couldn't draw one that would actually work. People climb stairs constantly but would struggle to build them to code. The gap between understanding something conceptually and executing it operationally is profound.
This applies to organizational processes at every level. If you write a standard operating procedure for updating voicemail greetings, you might outline it in five steps. Then you realize the procedure needs to accommodate different phone systems, needs to stay updated when you switch providers, needs to be accessible to people who need it, needs to live somewhere searchable, and needs to account for the cascade of changes when you move from Slack to Notion. Suddenly you've created fractal complexity—every action spawns multiple downstream consequences.
This connects to what Canter calls the "cascade of miracles problem." Complex products and organizations aren't single miracles—they're cascades of miracles, where each one has to work for the next to function. When you commit to building something, you're committing to solving hundreds of small problems that individually seem simple but collectively create multiplicative risk.
The implication for product building is profound. When you scope work incrementally—sizing features to fit into a single week's work, small enough to demo on Thursday—you're not just improving developer efficiency. You're reducing the number of cascading miracles required before something works. You're making it possible to catch architectural problems before they've created downstream dependencies. You're creating natural points to validate assumptions and adjust direction.
This is why Canter emphasizes continuous incremental shipping, not as an abstract best practice but as a necessary response to how reality actually works. A feature scoped too large creates a cascade of hidden complexity. A feature scoped to demo-day size becomes manageable, testable, and validatable. The difference is the difference between success and failure in complex domains.
Building Organizations That Survive Beyond the Founder
Perhaps the most ambitious part of Canter's vision is building a company that can outlast him—or more precisely, a company that wouldn't collapse if he left tomorrow. This requires translating tacit knowledge into explicit systems, personal judgment into organizational principles, and founder-level taste into teachable frameworks.
Canter explicitly models this on Bezos's achievement with Amazon. When assessing Bezos as a leader, Canter notes that Amazon would suffer from losing its CEO, but the organization's fundamental approach—the six-page memos, the doc-read culture, the principle-driven decision making—would persist. By contrast, companies dependent on a single visionary founder face an existential threat when that person departs or is incapacitated. Building organizational resilience requires institutionalizing judgment.
This is why Canter emphasizes writing. Decision records aren't bureaucracy—they're the mechanism by which organizations distribute judgment at scale. When a new manager encounters a decision point, a good decision record doesn't just tell them what was decided; it captures the reasoning, the context, the tradeoffs considered, and the principles that drove the conclusion. This makes it possible for organizations to maintain consistent culture and values as they grow beyond the founder's direct influence.
The mechanism also works in reverse. By reading PRs and understanding what's being built, by participating in demo days, by reviewing decision records, a founder can scale their own judgment. They don't need to approve every technical decision—but they stay connected to how the organization is reasoning through problems and can course-correct if patterns emerge that violate fundamental principles.
This creates something subtle but powerful: a culture where consistency in reasoning process matters more than consistency in outcomes. Two people might make different decisions given the same information, and both could be right—if they used the same reasoning framework and considered the same principles. The organization becomes coherent not through uniformity but through alignment in how problems get approached.
The Long Game: Why Forever Companies Think Differently
Most founders operate under a five-to-ten-year mental model. They're building toward a Series A, then a Series B, then growth, then either an exit or eventual IPO. The financial incentives and emotional energy of venture capital naturally creates this timeline. Even bootstrapped founders often implicitly assume a 10-year build before achieving a stable, mature business.
Canter thinks in terms of forever. This changes nearly everything about how you operate. You don't cut corners on technical debt if you're planning to run a business for decades—the compound interest of sloppy code becomes unbearable. You don't hire toxic people for their skills if you're planning to be in rooms with them for decades. You don't build features you hate if you'll be supporting them for decades. You don't take venture funding with expectations that don't match your vision if you'll be managing investor relationships for decades.
This doesn't mean forever companies are inevitably better or more important. It means they operate under different constraints and opportunities. The longer time horizon makes certain investments obvious—quality, education, culture—that don't make sense if you're optimizing for a Series B in 18 months. It also eliminates certain pressures that create genuine strain in venture-backed companies: the pressure to grow fast regardless of unit economics, the pressure to pursue markets with lower margins just because they're bigger, the pressure to bring on investors who don't align with long-term vision.
Early in Stedi's history, Canter consciously considered which type of company he wanted to build. He considered what regrets he might have if he built a business that ultimately caused him to want to leave it. The answer crystallized his principles: he would never build a company he'd want to abandon, he'd never take money that felt like subordination, and he'd never pursue a market that required sacrificing what he believed in.
This framework—starting by defining the things you'd never do—is counterintuitive. Most planning begins with what you want to achieve. Canter starts with what you refuse to tolerate. This simple inversion creates surprising clarity about what kind of company can be built and what actually matters to you as a founder.
Conclusion: The Compound Effect of Doing Things Right
Jack Canter's journey from a 16-year-old with a fake business card to the founder of a company processing billions in healthcare transactions reveals a through-line of consistent principle. The specifics—auto parts, EDI standards, healthcare clearing houses—matter far less than the approach. That approach can be summarized as an almost stubborn commitment to doing things the right way, even when doing them wrong would be faster, cheaper, or easier.
This philosophy produces companies that get stronger over time rather than more fragile. It attracts customers and employees who recognize quality isn't accidental. It enables founders to look at their organizations without shame or regret. And it creates the conditions necessary for a company to genuinely run forever—not as a financial instrument but as an operating business that employees and customers are genuinely happy to be part of.
For founders currently building, the core lessons are worth extracting from the specific context: Hire high-agency people who refuse victimhood. Build with real customers when complexity demands patience. Focus on quality before cost reduction and watch costs follow. Scope work to be manageable rather than heroic. Write down your reasoning so judgment can scale. And before anything else, decide what kind of company you can commit to running forever, because that decision will guide everything that follows.
The most sustainable competitive advantage isn't a moat in the traditional sense—it's a commitment to excellence that's so consistent and comprehensive that it becomes economically rational even when individual decisions seem irrational. It's the compound effect of dozens of small decisions made with integrity over decades, creating an organization that becomes stronger and more valuable over time, not despite its commitment to principles but because of it.
Original source: How to build a company you’ll run forever | Zack Kanter (Founder and CEO of Stedi)
powered by osmu.app