Skip to content

Web Development

Web development services for websites and web apps

Marketing websites that load fast and send every lead to your CRM, and web apps (portals, internal tools, marketplaces) that read and write the data in your ERP, CRM and payment systems. Design is included, and the code is yours.

Web appMobile appAPI layerERPCRM

Websites and apps fail at the edges, not the screens

A marketing site usually looks right on launch day. The problems show up later: forms that don't reach the CRM, analytics that miss conversions, pages search engines struggle to render. The marketing team then works around the site instead of with it.

Web apps slip for a different reason. The screens are rarely the hard part; the systems behind them are. Order status in NetSuite, subscriptions in Stripe, customers in HubSpot. We plan from the data outwards, so the interface sits on connections that already work.

Signs this is costing you

  • Website leads arrive by email instead of in the CRM.
  • Pages are slow or poorly indexed after a redesign.
  • Customers email to ask for information already in your systems.
  • Your team runs a process from spreadsheets because the right tool doesn't exist.
  • An existing app is fragile and its original developer has moved on.

How we approach it

  1. Step 01

    Scope around the data

    We define who uses the site or app, what they need to do, and every system it reads from or writes to. The first release is small enough to ship and still useful.

  2. Step 02

    Design before code

    Flows, wireframes and a clickable prototype first, then visual design and a component library. Accessibility (WCAG 2.2 AA) is part of the design, not a late fix.

  3. Step 03

    Build search-ready and measurable

    Server-rendered pages, clean URLs, structured data and fast templates for search. Forms and events connected to your CRM and analytics before launch.

  4. Step 04

    Build on a typed API layer

    For web apps, a documented backend sits between the interface and your systems, so the app never depends on an ERP's quirks.

  5. Step 05

    Launch, then improve

    Performance, accessibility and security checks before release, then error tracking and analytics to guide the next release.

Customers and staffWeb or mobile appAPI layerERP, CRM, payments
The app never talks to your ERP directly. A typed API layer sits in between.

What you get

Design and component library
Flows, prototype and a documented set of components in Figma.
Production site or web app
Deployed to your hosting, with the source in your repository.
CRM and analytics wiring
Forms, events and conversions reaching HubSpot or your CRM and GA4.
API layer to your systems
For apps: a documented backend connecting to ERP, CRM and payments.
Content management
A CMS or admin screens so your team can update content and data.

How the project runs

  1. Step 01

    Paid discovery

    Users, systems involved and a first-release scope. Credited to the build.

    You get: Scope and a fixed price

  2. Step 02

    Design

    Wireframes, prototype and visual design, reviewed with you.

    You get: Approved design

  3. Step 03

    Build

    Short cycles with a preview build after each one.

    You get: Working site or app in staging

  4. Step 04

    Launch

    Release checks, redirects from any old URLs, deployment.

    You get: Live site or app and documentation

Platforms and tools

Web
  • Next.js
  • React
  • Angular
  • TypeScript
  • Tailwind CSS
Content
  • Headless CMS
  • MDX
  • HubSpot CMS
Backend
  • Node.js
  • PostgreSQL
  • REST
  • GraphQL
Design
  • Figma
  • Design systems
  • WCAG 2.2 AA
  • HubSpot

Product names and logos belong to their owners. Listing them doesn’t imply a partnership.

How you can work with us

Websites and first releases of web apps are fixed price after discovery. After launch, teams continue hourly or with a dedicated developer.

  • Usual fit for this service

    Fixed price

    A defined integration, workflow or first release of an app.

    Discovery produces a written plan with scope, deliverables and a fixed price. Changes to scope are quoted before they're built.

  • Hourly

    Small changes, fixes, or work that's hard to scope until someone looks at it.

    Time is logged against each task, so you can see where every hour went.

  • Monthly retainer

    Integrations and automations that are live and need someone responsible for them.

    Monitoring, fixes and small changes during business hours, Monday to Friday (PKT), with a monthly summary.

  • Dedicated developer

    Ongoing product work where you want the same engineer every day.

    One engineer works in your tools and stand-ups full time. You set the priorities.

Common questions

Something else? Ask an engineer.

Do you build marketing websites as well as web apps?

Yes. Marketing sites are built in Next.js so they're fast and search-ready, with forms going straight to your CRM. Web apps (portals, internal tools, marketplaces) are built on an API layer connected to your business systems.

Next.js or Angular: how do you choose?

Next.js is our default for public sites and customer portals, because it's fast to load and works well with search engines. Angular makes sense when your team already maintains Angular apps and will take over the code.

Will the site be ready for SEO?

The technical foundations are built in: server rendering, metadata, sitemaps, structured data, redirects from old URLs and fast templates. Ongoing SEO is a separate service if you want it.

Do you design the site too?

Yes. UX, prototypes and visual design are part of every project. We can also build from your designer's Figma files.

Can you redesign or take over an existing site or app?

Yes. We start with a review of the code, content and search performance, and plan redirects so you don't lose rankings in the move.

Who hosts it and owns the code?

You do. It runs in your hosting accounts, the code is in your repository, and handover includes documentation of how to build and release it.

Plan your site or app around your data.

Tell us who it's for and which systems it depends on. An engineer replies within one business day with questions and a suggested first release.

We reply within one business day (PKT, Monday to Friday).