Define the business outcome first
Choosing a studio starts before you look at technology. Write down what should change after launch: more qualified enquiries from search, a clearer sales journey, self-service ordering, or one workspace replacing scattered spreadsheets and messages.
This helps you reject proposals that sell screens without connecting them to an outcome. A strong supplier asks about the audience, primary journey, traffic sources, required functions and constraints. If the conversation begins with button colours and animation styles, product discovery has not happened yet.
Use one sentence: “We need a website so that [user] can [action], allowing the business to achieve [result].”
Look for evidence in the portfolio
Do not count thumbnails. Open the work on a phone, try the forms and navigation, and check how quickly the offer becomes clear. For a web service, accounts, roles, status changes, uploads, notifications and administration are more useful evidence than a polished homepage.
Ask what problem the project solved, what the team actually delivered and which constraints shaped the result. A concept can demonstrate visual ability, but it cannot prove production experience. Live links, a detailed case study and honest labels for concept work create a much more reliable picture.
| What to inspect | Good evidence | Risk |
|---|---|---|
| Mobile experience | Readable content, clear CTA, usable forms | A desktop layout merely shrunk down |
| Live delivery | Working link and decisions explained | Only screenshots without context |
| Complex features | States, data and admin workflow shown | Claims without a working example |
Inspect process and scope
Before signing, you should understand how the task becomes a release: brief, scope, structure, design, development, responsive testing, domain setup and production launch. Services add database design, permissions, failure states, security checks and operational monitoring.
Ask what the price includes: mobile layouts, content support, basic SEO, analytics, forms, spam protection, deployment and post-launch fixes. Also define what counts as a new feature. A proposal does not need minute-by-minute accounting, but it must make the boundary of the result visible.
“Any website in three days” can be honest for a fixed template. For custom design, client accounts or integrations, a final price before discovery usually means hidden assumptions or later extras.
Ownership, access and security
The business should normally own its domain. Agree how access to hosting, databases, email delivery, analytics and source code will be transferred. This is not distrust; it prevents one supplier account from becoming a single point of failure.
If users have accounts, ask how passwords are stored, whether email is verified, login attempts are limited, roles are separated, actions are logged and backups are tested. A simple landing page does not need bank-level controls, but personal data should never rely on an obscure admin URL for protection.
Assess communication early
The first exchange predicts the working relationship. Useful questions reduce ambiguity; useful answers explain choices in plain language and separate facts from assumptions. Check who approves work, how often progress is visible and where changes are recorded.
A client portal with statuses and message history cannot replace professional delivery, but it reduces lost context. A returning customer should be able to start another project without entering identity and contact details again.
Red flags
- A final price appears before questions about goals, content and functionality.
- The contract does not define deliverables, review windows or change control.
- Domain, account and source-code ownership remain vague.
- Every example is a mockup while complex production experience is claimed.
- SEO is sold as a guaranteed first position for any query.
- Security is reduced to an SSL certificate and nobody discusses backups.
A short decision checklist
Compare suppliers against one required scope instead of different assumptions.
Why is this structure or technical approach appropriate for the goal?
Access, source code, instructions and support terms should be clear before payment.
The best proposal makes the outcome, boundaries, responsibility and next step understandable.
Need a transparent project estimate?
KAMERTON fixes scope, price and timeline after a short brief, with progress kept visible in the client area.
Describe your project →