AI Engineer World's Fair 2025

Shipping something to someone always wins

Kenneth Auchenberg· Partner, AlleyCorp16:17

Loading slides…

Read the talk

Shipping something to someone always wins

A useful product starts a feedback loop before the big launch: give real people something viable, learn where it fails, and keep the next improvement easy to ship.

From a talk by Kenneth Auchenberg

How do you build a great product in the age of AI?

How do you build a great product when AI makes it easier to build almost anything? Kenneth Auchenberg approaches that question through his experience on the early VS Code team, which he left in 2019, and his subsequent work on Stripe’s developer platform. At the time of this talk, he was a partner at AlleyCorp, applying that product-building experience to early-stage investing.

A conference launch is a visible milestone, but it is a poor unit for thinking about product progress. What matters is how many times a team can try an improvement, put it in front of real users, and learn enough to make the next attempt better. Optimize for iterations with users, not the number of big launches. AI makes that principle more relevant by expanding the opportunities to build and revise.

White slide with a centered sentence emphasizing “iterations,” alongside a speaker inset.Open full source frame
“It’s the number of iterations you crank at a problem.”
0:240:36
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

0:24 · section reference included

Keep every increment useful

Consider the question of how to build a car. One approach starts with wheels, adds a chassis, then an engine, and finally produces a functioning vehicle. Each step advances the construction project, but none of the intermediate steps gives the customer transportation. Until the end, there is no functioning product through which to learn whether those improvements solve the user’s problem.

The alternative starts with a skateboard, improves it into a scooter, then a bike, adds an engine, and eventually reaches a car. The important continuity is the user’s ability to get from A to B.

ApproachIntermediate deliverableWhen users can try transportation
Assemble componentsWheels, chassis, engineAt the completed car
Evolve a viable productSkateboard, scooter, bike, powered transportAt every stage

The intermediate products differ substantially, but each preserves the outcome that makes feedback possible. A continuously viable product gives every increment a chance to teach you something.

Auchenberg regards that continuity as vastly more valuable than reaching viability only at the end—an experiential judgment, rather than a measured multiplier. Real users are getting transported while the product evolves, so the team can learn from their experience instead of building in a vacuum. The practical design problem becomes how to make this product feedback loop as fast as possible.

1:542:04
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

1:54 · section reference included

Build the loop before locking in decisions

At Stripe, Auchenberg’s teams established a feedback loop before committing to major design choices or decisions that would be difficult to reverse. The loop had three requirements:

  1. Real users could see something.
  2. The team could get feedback from those users.
  3. The team could iterate and ship an improvement.

The first deliverable did not have to be the finished product. It had to make this sequence possible.

Auchenberg reports that Stripe’s goal was to complete this loop in less than a day, ideally faster. He says Patrick would push for hours. That is a process target: if the loop cannot run quickly, investigate what prevents users from seeing an improvement and the team from learning from it. Larger organizations make this harder because there is more complexity to manage. The distinction is being able to ship every day, not requiring a release every day.

4:084:21
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

4:08 · section reference included

Find reachable customers, then test the promise

A fast loop needs specific people at its other end. Personas and user research can help describe an audience, but they do not substitute for knowing someone’s name, having an email address, and being able to call. If the team knows only a persona, it still lacks the direct relationship needed to build with users.

Before proposing improvements, understand how those people solve the problem today. Seeing their existing workflow puts the team in their position and gives its hypotheses a basis in actual behavior. Once Auchenberg’s teams understood the problem and had people to work with, they articulated their hypotheses and wrote a PRFAQ—a press release and frequently asked questions document—or a launch blog post.

Writing the launch post early forces specificity. Can you explain what is being built to its intended audience? Can you describe its shape, communicate its value, and position it in terms users understand? For an API product, the team also drafted a rough API outline so customers could react to the proposed interface.

At Stripe, the team sent these documents to early users for feedback before building the product or making a prototype. The document itself gave the team something to ship and customers something concrete to respond to, establishing feedback from the beginning. In his 2025 tooling examples, Auchenberg names ChatGPT and Claude as drafting aids and Bolt as a prototyping option. Those newer tools can help produce the artifacts; the document-first feedback mechanism does not depend on them.

Slide titled “PR/FAQ or launch blog post” with bullets about writing for an audience, drafting an API shape, using AI, and vibe coding, followed by a request for customer feedback.Open full source frame
Draft a PR/FAQ or launch blog post, then seek prospective customers’ feedback.
5:105:19
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

5:10 · section reference included

Explore the best product, then resolve its constraints

Early product exploration can become dominated by legal, compliance, or financial constraints. Auchenberg’s preferred sequence is to first design the best product, then work through the constraints required to deliver it. Starting with every restriction can narrow the product before the team has understood what would make it valuable.

This does not remove the conditions for production release: the product still needs to be financially viable and compliant. It separates responsibilities. Legal counterparts help explain legal risks; other specialists help the team understand their parts of the problem. Product builders remain responsible for judging and shaping the product, using that advice to make informed decisions.

Once there is a product shape to explore, prototyping should be accessible across roles. Where teams previously relied on paper prototypes, AI-assisted coding now makes it easier to try working versions of an idea. In the talk’s 2025 context, Auchenberg points to Bolt as a way for product leaders, engineers, and people focused on strategy to make something tangible quickly. The expectation to prototype no longer belongs only to people with a technical background.

7:177:29
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

7:17 · section reference included

Make a few users successful

Once users have something to try, the quality of feedback matters as much as its speed. A dashboard can show activity without explaining what a customer struggled to do. In early Stripe prototypes, the team visited customers’ offices and shadowed developers integrating the APIs. Watching the integration work exposed difficulties that aggregate metrics alone could not explain.

When an office visit was impractical, the goal remained direct access and detailed understanding:

  • Shared communication: Bring customers into Slack or Discord so questions and problems can reach the team quickly.
  • Personal availability: Texting made some of Auchenberg’s strongest customer relationships immediate and accessible.
  • API observation: Monitor API responses closely to see where customers get stuck, then work with those customers to understand the difficulty.

These channels supported intensive work with a small set of users, rather than shallow feedback from an indistinct audience.

Early product work, in this account, should feel like running a professional services firm. Auchenberg illustrates the focus as delivering a piece of functionality to five people. His diagnosis is that the greater early danger is building something that is not useful at all, rather than something useful to only a few people. Narrow attention gives the team a chance to make the product work exceptionally well for someone.

The same approach applied to VS Code. Auchenberg worked through direct messages and shadowed users to understand why a CSS token did not receive the right completion or why the JavaScript debugger failed. Those are specific failures in specific workflows. Making a few users successful required investigating them at that level of detail.

White slide reading “Make a few users happy,” with “few users” bolded and the speaker visible at lower left.Open full source frame
“Make a few users happy.”
8:589:06
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

8:58 · section reference included

An API commits your customers, too

The cost of changing a product depends on what customers have built around it. Moving a button is comparatively easy. Changing a shipped API or data structure can force customers to change their own systems. For platform products, this makes early feedback on interfaces and abstractions especially consequential.

Stripe’s focus on the discerning developer meant working with a small group capable of helping the team build a surprisingly good developer experience. A trusted customer group gives the team people with whom it can closely iterate on API design. Auchenberg illustrates the asymmetry with an API change that takes its provider an afternoon but could require a six-month migration for a customer. This is a hypothetical contrast, not a reported migration benchmark: the burden comes from the customer’s dependence on the provider’s APIs and data structures.

10:5111:05
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

10:51 · section reference included

AI accelerates the work without removing the loop

How does this apply specifically to AI? Referring to illustrations from an earlier conference talk, Auchenberg describes the engineering, product, and design tripod changing shape. Responsibilities that were more isolated are blurring as AI lets people across all three functions build and iterate together.

His position is that the underlying craft of product building remains the same. Whether a team uses AI to build or is building an AI product, it still needs to talk to users and maintain a feedback loop. AI can accelerate the activities inside that loop without replacing the need for it.

His toolkit includes ChatGPT, Bolt, and Cursor, alongside Listen Labs for customer research and Granola for meeting notes. These tools help with different parts of product work. A future agent might accelerate more of the cycle, but the job remains getting useful changes in front of people and learning from their responses.

11:5512:09
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

11:55 · section reference included

Cheaper implementation raises the value of judgment

Auchenberg predicts that as the cost of writing code approaches zero, product management becomes more important. That is a directional prediction about implementation costs, not a measured cost result. If building becomes less of a bottleneck, deep customer knowledge and the ability to get feedback quickly become more consequential in deciding what deserves to be built.

White slide stating that product work still needs to get done and is “more important” than ever, with a speaker inset.Open full source frame
Product work is more important than ever.

The same applies to AI-native development that puts more emphasis on specifications than on code. Faster implementation does not supply the knowledge needed to write a useful specification. Knowing whom you are building for becomes more valuable when you can iterate faster. The tools need to support that understanding and the feedback loop around it.

13:2713:43
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

13:27 · section reference included

Turn product judgment into something people can use

From his investment perspective, Auchenberg connects these requirements to the AI-native founders he has written about. His proposed capabilities apply to product leaders as well as founders: taste, deep customer knowledge, high iteration velocity, distribution, and the ability to sell. Together, they describe more than the ability to produce software. They describe the ability to shape a useful product, reach its customers, and keep improving it—work that closely resembles product management.

Shipping still requires aligning many conditions. Auchenberg cites a post attributed to Michelle at OpenAI that describes shipping as a low-entropy state: there are many ways for a launch to be derailed and relatively few ways for everything to line up. Its challenge is direct: “The universe does not want you to ship, but you must do it anyway.” Product work includes finding that path while keeping the customer feedback loop intact.

In a heated product review, another abstract argument may leave the team exactly where it started. Shipping something to a real person creates evidence the discussion did not previously have. Return to the skateboard: identify the smallest viable product shape that someone can actually use, put it in their hands, and let their experience inform the next iteration.

14:1314:23
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

14:13 · section reference included

Resources

From the talk

  • Making sense of MVPArticle

    Henrik Kniberg explains the skateboard-to-car metaphor and how early product increments generate customer feedback.

  • Historical developer survey covering development environments, including VS Code's leading position among respondents.

Transcript download
Full transcript

Loading transcript…