What we will actually do for you.

We sell engineering capacity, not deliverables-as-packages. The four lines below describe the shape of an engagement: how long, how priced, what we hand over, and what we need from you to start. If your problem doesn't fit cleanly, message us — there is usually a way to scope it.

§ 1.1 Catalogue

All four, in order of typical engagement.

Most clients start with an audit, move to a build, then sign a retainer. We are happy to enter at any of the three doors.

WP-01

Web platform build

Production-grade web platforms from data model to deploy. Multi-tenant SaaS, internal tooling, customer portals.

PHP 8.3 PostgreSQL 16 Vanilla JS S3-compatible storage Cloudflare

Read full spec →

Price: € 900 from / project
Duration: 6–12 weeks
Team: 2 engineers · 1 lead
Inputs needed: Domain model, primary user flows, expected concurrency, must-have integrations

HC-02

Headless commerce

Commerce front-ends decoupled from legacy back-offices. Custom checkout, multi-region pricing, Klarna and Stripe.

PHP 8.3 PostgreSQL 16 Stripe Klarna Algolia Cloudflare

Read full spec →

Price: € 850 from / project
Duration: 8–14 weeks
Team: 2 engineers · 1 designer · 1 lead
Inputs needed: SKU catalogue, current back-office (Shopify / Magento / SAP), tax model, target markets

AU-03

Engineering audit

A two-week deep read of an existing codebase, infrastructure and team workflow. Outputs a written report and a 90-day plan.

Codebase agnostic AWS / GCP / Azure Docker Postgres / MySQL

Read full spec →

Price: € 450 fixed fee
Duration: 2 weeks
Team: 1 principal engineer
Inputs needed: Read access to repos, infra, error tracker, last 6 months of incident reports

RT-04

Engineering retainer

Ongoing senior engineering capacity, by the month. Sprints, support, on-call. Cancel with 30 days notice.

Your stack GitHub / GitLab Linear / Jira PagerDuty

Read full spec →

Price: € 350 per month
Duration: rolling, 30-day notice
Team: 0.5–1.5 FTE senior engineer
Inputs needed: Repo access, ticket system access, on-call rota if applicable

§ 1.2 Process

How a build engagement runs, week by week.

The same seven phases for every build, scaled in duration to fit the scope.

§ 0.1 Brief Discovery call, scoping doc, fixed price for build phase, signed engagement letter. 1 week

§ 0.2 Architecture Data model, endpoint inventory, hosting plan, security review, written architecture doc. 1 week

§ 0.3 Vertical slice Thin end-to-end path on a real domain. You see the system running by end of week two. 2 weeks

§ 0.4 Build out Weekly demo Fridays. Written changelog every Monday. No surprise scope drift. 4–8 wks

§ 0.5 Hardening Load tests, security scan, backup drill, runbook, on-call handover. 1 week

§ 0.6 Cutover Production deploy with rollback plan. Pair on first 24 hours of operation. 1–2 days

§ 0.7 Retainer Same engineer continues on retainer for changes, scaling, on-call. rolling

§ 1.3 Brief us

Ready to talk?

Tell us the shape of the problem. A reply within one business day, including whether and when.

Open brief form →