Páginas Web en PRA project by R21 Digital
← All posts

Questions to ask before hiring a website developer in Puerto Rico

· 5 min read · Updated

Reviewed by Carlos Jiménez, Owner & Digital Director

A new website feels like a big step. You want to get it up and running, so you might rush through the first call. But the questions you skip now are exactly the ones that cause headaches later. Here's a checklist to bring to that first conversation with whoever will build your site. Ask about these five things before you agree to anything.

Whose name is on the domain?

Your domain, like yourbusiness.com, is the address customers type or tap to reach your site. If someone else registered it under their own account, you depend on that person for renewals, moves, or any changes. Many developers register domains under their own account because it's faster. But later, when you want to switch providers, you need that person to give you access. If they don't respond, you waste time and could lose control of your brand.

Ask directly: "Will the domain be registered under my name, my email, and my payment method?" The right answer for a business owner is yes. If you already own a domain, don't just hand it over. Keep it in an account you control and add the developer as a technical contact if needed. Also ask who pays for renewal and when it expires. A forgotten domain can fall into someone else's hands.

At Páginas Web en PR, if you ever leave, we transfer everything to you: the domain, the site files and the content, once any pending balance is paid. Our FAQ explains how it works.

Who pays for and controls the hosting?

Hosting is the space on a server where your website lives. If the developer sets it up under their own account, you don't see invoices, you don't get alerts, and you can't move the site when you want. That creates an uncomfortable dependency. If the relationship goes bad, your site could go offline because the account isn't in your name.

Ask: "Will the hosting be in my name or in your account?" Both answers can work. If it's in your name, you see the invoices and can give access to anyone you hire. If the provider manages it, get it in writing that they will transfer the whole site to you if you leave. What can't happen is not knowing which one you have. Also ask what hosting costs, who pays it, and what's included: security certificate, backups, business email.

If a provider says hosting is "included", ask for details: what it covers, and how you would take your site with you if you switch providers. This isn't about distrust; it's about protecting your business. Our pricing page shows what we charge for hosting and maintenance, and our FAQ explains what happens to your site if you ever leave.

Who can edit the site after launch?

Many business owners end up trapped because every change requires calling the developer and waiting. A simple change to your hours or adding a new menu item shouldn't cost you phone calls or days. Before you hire, ask: "Will I be able to make basic edits myself, or will I always have to ask you?"

The right answer makes it clear from the start how changes get made: whether you make them yourself, or the provider does and what that costs. If you have a menu, a product catalog, or a news section, ask how each of those gets updated. Also ask if edits can be made from a phone, because many owners in Puerto Rico work from their phone, not a desktop computer.

Some providers will give you a manual or a short video. Ask to see an example of how a page is edited before you sign. If the answer is "don't worry, we handle that", ask what they charge per change. That way you avoid surprises when you need to publish a promotion on a Friday night.

What happens if the relationship ends?

Business relationships change. You might want a different developer, or the developer might close their operation. If you didn't make things clear at the start, you could lose access to your site, your domain, or your content. That's a preventable disaster.

Ask: "If we part ways, what exactly do I get?" You should receive the domain, a full copy of the site and its content, and the login credentials for anything that stays with you. A decent provider will spell out a clean handover process before you sign.

If you're unsure what a fair handover looks like, ask the provider to spell it out in the contract before you sign.

Get the scope and price in writing before work starts

Verbal promises don't protect you. Ask for a written proposal that lists exactly what you're paying for: pages, features, revisions, and any ongoing costs. Does it include training, content migration, or basic SEO? If something isn't in the proposal, assume it isn't included.

Also ask about the timeline: when will the project start, when will it finish, and what happens if it's delayed. Don't accept vague answers like "it depends" without a clear range. A written agreement protects both sides. It doesn't have to be complicated, but it should be specific. Before you sign, read it carefully. If you have questions, ask them now, not after the first invoice.

Frequently asked questions

Should the domain be in my name or the developer's?

Ideally, yes. That way you control renewals and can move it if you change providers. If the developer registers it, get it in writing that they will transfer it to you if you leave.

What if the developer says hosting is included but won't give me access?

Ask how you would take your site with you if you leave, and get the answer in writing. Some providers put the hosting account in your name; others manage it and transfer everything to you when you go. Either can work. Not knowing which one you have is the problem.

Do I really need everything in writing?

Yes. Verbal promises are hard to enforce. A written proposal with scope, price, and timeline protects both you and the developer. It doesn't have to be long, but it should be specific.

How does your site score today?

Check it for free before you ask for a price. It takes a few seconds.

Free check · no sign-up

Enter your domain and we'll check, on your own site, whether ChatGPT, Perplexity and Google can read it: robots.txt, llms.txt, structured data and more. It takes a few seconds.