The AI Record
we did a bake-off, two engineers completed the same integration task: add payment method support for a frontend-facing API. One engineer used vanilla Claude Code, while the other used Claude Code with a reusable set of prompts built from our prior experience. The difference was substantial: the vanilla setup required roughly 20 days of engineering effort, compared to 4 days when using the reusable prompts.

StripePublished by the organization itself (post), no named author

Post: Stripe's Payment Method Factory: Orchestrating agents for repeated, custom integrations, Stripe Dot Dev Blog (stripe.dev); authors David Dunne, Xenofon Vourliotis and Sai Samant, September 30, 2026, at Hardened reusable 'one-shot' prompts.

  • 20 days engineering effort, one bake-off task (post dated 2026-09-30). A person approves

Checked against the source [ Grade B ] Said in the last year

Filed under

How this was checked

Checked against the source by a first reader, then confirmed independently by a second reader who fetched the source without seeing the first reader's notes (Independent review agent (Claude Sonnet), blind second pass from passage text and citation only, no repository access, 2026-11-08).

Found verbatim on the live Stripe Dot Dev post, in the hardened reusable prompts section. Stripe's own engineering blog, written by its authors.

How to cite this passage

Stripe, “Stripe's Payment Method Factory: Orchestrating agents for repeated, custom integrations”, Stripe Dot Dev Blog (stripe.dev); authors David Dunne, Xenofon Vourliotis and Sai Samant, 2026-09-30, at Hardened reusable 'one-shot' prompts. https://stripe.dev/blog/stripes-payment-method-factory-orchestrating-agents-for-repeated-custom-integrations Archived at https://the-ai-record.com/passages/stripe-bake-off-two-engineers-same-integration-2026

More from the same source

As code generation becomes faster, code reviews started becoming a bottleneck. We help reviewers by keeping pull requests small and providing all relevant context, but ultimately, we found that giving agents the tools to test their integrations autonomously gives the reviewer the most confidence.

StripePublished by the organization itself (post), no named author

Post: Stripe's Payment Method Factory: Orchestrating agents for repeated, custom integrations, Stripe Dot Dev Blog (stripe.dev); authors David Dunne, Xenofon Vourliotis and Sai Samant, September 30, 2026, at Building confidence.

Checked against the source [ Grade B ] Said in the last year Passage page

The factory we built has so far created three new payment method integrations and migrated ten existing integrations to our modern stack, demonstrating its effectiveness for legacy migrations, too. The payment method factory reduced integration timelines from as long as six months to two-to-six weeks.

StripePublished by the organization itself (post), no named author

Post: Stripe's Payment Method Factory: Orchestrating agents for repeated, custom integrations, Stripe Dot Dev Blog (stripe.dev); authors David Dunne, Xenofon Vourliotis and Sai Samant, September 30, 2026, at Article.

  • 6 months integration timeline, before: as long as; after: two to six weeks (post dated 2026-09-30). A person approves

Checked against the source [ Grade B ] Said in the last year Passage page

Our first approach used a high-level orchestrator agent for this role. It worked, but it was expensive, slow, and sometimes unreliable. … We learned that although an LLM can orchestrate a workflow, predictable coordination is better implemented in code.

StripePublished by the organization itself (post), no named author

Post: Stripe's Payment Method Factory: Orchestrating agents for repeated, custom integrations, Stripe Dot Dev Blog (stripe.dev); authors David Dunne, Xenofon Vourliotis and Sai Samant, September 30, 2026, at Building the factory.

Checked against the source [ Grade B ] Said in the last year Passage page

Something wrong? Report a correction. JSON: /api/v1/passages/stripe-bake-off-two-engineers-same-integration-2026.json