Skip to content
Hedou Bibi
English
Let's talk

How we build your WordPress website

Know what you’re getting before we start. We agree on the pages, design and features, then keep track of feedback and approvals as we build.

Tell us about your project so we can prepare a useful quote

Share your goals, design files or reference sites, page list, features and languages. Your existing site, hosting requirements, budget and target launch date help us assess the work before we quote.

Pages and content

Page count, sections, copy, images and case study materials.

Features and interactions

Forms, search, filters, memberships, integrations and admin features.

Design and brand

UI files, reference websites, brand colors, fonts and images.

Deployment and timeline

Server, domain, languages, launch date and budget.

Agree the pages, features and responsibilities before development starts

Your contract sets out the schedule, revision rounds, any included support time and handover. We start development once you’ve approved the design and feature list.

Preparing your quote

Review the pages, design, development, testing and project coordination needed.

Development stage

Bring the quote, feature list, design approval and schedule together so everyone knows what will be delivered.

  • Quote: the work included, price, timing and payment stages.
  • Feature list: pages, modules, functionality, interactions and editable admin content.
  • UI approval checklist: style, device layouts, copy, images and final approver.
  • Schedule: milestones for UI, development, testing, client materials and approvals.

Once we have an initial quote,
we agree the full scope and project plan

Use the initial quote to agree on the feature list, schedule and contract. Settling these details now makes later decisions easier.

Project quote

The quote sets out the agreed pages, features, estimated work, price, payment milestones and service scope.

Scope and project schedule

Once the initial quote is accepted, we confirm the features, organize the pages and functionality, and plan the work to be delivered at each stage.

Contract

The agreed feature list and project plan are included in the signed contract to keep the project scope under control.

Project handover

At handover, you receive the design files, website code and review documents included in the contract. Third-party software, fonts and other licensed assets remain subject to their own licence terms.

Agree the visual direction and then design the remaining pages

Start by reviewing the homepage, then use the agreed direction for the other pages. Send your team’s feedback together for each design batch. We build from the version you approve.

  1. Homepage direction

    Brand, structure and key visuals

  2. Key pages

    Services, case studies and contact

  3. Responsive design

    Desktop, tablet and mobile

  4. One set of feedback

    Brought together by your project contact

  5. Final approval

    Version numbers and approval records

  6. Start development

    Based on the approved design

Design guidelines

Revisions
Each design batch is limited to the consolidated revision rounds agreed in the contract.
Feedback
The client consolidates internal feedback before submitting it in one batch.
Final touches
Minor text, image, color, font size and spacing changes can be handled as agreed.
Design freeze
Reversing approved structures or directions, or adding new ones, is handled as a scope change.

For new requests beyond the approved scope, record them first, then decide whether to proceed

Clients may request changes during development

Change requests

Small adjustments during development are handled within the scope and hours agreed in the contract.

New requirements

Small additions are assessed first; structural changes or substantial features require separate agreement on cost and timeline.

Tracked hours

We log small requests too, so you can see the time used, any included allowance and work that needs a separate quote.

Project contact

A project lead coordinates communication and delivery through completion to keep everyone aligned.

An important distinctionIf the implementation differs from the approved UI or feature list, correction is the developer's responsibility. Changes to previously approved content are treated as minor adjustments or new scope.

Review the complete staging site before it goes live

We check the pages against the approved design, test desktop and mobile layouts, and review features, forms, links and browser behaviour. You then try the staging site and send one list of issues against the agreed scope.

  1. Process milestone

    Internal testing

    A shared test checklist keeps open issues and review progress visible.

  2. Handover milestone

    Staging site

    Once deployed to the test server, the client can browse and try the website online.

  3. Handover milestone

    Your review and approval

    The website is deployed to production only after the client approves the online test version.

  4. Process milestone

    Fix and recheck

    Fix development issues that differ from the approved version; record scope changes separately.

  5. Handover milestone

    Final payment confirmation

    Complete acceptance and payment milestones as agreed in the contract.

  6. Handover milestone

    Receive your website files

    After the agreed final payment, we hand over the project files, database, deployment notes, review documents and access included in the contract. Third-party licence terms still apply.

After launch,
get help with site care and everyday changes

After launch, support follows the arrangement in your contract. This can include fixes, backups, security checks, updates and small changes. New features need their own assessment.

Security checks and monitoring

A maintenance plan can include uptime monitoring and alerts for detected problems. We agree the monitoring setup, notification contacts and response arrangements for your website.

Everyday fixes and changes

Use the agreed support hours for eligible small fixes and changes. We check larger requests with you before adding work.

Manual checks

Automated checks can detect downtime and timeouts, but may miss unwanted pop-ups, redirects, injected code or changed content. Manual page checks and their frequency are agreed as part of the maintenance scope.

Maintenance records

Keep a record of reported issues, the work carried out and the results. We agree how maintenance requests and review reports will be shared, so you can follow what has changed.