24 Hours Inside Stripe: How They Build So Fast

Summary

Stripe scales engineering output by combining small, accountable teams, shared infrastructure, strong internal documentation, developer-productivity tools, and increasingly capable AI agents. Rather than coordinating thousands of engineers as one large team, Stripe assigns ownership to organizations and teams that build on one another’s systems.

A major strategic choice is to invest in developer productivity (“dev prod”) as an internal product function. Its tools reduce friction in coding, research, planning, testing, and code review. Stripe’s newer tool, Orbit, brings several of these activities together so engineers can plan work collaboratively, delegate tasks to agents, and manage multiple projects in parallel.

AI speeds up implementation, but Stripe’s leaders stress that it does not remove the need for human judgment. Engineers still need to determine what customers need, shape the product, coordinate work, review code, and ensure systems are reliable and extensible.

Operating Model and Playbooks

• Small teams with clear ownership: Larger organizations own areas such as payments, treasury, data, security, and Link. Teams within them typically have 6–10 engineers and own a defined part of the system or a deliverable for other teams or customers.
• Build on shared infrastructure: Teams avoid recreating foundational capabilities. Stripe’s products act as financial building blocks that other teams—and customers—can use to build more complex services.
• Treat internal tools as products: The dev prod organization builds tools for Stripe engineers, including cloud development environments and AI-assisted research, coding, and review. Stripe considers this investment a way to help teams deliver to customers faster.
• Use documentation to scale organizational knowledge: As the company grew and knowledge could no longer stay in people’s heads, teams created documentation and systems to make it searchable. AI agents can now use that accumulated context to help engineers understand internal systems.
• Plan before delegating to agents: In Orbit, an engineer can research a problem across code and internal documentation, draft a multi-step implementation plan, share it for teammate comments, and then hand the approved plan to an agent.
• Keep humans responsible for product judgment: Agents can produce workable but overly utilitarian solutions. Engineers and product teams refine plans, simplify designs, reuse existing systems, and make sure the result meets customer needs.
• Ship with safeguards: Changes require code review and tests. Deployments begin on 1% of Stripe’s boxes; unusual errors can pause the rollout and trigger a rollback and investigation. The aim is to isolate failures rather than expose the whole system at once.
• Design for extension: Good code should be understandable and flexible, with interfaces that let other teams build on it. For example, a payments system should support additional card networks without requiring a ground-up rebuild.
• Maintain a learning mindset: Stripe’s stated operating principle, “we haven’t won yet,” reflects the need to keep adapting as technology and the company change.

Tools and Examples

• Minions: Agents that spin up a remote development environment, run tests, write code, and create a pull request for an engineer to review. They were initially suited to smaller, contained tasks.
• Gru: Stripe’s internal code-review engine, used to help identify problems in code changes.
• Orbit: Built to support more complex, multi-step work than Minions alone. It combines research, planning, collaboration, agent handoffs, and visibility into parallel projects.
• Trailhead: Internal documentation tool.
• Kai: Internal assistant that can review team email lists and surface notable information.
• Compass: System for tracking project progress.
• Stripe Terminal in the office: Stripe uses its own payment product to pay for coffee, giving employees a practical way to experience the product and provide feedback.
• Stripe Projects: A product built by a product manager, tech lead, and small engineering team. The product manager created a CLI prototype and used it in user-research sessions, updating the prototype between sessions based on feedback. The team launched the product in 7 weeks, using AI agents throughout the process.

Metrics and Timelines Cited

• Stripe has thousands of engineers and was described as shipping hundreds of products, features, and improvements. The video also refers to hundreds of products shipping in a year.
• A typical engineering team has 6–10 engineers.
• One engineer said they commonly work on 3–7 projects at a time with Orbit.
• An agent may work on a delegated task for as long as 12 hours, pausing to request input if needed.
• Deployments begin on 1% of boxes before broader rollout.
• Stripe was described as merging and deploying code every minute, or close to it.
• Stripe Projects launched in 7 weeks.
• A demo showed Orbit doing research that the engineer estimated might otherwise take 30 minutes or more. This was an illustrative estimate, not a measured company-wide productivity result.

Actionable Takeaways

• Keep teams small and give them clear ownership, while investing in shared systems that let them move independently.
• Treat internal engineering tools as a strategic product, not merely overhead.
• Document systems and decisions so knowledge can scale beyond individual employees—and so AI tools can use that context.
• Use agents for execution, but establish human checkpoints for planning, review, product judgment, and security.
• Introduce changes gradually, monitor for anomalies, and make rollback part of the deployment process.
• Optimize for reusable, understandable interfaces rather than code that solves only the immediate task.
• Shorten feedback loops by prototyping quickly and incorporating user-research feedback into the next iteration.

Sources and Participants

Host Peyton of Not My Business; Stripe employees Adam, Alex, Alicia, Michelle, and Romi (also rendered as “Ramy” in the subtitles). The host also promotes Clay’s Wedge, a free two-week go-to-market accelerator.