Case study: a travel agency backend in one afternoon

The brief: a boutique travel agency needed a marketing site backend: browsable destinations, a lead form their sales team would actually check, and Swedish + English content. Budget: small. Deadline: yesterday.

The build (41 minutes, mostly conversation)

The developer connected Claude to their MCP URL and described the system. The assistant scaffolded:

• destinations: resource with title, summary, image, price_from, region; public read, cached.
• leads (form endpoint from the lead-form template): name, email, phone, destination, message, consent.
• Email notifications on each lead, with quiet hours so the owner's phone stays silent at 3am.
• Localization en + sv; the seeded English destinations were AI-translated to Swedish in the editor (reviewed, then published).

The numbers

• 6 tool calls to a working API · 0 lines of backend code
• ~40 destination records imported from a spreadsheet via paste-import
• Swedish translation: ~2,400 tokens, a few cents, estimated up front in the cost popup

What mattered afterwards

The agency's coordinator edits destinations in the CMS without seeing a single developer screen (a manager role limited to content). Leads flow to email and the submissions table. When they later asked for "last-minute deals", it was one more conversation with the AI, not a contract change.