Ask Archie and the birth of BootApp

BootApp didn't start with code. It started with a conversation about how another site, Ask Archie, is run, and Archie stayed part of the process from the first idea to the last feature.

The starting point: Ask Archie's way of working

A friend runs Ask Archie as a live site on Cloudflare. The way it's run is unusual: an AI assistant does the hands-on work through Cloudflare's API and the wrangler command-line tool, while the owner only handles the account, payments and approvals.

That approach became the brief for BootApp:

• Cloudflare is the home of the site. Files are edited locally and published with wrangler deploy. There's no Git repository for the code.
• The owner stays in charge. Anything that costs money, changes DNS or deletes data is asked about first.
• Secrets never go in chat. API tokens live in environment variables or Cloudflare's secret store.
• Heavy jobs go elsewhere. Ask Archie uses GitHub Actions for work that's too big for a Worker, such as compiling software. BootApp keeps that as an option for later.

Planning with Archie

With the foundations in place, the plan was worked out with Ask Archie, one phase at a time.

The admin wish list. "An app with user accounts" became a structured list: user management, a dashboard with charts, content management, activity logs, settings, feedback and support, two-factor security and analytics.

Splitting it into phases. Archie helped separate what could be built straight away from what needed a decision first:

1. Phase 1, build now: user management, a dashboard, an activity log and admin-only access.
2. Phase 2, decide first: what content to publish, which settings matter, how feedback should work, which kind of two-factor login, and which analytics tool.

Making the Phase 2 decisions. Archie helped land on clear answers:

• BootApp would be a developer site focused on workflow and marketing solutions, with case studies, tutorials and resources.
• Settings would start simple: site name, a sign-up switch and a site-wide notice banner.
• Feedback would come through a contact form.
• Admins would use an authenticator app for two-factor login, with no email set-up needed.
• Analytics would be Cloudflare Web Analytics, with no cookies and no consent banner.
• The look should be modern, responsive and easy to use.

Building with Claude Code

Each plan from Archie went to Claude Code, which wrote the code, tested it on a local copy and deployed it to Cloudflare. The results, along with any questions, went back to Archie to shape the next round. The owner sat in the middle of the loop, approving changes and making the calls only a person should make.

How BootApp was built covers the technical side in detail.

Why it worked

• Planning and building were kept apart. Archie focused on what and why; Claude Code focused on how. Neither had to do both at once.
• Decisions were written down. Each phase ended with a clear list, so nothing was lost between conversations.
• One phase at a time. Shipping Phase 1 before deciding Phase 2 meant the later decisions were based on something real.
• A person stayed in control. Costs, DNS changes and publishing always waited for a yes.

The result

In a single day, BootApp went from an empty Cloudflare account to a live site with accounts, an admin area, articles, a contact inbox and two-factor login. It all started with copying how Ask Archie works.

Want to work this way on your own project? Get in touch.