Start from the business goal, not the moodboard
The most common mistake is leading with aesthetics. Visual polish matters, but if it is disconnected from goals you get a beautiful site with few leads. Define what success means first: calls, forms, demos, or purchases.
When the goal is clear, you can judge whether a vendor asks the right questions about audience, pricing, competitors, and existing traffic. If the conversation never leaves fonts and colours, expect a tactical build without strategy.
Five selection criteria that matter
Portfolio relevance beats pretty thumbnails—look for similar business models and clear user flows, not only visuals.
Process should be explicit: brief, IA, design, build, QA, launch, and support. Communication style and realistic pricing for the stated scope round out the checklist.
Red flags worth avoiding
Impossibly fast timelines for complex builds usually mean corners cut on structure, performance, or testing.
Ultra-low prices without a written scope often exclude SEO, speed work, revisions, tracking, and maintenance—then each item becomes an add-on.
Questions to ask before you contract
Ask what will be measured in the first 90 days and how reporting works. Ask what is included versus optional, including revision rounds and post-launch support.
Ask how the platform scales if you add services, languages, or integrations—cheap shortcuts often become expensive refactors.
Final comparison and next steps
Compare proposals on the same dimensions: scope, timeline, outcomes, support, and transparency. SMB teams usually win with a partner who can cover both technical delivery and conversion thinking.
When you are ready, align on a written scope and milestone plan. A good next step is a structured offer with budget band and delivery dates.