The Wealth
Experiment
Start an experiment

Software & automation · Full playbook

Web Development

Build websites and web applications for clients

Experience
Intermediate
Planning time
15-30 hours/week
Starter budget estimate
$0-$200

Illustrative planning ranges, not earnings projections. Check the full costs and customer demand for your own situation.

Is this a fit?

Build websites and web applications for clients

Skills to bring or develop

  • HTML
  • CSS
  • JavaScript
  • React

The starting sequence

  1. Learn web development fundamentals
  2. Build portfolio projects
  3. Master modern frameworks
  4. Find first clients
  5. Scale your agency

What the work involves

You need working code skills — not perfection, but enough to build something a real client can use. HTML, CSS, and JavaScript are the floor; React or another framework gets you to better-paying projects faster. Beyond the technical side, you need to communicate clearly with non-technical people, manage scope creep without flinching, and deliver on deadlines even when the project turns out harder than the estimate. Most of the work is problem-solving under mild pressure. The clients who pay well expect professional behavior as much as clean code.

Find your first customers

Treat this customer profile as a starting hypothesis. Talk to people in this role and find out what they already do, what it costs them, and whether they want help.

Role

Small Business Owner

Company size

1-20 employees

Problems to investigate

  • Current website is outdated
  • Not getting leads from website
  • Previous developer disappeared
  • Dont understand tech requirements

Channels to test

  • Upwork
  • LinkedIn
  • Referrals
  • Local Networking

First launch approach

Start with small business websites, build portfolio, raise prices

Ways to find your first customer

  • Build 3 free/cheap websites for portfolio
  • Complete Upwork profile with projects
  • Network at local business events
  • Partner with designers for referrals

Shape the offer & delivery

These are example packages to adapt, not current market rates or promises of sales. Choose one deliverable, set a revision limit, and test the scope with a real buyer before expanding.

Landing Page

$1,500-$3,000 example price

  • Single page design
  • Mobile responsive
  • Contact form
  • SEO basics

Business Website

$5,000-$10,000 example price

  • 5-10 pages
  • CMS integration
  • Blog setup
  • Analytics
  • 30-day support

Web App

$15,000-$50,000 example price

  • Custom functionality
  • User authentication
  • Database
  • Admin panel
  • Ongoing support

Build and deliver the offer

Service delivery

Packages

Name

Landing Page

Deliverables

  • 1-5 page marketing site
  • Mobile-responsive

Timeline

1-2 weeks

Included in this example

  • 1 design revision round
  • Basic SEO setup
  • Contact form

Outside this example

  • Custom backend/database
  • User authentication
  • Ongoing hosting management

Name

Web App

Deliverables

  • Custom application with database + user accounts

Timeline

4-8 weeks depending on scope

Included in this example

  • Full-stack build
  • Basic admin dashboard
  • Deployment setup
  • 2 weeks post-launch bug fixes

Name

Maintenance Retainer

Deliverables

  • Ongoing updates, fixes, and small feature additions

Timeline

Monthly, hours-based

Included in this example

  • Priority bug fixes
  • Dependency/security updates
  • Small feature requests

Client onboarding

Step

Client provides brand assets, copy, and any reference sites they like

Who handles it

client

Step

Confirm hosting/domain ownership and access before starting build

Who handles it

client

Step

Agree on tech stack and get client sign-off before writing code — changing stacks mid-project is expensive for both sides

Who handles it

you

Step

Set up a staging environment separate from production for review before launch

Who handles it

you

Kickoff conversation

  • Walk through the sitemap/feature list and confirm nothing critical is missing from scope
  • Agree on the design approval process — how many rounds, who has final sign-off
  • Confirm timeline milestones and what "done" looks like for each phase
  • Set up communication cadence (weekly check-in vs. async updates)

Your launch roadmap

Work through the phases at your own pace. Durations and task hours are estimates; client conversations, sales, and other outcomes depend on the response you receive. Growth and exit steps are optional later decisions.

01 · Skill Building 14 days · suggested pace

  1. Complete React tutorial and build 3 practice projects

    Tool examples: VS Code, React

    Planning allowance: 30 hours

  2. Master Vercel/Netlify for easy client deployments

    Tool examples: Vercel, Netlify

    Planning allowance: 5 hours

02 · Portfolio Building 7 days · suggested pace

  1. Create impressive demo sites for different industries

    Tool examples: React, Tailwind CSS, Vercel

    Planning allowance: 25 hours

  2. Build your own professional portfolio

    Tool examples: React, Vercel

    Planning allowance: 10 hours

03 · Exit 60 days · suggested pace

Prepare your web development business for sale, acquisition, or hands-off operation

  1. Create comprehensive standard operating procedures covering every repeatable process in your web development business — client onboarding, delivery workflows, billing, and support. A buyer needs to run this without you.

    Target deliverable: Complete SOP handbook with video walkthroughs

    Tool examples: Notion, Loom, Google Docs

    Planning allowance: 12 hours · AI can assist; review the output

  2. Record the questions this step raises for your business, location, and circumstances. Confirm requirements and assumptions with current official sources and a qualified professional before acting.

    Target deliverable: Valuation estimate with supporting financials

    Tool examples: Google Sheets, ChatGPT

    Planning allowance: 6 hours · AI can assist; review the output

  3. Organize all financial records, contracts, customer data, IP documentation, and legal documents into a virtual data room that a buyer or their advisor can review.

    Target deliverable: Organized virtual data room

    Tool examples: Google Drive, Google Sheets

    Planning allowance: 10 hours

  4. Identify every area where the business depends on you personally. Delegate, automate, or document each one. Test by taking 2 weeks off and measuring impact.

    Target deliverable: Owner dependency scorecard (before/after)

    Tool examples: Notion, Zapier, Slack

    Planning allowance: 20 hours

  5. Create a teaser document (blind profile) for your web development business and either list on marketplaces (Acquire.com, Flippa, Quiet Light) or reach out directly to 5-10 potential acquirers.

    Target deliverable: Teaser document + 5-10 buyer conversations started

    Tool examples: Acquire.com, Google Docs, Email

    Planning allowance: 8 hours · AI can assist; review the output

Checking a task saves its checkmark in this browser. It does not run an AI agent or confirm a business result. Reset removes this guide’s checkmarks. Saved work does not sync between devices.

Tools, budget & effort

These are tools named in the original playbook, offered as examples to evaluate. Check current capabilities, pricing, licensing, and data handling with the provider before subscribing. Start with the tools you already have.

  • VS Code
  • GitHub
  • Vercel

Tools to evaluate

Item

A hosting/deployment account (Vercel, Netlify, or similar)

Why consider it

You need somewhere real to deploy client sites — most plans have a free tier sufficient for early projects

Item

A design handoff tool (Figma)

Why consider it

Client design approval before you build saves rework — get sign-off on a mockup, not the finished site

Item

A contract covering scope, revisions, and IP handoff

Why consider it

Scope creep and "who owns the code" disputes are the top two sources of freelance dev conflict

Project & Client Management
  • Bonsai
  • Wave
  • Notion
Deployment & Hosting
  • Vercel
  • Netlify
  • Cloudways
Design & Prototyping
  • Figma
  • Framer
  • Whimsical

Make the numbers your own

Include setup, subscriptions, selling, fulfillment, revisions, support, and your time. Use your actual inputs and compare a cautious case with a better case.

Open the experiment calculator →

AI roles & prompt templates

Assign a clear job, provide approved inputs, and review the result. These are role and prompt ideas; this page does not run AI or connect your accounts.

Frontend Dev

Review this component structure and suggest a cleaner way to organize state

Ui Designer

Generate 2 layout options for this landing page based on the client brief

Sales Optimizer

Define a narrow first task and a review step.

Copy a prompt, then add your context

Replace the bracketed placeholders. Use information you have permission to share, ask for sources, and check every factual or numerical claim.

Write a cold outreach email to a local small business owner who has an outdated or missing website
You are helping me write a cold outreach email for my freelance web development business. Here is the context:

- I build websites for small businesses using modern tools (React, Next.js, or simple HTML/CSS depending on needs)
- My target is a [TYPE OF BUSINESS, e.g. local plumber / restaurant / law firm] called [BUSINESS NAME] in [CITY]
- Their current website problem is: [describe what you noticed — e.g. 'no website at all' / 'site looks like it was built in 2009' / 'not mobile-friendly']
- My ask is a 15-minute discovery call, not a sale
- Tone: friendly, professional, zero pressure, zero jargon
- Length: under 150 words
- End with one clear CTA (a Calendly link or reply to schedule)

Write 2 versions: one more direct, one more conversational. Do not use phrases like 'I hope this email finds you well' or 'I wanted to reach out.' Start with something specific to their business.

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.
Generate a project scope document and rough timeline for a client website project
I am a freelance web developer and I just had a discovery call with a client. Help me write a clear project scope document I can send them before we sign a contract.

Here are the details from our call:
- Client business type: [e.g. yoga studio]
- Pages needed: [e.g. Home, About, Services, Contact, Blog]
- Special features: [e.g. online booking integration, contact form, photo gallery]
- Their stated deadline: [e.g. 6 weeks from now]
- Budget range discussed: [e.g. $2,500–$3,500]
- CMS needed: [Yes/No — if yes, which one: WordPress, Webflow, Framer, etc.]
- Who provides content (copy and images): [client / me / shared]

Please produce:
1. A plain-English scope of work section (what IS included)
2. A short 'out of scope' section (what is NOT included)
3. A phased timeline with milestones (discovery, wireframes, design, dev, revisions, launch)
4. A list of 3-5 questions I should clarify with the client before starting

Keep it professional but not stuffy. This is a small business client, not a Fortune 500.

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.
Debug a specific JavaScript or React error you're stuck on
I am a freelance web developer working on a client project. I have a bug I cannot figure out. Please help me debug it.

Here is the context:
- Framework/language: [e.g. React 18 / vanilla JS / Next.js 14]
- What I am trying to do: [describe the intended behavior in plain English]
- What is actually happening: [describe the bug — error message, wrong output, etc.]
- Relevant code snippet:

[PASTE YOUR CODE HERE]

- What I have already tried: [list what you've attempted]
- Browser/environment: [e.g. Chrome, Node 20, local dev]

Please:
1. Explain what is causing the bug in plain English
2. Show me the corrected code with inline comments explaining the fix
3. Tell me if there are any related issues in my code I should know about
4. Suggest one way to prevent this type of bug in the future

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.
Create a portfolio case study write-up for a completed client project
Help me write a portfolio case study for my freelance web development website. This is for a project I just completed.

Project details:
- Client type (no need to name them if confidential): [e.g. independent real estate agent]
- The problem they had before: [e.g. no website, relying only on Zillow profile]
- What I built: [e.g. a 5-page Next.js site with a property listings page and contact form]
- Technologies used: [e.g. Next.js, Tailwind CSS, Netlify]
- Timeline: [e.g. 3 weeks]
- Results or outcome: [e.g. client reported 4 inbound leads in first month, or simply 'launched on time within budget']
- Do I have screenshots/images to include: [Yes/No]

Write a case study with these sections:
1. The Challenge (2-3 sentences)
2. My Approach (3-4 sentences — what decisions I made and why)
3. The Result (2-3 sentences — be honest, do not exaggerate)
4. Tech Stack (bullet list)
5. One testimonial placeholder I can ask the client to fill in

Tone: confident but not braggy. Written for a potential client reading my portfolio, not a developer audience.

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.

Build a personal AI team plan →

What a working week could look like

This is an example cadence. Include time for customer conversations, review, and admin; reduce the scope to fit your available hours.

What

Chief of Staff check-in — review yesterday's blockers, set today's one shipping goal

When

Daily · 15 min

What

Client project work — focused build time, no context switching

When

Mon–Fri · 2–3 hrs

What

Outreach batch — email or LinkedIn messages to 5 local or niche businesses

When

Tue & Thu · 30 min

What

Weekly review — log hours, check project scope, update any active proposals

When

Sun · 45 min

Problems to plan for

Use these playbook prompts to question your plan. Pricing, channels, and delivery models should be tested with your own customers.

Taking on projects without a written contract or scope document

Use a simple one-page contract for every project, even friends and family. Include: scope of work, revision limit (e.g. HelloSign or Docusign make this free and fast.

Underpricing projects to win clients, especially early on

Your time has a floor. Use value-based framing: 'This site could bring you 2-3 new clients a month' is a stronger conversation than competing on price. Raise rates after every 2-3 completed projects.

Building a portfolio with only personal or fake projects

Do 1-2 real projects early — even at a steep discount or for a nonprofit — to get genuine testimonials and real URLs you can show. Ask every completed client for a written or video testimonial immediately after launch.

Ignoring the content bottleneck — waiting on clients for copy and images

Set a hard content deadline in your contract: 'Client must provide all content by [date] or the project timeline shifts accordingly.' Create a simple content checklist (Google Doc) you send at kickoff. Offer to write copy for an additional fee — many clients will take it.

Building everything from scratch when templates and frameworks exist

Build a personal starter kit: a GitHub repo with your preferred stack (e.g. Next.js + Tailwind + shadcn/ui), common components (nav, footer, contact form), and deployment config. Reuse it on every project. Customize, don't rebuild.

Your first small test

  1. Choose one customer. Find five people who have the problem described in this guide.
  2. Show one useful sample. Ask about their current process, priorities, and objections.
  3. Offer a clearly scoped pilot. Agree on deliverables, a price to test, and what success means.
  4. Record the evidence. Track responses, costs, hours, and what the buyer actually used. Decide whether to continue, change, or pause.

Explore related ideas

Adapted from Ashley’s Waymaker side-hustle playbooks, imported October 15, 2026. This is a published snapshot, not a live connection to your Waymaker account. Source examples are planning material, not verified customer outcomes. Explore Waymaker.

Free download · The Experiment Scorecard

Know if your side idea is actually working.

A 6-page scorecard for testing one income idea: the signal ladder, a four-week evidence log, the true-cost check, and a clear continue / change / pause decision. Download it now, with no signup required. You can also request occasional notes from Ashley’s experiments.

Download the free scorecard

Follow at your own pace

Keep a place
in the experiment.

Read the latest field note, or add the free feed to your RSS reader for new articles and build walkthroughs.

Email signup is not available yet. The journal, feed, and downloads are ready to use.