The process, in one screen
- Define the job in business terms — what changes when the project succeeds.
- Set a real budget band — a range you can spend, stated upfront.
- Source candidates — the five channels, ranked by what they are good for.
- Vet with the script — 14 questions, not vibes.
- Contract the five clauses — IP on payment, repo access, milestones, changes, warranty.
- Manage the build — weekly rhythm, verify milestones, protect the handover.
Each step has a failure mode that produces the horror stories. Here is how to run each one so it produces a project instead.
Step 1 — Define the job
"We need a website" is not a definition; it is a category. The definition that gets real quotes is a business goal attached to a scope: generate 30 qualified leads a month, sell our 200-product catalog, stop losing mobile visitors. Write the goal first, the pages and features second — technology decisions made backwards from a goal are always better than goals invented to justify technology.
The full structure for this is the brief template — eight fields, twenty minutes, and every step after this one gets easier because of it.
Step 2 — Set the budget band
The taboo that hurts both sides. Developers skip briefs they cannot price; you receive quotes for a project that is not yours. A stated band — "6 to 9 thousand, could stretch for the right case" — gets you real numbers, faster, from better matches. Sanity-check the band against the cost guide and the rate benchmarks before committing it.
Step 3 — Source candidates
Five channels, honestly ranked:
- Referrals from businesses like yours — the highest-signal source there is. Ask what went wrong, not just what went well.
- Independent sites like this one — you can evaluate the developer's thinking before paying anything.
- Marketplaces (Upwork, Fiverr) — wide, fast, quality a lottery; the reviews are the vetting, do not skip your own.
- Premium networks (Toptal, Lemon) — pre-vetted, priced accordingly; you pay to skip vetting risk.
- Agencies — for multi-discipline builds; the honest math is its own guide.
Step 4 — Vet with the script
Sales calls reward sales skills. The 14 vetting questions reward having done the work — because they cannot be answered well without it. Minimum bar before money moves: a live site you can check on your phone, a Git repository they can show you, and the name of the actual human doing the work.
Step 5 — Contract the five clauses
IP transfers on payment. Repo and credentials access from day one. Milestones you can verify with deposits under 50%. A written change mechanism. A warranty window and documented handover. All five, in writing, before signing — the contract guide has the full version. A developer who resists these is answering the question you actually asked.
Step 6 — Manage the build
Projects do not fail in the code; they fail in the cadence. The working rhythm: a weekly check-in against the milestone list, decisions made within 48 hours when asked, and content — always the bottleneck — scheduled like the engineering, not after it. Your three jobs: decide fast, pay milestones on verification, and read what is sent.
The shortcut that is not one
This entire process compresses to: write the six-question brief, state the band, send it to three candidates who pass the referral or live-site test, run the 14 questions on each, contract the five clauses, manage the cadence. Two weeks of evenings, most of it reusable. When you are ready, the brief form here runs steps 1 and 2 with you — and the quote that comes back shows its spec, its milestones and its model in writing.