The first Chris Strahl product story on the public record is shaped like a cylinder. In 2004, as a graduate student at Washington State University, he joined a business-plan team proposing Key-Wi, a portable keyboard that rolled an ordinary interface into something novel. The team won its preliminary league and $300. It was hardly a prophecy of venture-backed software, but it established the habit: take a familiar object, pull apart its assumptions, and rebuild the way its pieces meet.
Two decades later, Strahl is still working the joins. As co-founder and chief executive of Knapsack, he focuses on the seam between design and engineering, a place where a great deal of expensive nonsense can accumulate. A button exists in a design file. Another button exists in code. A third exists in the documentation. Each is perfectly intelligible to its owner. Together, they may be strangers.
Strahl's career has been a long education in this particular absurdity. He moved from technical program work into Portland's Drupal scene, founded the technology firm Orchestra, managed major enterprise accounts at Acquia, and later held practice and business-development roles at Phase2. His Drupal profile records years of conferences and work as the Drupal.org redesign project manager. Before “design systems” became a tidy software category, he was already learning how open communities, enterprise clients and technical teams negotiate ownership.
Key-Wi wins a preliminary WSU business-plan round.
Orchestra, Acquia, Phase2 and Tag1 turn technology into a client-facing education.
Basalt begins building bespoke design systems for large organizations.
The consultancy closes; Knapsack becomes the product company.
Knapsack announces a $10 million Series A.
The problem kept wearing different clothes
At Basalt, the consultancy Strahl led from 2017, the same organizational defect appeared across large clients. Designers worked in one universe, engineers in another, and the shipped product became the uneasy border. Teams patched the separation with meetings, documentation and specialized tools. Then they did it again on the next project.
One engagement supplied the useful clue. A client wanted its content-management interface to recognize changes to a component automatically. If a button gained an extra-large option, the editing form should gain that option too. The team represented the component with a JSON schema - less a picture of a button than a contract describing what the button could be. The schema could travel where a static mockup could not.
That distinction became central to Knapsack. A component in Figma is not necessarily the same thing as a component in React, and neither guarantees what appears in production. The durable asset is the agreement between them. Strahl later called a design system “the connective tissue” of what a company is building. It is an anatomical metaphor for a managerial problem: parts are only useful if they can move together.
The year the bench became a laboratory
Then the market performed an experiment of its own. When COVID arrived in 2020, Basalt's agency pipeline collapsed. In Strahl's account, bookings fell from roughly $800,000 to less than $200,000 almost overnight. The firm took a PPP loan of nearly $400,000. Suddenly a consultancy built to keep skilled people busy had an abundance of bench time.
The team used it to turn its accumulated tools into a repeatable product. At first, they did not know whether the software would remain an advantage for the agency or become the business itself. By summer, the choice had sharpened. The whole company discussed it; a five-person leadership group aligned around becoming a product company. Basalt shut down in September. The new corporation formed in October. Fundraising began while the new product had more conviction than revenue.
The first outside round closed in January 2021: $2.3 million at a $7.5 million post-money valuation, with one or two customers and about $11,000 in annual revenue. This was a clean break, not a consultancy wearing a software hat. Only four people from the old agency ultimately continued among the 12 full-time employees in the young product company.
Knapsack's first selling motion also needed rebuilding. Large enterprises understood their design-system pain but were not accustomed to buying a SaaS category for it. In mid-2021, the company stopped insisting that the whole organization walk through the door first. It offered an inexpensive team plan, landed with five or ten users, and let success make the internal argument.
The smaller doorway changed the business. By November 2021, Knapsack counted about 15 enterprise customers plus a couple dozen smaller accounts. Its largest customer had more than 700 seats and paid roughly $200,000 a year. Strahl reported 190 percent net dollar retention, a young company's evidence that one team's experiment could spread.
A microphone beside the product
Strahl's other durable project began in 2019 with a microphone and modest expectations. The Design Systems Podcast placed him in conversation with the practitioners doing the work at companies such as Meta, Pinterest, Dropbox, ServiceNow and H-E-B. The first episode, recorded with co-founder Evan Lovely, was rough enough that both men still tease it. Five years later, it had become a professional commons as much as a company show.
The podcast reveals something useful about Strahl's operating style. He likes specifications, but not isolation. The guests are designers, engineers, product managers, accessibility specialists and organizational leaders. Their problems refuse to respect department charts. The show, now called the Patterns Podcast, gives those overlaps somewhere to be examined in public.
Community is not a decorative word in his biography. He came from Drupal, where software and belonging arrived together. He hosts gatherings and conversations, calls himself a tabletop-game dungeon master, and is described in public bios as an occasional river guide. The combination is almost suspiciously on theme. All three activities involve a party, a route, some constraints and the possibility that somebody will wander into trouble.
His advice about fundraising is equally practical. Investors should be chosen for the access or ability they add, he has argued, not merely their check. When the process becomes stressful, his prescription is to double down on the parts of life that bring peace or harmony. It is not the standard chest-beating founder maxim. It sounds more like something learned by a person who has already watched one business model vanish in a week.
When software starts making software
Knapsack announced a $10 million Series A in October 2025, led by Builders VC, bringing its company-reported funding total to $20.8 million. The announcement said annual revenue had grown 2.6 times and that Fortune 500 product teams were using the platform. More revealing than the round was the new vocabulary around it: intelligent product engine, ingestion, context, agents.
Strahl's AI argument follows directly from the old button problem. A generative model can draw a persuasive interface, but persuasion is not compliance. It may invent a color, ignore an accessibility requirement or produce code that resembles the company's software without belonging to it. Fast ambiguity is still ambiguity; it merely arrives before lunch.
His proposed answer is an authoritative layer containing real components, properties, tokens and usage rules. Knapsack's model-context-protocol server is intended to make that organizational knowledge available to the tools producing interfaces. The company released its Intelligent Product Engine in 2026, moving the project beyond the limited beta announced with the Series A. The ambition is for the design system to graduate from advice for people into usable context for both people and machines.
This is a larger claim than syncing design files with code, yet it preserves the same suspicion: more tools do not automatically produce more agreement. In Strahl's five-year view, teams will compose products against live component graphs instead of passing static mockups from one discipline to another. Agents will generate surfaces, but policies, performance budgets and brand constraints will determine whether those surfaces can ship.
There is a tidy temptation to call this foresight. The less romantic explanation is more convincing. Strahl has spent years close enough to enterprise production to watch small disagreements become large invoices. The thousand repeatable losses - the wrong button, the drifting style, the stale documentation - taught him where complexity hides. AI changes the speed and author of the output. It does not repeal the need for a shared truth.
The cylinder from 2004 has disappeared, but the original instinct remains. Find the structure inside the familiar object. Make the parts legible to one another. Give people rules that help them move, rather than rules that merely tell them when they are wrong. The grandest version of Knapsack's future is an infrastructure layer for digital production. The human version is simpler: fewer talented people spending their afternoons reconciling three slightly different buttons.