01 · Websites
Websites that work harder
Beautiful, fast websites that represent your business, attract the right audience and turn visits into opportunities.
Typical timeline: Typically 4 weeks
Typical for a well-scoped first release, agreed in week one. Larger scopes are planned in phases.
What it is
Your website is often the first serious conversation someone has with your business. It should say clearly what you do, load fast on any phone, be found by the people looking for you, and make the next step obvious.
Who it’s for
- Businesses whose current site no longer reflects who they are.
- Companies launching a new offer, brand or market.
- Teams that need a site they can keep up to date without a developer.
Typical scope
A first release covers the pages that matter most, the content written or edited with you, search foundations, analytics without invasive tracking, and an editing setup your team can use. We plan it so new pages and languages can follow without a rebuild.
How we work
How the project runs
01Week 01
Discover
Understand the business, clarify objectives, identify users and agree on scope.
You receiveA written scope and plan, agreed together.
02Week 02
Design
Shape the experience and settle what will be built before development begins.
You receiveDesigns you can click through, and the technical plan.
03Weeks 03–04
Build
Develop, test, refine and prepare the solution for launch.
You receiveTested software, live on accounts in your name.
04Ongoing
Run
Agreed maintenance, support and improvements after launch.
You receiveUpdates and improvements, or a documented handover.
Four weeks is our standard for a well-scoped project, agreed together in week one — not a promise for every project. Larger work is planned in phases, and ongoing support follows the engagement we agree.
Quality, shown
The technical standard
What every project includes, whichever service you choose.
See how this site measures up| Commitment | Standard |
|---|---|
| Code review | Code review on every change before it’s merged |
| Automated tests | Unit and end-to-end tests, with a DevSecOps pipeline, scope agreed per project |
| Accessibility | Designed and tested against WCAG 2.2 AA |
| Performance | Performance budgets targeting “good” Core Web Vitals, tested on mid-range Android |
| Security | Security review based on the OWASP Top 10 before launch |
| Updates | A written update every week |
| Ownership | Repository and accounts set up in your name; you own the code as set out in your contract |
| Handover | Documentation, architecture notes and a handover walkthrough (recorded on request) |
Websites
Frequently asked questions
Will people find the site on Google?
We build the foundations search engines reward: clear structure, fast pages, correct metadata, and content written for the questions your customers ask. Rankings also depend on your content and competition over time, so we don’t promise positions — we show you what to measure.
Can we update the content ourselves?
Yes. We set up editing that fits how often you publish, and show your team how to use it. You don’t need to call us to change a sentence.
Can the site be in French, English and Arabic?
Yes. We build multilingual sites with each language written properly, not machine-translated, and layouts that work right-to-left for Arabic.
Who owns the site?
You do. The domain, hosting and analytics are set up in your name from the start, and you own the code as set out in your contract.
What happens after launch?
We can look after updates, security patches and improvements under an agreed support plan, or hand everything over to your team with documentation.