8 Questions to Ask the Nephew Who's Building Your Website
Reed Verdesoto · · 5 min read

Before someone builds your website, ask how people will find it, how inquiries will reach you, how it will connect to your other tools, and who will keep it working. A good-looking page is part of the job. These eight questions help you understand whether there is a plan for the rest.
Your nephew might be a good builder. So might your friend, a freelancer, or the agency you have been talking to. The point is to understand what they are building and what you will be responsible for when they are done.
You do not need to know the technical answers. You need someone who can explain the answers in terms of your business.
1. How will people who have never heard of me actually find this?
Ask what someone would search for when they need what you do. Then ask which page on your website will answer that search.
A useful answer connects your services, your customers' questions, and the structure of the site. It also explains how you will check whether people are finding you. Nobody can promise where you will rank. They can explain what they are doing to make the site understandable and findable.
If the entire plan is for you to share the link, make sure you know that before you pay for the build.
2. What does ChatGPT and AI know about my business and how does it answer someone looking for what I do?
Start with whether the public information about your business is accurate. Your website should clearly explain who you help, what you do, and how someone takes the next step. The same facts should agree wherever your business appears.
AI search answers can vary, and a builder cannot guarantee a recommendation. Ask how they will make your information accessible, check the answers that appear, and correct the sources when something is wrong.
The useful answer is a plan for clear information. A promise that AI will send you customers is not enough.
3. Do I have to update my website, my Facebook, my Instagram, and everywhere else separately or is there a plan?
Pick a normal change in your business. New hours. A new service. A different booking link. Ask the builder to walk you through every place that change needs to happen.
Some updates can be shared between tools. Others need a person to review or publish them. What matters is knowing where the current information lives, which changes move automatically, and who handles the rest.
A connection should remove work you actually do. You should not have to discover the missing steps after a customer shows up at the wrong time.
4. When someone fills out a form, books a meeting, or reaches out through my site, where does it go and is there a record so it doesn't get lost in my inbox?
Ask to follow one inquiry from beginning to end. Where is it stored? Who gets notified? How do you know someone responded? What happens if the notification fails?
An email can tell you that something happened. A record lets you find it again and see what happened next. You need to know which tool holds that record and who owns the follow-up.
Before launch, test the whole path with an agreed test submission. Seeing a success message on the website is only one part of that check.
5. How do you know what's actually right for my business and not just a template that looks good?
Listen for questions about your customers, your work, and what is currently getting in the way. A builder needs those answers to decide what belongs on the site and what the site needs to do.
Ask them to explain one important design choice. Why is this page here? Why is that the main action? What does the customer need to understand before taking it?
A template can be a useful starting point. The decisions still need to come from your business.
6. How do I know what tools and subscriptions to keep, what to cut, and what's actually being used?
Start with a list of what you already pay for and what each tool does. Ask where features overlap, which tools contain important records, and which connections depend on them.
Then ask for the expected ongoing costs of the proposed build. Hosting, booking, forms, email, and maintenance should be understandable before you take them on.
Do not cancel something just because another tool looks similar. First establish what uses it and how you would move the information or replace the work it does.
7. After you're done and this is in my hands, how do you make sure I know how to use it correctly?
Ask to see the handoff plan. You should know how to make a routine change, find an inquiry, manage access, and get help when something goes wrong.
Written instructions are useful. So is practicing the tasks you will actually do. A walkthrough is more useful when you are the one making the change and the builder is there to help.
Make sure you know which accounts you own and where your access is managed. Knowing how the system works includes knowing how to get into it.
8. What happens to all of this when you get busy with something else?
Ask who is responsible after launch. Who handles updates? What does ongoing support include? How do you request a change, and what happens if the original builder is unavailable?
The answer should include a practical way for someone else to understand and maintain the work. That means access, documentation, and clarity about the services the site depends on.
You are planning for the ordinary life of a business. People get busy. Priorities change. Your website should have a plan for that.
If your nephew went quiet on any of these, that's your answer.
You can bring these questions to any builder. If the bigger problem is that your online presence no longer matches your business, start with Presence. If you want to work through what is actually going on, we can start with a conversation.