Choosing who builds your website, app or automation is an important decision. Portfolios and prices only tell part of the story. The answers to a few simple questions often reveal far more about how a project will actually go.
How do you start a project?
Listen for a process that begins with understanding your business and goals, not with a design or a price. A good partner will ask about your customers, your current tools and what success means to you.
It is a good sign if they ask about your budget and timing early and explain how those choices shape the project. It is a warning sign if every request gets a quick yes without any questions about why you need it.
Who will I talk to, and who does the work?
Ask who your main contact will be and who will actually work on your project. It is reasonable to want one clear point of contact and to know in advance if other people will be involved or will need access to your systems.
Ask how quickly they usually reply to messages and which channel they prefer. Agreeing on this at the start avoids frustration later, especially when a decision is needed quickly.
What exactly is included?
A written scope protects both sides. Ask for it to cover:
Also ask how they handle changes once the work has started. A clear answer, such as estimating the change and waiting for your approval before doing it, keeps the budget predictable and avoids awkward surprises on the final invoice.
- The pages, features or automations included
- How many rounds of feedback and changes are expected
- What happens if you want to add something later
- Any third-party costs such as hosting, domains or subscriptions
How will I see progress?
Regular check-ins and working previews let you give feedback early, when changes are easy. Be cautious of projects where you see nothing until the very end.
Ask to see a project plan with the main stages and what you will be asked to review at each one. Knowing when your input is needed lets you plan your own time, which often matters as much as the developer’s schedule.
Who owns the finished work and my data?
Make sure you will own your website or software, your domain name and your data, and that you will have the access details you need. You should be able to move to another provider in the future without starting over.
Ask specifically whose name the domain, hosting and app store accounts will be registered in. Ideally they belong to your business from day one, with the developer given access rather than ownership. Ask too where the code will be kept and whether you will receive a copy.
Clear answers here are a sign of a trustworthy partner. Vague answers about ownership are worth pausing on before you sign anything.
What happens after launch?
Websites and software need care: updates, security fixes and small changes. Ask what support is available after launch, how it works and what it costs, so there are no surprises later.
Ask what a typical month of support includes, how urgent problems are handled and how quickly you can expect a reply. If you prefer to manage small updates yourself, ask whether they will show you how.
Questions they should be asking you
A good conversation runs both ways. Pay attention to what the developer wants to know about you. Thoughtful questions show they are thinking about your business, not just the technology.
If the conversation leaves you with clearer thinking about your own project, even before any work begins, that is usually a sign you are talking to the right people. Take notes during each conversation, and compare the answers side by side before you decide.
- Who are your customers, and what do they need from you?
- What is not working today, and what have you already tried?
- Who will make decisions and give feedback on your side?
- What content, photos and logins do you already have?
- Is there a date that truly matters, and why?