Build a polished business website on a US$50 software budget

“A $10,000 website for under $50?” Start with the part you can control: a useful, polished brochure site and a tightly defined software budget. This guide takes a fictional service business from a clear brief to an agent-built site, a preview and a Cloudflare deployment. The budget sets aside US$20 for an optional first month of Claude Pro, US$15 toward a domain and US$15 in reserve; static hosting uses Pages Free. Existing subscribers can use their current tool and the included pages.dev address with no additional software or hosting purchase. You supply the business facts, make the design choices and review the result before it goes live. The $10,000 figure is a creative brief, not an appraisal or a claim of equivalent agency work. The budget is in US dollars, excludes your labor and tax, and covers one initial month; renewals and extra services come later.

Before you start

• An existing AI coding assistant you are allowed to use for this work, with enough included usage. Optional newcomer example: Claude Pro is US$20/month in the US and includes Claude Code; regional prices, tax and usage limits vary. No paid model API is needed. This guide does not require buying another subscription.
• A Cloudflare account on the Free plan, a computer with a supported Node.js/npm installation, and permission to create one isolated Pages project. Existing production sites should remain outside its scope.
• Approved business facts, a real contact destination and rights-cleared images. Keep customer lists, private prices, passwords and account credentials out of the brief and generated public files.

Tools: AI coding agent, Cloudflare Pages, Wrangler. Use an assistant approved by your organization. This text-based first version does not require new integrations; account features and data policies still apply.

The workflow, step by step

1. Give the site one job and a fixed budget

   Use a fictional example, Cedar & Finch, a small office-organizing service. Its website needs to explain three services, show approved project photos and invite a consultation enquiry. It needs no checkout, customer accounts or admin system. Write the goal in site-brief.txt, with the intended customer and the action they should take. Ask the agent: 'Propose a one-page sitemap and list missing facts before coding.' Expect a short content outline and questions. Reject invented testimonials, credentials and starting prices. Set the incremental spend cap to US$0 for this version; the US$50 newcomer envelope is a planning ceiling, not permission to add purchases. Keep a requested booking system on the future-work list until its costs and responsibilities are understood. If using Claude Pro, keep extra paid usage off; wait for included limits to reset rather than adding credits.

2. Turn approved facts into a specific design direction

   Give the agent your approved service descriptions, coverage area, contact route and images. Ask for two concise visual directions, then choose one. For Cedar & Finch, the example brief calls for warm paper tones, generous spacing, dark readable text and one large genuine workspace photo. Ask: 'Sketch the hero, service section, process and contact block; explain the hierarchy at phone width.' Expect a visible first draft, rather than just a description of how polished it will be. Check whether a visitor can identify the service and next action immediately. Replace vague feedback such as 'make it premium' with concrete edits: shorten the headline, enlarge the photo, remove decorative boxes or give the enquiry link more space.

3. Ask the agent for the smallest complete site

   Request plain HTML and CSS, minimal JavaScript and a deployable dist folder. Include a useful title, description, semantic headings, image alternative text, visible keyboard focus and a real 404 page. Ask for a README explaining how to edit and rebuild it. Expected output is a folder you own and can inspect, not a screenshot or a hosted editor that requires another paid plan. Open the generated files and check every public claim against your fact sheet. Use a visible email or telephone link for the first contact route; replace all demonstration destinations before publication. A form that merely displays 'sent' is not a working enquiry channel. Avoid adding databases, analytics, paid widgets and stock libraries simply because the agent suggests them.

4. Review the finished pages before connecting deployment access

   Ask the agent to inspect the site at narrow phone and desktop widths, then review it yourself in a browser. Read the headline aloud. Use only the keyboard to reach every link. Enlarge text, check contrast and verify that the layout survives long service names. Inspect every image and its permission record. Expected output is a short defect list with fixes, plus the final deployable folder. Check that dist contains only intended public assets: no .env files, internal notes, private source samples or credentials. Search for placeholders and test the contact destination. AI review can help find defects, but an agent saying 'all good' does not establish accessibility, legal compliance or successful customer delivery.

5. Choose static hosting and understand what free covers

   Cloudflare documents free, unlimited Pages static-asset requests when no Function is invoked. Pages Free currently allows 500 builds per month with one concurrent build, up to 20,000 files and a 25 MiB maximum individual asset. Our small brochure site stays static; do not silently turn it into an application. Pages Functions use the Workers request allowance, shared with other Workers: Free currently permits 100,000 requests daily, resetting at midnight UTC, with Workers Free CPU limited to 10 milliseconds per invocation. These are service allowances, not unique-visitor counts or a complete database budget. Ask: 'Confirm this output needs no Functions, database or paid service.' Expect an inventory. If you later add an API, plan authentication, validation, abuse controls, storage, quotas and failure behavior separately.

6. Connect the deployment API with limited authority

   Use Cloudflare's documented Direct Upload workflow. Wrangler handles the API-backed asset upload; you do not need to write the upload protocol yourself. Create a custom token with Account → Cloudflare Pages → Edit, select only the intended account and give it a short expiry. This permission can affect Pages projects in that account; it is not a promise of project-only isolation. Have the operator or protected CI environment provide CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID without pasting values into chat, source files, browser JavaScript or screenshots. Never use a Global API Key for this workflow. Alternatively, an operator can authorize Wrangler's browser login. Ask the agent to show the target account, project and planned commands before execution. Expect a reviewable plan without credential values. Revoke the token when it is no longer needed.

7. Upload a preview, inspect it, then approve production

   Before uploading, use a clean isolated deployment folder and confirm there is no functions/ directory in Wrangler’s working directory and no dist/_worker.js. Wrangler can pick up server-side code from these locations; stop and review the dynamic-service scope and limits if either exists. Create a uniquely named Direct Upload project with 'npx wrangler pages project create'; set main as its production branch. Upload dist with 'npx wrangler pages deploy dist --project-name=YOUR_PROJECT --branch=review'. Replace YOUR_PROJECT with the actual name. Inspect the returned preview URL on a phone and desktop, including its images, links and missing-page behavior. Preview addresses are not automatically confidential: upload only public-approved material. After human approval, deploy the same reviewed folder with --branch=main and read back the live pages.dev URL. The REST endpoint is POST /accounts/{account_id}/pages/projects/{project_name}/deployments; Direct Upload requires a manifest referring to uploaded content hashes, so a single POST containing arbitrary source files is insufficient. Direct Upload projects cannot later switch to Git integration; that requires a new project.

8. Keep the address simple and make maintenance repeatable

   The included pages.dev address keeps this example within its zero-incremental budget. A custom domain is optional and registration is a separate recurring purchase; obtain its actual first-year and renewal quote before changing the arithmetic. Cloudflare Registrar charges registry/ICANN costs rather than making every name free. If you add a domain, associate it in Pages and follow the documented DNS path: apex domains require Cloudflare nameservers, while an externally managed subdomain can use a CNAME. Preserve existing email and other DNS records. Keep the source, approved dist folder, deployment identifier and checklist together. For the next edit, ask the agent for a small change, inspect the preview and repeat the same checks. Assign someone to refresh business facts and dependency/security decisions. Publishing once does not complete maintenance.

Try it with a sample

Use this synthetic input to see the distinctions your output should preserve.

What a good result should preserve

A prompt you can adapt

Build a small static brochure website from the approved fact sheet below. First return a one-page outline, missing facts and two visual directions. Wait for a direction choice before writing files.

Business: [approved name, audience, services, service area].
Primary action: [real reviewed contact destination].
Images: [files with permission and descriptions].
Design: [selected direction].

Use semantic HTML, CSS and minimal JavaScript. Return dist with index.html, styles, approved assets and 404.html, plus a README. No invented claims, testimonials, prices or stock imagery. No form without a working reviewed destination. No accounts, checkout, Functions, databases, tracking, paid widgets or paid model API. Identify placeholders that block publication.

Incremental software/hosting budget for this version: US$0, using my already-owned permitted AI subscription, Pages Free and pages.dev. Stop if any new charge or quota upgrade is required.

Show phone/desktop review findings and a deploy plan. Do not request credentials in chat. Use operator-managed Wrangler login or protected scoped token configuration. Target only the approved isolated Pages project. Upload a public-safe review branch only after authorization; production requires my review of the actual preview. Return the deployment URL and identifier; never claim customer delivery, accessibility certification or business results from a successful upload.
Before any upload, inspect for a functions/ directory in the current working directory and dist/_worker.js. Stop if either exists; do not silently deploy dynamic code.

Check the result

• Facts and scope: every service, destination and image is approved; fictional examples and placeholders are replaced. No invented proof or hidden new functionality.
• Usability: real browser checks at phone/desktop widths, keyboard navigation, enlarged text, image loading, contact links and 404 behavior. Record defects and recheck fixes.
• Access and assets: only intended public files upload; no tokens, .env files or private notes. Token permissions/account/expiry reviewed; no Global API Key or browser-embedded secrets.
• Deployment: correct isolated project, review branch first, human approval, same reviewed assets to production; live URL and deployment identifier read back.
• Budget and maintenance: Free static path confirmed, no new model API or paid add-ons; domain/renewal quotes excluded unless explicitly added; owner assigned to future edits.
• Static-only check: no functions/ folder in the Wrangler working directory and no dist/_worker.js; an unexpected function stops this budget workflow.

What to keep in mind

A researched guide checked against primary documentation on 14 October 2026, with an original fictional example. It is not a tested deployment, agency-quality certification, conversion promise or fixed completion-time claim; the reading estimate excludes building and revision. An AI subscription's included usage and permitted tooling vary. Free plans, quotas and CLI behavior may change. The initial-cash example excludes labor, taxes, existing subscription payments/renewals, custom domains, paid assets, email delivery, dynamic services and ongoing extras. Commerce, regulated content, customer accounts and private administration need separate engineering and review. No comparable US$10,000 agency scope was verified, so no savings or value-equivalence claim is made.

Sources & review notes

These sources support the tool context and review principles. The workflow, prompt, and synthetic example are original editorial material.

• Cloudflare: Pages Functions pricing

  Static requests are free and unlimited only when they do not invoke Functions; Functions share Workers quotas.

• Cloudflare: Pages limits

  Free plan: 500 builds/month, one concurrent build, 20,000 files; individual assets maximum 25 MiB.

• Cloudflare: Direct Upload

  Prebuilt asset folder, project creation, pages.dev URL, branch previews and inability to convert a Direct Upload project to Git integration.

• Cloudflare: Direct Upload with continuous integration

  Account / Cloudflare Pages / Edit token; account ID and token passed through protected environment configuration.

• Cloudflare: Create an API token

  Custom permissions, account resources, expiry and optional client-IP restrictions.

• Cloudflare API: Create a Pages deployment

  POST accounts/{account_id}/pages/projects/{project_name}/deployments accepts Direct Upload manifest of uploaded content hashes; recommends bearer tokens.

• Cloudflare: Workers pricing

  Workers Free has 100,000 requests/day and 10 ms CPU/invocation; paid services and storage have separate allowances.

• Cloudflare: Registrar overview

  Registration and renewal incur registry/ICANN costs; default auto-renew. No exact domain quote used.

• Cloudflare: Pages custom domains

  Associate custom domain in Pages; apex needs Cloudflare nameservers while an externally managed subdomain can use a CNAME.

• Anthropic: What is the Pro plan?

  US monthly Pro price is $20; includes Claude Code; API usage is separate. Regional pricing/tax and usage limits vary; additional paid usage is optional.