← Back to library

Build and launch a hobby web app with a hosted coding agent

Günter Richter, a data strategy consultant who last coded seriously in the early 2000s, built his app on Replit's paid plan in the final week of 2024. He described features, fed error messages back, switched image hosting when the first choice failed, then added site tracking, a front page and a mailing-list hook. Total spend: $35.82 plus a custom domain.

  • OutcomeGo from a feature list to a live web app with storage, analytics, sign-up email integration and a landing page, without writing the code yourself.
  • SetupAn afternoon+
  • LevelStarter
  • CreditGünter Richter
View original
Works with
Custom agent

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You have an idea but no recent coding skills
  • No-code builders hit limits on your interface
  • You want a working app rather than a mock-up

Not for: Apps handling payments or health data without expert review; Teams that need a maintainable codebase from day one

What do you need, and what do you get?

You need

  • A list of key features
  • A paid account on an agent-based app builder
  • API keys for any services you connect

You get

  • A deployed web app
  • A landing page from your brief and copy
  • An integration with your email tool

How does it work, step by step?

  1. List the featuresWrite down the must-haves before opening the builder.
  2. Iterate in conversationReview each version and ask for refinements; the builder checkpoints major changes so you can roll back.
  3. Paste errors straight backWhen something breaks, give the agent the error message verbatim.
  4. Steer on servicesIf a storage or third-party choice fails, suggest an alternative you trust.
  5. Use the cheaper helper for small fixesThe author found the assistant mode far cheaper than the full agent for minor edits.

The prompt

Our own prompt, inspired by Günter Richter and written to work in Custom agent. Values in lime are placeholders.

Prompt0 variables
I want a working site named [name]. Core features: [list]. Use a free-tier database and image storage unless I say otherwise. After each major change, tell me what you changed and how to test it. If an integration fails twice, stop and suggest an alternative instead of retrying. Before launch, list how user data is stored and protected.

Inspired by Günter Richter: How I Used Replit to Build a Fully Functioning Web App. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • The agent sometimes looped on integration problems; stepping away and retrying with a fresh request helped.
  • Costs climb once monthly credits run out, so watch usage.

Our take

Günter Richter's account is valuable because it comes from someone outside software, with real dollar figures and real dead ends rather than a polished success story. Describing features in conversation, pasting errors straight back and letting the agent propose a mini plan to validate are habits any non-coder can copy. His tip to use the cheaper assistant for small edits is the most practical takeaway, since burning the expensive model on copy tweaks adds up. Before inviting real users, have someone check how sign-ups, passwords and stored images are secured, because agent-built apps often skip that unless asked. Keep checkpoints so rolling back a bad change is easier than describing it away. Confirm that the mailing-list hook has a real double opt-in and an unsubscribe path. Move off the prototype host once traffic or personal data grows. Write down what you spent and what still feels fragile, so the next hobby project starts wiser.

Where the time goes back: The agent removes the server, interface and data-layer learning curve that kept the author from building for two decades.

FAQ

What did it cost?
The author reports $35.82 in total, with storage and database on free tiers.
How did he connect the mailing list?
He had the assistant write custom code against the email platform's API, which worked within about half an hour.

Source and credit

Inspired by Günter Richter. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
How I Used Replit to Build a Fully Functioning Web App
Creator
Günter Richter
Published on
thedatacoach.substack.com (Substack)
Original date
Jan 20, 2025
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Custom agent
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminSkill✓ AI dry run

Keep your coding agent on current web platform features

Add Google Chrome's modern-web-guidance skill to Claude Code, Codex, Cursor or another coding agent so that before it writes front-end code it looks up a vetted guide for the pattern at hand, uses built-in browser features such as native dialogs instead of old JavaScript workarounds, applies fallbacks only where browser support requires them, and tells you which guides shaped the change.

Credit: GoogleChrome

Minutes
Operations & AdminWorkflow✓ AI dry run

Build a funding database from grants found online

Have an automation agent search the web for grants by country and add each one to a structured table you can review and publish.

Credit: u/Ste_XD on r/zapier

Under an hour
Operations & AdminRoutine✓ AI dry run

Publish the sprint changelog from completed tickets

On a schedule, pull completed tickets, decide which are user-facing, draft the changelog from ticket context, and wait for your review before publishing or emailing users.

Credit: u/Senseifc on r/ClaudeAI

Under an hour