Same work, two-thirds less of it

Here is what a release week looks like on either side of the switch.

Without Acme

  • Config lives in three places and drifts apart
  • Every environment needs a hand-written script
  • Nobody can say who changed the staging key
  • Rollbacks mean a call with the one person who knows
  • Onboarding an engineer takes most of a week

With Acme

  • One file describes every environment
  • Preview environments open with the pull request
  • Every change is attributed and reversible
  • Rollback is one command, from anyone on call
  • New engineers deploy on day one
Median setup time across 1,200 teams: 9 minutes
">

The prompt

Build a two-column contrast section with Tailwind CSS that sets the old workflow against the new one. A centered heading and subline, then two panels side by side on md and up. The left panel is muted — dashed border, neutral-50 background, an "Without Acme" label, and a list of five pain points each prefixed by a small grey ✕ tile, with the text in a softer grey. The right panel is the hero: solid neutral-900 background, a "With Acme" label in a translucent pill, the same five topics rewritten as outcomes, each prefixed by a white ✓ tile, and a footer strip inside the card quoting a hard number such as "Median setup time: 9 minutes". Keep both lists on the same baseline so the rows read across, and stack them with the muted panel first on mobile.

Paste it into Claude, Cursor, v0 or any AI coding tool. Prefer the finished markup? .

More features / bento prompts

All Features / Bento prompts →