Googling the term, “top tips on building a great website – can a friend do it”? Yes, a friend can build your business website – provided they have the right experience, capacity and commercial processes.
The problem is not that they are your friend. The problem begins when “I know someone who can knock up a website” is treated as a substitute for strategy, user experience, SEO, development, security and ongoing support.
Your website is often one of the first places a potential customer checks before deciding whether to trust your business. It therefore needs to do far more than exist or look reasonably smart.
TL;DR
A friend or DIY website may be suitable for a temporary, low-risk project, but a business website usually needs specialist support when it must generate enquiries, take payments, manage bookings, rank in search or connect with other systems.
Before choosing who builds it, consider:
- Their design and development experience.
- Their understanding of your audience and business objectives.
- User experience on desktop and mobile.
- Search engine optimisation.
- Hosting, security and backups.
- Accessibility and website compliance.
- Analytics, forms and conversion tracking.
- Ownership of the domain, website and accounts.
- Their availability after launch.
- The effect the project could have on your personal relationship.
A genuinely qualified friend may still be the right person. Just make sure the project is treated professionally from the beginning.
Is it a bad idea to ask a friend to build your website?
Asking a friend to build your website is not automatically a bad idea, but it becomes risky when the decision is based on price or convenience rather than capability, scope and accountability.
Your friend might be a brilliant developer, designer or marketer. They might do this professionally every day and have a process that would put plenty of agencies to shame.
Equally, they might have built one WordPress site, watched a few tutorials and assured you that it will all be “fairly straightforward”.
Those are two very different propositions.
The real question is not:
“Are they my friend?”
It is:
“Can they deliver the website my business needs, and will the project be managed professionally?”
That means considering the strategy, design, content, development, SEO, functionality and support – not just whether they can install a theme and upload your logo.
What does a great business website actually need?
A great business website needs a clear purpose, an intuitive user journey, strong content, reliable development, search visibility and an obvious next action.
How much specialist input it needs depends on what the website is expected to achieve.
A simple site for a temporary community project is very different from an ecommerce website processing payments, a SaaS website managing registrations or a lead-generation site connected to a CRM.
A clear business objective
Before anybody starts discussing colours, fonts or homepage animations, they need to understand what the website is there to do.
Possible objectives include:
- Generating enquiries.
- Selling products.
- Taking bookings.
- Encouraging registrations.
- Attracting investors or partners.
- Supporting recruitment.
- Explaining a complex service.
- Building trust before a sales conversation.
- Improving organic search visibility.
- Giving existing customers access to useful information.
Without a clear objective, website decisions become based on personal taste.
You end up debating whether a button should be green or blue without asking whether anybody can find the button, or whether it leads somewhere useful.
A properly defined audience
A great website is designed around the people using it, not only the people commissioning it.
The designer or agency should understand:
- Who the visitors are.
- What brought them to the website.
- What they already know.
- What information they need.
- What might make them hesitate.
- Which device they are likely to use.
- What action they need to take next.
Your internal team may understand the business perfectly, but your visitors do not have the same background knowledge. Navigation, page structure and content therefore need to make sense to somebody arriving for the first time.
A clear user journey
A user journey is the route somebody takes from arriving on the website to completing an action.
That action could be buying, booking, enquiring, subscribing or simply finding an answer.
Good user experience removes unnecessary effort. Visitors should not need to dig through five menu levels, decode internal jargon or play a digital game of hide-and-seek with your contact details.
A clear user interface helps people understand where they are, what they can do and where they should go next.
For larger website projects, a wireframe can map the layout and user journey before time is spent on the finished visual design.
Strong content and messaging
A beautiful website cannot compensate for unclear messaging.
Visitors need to understand:
- What the business does.
- Who it helps.
- Which problem it solves.
- Why they should trust it.
- What makes it different.
- What they should do next.
Website copy also needs to work with the design. Huge walls of text are difficult to scan, while a page containing six vague sentences and a stock photograph may not give visitors enough information to make a decision.
Content, design and SEO should be planned together rather than passed between separate teams at the last minute.
Search engine optimisation
SEO should be considered while the website structure, pages and content are being planned – not bolted on the day before launch.
A properly planned website should consider:
- Search intent.
- Keyword and topic research.
- Page structure.
- Headings.
- Internal links.
- Metadata.
- Image optimisation.
- Crawlability.
- Indexability.
- Redirects.
- Canonical URLs.
- Structured data.
- Mobile performance.
- Page speed.
A website can look fantastic and remain almost invisible to potential customers.
Our guide to why a business cannot be found online explains some of the wider strategy and visibility issues that can cause this.
Responsive and accessible design
A professional website should work properly across mobile phones, tablets, laptops and larger desktop screens.
That does not simply mean squeezing the desktop layout onto a smaller screen. Menus, forms, text, buttons, images and interactive features need to remain usable.
Accessibility should also be considered throughout the design and content process. This includes readable typography, sensible colour contrast, keyboard navigation, descriptive image alt text, clear link wording and properly labelled forms.
These details improve the experience for real people. They should not be treated as optional finishing touches.
Reliable technical foundations
Websites depend on technology that most visitors never see.
This can include:
- The content management system.
- Hosting.
- Domain and DNS configuration.
- SSL certificates.
- Plugins and integrations.
- Forms.
- Payment providers.
- Booking systems.
- CRM connections.
- Analytics and tracking.
- Backups.
- Security monitoring.
- Email delivery.
Someone building a website should be able to explain who is responsible for each part.
For a plain-English explanation of one of those foundations, see our guide to web hosting.
Privacy and cookie management
A website may collect information through forms, analytics, advertising platforms, ecommerce tools and embedded services.
The build therefore needs to consider privacy notices, cookie controls, consent settings and how data moves between systems.
It is surprisingly easy to add a tracking tool or plugin without fully understanding what information it collects. Our guide to website cookies and cookie management explores this subject in more detail.
Testing before launch
A website is not ready merely because the homepage looks good on the designer’s laptop.
Testing should cover:
- Mobile and desktop layouts.
- Major browsers.
- Forms and email notifications.
- Payment or booking journeys.
- Internal and external links.
- Page speed.
- Tracking and analytics.
- Search-engine crawlability.
- Redirects.
- Error pages.
- Cookie controls.
- Accessibility basics.
- Spelling and content accuracy.
The person building the website should have a clear launch checklist and know how to fix anything that goes wrong.
Support after launch
A website is not finished when it goes live.
Content changes. Software is updated. Plugins become incompatible. Team members leave. Services evolve. Search behaviour shifts. Forms occasionally stop behaving themselves.
Someone needs to own:
- Updates.
- Security.
- Backups.
- Content changes.
- Technical fixes.
- Performance monitoring.
- SEO improvements.
- New functionality.
- User feedback.
- Account and password management.
KAYBE’s current website design, development and SEO support brings these areas together so the website remains useful after launch day.
Why can a cheap website become expensive?
A cheap website can become expensive when missing strategy, technical shortcuts and unclear ownership create additional work later.
The initial build price is only one part of the real cost.
You should also consider:
- Your own time managing the project.
- Delays caused by limited availability.
- Paid themes, plugins and software.
- Hosting and domain charges.
- Content writing.
- SEO repairs.
- Security problems.
- Accessibility corrections.
- Broken integrations.
- Rebuilding work that cannot be expanded.
- Lost enquiries while the site underperforms.
A low-cost build can still offer excellent value when the requirements are simple and the scope is clear.
The warning sign is a price that appears low because important work has not been discussed.
Before making a decision, confirm exactly what is included, excluded and expected from you.
What can go wrong when a friend builds the website?
The most common risks are unclear boundaries, inconsistent availability, missing specialist skills and uncertainty about who is responsible when something goes wrong.
None of these mean your friend is unreliable. They mean personal favours and commercial projects operate differently.
The project drifts
A professional project should have an agreed scope, milestones, feedback stages and launch process.
A favour is more likely to be completed around evenings, weekends and other commitments. That may be acceptable at first, but frustrating when a launch date or campaign depends on it.
Feedback becomes awkward
Telling a supplier that a page does not work is a normal part of a commercial project.
Telling a friend that you dislike the design they spent three weekends creating can feel rather different.
Clear review stages and written deliverables help prevent feedback from becoming personal.
Nobody has full ownership
Problems often appear after launch:
- Who owns the domain?
- Whose email address controls the hosting?
- Where are the backups?
- Who has administrator access?
- Who owns the theme or plugin licences?
- Can another developer take over?
- What happens when an update breaks something?
These questions should be answered before the build begins.
One person cannot cover every discipline
Website projects can involve strategy, UX, UI, branding, copywriting, SEO, development, accessibility, analytics, integrations and technical support.
A talented individual may cover several of those areas brilliantly. Very few people specialise in all of them.
Where skills are missing, confirm whether additional specialists will be involved.
The friendship carries the risk
A commercial agreement gives both sides a framework for resolving problems.
A loosely defined favour can create resentment:
- The business expects more work.
- The friend feels taken for granted.
- The deadline keeps changing.
- Extra features appear without extra budget.
- Support is expected indefinitely.
Protect the friendship by treating the project professionally.
When is a friend or DIY website good enough?
A friend or DIY website may be entirely suitable when the project is simple, the commercial risk is low and you understand its limitations.
Examples might include:
- Testing a new business idea.
- Creating a temporary event page.
- Building a small personal portfolio.
- Publishing basic contact information.
- Launching before a larger website budget is available.
- Creating an internal or community resource.
A template may also provide everything a small organisation needs.
The choice between custom web design and a website template should be based on objectives, functionality, flexibility and budget – not the assumption that one route is always right.
A DIY or friend-built website becomes less suitable when it is responsible for:
- Significant lead generation.
- Ecommerce revenue.
- Online payments.
- Complex bookings.
- Sensitive data.
- Business-critical integrations.
- Competitive organic search visibility.
- Multiple customer journeys.
- A major repositioning or rebrand.
The greater the commercial importance, the stronger the case for specialist support.
How should you choose a professional website partner?
Choose a website partner by assessing their process, relevant experience, technical capability, communication and approach to ongoing support.
Do not make the decision based only on the portfolio.
A visually impressive website may still be slow, difficult to update, poorly structured or invisible in search.
Ask potential partners:
- How will you understand our audience and objectives?
- Who will work on strategy, design, content, SEO and development?
- What is included in the agreed price?
- Which platform do you recommend, and why?
- How will the site work on mobile devices?
- How will accessibility be considered?
- What SEO work is included?
- Who writes and uploads the content?
- How are forms, analytics and integrations tested?
- Who owns the website, domain and accounts?
- What happens if the project changes?
- What support is available after launch?
- Can another supplier take over the website later?
- How will success be measured?
A good partner should explain their recommendations clearly rather than hiding behind technical language.
Our guide to working with a digital agency provides more advice on evaluating expertise, processes and working relationships.
What should be agreed before the website build starts?
The scope, responsibilities, ownership, timings, costs and post-launch support should all be agreed before design or development begins.
At minimum, document:
- The website objective.
- Target audiences.
- Required pages.
- Features and integrations.
- Content responsibilities.
- SEO deliverables.
- Design and feedback stages.
- Accessibility requirements.
- Testing responsibilities.
- Hosting arrangements.
- Domain ownership.
- Account access.
- Launch responsibilities.
- Training.
- Maintenance and support.
- Costs for changes outside the scope.
- What happens if either party cannot complete the work.
This may feel formal when working with a friend.
That is precisely why it is useful.
Clear expectations protect the business, the person doing the work and the relationship between you.
Key takeaways
A friend can build a great business website when they have the necessary experience, availability and professional processes.
Before making the decision, remember:
- A website needs a clear commercial purpose.
- Design should begin with the audience and user journey.
- Content, SEO and development need to work together.
- Mobile usability and accessibility should be considered from the start.
- Hosting, security, privacy and tracking need proper ownership.
- The cheapest initial option is not always the cheapest long-term option.
- Scope, deadlines, accounts and intellectual property should be agreed in writing.
- Ongoing maintenance matters just as much as launch day.
- A professional relationship can protect a personal friendship.
- The right solution depends on the website’s importance to the business.
Your mate may be exactly the right person.
Just make sure the decision is based on more than a friendly price and the promise that it will only take a couple of weekends.
Frequently asked questions
Should I build my own business website or hire a professional?
Build it yourself when the requirements are simple, the commercial risk is low and you have enough time to learn the platform. Hire a professional when the site needs to generate leads, rank competitively, take payments or connect with business-critical systems.
Is it a bad idea to let a friend build my website?
Not necessarily. A qualified friend can produce an excellent website. Treat the arrangement as a professional project, with a written scope, realistic deadline, agreed price and clear ownership of every account.
Is hiring a professional web designer worth it?
It is usually worth it when the website has an important commercial role. A professional should help with strategy, user experience, design, development, mobile performance, SEO, testing and post-launch support—not only how the site looks.
How much does a professional business website cost?
The cost depends on the number of pages, design requirements, content, functionality, ecommerce, integrations, SEO and support. Compare like-for-like scopes rather than choosing the lowest headline figure.
Will hiring a web designer help my website rank on Google?
It can improve the website’s foundations, but hiring a designer does not guarantee rankings. Search visibility also depends on technical SEO, content quality, competition, authority, internal links and ongoing optimisation.
Who should own my domain and website hosting?
The business should normally retain ownership and administrative access, even when an agency or developer manages the accounts. Make sure the registration details, passwords and renewal arrangements are documented.
Can I update the website myself after launch?
Usually, yes. Ask which content management system will be used and what training is included. Also confirm whether changing certain templates, features or integrations will still require developer support.
Do I need website maintenance after launch?
Yes. Websites need software updates, security monitoring, backups, content changes and performance checks. Maintenance reduces the risk of technical issues and helps the site continue supporting the business.
How long does it take to build a business website?
It depends on the scope, content, feedback process, functionality and availability of everyone involved. Agree milestones and responsibilities at the start, because delayed content and feedback are common causes of project slippage.
What should I look for in a website designer or agency?
Look for relevant experience, a clear process, strong communication, transparent pricing and evidence that they understand UX, SEO, mobile design and ongoing support. Ask who will actually complete each part of the work.
Need a website that works as hard as you do?
Your website should help the right people find you, trust you and take action.
KAYBE combines website strategy, UX, design, development, content, SEO and ongoing management – without turning the project into a black hole of technical jargon and unanswered emails.
Explore our website design, development and SEO support for more information.
