The right partner starts with understanding
You do not choose a web partner only by looking at a beautiful portfolio. The more important question is whether the team understands your business problem, makes difficult choices visible and takes responsibility for what happens after launch.
A studio can be technically strong and still be a poor fit for the way you work. A smaller partner may offer exactly the attention and context a complex SME offer needs. Use the first conversations to explore that fit.
Nine questions for a first conversation
1. What problem are we trying to solve?
A good partner does not immediately jump to colours, technology or a list of features. They first ask what is not working today: do customers struggle to find the offer, is the site difficult to maintain, has the organisation changed or are enquiries declining?
Listen for whether the answer becomes a concrete approach. If every conversation starts with screens before anyone asks about customers and the offer, important strategy may be missing.
2. How will you learn about our business?
Ask how information is gathered. That may include a discovery conversation, interviews, existing data, customer questions, cases or a workshop. The process does not have to be heavy, but it should go further than a standard questionnaire.
You should be able to explain why a certain structure, message or feature fits your situation.
3. Who makes which decisions?
Ask who guides strategy, UX, copy, design and development. One point of contact makes it easier to keep decisions connected, but only if that person has real overview and decision-making responsibility.
A clear division of roles prevents you from repeating the same context five times or coordinating separate suppliers yourself.
4. What do you need from us?
A website project moves faster when both sides know what is required. Ask which copy, imagery, feedback and approvals are needed and when. Also ask what happens if that input arrives late.
Use the SME website briefing checklist as a starting point for the conversation.
5. How do you work with content?
Content is often the largest invisible part of a website project. Ask whether the partner only places your copy, helps edit it, writes it or works with you to sharpen the message.
A reliable partner does not pretend missing content will appear by itself. They make clear what exists, what needs to be created and who checks the facts.
6. Who owns the website after launch?
The domain, hosting, accounts, source code, licences, analytics and content are practical parts of ownership. Ask where they live, who has access and how a handover works if you change partner later.
Also read how to agree CMS, ownership and maintenance arrangements. A good answer is not defensive; it makes the collaboration safer for everyone.
7. How do you test before launch?
Ask how the site is checked for mobile use, forms, links, performance, accessibility, language versions and indexability. You do not need a technical report, but you should understand what “ready” means.
A checklist is useful, but ask who walks through the important routes as a real visitor. A form can work technically and still be unclear.
8. What happens after launch?
Discuss training, maintenance, support, security updates and focused improvements. Not every business needs an ongoing retainer, but every business needs a plan for who maintains the site and what happens when something changes.
Ask for a simple distinction between included work, optional help and external services such as advertising campaigns or ongoing content production.
9. What does a good collaboration look like?
Ask how feedback is gathered, how decisions are recorded and how the schedule is managed. A good process makes room for discussion early and clear decisions later.
Notice how the conversation itself feels. Are questions answered calmly? Are limitations stated honestly? Does the proposal use your words rather than a standard package?
Signs of a good fit
A suitable web partner:
- asks questions beyond the homepage;
- makes scope, content and responsibilities visible;
- shows work with an explanation of choices and outcomes;
- talks about technology clearly without hiding behind it;
- gives you access to your own domain, accounts and data;
- promises no fixed Google position or guaranteed enquiries;
- shows how you can continue independently after launch.
Compare the process, not only the portfolio
A portfolio shows the final image, not how a partner handles uncertainty. For two or three relevant cases, ask what problem existed, which choice was difficult, what the client supplied and what happened after launch.
That conversation often tells you more than a gallery of polished screens. You are not looking for a supplier who only executes, but a partner who can reduce complexity to workable decisions.
For example, review The District website case. Read the brief, content structure decisions and visitor journeys alongside the screenshots. Apply the same distinction to every portfolio: what was built, which decisions did the designer make, and which outcomes were actually measured?
UNIZO’s website management guide also covers domains and transfers in Dutch. Record the arrangements for your own project before development begins.
Explore the JF-ICT web design approach or discuss your project.