Service 01

Web & App Development

Your website is the first impression and the closing pitch. We build sites and applications that load fast, convert decisively, and keep working on the visitors you never get to speak to.

Built to convert. Made to last.

Why this exists

A beautiful site that does not sell is an expensive brochure.

Most of the sites we are handed were not built badly. They were built without a job to do. Nobody decided what the page was supposed to make a stranger do, so every section became decoration, and the traffic that arrives has nowhere to land.

  1. Traffic arrives and leaves

    Analytics show visitors. The inbox does not. Somewhere between the ad and the enquiry form, the argument for buying from you was never actually made.

  2. Every change needs a developer

    Updating a price or adding a page turns into a ticket, a wait, and an invoice. A site you cannot edit is a site that quietly goes out of date.

  3. It is slow where it matters

    It feels fine on your laptop on office WiFi. On a mid-range phone on mobile data the hero takes four seconds, and most people never see it at all.

What you get

What actually gets built.

Not a list of technologies. A list of things that are handed over, working, at the end of the engagement.

01

A conversion-mapped structure

Every page is assigned one job and one next step before any design happens. That map is agreed in writing, so the build is never a matter of taste.

02

A design system, not screens

Type scale, colour, spacing and components defined once and reused. New pages come out consistent because there is only one set of parts to build them from.

03

A production front end

Next.js and TypeScript, server-rendered for speed and search. Accessible markup, real focus states, and behaviour that degrades gracefully on old devices.

04

A CMS you can actually use

Content, pages and posts editable by your team without touching code, with the fields constrained so nothing can be edited into a broken layout.

05

Measurement wired in

Analytics, event tracking on the actions that matter, and a form that lands in your CRM. You should be able to answer "did it work" without guessing.

06

Launch and 30 days after

Deployment, SSL, redirects from the old URLs, and a month of watching real behaviour and fixing what the data exposes. Launch is a milestone, not the end.

How it runs

Four phases, nothing hidden.

The Ihsan Process, applied to a build. Each phase ends with something you can review, so you are never waiting weeks to find out what we understood.

  1. Week 1

    Discovery and diagnosis

    We audit what exists, read the analytics, and get clear on who this has to convince and what it has to make them do. Output: a written diagnosis and a page map.

  2. Weeks 2–3

    Structure and design

    Wireframes first, then the design system, then the key pages. You review at each stage. No surprise reveal at the end, because a surprise reveal is a rebuild risk.

  3. Weeks 4–6

    Build and integration

    Front end, CMS, forms, analytics, and the third-party pieces you already rely on. Staging is live throughout, so progress is something you can click, not a status call.

  4. Week 7 onward

    Launch and optimisation

    Migration, redirects, and go-live — then 30 days of reading real behaviour and tightening the pages that are underperforming.

What changes

What you walk away with.

  • A site that states, on every page, what it wants the visitor to do next
  • Sub-two-second loads on a mid-range phone, not just on your laptop
  • A design system your next five pages can be built from without us
  • Enquiries arriving with enough context that the first call is not a discovery call
  • Full ownership — the code, the domain, the accounts, all in your name

This is for you if

  • You have traffic, or a way to get it, and it is not converting
  • Your business depends on the site being the first thing people trust
  • You want to own the system, not rent a page builder subscription

This is not for you if

  • You need a single landing page live by the weekend
  • The offer itself is still unclear — start with a Halal Brand Audit
  • The build would serve something we do not build for

Before you ask

Straight answers.

How long does a build take?

Six to eight weeks for a marketing site of ten to twenty pages, from kickoff to launch. Applications with real functionality behind them run longer and are quoted separately. We give you a dated schedule in week one and tell you early if it moves.

Do we own the code?

Yes, entirely, and the accounts with it — hosting, domain, analytics, and the repository, all in your name from day one. There is no lock-in and no licence to keep paying. If you take the project elsewhere, everything goes with you.

Can our team edit the site afterwards?

That is a requirement, not an extra. Pages, posts and the content that changes often are editable without code, with fields constrained so nothing can be edited into a broken layout. We hand over a walkthrough recording at launch.

What if we already have a site we do not want to throw away?

Then we should not throw it away. A Halal Brand Audit gives you a written read on what is costing you conversions and what to fix first — often that is three pages and a load-time problem, not a rebuild. We will tell you if that is the case.

Start here

Tell us what the site has to do.

A 15–30 minute fit call. Bring the problem, not a brief — we will tell you whether a build is the right answer, including when it is not.