SME First Website Project: From Brief to Launch

Unclear next steps drive most anxiety

Before handing a site to an outside team, owners are rarely stuck on the budget figure itself. The real uncertainty is how the months after signing will actually move: what comes next, which materials they must prepare, and where responsibility is drawn. A typical build takes about 8 to 14 weeks and splits into 8 stages. The sections below cover the work, the time, and the checks for each stage so a first collaboration can keep a steady pace.

Eight-stage process at a glance

Stage	Client prepares	Vendor handles	Typical time
1. Clarify goals	Write the site purpose and must-have features	Interview and summarize the requirements	About 1-2 weeks
2. Draft the brief	Turn needs into a one-page brief; the vendor can help	Supply a fill-in template	About 3-5 days
3. Request proposals	Send the same brief to 3 to 5 firms	Submit a quote and a presentation	About 1-2 weeks
4. Sign the contract	Review the contract and confirm the terms	Provide the contract and attachments	About 3-5 days
5. Interface design	Supply assets and comment on designs	Design the homepage, then the full site	About 2-4 weeks
6. System build	Enter content and join testing	Build front end, back end, and integrations	About 3-6 weeks
7. Acceptance training	Check browsers and learn the admin	Hand over the list and run training	About 1-2 weeks
8. Launch and cover	Use the live site and report issues	Provide at least one free year of fixes	Ongoing

A capable team usually needs two to three and a half months for the whole job. If the work is not a ready-made template, a promise to deliver a custom site in about a month should be treated as a warning. Depth of customization and the feature set set the floor on time; a very short promise usually means a light template tweak. One trading firm chose a one-month delivery to move faster, then found multilingual tags missing after launch and spent another eight weeks on a rebuild.

First steps: turn needs into a brief

These two steps are the ones owners skip most often, and they seed roughly six in ten of the disputes that follow. Asking firms to “just price it” almost always breaks comparison: one quote lands at 250,000 and another at 80,000, and the numbers cannot be lined up because each side pictured a different product.

When you narrow the need, answer three questions first:

Who is the site mainly for? (business buyers, consumers, or internal staff)
What counts as success? (inquiry forms, messenger follows, call volume, or brand exposure)
If an old site exists, where is it stuck?

A requirements brief should cover at least six items: page count, required features, responsive scope, search and AI-friendly conditions, source-code ownership, and warranty scope. Send that same document to 3 to 5 firms so the quotes that come back can actually be compared.

Further reading: Why website quotes vary so widely: five cost drivers, How to prepare content and assets before a build.

Middle steps: compare bids and sign

When you compare proposals, test seven areas: in-house team, source-code handover, staged schedule, payment split, warranty wording, same-industry cases, and how far AI-friendly work actually goes. Further reading: Seven questions worth asking while comparing bids.

When you sign, check at least four attachment points:

Clause	What to confirm
Copyright	Copyright may stay with the vendor, but usage rights and source code must belong to the client
Termination	Exit terms must be mutual, not a penalty that only the client pays
Delivery list	Name source code, database backup, design files, and admin code
Hosting account	Register the account in the client’s name; the vendor only administers it

Further reading: How to avoid hosting lock-in and a site you cannot move, Contract clauses a custom site should not skip.

How design and build should run

The design stage usually takes 2 to 4 weeks: lock the homepage first, then extend it across the site. A common setup is:

Offer 1 to 2 first directions (more than three makes the choice harder, not easier)
Allow three revision rounds before sign-off, then one small pass after
Return the design source files (Figma or Adobe) to the client

The build stage usually takes 3 to 6 weeks, and this is when owners most often lose the thread: they assume the handoff is the end, then find a week before acceptance that the result is far from what they pictured. A better rhythm is:

Hold a fixed 30-minute progress check each week (online is fine; skipping it is not)
Give a test URL in the build environment so progress is visible every week
Load copy while development is underway, instead of dumping it all at the end; one project stretched from six weeks to ten only because the copy was never finished

Acceptance list and post-launch cover

Acceptance should clear at least five items:

A cross-browser test report (Chrome, Safari, Edge, and mobile Safari all pass)
Responsive screenshots (phone, tablet, and desktop)
Structured data verified in Search Console
Admin training (video or written guide)
Signed receipt of source code, database export, and Figma design files

Post-launch cover should be written into the contract:

At least one free year for code errors, cross-browser faults, SEO meta issues, broken structured data, and form failures
New features, redesigns, and large content updates outside that scope are priced separately

Further reading: How to check a website delivery list, How to estimate a build schedule.

Five traps that catch clients most

Trap	Typical result	How to prevent it
1. Comparing prices with no brief	Quotes can differ by five to ten times and cannot be compared	Spend about a week writing the brief; the vendor can help
2. Paying more than half up front	The vendor carries almost no risk while the client carries too much	Pay by milestone and tie each payment to a deliverable
3. Leaving source code out of the contract	Years later the site cannot leave with a change of vendor	State a full handover in the attachment
4. A vague warranty	Every post-launch fault becomes a new invoice	List warranty items line by line in the attachment
5. No AI-friendly requirement	Six to twelve months later the site is hard to surface in AI search	Add AI-friendly conditions to the brief

Further reading: Five mistakes to avoid before you sign, A starter guide to small-business site security.

Three rules before you wrap up

Hiring a design team for the first time is not the scary part. The risk is an unclear process, no idea what to accept, and no idea who owns the next step. Distilled from common practice, three rules are enough:

A clear process beats the lowest quote: a team that can explain all eight stages is usually steadier at delivery.
Payments follow progress: the first installment stays at or under half, and each slice maps to a named deliverable.
Put the acceptance items in an attachment: a verbal “it’s done” is not acceptance; the final payment waits until all five items are checked.

For a finer view of the working rhythm, see how to work through a design-team collaboration. If you are still shortlisting firms, a 2026 website-design company evaluation list sets out criteria and reference names.

ARTICLE