Get in touch
Get in touch

Services

What we buildand what you get

Build · design · test · break — six engagements, one way of working

Every project is one of the six below. This page says what each one starts from, what we build, and exactly what lands in your accounts at the end — so you can pick before you talk to anyone.

Start a buildCompare them
Scope
Written before code
Priced
One figure, up front
Cadence
A working URL weekly
Handover
Repo, docs, access
  • React
  • Next.js
  • Vue.js
  • TypeScript
  • Node.js
  • Python
  • Astro
  • Bun
  • React Native
  • Expo
  • GraphQL
  • REST
  • Playwright
  • Vitest
  • Figma
  • Burp Suite

01What we build

Six engagements

Most work falls into one of these, and plenty spans two — a build with the design in front of it, or a release with a penetration test behind it. When it does we say so on the first call and scope it as a single project rather than billing you twice for the seam.

WEB

Web development

The surface your customers use — a site or an app that stays fast as the content and the traffic grow.

Best whenYou have designs, or a site that has stopped keeping up.

Read the detail

In scope

  • React, Next.js or Astro front end
  • Screens and states agreed before the build starts
  • A content model you can edit without us
  • Core Web Vitals and keyboard access checked before launch

APP

Mobile development

One codebase, both stores — an app that behaves like it belongs on the phone rather than a website in a frame.

Best whenYour customers reach for a phone before a browser.

Read the detail

In scope

  • React Native and Expo — iOS and Android from one codebase
  • Offline state and push notifications, not bolted on later
  • App Store and Play Store submission handled for you
  • Crash reporting and release analytics from the first build

QA

Software testing

A suite that catches the regression before your customer does, on the paths that actually cost you money.

Best whenEvery release breaks something that used to work.

Read the detail

In scope

  • End-to-end tests on the flows that move money or lose data
  • The suite wired into your pipeline, so a red build blocks the merge
  • A manual pass on each release candidate, not only the robots
  • A written defect report ranked by impact, with steps to reproduce

PEN

Penetration testing

We attack the system the way someone else eventually will, then hand you the findings ranked by what each one would actually cost.

Best whenYou are going live, taking payments, or a client has asked for a report.

Read the detail

In scope

  • A written, signed scope and authorisation before any testing starts
  • OWASP Top 10 plus the business-logic flaws a scanner cannot see
  • Findings ranked by real impact, not by a tool severity score
  • One free retest once your fixes are deployed

UX

UX & UI design

Flows and screens agreed before anyone writes code, in a file a developer can build straight from.

Best whenYou know what it should do, not yet what it should look like.

Read the detail

In scope

  • User flows and wireframes settled before any visual design
  • A Figma file with a real component library, not a pile of frames
  • Every state drawn — empty, loading, error, too much content
  • Contrast and type sizes checked against WCAG before handover

MVP

MVP development

The smallest version that proves the idea, built so version two is not a rewrite.

Best whenYou have an idea and a date, and need something real in front of users.

Read the detail

In scope

  • One flow, built end to end and actually working
  • Scope cut in the open, with you in the room
  • A foundation the next features can sit on
  • Analytics from the first release

02Side by side

Which one is yours

The same four questions answered for all six. Find the row that matches your situation and read across — the column you care about is probably the third.

ServiceYou start withWe buildYou get backBuilt on
WEBWeb developmentDesigns, or a live siteFront end and content modelDeployed site, repo, runbookReact · Next.js · Astro
APPMobile developmentA web product, or a phone-first ideaBoth apps from a single codebaseSigned builds, store listings, repoReact Native · Expo · TypeScript
QASoftware testingA product with no tests, or flaky onesAutomated suite and a CI gateTest suite, pipeline, defect reportPlaywright · Vitest · TypeScript
PENPenetration testingA live system and a signed scopeManual and automated attack pathsReport, ranked findings, retestBurp Suite · OWASP ZAP · Nmap
UXUX & UI designRequirements, or a design that is not workingFlows, wireframes, a component libraryFigma file, design tokens, prototypeFigma · Design tokens · WCAG 2.2
MVPMVP developmentAn idea and a deadlineOne flow, end to endWorking product, next-step listNext.js · TypeScript · Bun

PricingEvery engagement is priced from the written scope — one figure, agreed before code. No hourly billing, no change-request desk.

03In every build

What all three ship with

Not upsells. These sit in the base scope of every engagement, because leaving any of them out costs more to add later than to do now.

Typed end to end
TypeScript on both sides of the wire, so a rename breaks the build instead of production.
Tested where it counts
Automated tests on the paths that move money or lose data. Not a coverage number.
Fast and reachable
Core Web Vitals in the green and full keyboard access, checked before launch rather than after a complaint.
Documented to hand over
A runbook another developer can follow: how it deploys, what the variables are, what breaks first.

Next step

Tell us what
you need built

Send the idea in whatever shape it is in — a document, a sketch, or two sentences. You get a written scope and a fixed figure back before anything is committed to.

Start a build
contact@compaxtech.com095 016 9701