Advice on this often reduces to a list of questions. Useful, but incomplete — because the answers matter less than whether they’re specific, and because the questions they ask you are often more revealing than anything on your list.
Here’s what’s worth asking, including the parts that feel awkward.
About the work itself
“What exactly is included, and what isn’t?”
The best answers volunteer the exclusions before you ask. Someone who’s run enough projects knows precisely where scope disagreements happen and heads them off. Vagueness here isn’t laziness — it’s a preview of how the conversation goes in month two when you want something that wasn’t discussed.
“Can I see work you’ve done recently?”
Recent matters more than plentiful. A portfolio of work from four years ago tells you what someone used to be able to do. Ask for something live you can actually open and click around in — a real site serving a real business beats a polished case-study image every time, because you can inspect it yourself.
“What do you need from me, and when?”
Late or missing content — copy, photos, business details — can stall a project that’s otherwise ready to move. Someone who can answer this crisply — content, photos, business details, in this order, by this point — has done this before. Someone who hasn’t thought about it will discover the bottleneck at the same time you do.
“How many rounds of changes are included?”
Not because you’ll use them all, but because the answer reveals how the scope is structured. “Unlimited” usually means the price already assumes a lot of them.
About what happens after
“Do I own the domain, the content, and the site?”
Ask about all three separately — they can be held by different people. What you actually own goes into why this matters more than it sounds like it does, including what the major platforms’ own documentation says you can and can’t take with you.
“What happens if something breaks?”
Get specifics: what counts as a defect versus a change, how long defects are covered, and what changes cost afterward. “We’ll take care of you” is warm and unenforceable.
“Can someone else work on this later?”
You’re asking whether the site is built on something standard or on a proprietary system only they can maintain. This is the difference between hiring someone and marrying them.
The uncomfortable ones
These feel rude. Ask them anyway — a professional won’t be offended, and the reaction itself is informative.
“Who is actually building this?”
At agencies, the person selling the project may not be the person doing the work. That’s not inherently bad, but you should know it, because what you saw in the pitch and what you get can drift. With a solo builder the answer is obvious, which is one of the genuine advantages of hiring one.
“What happens if you become unavailable partway through?”
This is the structural weakness of hiring one person, and it deserves a direct question rather than an assumption. We’re not going to attach a statistic to how often projects stall this way — nobody publishes reliable data on abandoned web projects, and the figures that circulate are estimates dressed up as measurements. What’s true without a number: with a solo builder there is no second person, so the plan for that has to be explicit.
Good answers are concrete: staged payments tied to progress, work you can retrieve mid-project, code stored somewhere you can access. “That won’t happen” is not an answer.
“What would make you turn this project down?”
Someone who says yes to everything either has no standards or no work. A designer who can describe the projects they’d decline is telling you they have a wheelhouse — and that they’d tell you if you fell outside it, rather than taking the money and improvising.
Three where the answer’s shape is the tell
For these, listen less to what’s promised and more to how specifically it’s said. A strong answer names accounts, timings, and documents; a concerning one names vibes.
“Who registers and controls the domain?” Why it matters: losing access to the registrar account can disrupt your website and your email, and it means someone else controls your business’s address online. A strong answer sounds like: “You register it in your own account, and we never need your password” — or “we register it and transfer it into your account at handover, and you keep the login.” Either shape is fine. What matters is that the domain ends up in an account that is yours, and that nobody needs to hold your registrar credentials to keep the site working. A concerning answer sounds like: “We handle all that for you.” Convenient, common, and exactly how the domain trap gets set — usually with no bad intent at all.
“What access will I hold when we’re done?” Why it matters: access is the practical form of ownership. A strong answer sounds like: a short list — hosting account, files, form destination, Search Console — with which are yours outright. A concerning answer sounds like: “You’ll have everything you need.” Which, translated, means they haven’t decided, or you won’t.
“Who writes the content, and what happens if I’m slow delivering mine?” Why it matters: late or missing content can stall a project that’s otherwise ready to launch, and the answer reveals whether they’ve managed that reality before. A strong answer sounds like: a clear split — what you supply, what they write, and what happens to the schedule when materials arrive late. A concerning answer sounds like: “We’ll figure that out as we go.” That’s a timeline dispute with a start date.
Context matters with all of these — a concerning-shaped answer is a prompt to dig, not proof of bad faith. Some excellent providers just communicate loosely. But a crisp answer is a sign someone has thought about it before.
What their questions tell you
This one gets overlooked. Pay attention to what they ask you before quoting.
A designer who asks what the site is supposed to do — bring in leads, replace phone calls, look credible to a specific kind of customer — is going to build something aimed at that. One who only asks how many pages you want is going to build you however many pages you asked for, and whether it works is your problem.
Someone who asks about your customers, your competitors, and what happens after a visitor lands on the page is doing the actual job. Someone who leads with platform preferences is selling you what they already know how to make.
A quote issued without meaningful discovery is a reason to ask how the provider understood the scope.
Signals worth weighting
Response speed during the sales conversation. Not because urgency is a virtue, but because it’s one of the few things you can observe before committing. Pre-sale communication can be a useful signal about communication habits, but it is not a guarantee of project response times.
A plain-English written agreement. Scope defined, ownership defined, timeline defined, what happens if things end. This protects both sides, and someone who resists putting it in writing is telling you something.
Willingness to say the unhelpful thing. A designer who tells you that you don’t need what you’re asking for — or that a site builder would serve you better right now — is demonstrating that their advice isn’t purely a function of what they’d get paid. Custom build vs. website builders is the version of that conversation we’d have with you before quoting.
Where TruePoint sits
There’s no handoff from a salesperson to a separate delivery team. TruePoint is a one-person studio — every site is scoped, designed, and built by the same person — with Aster as the communication layer from the first message through launch, so there’s no gap between what gets discussed and what gets made.
That means the continuity question above applies to us in full, and here is our answer to it, managed the way this guide says it should be: the site is built on a standard foundation another developer could take over; your domain, hosting, and accounts sit in your name; and if we can’t complete a project, our terms require a prompt refund in full, with the obligation sitting on us rather than on you. Payment is in full before work begins, so that refund obligation is the protection, and it is written down rather than implied. Builds run about a week, which keeps that window short.
Pricing is published rather than quoted case by case, and scope is agreed in writing before anything starts, so “what’s included” is settled before money moves. Our work is live and inspectable — you can open the Appalachian Home Worx site and click through the real thing rather than looking at a screenshot of it.
Defects in the agreed scope are fixed free for 30 days after launch; changes are quoted per job, with no retainer.
And to the last signal above: if a project isn’t a fit — you need frequent self-editing, or you’re early enough that a site builder genuinely serves you better — we’ll say so. What a small business website actually costs includes the cases where hiring anyone is the wrong move, and the website packages page lists exactly what each scope covers if you’d rather start there.