Most of the risk in a website project is not whether it looks good. It is what happens in year three when you want to change something and the person who built it has moved on.
These are the questions worth asking before you sign anything. The answers matter less than whether they are given plainly.
1. Whose name goes on the domain and hosting?
It should be yours. If the answer is anything else, ask why, and be ready to insist.
2. Do I own the finished site?
Ask specifically about the code, the content, and the images. Some agreements license the site to you rather than transferring it, which means you are renting something you paid to build.
3. What happens if we stop working together?
A reasonable answer describes a handover: files, credentials, documentation. An unreasonable one is vague, or reveals that the site cannot leave their platform.
4. What is it built on?
There is no single right answer. What you want is a specific one, and a reason. "A custom platform" that only they can maintain is a lock-in risk regardless of quality.
5. Who can edit it after launch?
Some sites are built for you to edit; some are built to be edited by the developer. Both are legitimate, but you should know which you are buying, and what changes cost if it is the second.
6. What is explicitly not included?
The most useful line in any proposal. Copywriting, photography, ongoing changes, and hosting are the usual gaps. A proposal that lists what is out of scope is written by someone who has done this before.
7. How will it perform on a phone with poor signal?
Especially here. If the answer is only about looking good on mobile, that is a different question from loading on mobile. Ask what the pages will weigh.
8. What happens after launch?
Whether support exists, what it costs, and who provides it. Launch is when real problems first appear, so a handover to nobody is a poor plan.
9. Can I talk to someone you built for?
Not a portfolio screenshot. A conversation, where you can ask what went wrong and how long it really took.
Local, off-island, or overseas
You have three broad options here, and each has a real trade-off.
Someone in the territory. Same time zone, can sit down with you on St. Thomas, St. John, or St. Croix, and already understands why a ferry schedule matters and what a territory address does to an export. Usually costs more per hour than an overseas team and there are not many to choose from.
A mainland US agency. Deep bench, professional process, and no particular feel for how anything works here. Fine for a straightforward website. Less good when the system has to handle multi-island logistics or a local payment processor.
An overseas team or marketplace. Cheapest by a wide margin. The risk is not skill, which is often excellent, but distance: a twelve-hour time difference turns a five-minute question into a two-day round trip, and nobody is available in the week after a storm.
There is no universally right answer. What matters is being clear about which trade you are making, rather than discovering it in month three.
One thing you do not need before you call
Keep reading