01
Two-week sprints. No exceptions.
Every engagement is structured in two-week sprints with a written demo on the last Friday. We do not run a sprint zero, a sprint half, or a sprint extension. If the work does not fit, we re-scope.
Hadsund · Nordjylland · since 2018
A web development collective that ships in two-week sprints.
We build product platforms, headless storefronts, and internal applications for European clients — and stay on to operate them. Every engagement is measured in sprints; every sprint ends with a demo on a Friday.
Atlas
Edition IX
- Folio
- F.IDX.00
- Status
- in production
- Pressed
- 2026-06-13
- Collective
- 6 engineers + 1 designer
- Director
- M. Krogh Bertelsen
I
Folio F.PR.00 · Operating principles
Six rules that survived seven years of practice.
Six tenets that govern how the collective works in 2026.
02
Flow is a number, not a feeling.
We measure flow as deploy frequency, lead time for changes, change-failure rate, and mean time to recovery. We share the numbers in every monthly review and tune the process against them.
03
No dependency lives forever.
Every Friday afternoon is reserved for upgrading dependencies, deleting unused code, and writing the deprecation notes for the things we are about to remove. Nothing rots in a corner.
04
The runbook is the deliverable.
Code without a runbook is half a deliverable. Every engagement ends with a written operations document that an on-call engineer can read at 03:00 without phoning a friend.
05
One way to do each thing.
Three forms of validation in one codebase is two forms too many. We pick one, document why, and review pull requests against that decision.
06
We name engineers, not roles.
You will know the names of the two engineers on your engagement on the first call. They will sign every email. They will not be replaced mid-sprint.
II
Folio F.SV.00 · Services
Six chapters of engineering work.
Each chapter has a written deliverable list, a measurable target, and a stack we have shipped at least four times.
I
v1.0 applications · multi-tenant platforms
Product engineering
Custom web applications with the boring parts done well — auth, billing, audit logs, role-based access.
Next.jsRemixPostgresPrismatRPCStripe
II
storefronts that don't look like Shopify
Headless commerce
Storefronts on Shopify Hydrogen, Saleor, or BigCommerce — paired with a custom front end you actually own.
Shopify HydrogenSaleorNext.jsTypeScriptCloudflare Workers
III
Core Web Vitals · edge rendering
Performance overhauls
Get your Lighthouse above 95, your LCP under 1.0 second, and keep them there.
Lighthouse CIWeb Vitals APICloudflare WorkersVercel Edge
IV
framework + CMS migrations · no SEO loss
Re-platforming
Move from WordPress, Drupal, or a creaky bespoke stack to something maintainable — without losing rankings.
Next.jsAstroSanityStoryblokCloudflare DNS
V
REST · GraphQL · integrations
API engineering
Public and private APIs that age well — properly versioned, properly documented, properly rate limited.
OpenAPI 3.1HonoFastifyGraphQL YogaPostgREST
VI
architecture · security · accessibility
Engineering reviews
A second pair of eyes on a code base, with a written report you can hand to your board.
Static analysisOWASP ZAPaxe-coreLighthouseSnyk
III
Folio F.JN.00 · Selected journeys
Three engagements, three sectors.
A small selection — six are published in full on the journeys page.
F.JN.01 DTC food · Jutland Headless commerce 4 sprints · 8 weeks
Kalvebjerg
A 47-year-old family-run meat producer in Jutland selling subscription boxes to homes across Scandinavia — on a Magento install nobody at the company could maintain.
“The orders used to be sorted by hand from a printed list. Now they are sorted by a small piece of code we can both read.”
Stack Shopify Hydrogen · Cloudflare · Sanity · Stripe Tax
F.JN.02 Regional news · Thy Performance overhaul 2 sprints · 4 weeks
Thylandske Tidende
A regional Danish newspaper on Drupal 7, slow on mobile, losing readers to faster competitors. We rebuilt the front end on Astro without touching the back office.
“Same editors, same Drupal, new paper — and it actually loads in time for the morning coffee.”
Stack Astro · Drupal JSON:API · Cloudflare · Plausible
F.JN.03 B2B SaaS · operations Product engineering · v1.0 6 sprints · 12 weeks
Rødvig Inventory
A founding team of two with a working spreadsheet and a paying pilot customer. We turned the spreadsheet into a multi-tenant inventory platform — auth, billing, dashboards.
“They shipped the parts of the product I dreaded. Auth, billing, admin. We could focus on the customer-facing pages.”
Stack Next.js · Postgres · Prisma · tRPC · Stripe Billing
IV
Folio F.LD.00 · Ledger
The collective in four figures.
Sprints shipped
184
Journeys completed
46
Median LCP, p75
< 1.0 s
Production uptime SLA
99.95%
V
Folio F.VC.00 · Voices
What clients say after the demo.
They scoped a feature we had been afraid to touch for a year and shipped it in a single sprint. The honesty of the two-week unit is what made it possible.
Birgitte Holm
Product lead · Kalvebjerg
Half of what they delivered was code. The other half was a runbook our on-call engineers actually use at three in the morning.
Henrik Sørensen
Head of platform · Havnegade
A collective that says no to features without flinching. The product is sharper because of it.
Tobias Dahl
Co-founder · Rødvig Inventory