Vertical niche
One industry, any tech.
"Websites and booking systems for dental clinics."
Field guide · Freelance web & app development
Everything you need to know to run a freelance agency that designs and builds websites, web apps and mobile apps. Part I covers the business: services, pricing, sales, contracts, delivery and growth. Part II turns it into a practice plan you can work through. The goal is autonomy: your own business, where you control your money, time and energy and keep the full value of your work. Freelancing and running an agency are stages 2 and 3 of the Leverage Roadmap toward a digital and tech business that doesn't depend on your hours.
Chapter 01
A web and app development agency sells one thing: working software that solves a client's business problem. That might be a site that brings in leads, a store that takes orders, or an app that runs part of their operations. The code is how you deliver it. Clients judge you on outcomes, communication and reliability, and rarely on the framework you chose.
Most agencies start as one freelancer and grow in stages. Each stage has a different job for the founder:
| Model | Team | How it earns | Founder's main job |
|---|---|---|---|
| Solo freelancer | 1 | Hourly or per project | Doing the work, plus sales and admin |
| Freelancer + subcontractors | 1 + 1–4 on demand | Project margin on subcontracted work | Sales, scoping, quality control |
| Micro-agency | 3–8 | Projects + monthly retainers | Sales, account management, hiring |
| Studio / boutique agency | 10–25 | Larger projects, long retainers | Strategy, pipeline, leadership |
| Productized service | 1–5 | Fixed package at a fixed price | Marketing and refining the process |
| White-label partner | 2–10 | Builds for other agencies under their brand | Partner relationships, throughput |
Chapter 02
The typical service catalog, with indicative price ranges for freelancers and small agencies serving clients in North America and Western Europe. Rates vary a lot by region, niche and reputation. Use the ranges to sanity-check your quotes, not as fixed prices.
| Service | Typical scope | Price range (USD) | Timeline |
|---|---|---|---|
| Landing page | One page, copy support, form, analytics | 1,500–5,000 | 1–2 wks |
| Marketing website | 5–15 pages, CMS, SEO basics, blog | 5,000–25,000 | 4–8 wks |
| E-commerce store | Shopify or WooCommerce theme, products, payments, shipping | 5,000–40,000 | 4–10 wks |
| Web app MVP | Auth, dashboard, core workflow, admin, payments | 25,000–120,000 | 8–16 wks |
| Mobile app MVP | Cross-platform iOS + Android, backend, store submission | 30,000–150,000 | 10–20 wks |
| UX/UI design sprint | Research, wireframes, clickable Figma prototype | 3,000–15,000 | 1–3 wks |
| AI feature integration | Chat, search or document automation using an LLM API | 5,000–40,000 | 2–8 wks |
| Audit (speed, SEO, a11y, security) | Report with a prioritized fix list | 1,000–5,000 | 1 wk |
| Maintenance / care plan | Updates, backups, monitoring, small fixes | 300–3,000 / mo | Ongoing |
| Dev retainer | A fixed block of hours or a dedicated developer each month | 3,000–20,000 / mo | Ongoing |
Chapter 03
Positioning is the answer to "why should I hire you instead of the 500 other people who build websites?" A specialist can charge more, writes proposals faster (the problems repeat) and gets referrals more easily (people remember what you do).
One industry, any tech.
"Websites and booking systems for dental clinics."
One technology or problem, any industry.
"Shopify speed optimization." "React Native apps for startups."
One fixed package, one price, one timeline.
"A 5-page Webflow site in 10 days for $6,000."
We help [specific client] achieve [business outcome] by building [type of product], unlike [alternative], we [your difference].
Example: We help independent fitness studios get more members by building booking-ready websites and apps. Unlike template builders, we connect class scheduling, payments and email into one system you never have to fix yourself.
Specializing doesn't mean turning down other work. It changes what you advertise. You can still take a good project outside your niche.
Chapter 04
Pricing is the biggest lever on profit. Most new freelancers undercharge because they divide a salary by 2,080 hours. But a freelancer bills maybe 50–70% of their working time. The rest goes to sales, admin, learning and gaps between projects, and you also pay your own tax, tools, insurance and time off.
| Model | How it works | Use it when | Watch out for |
|---|---|---|---|
| Hourly | Bill tracked time weekly or monthly | Scope is unclear, ongoing support, small fixes | Caps your income; you earn less by working faster |
| Daily / weekly | Sell days or sprint-weeks of a dev's time | Agile builds where scope will change | Needs a client who trusts you |
| Fixed price | One price for a defined scope | Clear requirements, repeat project types | Scope creep, bad estimates |
| Milestone | Fixed price split into paid phases | Most projects over $10k | Define "done" for every milestone |
| Value-based | Price on the business value delivered | Measurable outcome (revenue, hours saved) | Needs strong discovery and confidence |
| Retainer | Monthly fee for hours or a service | After launch: maintenance, growth work | Define rollover and response times |
| Productized | Fixed package, fixed price | Highly repeatable deliverables | Custom requests breaking the package |
Work out the minimum hourly rate you need, then a quote for a project. The example values are for a solo developer; replace them with your own.
Chapter 05
New agencies usually get their first clients from their own network and marketplaces, then move toward referrals and inbound leads. Pick two channels and do them consistently before adding more.
| Channel | Speed to first client | Deal quality | How to do it well |
|---|---|---|---|
| Your network | Fast | High | Tell 50 people exactly what you do and who it's for. Ask for introductions. |
| Referrals | Slow to build | Highest | Ask every happy client at launch. Offer a referral fee (5–10% of the first project). |
| Marketplaces Upwork, Fiverr, Contra, Toptal | Fast | Mixed | Niche profile, portfolio pieces, fast replies. Platforms take a fee (up to ~20%). |
| Medium | High | Post case studies and lessons 2–3 times a week. Comment on your target clients' posts. | |
| Cold outreach | Medium | Mixed | Short, personal emails with a specific observation ("your checkout takes 9 s on mobile"). Follow local laws on commercial email. |
| Agency partnerships | Medium | High | Partner with design, marketing and SEO agencies that don't build in-house. |
| Content & SEO | Slow | High | Write what your niche searches for: "how much does a booking app cost". |
| Directories Clutch, GoodFirms, Shopify Partners | Medium | Mixed | Collect verified reviews; they rank on review count and recency. |
Show 3–6 case studies, not 30 screenshots. Each one should cover the client's problem, what you built, the result in numbers ("bookings up 40%", "page load from 6.1 s to 1.4 s") and a client quote. No client work yet? Build two realistic concept projects for your niche and label them as concepts.
Chapter 06
The same steps every time, from first contact to a paid deposit. Writing each step down lets you see where deals get stuck.
Reply within one business day. Send a short intake form: goals, budget range, deadline, decision-maker, links to examples they like.
Check BANT: Budget, Authority, Need, Timeline. If the budget is well below your minimum, say so politely and refer them on.
Ask more than you talk. What problem are they solving? What happens if they don't solve it? How will they measure success? What have they tried?
For complex projects, sell a 1–3 week roadmapping phase that produces requirements, a sitemap or user flows, and an accurate estimate.
Send within 2–3 days, ideally walked through on a call rather than emailed cold. Include three options.
Master services agreement plus a statement of work for this project. Signed electronically.
No work starts before the deposit clears. This is the single most important rule in the handbook.
Book the kickoff meeting, share the project board, collect access and assets.
Chapter 07
A proposal persuades; a statement of work (SOW) defines. The proposal says why you and what the client gets. The SOW is the part of the contract that lists exactly what will be delivered. Most disputes come from a vague SOW.
| Project size | Schedule |
|---|---|
| Under $5,000 | 50% upfront · 50% before launch |
| $5,000–$30,000 | 40% upfront · 30% design approval · 30% before launch |
| Over $30,000 | 25% upfront · monthly or per-milestone invoices |
| Retainers | Billed in advance on the 1st of each month |
Take the final payment before you launch or hand over the code, not after. Once the site is live, the client has little reason to hurry.
Chapter 08
This is general information, not legal advice. Laws differ by country and state. Have a local lawyer review your contract template once; it is a small, one-time cost.
§ Scope
Work is limited to the SOW. Anything else is quoted as a written change request and approved before it starts.
§ IP
Ownership of custom work transfers to the client on full payment. You keep your pre-existing tools, libraries and know-how and license them to the client.
§ Payment
Deposit, schedule, due dates (Net 7 or Net 14), late fee, and your right to pause work on overdue invoices.
§ Warranty
Bugs reported within 30 days of launch are fixed free. New features and changes caused by third parties are not bugs.
§ Liability
Your total liability is capped, usually at the fees paid under the contract. No liability for indirect or lost-profit damages.
§ Termination
Either side can end the contract with notice. The client pays for work done to date plus a kill fee, often 25% of the remaining value.
§ Client duties
Timely feedback, content and access. Delays from the client move the timeline and may add cost.
§ Third parties
You aren't responsible for outages or price changes in hosting, APIs, plugins or app stores. Open-source licenses apply as published.
§ Confidentiality
Both sides keep confidential information private. You may show the finished work in your portfolio unless agreed otherwise.
The client should own the accounts for their domain, hosting, app store listings (Apple Developer Program: $99/year; Google Play Console: $25 once), payment processor and analytics, and invite you as a collaborator. Keeping client assets in your personal accounts creates a mess when the relationship ends.
Chapter 09
A standard project lifecycle. Each phase ends with a client approval, which also works as a natural invoice point.
Chapter 10
Choose a small, stable stack and get very good at it. Clients benefit from your speed, and your estimates become reliable. These are common, well-supported choices as of 2026.
Astro, Next.js, WordPress, Webflow, Framer
Sanity, Payload, Strapi, Contentful, Storyblok
Shopify (Liquid, Hydrogen), WooCommerce, Medusa
React + TypeScript with Next.js or Vite; Vue with Nuxt; SvelteKit
Node.js (Express, NestJS, Hono), Laravel, Django, Ruby on Rails, Go
Supabase, Firebase, Convex, Appwrite
PostgreSQL, MySQL, SQLite, Redis; Prisma or Drizzle ORM
React Native with Expo, Flutter; native Swift / Kotlin for device-heavy apps
Clerk, Auth.js, Supabase Auth; Stripe, Paddle, Razorpay
Vercel, Netlify, Cloudflare, Render, Fly.io, AWS, Google Cloud
LLM APIs (Anthropic Claude, OpenAI, Google Gemini), vector search with pgvector
ESLint, Prettier, Vitest / Jest, Playwright, GitHub Actions CI, Sentry
For marketing sites: Astro or Next.js + a headless CMS + Vercel or Netlify. For web apps: Next.js + TypeScript + PostgreSQL (via Supabase) + Stripe. For mobile: React Native with Expo, which shares TypeScript skills with your web work.
Web and app development is one part of software engineering. For the wider field (infrastructure, data, distributed systems, operating systems, embedded and more) see Beyond Web & Apps.
Chapter 11
| Job | Common tools |
|---|---|
| Project management | Linear, Jira, Trello, Asana, ClickUp, GitHub Projects |
| Docs & wiki | Notion, Google Docs, Confluence |
| Design | Figma, FigJam |
| Code & CI | GitHub, GitLab, GitHub Actions; AI coding assistants |
| Communication | Slack, Google Meet, Zoom, Loom |
| Scheduling | Cal.com, Calendly |
| Proposals & e-signature | PandaDoc, Bonsai, Dropbox Sign, DocuSign |
| Time tracking | Toggl Track, Harvest, Clockify |
| Invoicing & accounting | Stripe Invoicing, Xero, QuickBooks, FreshBooks, Wave, Zoho Books |
| CRM / pipeline | HubSpot (free tier), Pipedrive, Attio, a simple Notion board |
| Password & access sharing | 1Password, Bitwarden |
| Monitoring | Sentry, Better Stack, UptimeRobot, Google Search Console |
Start with the free tiers. Add a paid tool only when a specific problem costs you more time than the tool costs money.
Chapter 12
Agencies rarely fail from lack of work. They fail from cash-flow gaps: a big project finishes, the next one hasn't started, and invoices are 45 days late.
When a payment arrives, move fixed percentages into separate accounts straight away. A common starting split:
Invoice number, issue and due dates, your business and tax details, the client's legal name, line items that match the SOW, tax lines, total, payment methods and the late-payment terms. For international clients, state the currency and who pays transfer fees.
Chapter 13
Scaling means the business can take on more work without the founder doing all of it. Grow in this order:
Write SOPs (standard operating procedures) for sales, onboarding, delivery and handoff. Use templates for proposals, SOWs, contracts, kickoff decks and QA checklists.
Start with trusted freelancers for design, QA or extra dev capacity. Pay them 50–65% of what you bill to keep a healthy margin.
Usually the first hire that frees the founder for sales. A PM can handle 3–6 active projects.
Offer a care plan on every launch. Retainers make hiring safe.
Senior developer, designer, then account manager. Hire when you're consistently turning down work, not before.
Aim for a 40–60% gross margin on projects (revenue minus direct labor cost), leaving room for overhead and a 15–25% net profit.
Chapter 14
Track a handful of numbers monthly. They tell you early when something is going wrong.
| Metric | Formula | Healthy range |
|---|---|---|
| Utilization | Billable hours ÷ available hours | 60–80% |
| Effective hourly rate | Project revenue ÷ actual hours spent | ≥ target rate |
| Gross margin | (Revenue − direct costs) ÷ revenue | 40–60% |
| Recurring revenue share | Retainer revenue ÷ total revenue | 30–50% |
| Close rate | Signed proposals ÷ sent proposals | 30–50% |
| Pipeline coverage | Weighted pipeline ÷ revenue target (next 90 days) | ≥ 2–3× |
| Days sales outstanding | Average days from invoice to payment | < 30 |
| Client concentration | Largest client's share of revenue | < 30% |
| Estimate accuracy | Actual hours ÷ estimated hours | 0.9–1.1 |
Chapter 15
Fix: no deposit, no calendar slot. No exceptions for "urgent" projects.
Fix: log every request; anything outside the SOW becomes a priced change request.
Fix: estimate in tasks, not features; add contingency; track actuals against estimates.
Fix: keep prospecting even when busy; cap any client at about 30%.
Fix: state the number of revision rounds per phase in the SOW.
Fix: content deadlines in the SOW; you can reschedule if they're missed.
Fix: offer a care plan in every proposal, so post-launch support is paid work.
Fix: pick a stack for a year; learn new tools on internal projects.
Chapter 16 · Part II
Turn the handbook into a working agency setup. Each task produces something you'll reuse with real clients. Your progress is saved in this browser.
0 of 0 tasks done
Appendix A
No terms match that filter.