Custom development

We build the thing you keep postponing

Websites, web applications, mobile apps, browser extensions and AI features — designed, built and shipped by the same small team behind every product on this site.

What we take on

Websites & landing pages

Marketing sites that load fast, rank well and read clearly on every screen. Built as static or server-rendered pages with real metadata, structured data and multilingual routing when you need it.

  • Design and build from scratch or from your brand kit
  • SEO foundation: metadata, sitemap, JSON-LD, Core Web Vitals
  • CMS or file-based content, whichever fits the team

Web applications

Dashboards, internal tools and customer-facing products. We handle the full path from data model and API to the interface people use every day, with authentication and roles wired in properly.

  • API design, database schema and migrations
  • Auth, roles and audit trails
  • Background jobs, integrations and webhooks

Mobile applications

Cross-platform apps for iOS and Android from a single codebase, or a progressive web app when a store listing is not worth the overhead. Offline behaviour and push notifications included where they matter.

  • iOS and Android builds from one codebase
  • Offline-first storage and sync
  • Store submission and release pipeline

Browser extensions

Our home turf. Manifest V3 extensions for Chrome, Edge and Brave — content scripts, service workers, declarative network rules — plus the store listing and privacy disclosures reviewers ask for.

  • Manifest V3 architecture and permission review
  • Chrome Web Store listing, assets and policy copy
  • Update pipeline and version management

AI features & automation

Language models wired into a product where they earn their keep: drafting, extraction, classification, search. Scoped prompts, streaming responses, cost controls and a fallback for when the model is wrong.

  • Model selection, prompting and evaluation harness
  • Streaming UI with graceful degradation
  • Token budgets, caching and usage reporting

Maintenance & rescue

Inherited a codebase nobody wants to touch? We audit it, document what is there, fix what is broken and set up the deployment and monitoring so the next change is not a gamble.

  • Codebase audit with a prioritised action list
  • Dependency and framework upgrades
  • CI/CD, monitoring and error tracking

How it runs

Four stages, fixed price per milestone, and a staging URL you can open on any day of the project.

  1. 01

    Scope

    A short call or a written brief. We map what you need, what can wait, and where the real risk sits — then send back an estimate with a fixed first milestone.

  2. 02

    Design

    Structure before pixels: user flows, page inventory, data model. You see clickable screens or a live staging build before we commit to the full scope.

  3. 03

    Build

    Weekly increments on a staging URL you can open at any time. Every release is reviewable, so feedback lands while it is still cheap to act on.

  4. 04

    Ship & support

    Deployment, analytics, monitoring and a handover doc. After launch we stay available for fixes, iterations and whatever the roadmap turns into.

The stack we know cold

We stay deliberately narrow. Everything below is something we use in production on our own products, not a list of things we have read about.

Frontend

  • TypeScript
  • React
  • Next.js
  • Tailwind CSS
  • Vite

Backend

  • Node.js
  • PostgreSQL
  • Supabase
  • Edge functions
  • REST & RPC

Mobile & extensions

  • React Native
  • PWA
  • Manifest V3
  • Chrome APIs

Delivery

  • Vercel
  • Docker
  • GitHub Actions
  • Analytics
  • Error tracking

Questions we get asked first

How do projects usually start?

With a message describing what you need. We reply with clarifying questions, a rough estimate and a proposed first milestone, usually within a day. No forms, no discovery calls you have to schedule two weeks out.

What does a project cost?

It depends on scope, but we quote a fixed price per milestone rather than an open-ended hourly rate, so you always know what the next deliverable costs before it starts. A marketing site is a different order of magnitude from a multi-role web application, and we will tell you which one you are actually describing.

How long does it take?

A landing page or a focused browser extension typically takes two to four weeks. A web application with authentication, roles and integrations usually runs six to twelve weeks depending on scope. We ship to a staging URL weekly, so progress is visible rather than promised.

Do we own the code?

Yes. The repository, the infrastructure accounts and the deployment pipeline are yours, handed over with documentation. There is no lock-in and nothing that only we can maintain.

Can you take over an existing project?

Often, yes. We start with a paid audit that produces a written assessment of the codebase, the risks and a prioritised plan. If the honest answer is that a rewrite costs less than the rescue, we say so.

What happens after launch?

You can take it from there with the handover documentation, or keep us on for fixes, iterations and new features. Most clients start with a light monthly arrangement and scale it up when a new phase begins.

Tell us what you are building

A paragraph about the problem is enough to start. You will get real questions and a rough estimate back, usually the same day.