Choosing a provider
Small business web development services
Small businesses rarely have someone in-house who can judge a developer's technical choices. Yet those choices decide what the website costs to run, how safe it is and whether another developer could take it over later.
This page explains what to ask a web developer in plain terms, so you can compare providers without needing technical knowledge.
Illustrative diagram
- Account list — domain, hosting, platform
- Access confirmed — all in your name
- Backups — where and how to restore
- Editing guide — common changes
- Custom parts — what they do
- Renewal dates
Avoiding lock-in
Lock-in happens when a website can only be maintained by the person who built it. It can come from a proprietary system, from undocumented custom code, or simply from logins that only the developer holds.
You can avoid it by asking for the site to be built on a widely used platform or with standard tools, for all accounts to be in your name, and for a short handover document explaining how the site works. Any competent developer should be comfortable with all three.
Plain-language questions to ask
| Ask | Good answer includes |
|---|---|
| What will you build the site with, and why? | A reason linked to how you will update the site |
| Who will have the logins? | You, with your own access to everything |
| How will the site be kept secure? | Updates, backups and limited admin access |
| What happens if you are unavailable? | Documentation another developer could follow |
| What will it cost to run each year? | Hosting, domain and any licences listed |
What a handover pack should contain
Access
- List of every account: domain, hosting, platform, email sending
- Confirmation that each is in your name
- Where backups are kept and how to restore one
Knowledge
- How to make common content changes
- Any custom parts of the site and what they do
- Renewal dates for domain, hosting and licences
Looking after the site after launch
You maintain it
Suits you when
- The platform is simple
- You are comfortable applying updates
Watch out for
- Updates must not be ignored
- Keep backups current
Developer maintains it
Suits you when
- The site has plugins or custom parts
- You prefer not to handle updates
Watch out for
- Agree what is included and how quickly issues are handled
Warning signs
Only the developer has access
You cannot change provider or recover the site without them.
No backup plan
A single failure could lose the whole site.
Jargon instead of answers
A developer should be able to explain choices in plain terms.
Working well with a developer
Small business owners are busy, and website projects stall when decisions wait. A good developer asks clear questions in batches, explains the consequences of each choice and tells you what they need and by when.
Agree at the start how you will communicate, how quickly answers are needed and who in your business can approve changes. These simple arrangements prevent most delays.
How a development engagement runs
Brief
What the site must do, who updates it and your budget.
Output: Agreed scope
Build
Site built on the chosen platform with accounts in your name.
Output: Site for review
Test and launch
Forms, speed and devices tested; domain connected.
Output: Live site
Handover
Logins, notes and renewal dates provided.
Output: Handover pack
Security without jargon
For a small business site, good security mostly means doing simple things consistently: a secure connection for every page, software kept up to date, strong unique passwords for each admin account, as few admin accounts as possible and regular backups stored away from the site. Ask a developer which of these they set up and which become your responsibility.
Questions about small business web development services
How do I judge a developer if I am not technical?
Ask plain-language questions about access, security, running costs and documentation. Clear, specific answers are a good sign.
What is lock-in and why does it matter?
Lock-in means only one person can maintain your site. It makes changes expensive and leaves you stuck if they become unavailable.
Do I need a maintenance plan?
Not always. Simple sites may need little; sites with plugins or custom code benefit from regular updates by someone who knows them.
Should I get a handover document?
Yes. It should list your accounts, renewal dates, how to make common changes and any custom parts.
Can you take over a site another developer built?
Usually, yes. We review it first and tell you about any risks before taking it on.
Will you use my existing hosting?
If it is suitable and you have access, yes. If not, we explain why and recommend an alternative.
What if my current developer will not hand over access?
Start with the domain registrar, which usually has a recovery process for the registered owner. We can help you work out what you control and what needs recovering.
Do you work with businesses outside my country?
Yes. We work remotely with businesses worldwide and agree communication times that suit both sides.
Request a Custom Quote
Ask about Small business web development services
Thank you — your enquiry has been sent.
We have received your message and will reply by email. If you need to add anything, email info@letgetgrow.com.