Website development

A website development company that builds on a stack your team can maintain

Your site is built in a repository you own, on a platform your staff can edit, with handover documents written as the work goes.

Get your build review
Trusted by the world's fastest-growing brands

Portfolio · selected work

The work, not the deck.

Every site below is live and owned by the client. Each window is a capture of the real page, not a drawn mockup.

Categories we work across
HospitalityFinancial servicesManufacturing and exportConsulting and researchRecruitmentD2C
urjalifes.inUrjalife's Pravaah resort website: rooms, activities and dining across a photographic homepage.
UrjalifeHospitality
adventswealth.comAdvents Wealth website: a financial planning homepage covering wealth building, tax and retirement.
Advents WealthFinancial services
syounaa.inSyounaa website: a wellness apparel storefront built around smart-textile product ranges.
SyounaaWellness apparel
infokool.comInfokool website: a precision cooling manufacturer, with an outdoor cabinet product grid and capability sections.
InfokoolManufacturing
howardjohnsonhinton.caHoward Johnson Hinton website: a mountain-lodge hero over a room-booking bar, followed by renovated room types.
Howard Johnson HintonHotel
sycamoreconsultant.comSycamore Consultancy website: a recruitment agency, with separate paths for employers and candidates.
Sycamore ConsultancyRecruitment
stutiexports.comStuti Exports website: a technical fibers and specialty yarns exporter, with core markets and capability sections.
Stuti ExportsTechnical textiles
duhomespg.inDuhomes website: student housing, with walking distances to nearby colleges and a room rate table.
DuhomesStudent housing
vaspro-global.comVasPro Global website: a technical advisory and project consulting firm, with expertise and mission sections.
VasPro GlobalConsulting
pretor.aePretor website: a marketing research and promotion consultancy, opening on research, strategy and growth planning.
PretorMarketing research

What development covers

Three decisions that set what the site costs to run

A website development company makes three decisions for you before the first page is built: the stack, the CMS and where the code lives. We make each one in writing, so you can see the reason and so another developer could take the site over.

Decision recordSample Dental CenterStackOffice edits it; 18 pages on 4 templatesCMSOne description feeds several pagesCodeREADME and runbook sit beside the codeWordPressWebflowShopifyNext.jsLayout lockedContent as fieldssample-dental/websiteIn your name

The stack

We choose the platform from what your team already knows and how often the site will change. WordPress, Webflow, Shopify and a custom Next.js build each suit a different team, and the scope names the choice and why.

The CMS

Your staff edit text, photos, pages and posts in a CMS with the layout locked, so an edit can’t break a page. Content is stored as fields, so one service description can feed several pages.

The repository

Where the platform has one, as WordPress and Next.js do, the code lives in a repository in your name, with a README and a runbook. On Webflow and Shopify the site sits in your account with admin access, and the handover is the access and a guide.

How it’s built

A stack that anyone can take over

Two ways to build the same site. They look alike on launch day and differ the first time something has to change.

A builder’s own frameworkOnly the builder canA common, documented stackAnyone can maintain it
The stackA framework or theme the builder wrote and maintainsWordPress, Webflow, Shopify or Next.js, each with a large pool of developers
Where the code livesOn the builder’s server or in the builder’s accountsOn WordPress and Next.js, a repository in your name with every change recorded; on Webflow or Shopify, the site in your account
DocumentationHeld by the builder, and written up if askedA README and a runbook, written as the site is built
A new developerLearns the builder’s framework firstClones the repository and deploys from the runbook
Updates and changesMade by the builder, on the builder’s scheduleMade on a staging site, approved by you, then released
Why we build it this way

A site outlives the team that built it. A common stack and a repository you own mean you can change developers, or run the site yourselves, without a rebuild.

The standards

Six standards that shape how we build

Six rules and metrics we build to. Each carries its source.

  1. StagingGoogle

    A robots.txt file does not keep a staging site out of Google.

    Google says robots.txt is not a way to keep a page out of search, and names a noindex rule or password protection for pages that must stay private. Our staging sites sit behind a password, so a test copy of your site is never indexed.

  2. Sign-inW3C

    WCAG 2.2 asks that signing in not rest on memory alone.

    Success criterion 3.3.8, at level AA, says no step of signing in may require a cognitive function test, such as remembering a password, unless another method or a helping mechanism is offered, among other exceptions. On portals and member areas we allow paste and password managers.

  3. MarkupW3C

    WCAG 2.2 removed its HTML parsing criterion.

    The W3C marked criterion 4.1.1 Parsing obsolete and removed it, because assistive technology no longer needs to parse HTML directly. Clean markup is still good practice. Our accessibility testing spends its time on keyboard use, focus, labels and names instead.

  4. Responsivenessweb.dev

    Interaction to Next Paint replaced First Input Delay.

    INP is the successor to First Input Delay. FID measured only the first interaction on a page; INP observes every interaction, from the tap to the next paint. Scripts such as chat widgets and tag managers can slow it, so we set a script budget before the build.

  5. RedirectsGoogle

    Google says to keep redirects for at least a year.

    In its guidance on moving a site, Google says to keep redirects for as long as possible, generally at least one year, and to update the sitemap with the new URLs. Our redirect map is a file in your repository, so it stays with the site and later redesigns add to it.

  6. Redirect typeGoogle

    Google calls a JavaScript redirect the last resort.

    Google says to use JavaScript redirects only when server-side or meta refresh redirects aren’t possible, because rendering can fail and Google might never see the redirect. We set redirects at the server or host, where they work without scripts and return a status code.

The scope

The six parts of the build and what you keep from each

Six parts of the build, each with the document or access you take away.

Responsive checkStagingService template390 × 844PhoneTabletDesktopBook a visit390Phone768Tablet1280Laptop1920Wide desktop

Stack and front end

The approved designs built as templates that work from a phone up to a wide desktop, on the platform we recommended in the scope. We keep plugins and dependencies few and list each one with the reason it is there. You receive: the built templates on a staging site, and a list of every plugin or package with its purpose.

WordPressNext.jsWebflow
Site structure18 pagesPagesCMSPostsCMSFormemailBookinglinkedCustom theme4 templatesWWordPress coreupdates tested on stagingHost, in your accountBackups run

Structure and modules

Pages, posts, forms, search and any store built as separate parts that can be changed one at a time, so adding a section later doesn’t mean rebuilding the site. You receive: a one-page diagram of the parts and how they connect.

Edit serviceLayout lockedService nameDental implantsUsed on 3 pagesHomeImplantsServicesTest submissionsHubSpottest contactSStripetest paymentAnalyticsform event

CMS and integrations

A CMS your staff can edit without us, with layout locked, and connections to the systems you already run, such as a CRM, a booking tool, payments and analytics. Each connection is tested with a real submission. You receive: an admin login, a short editing guide and a test record for each integration.

HubSpotStripeAnalytics
Budget sheetWithin budgetLargest Contentful Paint, phone1.7 sbudget 2.0 sGoogle 2.5 sPage weight, home page1.2 MBbudget 1.5 MBINP ≤ 200 ms · CLS ≤ 0.1 · real visits

Performance budgets

Limits set before the build for page weight, scripts and the three Core Web Vitals, then checked on every template as it is built. The scope says what happens when a page goes over budget. You receive: the budget sheet, and the measured result against it for each template.

LCPINPCLS
Screen reader passWCAG 2.2 AA“Book a visit, link”VoiceOver1Skip to content, link2Book a visit, link3“button”icon, no nameIssue 1Fixed: “Menu, button”4Your name, edit text, required

Accessibility testing

Each template tested with a keyboard alone, with a screen reader and with automated checks, against WCAG 2.2 AA. Automated tools catch some issues and miss others, so the keyboard and screen reader passes are done by hand. You receive: a written test record, each issue with its fix.

WCAG 2.2 AAKeyboardScreen reader
RepositoryIn your namesample-dental/websitePrivateAdd redirect map, tested on stagingmaintheme/custom theme, 4 templatesREADME.mdset up and deployRUNBOOK.mdrelease from stagingredirects.csv62 of 62 tested

Staging, launch and handover

A staging site for releases, as the scope specifies, a redirect from each old URL to its closest new page tested before launch, and a deploy you can repeat from the runbook. The accounts are in your name throughout. You receive: the repository, the redirect map, a README and a runbook.

How it runs

Choose the stack, set the budgets, build on staging, hand it over

Nothing moves to the next stage without your sign-off, and each stage ends with a document for your files.

stack-decision.csv

Stack decision record

Sample · Sample Dental Center
DecisionChoiceReason
PlatformWordPressThe office already edits WordPress, and 18 pages on 4 templates fit it
ThemeCustom theme, no page builderFewer plugins to update, and lighter pages
HostingManaged WordPress host, in your accountBackups and core updates run on the host
BookingYour existing booking systemLinked from every page, so there is no second calendar
FormsForms email the front deskNo patient details go in the form
A custom Next.js build was considered and set aside. It would add developer cost to maintain for a site this size.

Our stack

The tools behind the build and the checks

These are the platforms and checks a build draws on.

WordPress
Why WordPress

WordPress is a widely used CMS, with a large pool of developers who know it.

How we use it

We build a custom theme with few plugins, each listed with its purpose, so updates are predictable and a new developer can read the code.

Editor controlSpeed ceilingUS use
Tuned WordPressHigh
Page buildersHigh
HeadlessMid

Questions

Website development, answered

Start here

Get a review of how your site is built

Send us your current site, or describe what you plan to build. We’ll check the stack, its speed on a phone and its upkeep, and tell you what we’d choose and why.