Versioned infrastructure, CI/CD on every pipeline, a governed multi-tenant lakehouse: the year our transformation work stopped being bespoke and became something we could repeat, client after client.
By 2020 we'd delivered enough data and software platforms to see the same scaffolding being rebuilt each time. So we stopped rebuilding it. Infrastructure became versioned and reproducible, CI/CD ran on every pipeline, and a governed, multi-tenant lakehouse gave new clients a running start instead of a blank page.
This was the year the work shifted from one-off projects to repeatable platforms — the same standards, applied faster, with fewer surprises.
Repeatability is what lets a small company punch above its size. A new engagement could inherit a proven landing zone, a tested deployment path and governance baked in from day one, rather than waiting weeks for an environment to be hand-assembled.
It also changed the economics for clients. When the platform is a pattern rather than a bespoke build, more of the budget goes into the work that's actually unique to them — and less into plumbing everyone needs but no one wants to pay for twice.
The repeatable pattern set in 2020 is what made the next chapter possible. When Kvika moved its portfolio companies onto Moberg builds, the day-one client environment was already a known quantity. The landing zones we now stand up on Fabric and Databricks are the direct descendants of the platform discipline we committed to that year.