Table of contents
Open the sites of five website development companies and the portfolios look interchangeable: clean heroes, smooth motion, consistent palettes. But a portfolio shows outcomes, not process — and nearly all project risk lives in the process. Who defines requirements, who chases the schedule, who maintains the thing after launch.
1. Agree on What "Good" Means First
A good website is not a good-looking one. It is one that carries a business objective. So the conversation should start with three statements: whether the site will capture search traffic or receive paid traffic, which customer type it addresses, and what action a visitor should take.
A vendor who starts discussing style has a template in mind. A vendor who asks about the acquisition path and the content inventory has run whole projects.
2. Six Questions
| Question | What a good answer sounds like | Red flag |
|---|---|---|
| How many projects in our industry? | Specific sectors and counts | "We do everything" |
| Who writes the requirements? | A dedicated planner or PM | You fill in their template |
| How is progress reported? | Fixed milestones and weekly notes | "Just call us anytime" |
| Who maintains it after launch? | Named responsibility and response time | Maintenance billed separately, undefined |
| Who enters the content? | Migration support or training | Pushed entirely to the client |
| How is data handed over? | Admin accounts and source files | Vague |
There are no standard answers, but the specificity of the answers reveals working habits. The more concrete the reply, the fewer arguments later.
3. Compare Quotes in Three Layers
Layer one, fixed deliverables: page count, section structure, languages, form count. This layer defines what you buy.
Layer two, service boundary: revision rounds, content entry, image processing, deployment, and who owns domain and hosting.
Layer three, ongoing cost: maintenance, renewals, and how new features are priced.
Comparing only totals produces the "cheaper is more expensive" outcome: the low bid excludes content entry and image work, and the client supplies the missing labour and time.
4. Verifying a Portfolio
Ask three things: is the site still running, how long did the project take, and what was added afterwards.
Then look at details: mobile typography, article reading experience, the feedback after a form submits. These say more about engineering quality than a hero animation.
For a conventional corporate portal, focus on section structure and permission design. Companies asking which vendor builds the better site are usually building for the first time; write the requirement list in the three layers above before requesting quotes.
5. A Low-Cost Test
Before signing, assign a small task: rebuild one existing page for mobile, or produce a landing page from your product material.
Delivery quality, communication speed, and whether they ask questions will predict the main project. It costs little and avoids a lot.
6. FAQ
Quotes differ by a factor of two. How do we judge? Put the deliverable lists side by side. The gap usually sits in page count, revision rounds and content entry. Those items are the price difference.
Should we sign a long maintenance contract? Start with one year, with response time and scope written in, then decide on renewal after seeing it work.
Can a corporate site be built by a freelancer? For a small brochure site, yes — but secure the source files and admin access, and agree how future changes are handled.
Related
- See also: planning site sections from customer questions
- See also: a website acceptance checklist
GrowLab focuses on integrated content marketing, covering brand strategy, website development and search marketing (SEO/GEO). Contact us for an assessment of your own promotion plan.
Need a professional growth plan?
Add our WeChat for a tailored strategy and annual quote.
Contact Us