All posts

How to build a website to sell your services (beyond Upwork)

You can build a website to sell your services in an afternoon for $0 in hosting fees if you only need a booking page and a payment link, or you can build a self-hosted site with accounts, subscriptions and file delivery if you are turning your service into a repeatable online product. The right approach depends less on your coding skill and more on how clients buy from you, how you deliver the work, and whether you want to stop paying marketplace commissions on platforms like Upwork.

This guide walks through the real cost of "free" service sites, how to pick the right stack for your business model, the exact steps to launch, how to handle productized or AI-assisted services, and how to bring in clients once you step outside a freelance marketplace.

Why build your own service website besides Upwork?

Marketplaces like Upwork solve discovery at the start, but they charge ongoing platform fees, keep the client relationship inside their interface, and push buyers to compare providers on hourly rate. Running your own site gives you direct control over positioning, packaging, payment terms and client data.

That does not mean you must quit Upwork on day one. A practical transition is to treat your website as your permanent home base—where referrals, LinkedIn contacts and search visitors can inspect your scope, pricing and past work—while keeping existing marketplace contracts compliant with the platform’s terms of service.

Can you build a website to sell services for free?

Yes, you can launch a working service website without a monthly subscription fee, but no online payment setup is completely free once money changes hands.

Here is what "free" actually covers and where costs appear (as of November 2026; check each provider’s current pricing page before committing):

  • Website hosting ($0 on free tiers): Tools such as Square Online, Payhip’s free tier, or Google Sites let you publish a live page at no monthly cost. The tradeoff is usually a platform subdomain (for example yourname.square.site), platform branding in the footer, or limited layout control.
  • Payment processing fees (unavoidable): Even when a website builder takes 0% commission, payment processors such as Stripe, PayPal and Square charge standard card processing fees (commonly around 2.9% + $0.30 per domestic card transaction, with higher rates for international cards or currency conversion).
  • Platform transaction fees (depends on the tier): Some free plans offset $0 monthly hosting with an extra platform cut per sale (for example, Payhip’s free plan adds a 5% fee on top of payment processing).
  • Custom domain (optional at first, recommended early): Registering a .com or similar domain typically costs around $10–$15 per year and immediately makes cold outreach and referrals look more credible.

If you are validating a new freelance offer and have zero revenue yet, start on a free tier plus a custom domain and upgrade only after your first paying clients confirm the offer.

Which way to build fits your service model?

The biggest mistake service providers make is picking a tool built for a different business model—either overbuilding a custom app for simple 1-on-1 coaching, or forcing a recurring digital service into a basic brochure site. Use the table below to match your service type to the right setup.

Service model Best fit Typical setup Main limitation
1-on-1 consulting, coaching, local services Free or lightweight builder (Square Online, Google Sites + Stripe Payment Links + Calendly) 1–2 hours, $0/mo + processor fees Manual follow-up, no client portal or usage ledger
Freelance design, writing, advisory (custom scope) Hosted site builder or freelancer portfolio (Squarespace, Wix, Contra) 1–2 days, low monthly fee (or free on Contra) Limited backend customization; tied to platform pricing and rules
Productized services, retainers, credit-based or AI-assisted online services Self-hosted SaaS starter (such as SaaScaffold, our own starter) Own Cloudflare account, full code and database Requires basic technical setup (or a coding agent) and a one-time license fee; not meant for simple brochure sites

Disclosure: SaaScaffold is our own commercial source-code starter. If you only need a portfolio page and a Calendly link, you do not need SaaScaffold—a lightweight hosted builder is faster and cheaper.

Step-by-step: how to build and launch a website to sell your service

Follow these six steps in order so you do not spend weeks polishing design before your checkout works.

1. Package your service so buyers can understand it in 10 seconds

On Upwork, clients write a brief and wait for proposals. On your own site, visitors leave if they cannot tell what you sell. Turn open-ended hourly work into concrete offers:

  • Fixed-scope packages: State the deliverable, turnaround time, revision limit and price (or "starting at" price).
  • Monthly retainers / subscriptions: Ideal for ongoing SEO, maintenance, design queues or technical support.
  • Credit packs or pay-per-request tiers: Useful when clients submit variable volumes of tasks (such as audits, content assets, or AI-assisted workflows) and want predictable unit pricing.

2. Build the five pages that actually close clients

You do not need a 20-page site. Focus on five clear pages:

  1. Homepage: State who you help, the outcome you deliver, and one primary call to action on the first screen.
  2. Services / Pricing page: Show packages, what is included, what is excluded, and how billing and refunds work.
  3. Proof / Case studies: Show concrete before-and-after examples, deliverables or client quotes (only publish real work you have permission to share).
  4. About page: Explain your background and operating entity so buyers know who stands behind the work.
  5. Contact / Policies: Make it easy to ask pre-sale questions, and publish clear Terms, Privacy and Refund policies—payment processors often require these before approving live accounts.

3. Connect payments, subscriptions and tax handling

For simple fixed packages, Stripe Payment Links or PayPal buttons get you live quickly. Once you sell internationally or run recurring plans, two practical issues show up fast:

  • One provider is rarely enough: Stripe does not support merchants in every country, some corporate buyers prefer PayPal, and selling cross-border digital services can trigger VAT or sales tax obligations.
  • Merchant of Record (MoR) options: Providers such as Dodo Payments act as a Merchant of Record, collecting and remitting sales tax and VAT on your behalf so you do not have to register in dozens of jurisdictions.

4. Set up booking, onboarding and delivery

Decide what happens in the five minutes after a client pays:

  • For calls and consulting, embed a scheduling tool (Calendly, Cal.com, or built-in booking) and send an intake form automatically.
  • For recurring or file-based deliverables, give clients a predictable place to submit requests, track status, and download private deliverables instead of burying files in email threads.

5. Test the entire payment-to-delivery flow before going live

Before sharing your URL publicly, run a real test purchase in sandbox/test mode:

  • Confirm the confirmation email arrives.
  • Confirm the order status updates from a verified server webhook, not just from the browser landing on a "thank you" page.
  • Confirm you know how to issue a full refund and revoke access if a client cancels.

6. Publish and connect analytics

Connect a custom domain, verify mobile readability (especially your pricing cards and checkout button on a phone screen), and enable privacy-aware analytics so you can see which pages bring inquiries.

Turning a service into a productized or AI-assisted site with SaaScaffold

If your service is evolving beyond manual 1-on-1 calls—for example, a productized design/audit service with a client portal, a subscription service with monthly task allowances, or an online service backed by AI generation—stitching together a website builder, a separate billing tool, a file host and a helpdesk gets brittle quickly.

This is the exact gap SaaScaffold is built for. Rather than renting a closed SaaS platform, you license the full TypeScript repository (React + TanStack Start on Cloudflare Workers, with Cloudflare D1 or PostgreSQL) and run it in your own Cloudflare account:

  • Built-in accounts and client workspace: Email verification, password reset, Google sign-in, optional Cloudflare Turnstile bot protection, plus a customer workspace showing orders, credit history, private files and support tickets.
  • Four payment providers, one ledger: Stripe, PayPal, Waffo and Dodo Payments share one order flow and one atomic credit ledger. All four support both one-time credit packs and recurring subscriptions, with server-verified webhooks, idempotent event handling and refunds. See how one credit ledger handles four payment providers.
  • Private deliverable storage: Public assets and private client files live in separate Cloudflare R2 buckets, with private downloads served through access checks.
  • Optional AI workflows: If part of your service uses AI (text, image, video, speech or music), built-in AI adapters connect to APIMart, fal.ai, Kie and SeeAPI, reserving credits before a job runs and settling only on a delivered result.
  • Agent-first setup: The repository ships with 40 Markdown runbooks (agents/) that Claude Code or Codex can follow to brand your site, run tests, verify pre-launch checklists and deploy to Cloudflare—while stopping for your approval before cloud releases and never handling your secret keys.

Important license boundary: SaaScaffold’s standard commercial license lets you build and operate unlimited sites that you own and operate for your own business. It does not permit using the source code to build websites for clients as an agency or freelancer without a separate extended license. Read the full terms in the SaaScaffold software license.

How to get service clients without Upwork

Launching a website does not automatically bring traffic. Pair your new site with two or three repeatable acquisition channels:

  • Search-focused articles and case studies: Write specific guides answering the exact problems your buyers search before hiring (for example, pricing breakdowns, checklists or technical audits).
  • LinkedIn and niche communities: Share concise breakdowns of real work and link back to a clear service page rather than a generic homepage.
  • Direct outreach with a concrete observation: Email a small list of well-matched businesses with one specific issue you noticed and a link to a fixed-scope package that solves it.
  • Referrals from past clients: Ask satisfied clients to share your service page URL—a clear package page converts far better than "email me for a quote."

Note on existing Upwork clients: always follow Upwork’s current circumvention and opt-out rules before moving an existing platform relationship to direct billing.

Common mistakes to avoid when building a service site

  • Hiding prices completely: Even if every project varies, publishing a starting price or package tiers filters out mismatched leads and builds trust.
  • Trusting the checkout return URL as proof of payment: Users can close the browser before returning, or revisit a success URL. Always fulfill orders from verified server-side webhooks or provider API checks.
  • Overbuilding before validating demand: Do not spend two months building a custom dashboard before you have confirmed that buyers will pay for the service itself.
  • Leaving scope and refund rules vague: Put revision limits, turnaround times and refund conditions on the checkout path, not buried after a dispute starts.

Next steps