Nine ways in. One way out.
Every engagement begins with a diagnosis and ends with a handover you can hold us to. What sits between them is the part you choose.
We build and operate our own products on the same stack we sell, so none of this is advice we have not had to live with ourselves.
Product engineering
From a whiteboard to something your users can break.
We build and ship product software end to end — domain model, API, interface, pipeline, on-call runbook. Small teams, short feedback loops, and a codebase your...
Read moreScalability & performance
Find the ceiling before your customers do.
Traffic rarely grows politely. We measure where a system actually bends, fix the handful of things that matter, and leave you with the load model and...
Read moreLegacy modernisation
Change the engine without stopping the car.
Most systems we meet are not bad, just rigid: every change costs more than the last. We make them movable again through incremental strangler work, with...
Read moreQuality engineering
Confidence, expressed as a pipeline.
Quality is not a phase at the end of a project — it is how fast you can change something and still sleep. We build the...
Read moreArchitecture & due diligence
An honest second opinion, in writing.
Before you commit a year of budget — or buy someone else's codebase — it is worth having people who build these systems read it. We...
Read moreEmbedded teams
Senior capacity that arrives already knowing how to work.
Sometimes the plan is fine and you are simply short of people. We embed senior engineers into your team on your process and your board —...
Read moreFullstack SaaS
The whole product, not one layer of it.
Schema, API, interface, billing, onboarding, alerting and the on-call rota — the parts of a SaaS that only become visible once someone is paying for it....
Read moreInfrastructure & platform
The part that decides whether Friday deploys are frightening.
Docker, CI, deployment, backups, monitoring and a recovery path you have actually rehearsed. We host our own products on European infrastructure and operate them ourselves, so...
Read moreApp development
Native when the platform matters. One codebase when it does not.
iOS and Android apps, designed before they are built. Swift and Kotlin when a product needs the platform underneath it; Flutter or React Native when one...
Read moreOne team for the parts that usually need three.
Front end, back end, mobile, database, infrastructure, pipeline and the on-call rota underneath it. Below is every capability the services above are made of — not a wish list, the work we actually do.
- Domain modelling and event storming
- Laravel, PHP 8.4+, Livewire and Inertia
- TypeScript, React and Vue front-ends
- PostgreSQL and MySQL schema design
- CI/CD on GitHub Actions and GitLab
- Observability from day one: logs, traces, metrics
- Load and soak testing with k6 and Gatling
- Database profiling, indexing and partitioning
- Caching strategy: HTTP, application and query layers
- Queue, worker and background-job architecture
- Horizontal scaling on AWS, GCP and bare metal
- Cost-per-request modelling
- Strangler-fig and branch-by-abstraction migrations
- Laravel and Symfony version upgrades
- Monolith decomposition — and monolith consolidation, when that is the right call
- Data migration with dual-write and backfill
- Dependency and CVE remediation
- Test strategy and coverage triage
- PHPUnit, Pest, Playwright and Cypress
- PHPStan and Psalm at the highest level your code can carry
- Contract testing between services
- Code review standards and definition of done
- Architecture and code-quality assessment
- Technical due diligence for VC and PE transactions
- Cloud cost and vendor lock-in analysis
- Security and compliance readiness review
- Team capability and delivery-process assessment
- Senior and principal-level backend and full-stack engineers
- Fractional engineering leadership and technical management
- Pairing, mobbing and structured mentoring
- Hiring support: scorecards, take-homes and interview panels
- Subscription billing and metered usage
- Multi-tenancy and per-tenant data residency
- Transactional email, onboarding and lifecycle flows
- Background processing, queues and scheduled work
- Alerting, escalation and on-call design
- Docker and container build pipelines
- GitHub Actions and GitLab CI
- Hetzner, Kubernetes and plain Linux hosts
- PostgreSQL, MySQL and Redis operations
- Observability: logs, traces, metrics, alerts
- Backup, restore and disaster-recovery drills
- Native iOS in Swift and SwiftUI
- Native Android in Kotlin and Jetpack Compose
- Flutter and React Native for shared codebases
- Interface design and prototyping before build
- App Store and Play Store release pipelines
- Push, offline-first sync and background processing
Fixed price where it is honest. Rolling where it is not.
Diagnosis and review work is fixed price and fixed scope. Delivery is monthly rolling with one month notice, because fixed-price delivery rewards defending the scope instead of doing the right thing.
-
01
Conversation
One hour, free
You describe the problem; we ask uncomfortable questions. By the end of it we will tell you honestly whether this is work we are good at — and roughly a third of the time, we point people somewhere else.
-
02
Diagnosis
One to four weeks, fixed price
We get into the code, the pipeline, the data and the incident history, and take a baseline of the numbers we intend to move. Nothing large gets proposed before this — quotes given without reading the system are guesses with an invoice attached.
-
03
Agreement
A few days
A scope, a price, a named team and an exit plan — all before the work starts. Monthly rolling, one month notice either way. If the diagnosis says the work is not worth doing, we say so and stop here.
-
04
Delivery
Two-week cycles
We ship to production every cycle, working inside your process and your repository. You get a demo, the current numbers against the baseline, and an honest note about anything that is going worse than planned.
-
05
Handover
Built in from week one
The last stretch of every engagement inverts: your engineers write, ours review. We are finished when your team has shipped a meaningful change without us in the room.
Tell us what is not working.
An hour on a call, no charge and no deck. We will tell you honestly whether this is work we are good at — and if it is not, who to talk to instead.
- Reply within
- One working day
- First call
- One hour, free
- Notice period
- One month, either way
- Based in
- Odense & Copenhagen