Your initial quote covers the full design and build of your website. However, there are a few additional services every site needs:

• Hosting

• Domain registration

• Email services

Two servers are required: one for staging and one for production. The staging site is a private environment for development and testing, while the production site is the live, public version of your website. Using a staging site means new features, updates, or fixes can be tested safely before anything goes live, reducing risk and avoiding disruption.

These services are paid for directly by you, the client. This ensures you retain full control and ownership of the infrastructure behind your company website. You’ll never be locked in, all I need is access to configure and optimise these services on your behalf.

It’s also wise to budget for ongoing website maintenance to keep your site secure and up to date.

You may also want to subscribe to services like Plausible Analytics, which tracks your website visitors, and Termly, which handles legal text and cookie management to keep your site GDPR compliant.

No, reasonable revisions are included in your project price. The design stage is collaborative, and some back-and-forth is expected to ensure the final design matches your vision.

The only time additional costs apply is if the scope changes significantly - for example, restructuring the site or adding new functionality. Those are considered scope changes rather than simple revisions.

Minor tweaks, like adjusting colours, fonts, spacing, or content placement are all part of the normal design process and included in your quote.

I use a simple 50/50 payment structure. I’ll send two invoices at the start of the project: the first 50% is due upfront to secure your slot and cover initial planning and design work (non-refundable), and the second is dated for payment in week 4 of the project timeline.

The week 4 invoice is due regardless of launch status. This keeps development work compensated and on schedule while still giving you flexibility with content preparation and launch timing.

This structure gives clients predictable costs while accommodating the realities of website project timelines.

The final price mainly depends on two things: how many custom templates are needed and how complex the design or functionality is.

A small site might only need a handful templates (homepage, about, services, contact), while a larger one could require 10 or more unique layouts. Each template requires design, frontend development, CMS integration, testing, and documentation. Other factors that can influence cost include:

• Third-party integrations (e.g., CRM, payment gateway, booking system)

• Additional revisions if the scope changes

• Integration with existing systems

Unfortunately, custom website development isn’t suited to quick turnarounds. Quality work takes careful planning, design iteration, testing, and documentation. These steps can’t be rushed without compromising the end result.

Project duration depends on a number of factors. Each phase builds on the last, and cutting corners usually causes problems that are more expensive to fix later.

If you have an urgent deadline, a custom site may not be the right fit. A short-term solution—such as a one-page site or MVP—can work while planning a proper build later. For future projects, the best approach is to start discussions early so I can schedule a quality build within your timeline.

Timelines vary depending on the size and complexity of the project, but most custom websites take between 8–15 weeks from consultation to completion.

• A startup or corporate site with standard functionality typically takes 8–15 weeks.

• A more complex, enterprise-level site with custom features or many unique templates can take 25+ weeks.

The process includes four key phases:

• Planning

• Design

• Development

• Documentation

Client response times also play a major role. Projects move fastest when content, feedback, and approvals are provided promptly at each stage.

During the initial consultation, I’ll provide a tailored timeline with key milestones and outline what I’ll need from you to keep things on track.

Most delays come from finalising content, which is normal when multiple teams are involved.

To avoid bottlenecks, I give you early access to the CMS so your team can add and manage content during development. This centralises content and keeps things moving while I focus on design and build.

I book a set amount of time for each project and aim to complete within that window. Once development is done, your staging site stays live so you can keep adding content. When you’re ready to launch, give me a few days’ notice and I’ll push the site live and finalise any integrations.

If technical issues or new requirements arise, I’ll flag them early and discuss adjustments. Open communication keeps everything on track.

Yes. I provide comprehensive training materials through a private documentation section created specifically for your website.

This includes short, bite-sized video guides that walk you and your team through all the essential CMS functions. The videos are designed to be easy to follow and focus only on the features and content areas relevant to your website.

The training materials are useful both as a refresher for you and as an onboarding tool for new staff who may need to learn the system later.

Having these resources means you’re not dependent on remembering everything from a single training session, you can revisit the guides anytime, ensuring you always feel confident managing your site content.

Your involvement varies across project phases, with closer collaboration at the start and key checkpoints along the way.

• Planning: We’ll meet via Microsoft Teams at least twice per week to confirm requirements, set goals, and create the sitemap and wireframes together.

• Design: Weekly reviews to give feedback on concepts and ensure we’re aligned before moving into development.

• Development: Weekly check-ins to track progress and review the private staging site as it comes together.

• Content: I’ll add content to some areas, but your team will be responsible for most of it. Early CMS access lets you start adding content directly to the staging site.

• Documentation: In the final week, you’ll receive access to training materials (including video guides) showing you how to update and maintain your website.

This structured approach ensures you’re involved and informed at every stage, while keeping the project moving efficiently.

The 30-day post-launch support period ensures your website runs smoothly during the critical first weeks after going live.

During this time, I’ll:

• Monitor your site to track search performance and indexing.

• Check error logs to catch and resolve any technical issues.

• Address problems like broken links, server errors, or indexing issues that may only appear once the site is live and receiving traffic.

If any issues are identified, I’ll resolve them promptly to keep your site performing well and visible in search.

The support period begins when your site officially launches, not when development ends, giving you peace of mind during those first important weeks online.

Post-launch is not for development, last‑minute design or feature changes - it focuses on monitoring, troubleshooting, and ensuring stability.

The 30-day support period is only for monitoring and fixing technical issues after launch—not for design or development changes.

For ongoing support beyond that, I offer a support and maintenance service with three package options. These are designed to keep your site secure, updated, and running smoothly long term.

If you need additional design or development—like new templates or added functionality—I’ll provide a separate quote based on your requirements.

This way, you have clear options for both routine maintenance and future enhancements, ensuring your site continues to evolve with your business. During handover.

The initial consultation focuses on understanding your business goals, target audience, and website requirements. From there, the information needed depends on the project phase.

Once we’ve created a sitemap during the planning stage, we’ll identify what content is required. This typically includes written copy, images, and any other materials relevant to your pages.

For branding, I’ll need access to your logo files (both full and single-colour versions). If you have brand guidelines, these are extremely helpful for ensuring the website aligns with your identity—covering colours, fonts, tone, and style.

If you don’t have formal brand guidelines, that’s fine—I can work with your existing materials and maintain consistency based on those.

The key is starting with a clear picture of your goals. From there, we’ll identify exactly what’s needed as the project progresses.

Quick checklist:

• Business goals and target audience

• Sitemap and page requirements (we create this together)

• First draft of copy and images

• Logos (full and single-colour)

• Brand guidelines (if available)