Skip to content
01Case 01 / Swiss Climate-Tech

Rebuilt a scaling platform.
Without pausing the business.

A Swiss climate-tech B2B platform was hitting ceilings: slow releases, fragile data model, AI features that kept slipping. We embedded as the architecture voice and shipped the rebuild incrementally.

Product DevelopmentB2B SaaSArchitecture
faster release cadence
02Context

Three years in,
the platform was fighting back.

The platform had grown faster than the original architecture assumed. Releases that used to ship weekly were now monthly. Every feature touched three services. The ML team had a roadmap of AI capabilities ready to go, and no clean place to plug them in.

The CTO didn't need a vendor to do work. She needed a senior architecture voice in the room. Someone who'd argue with her decisions and ship the smaller ones.

03Approach

Rebuild the bones,
ship every Friday.

  1. i.

    Map the seams

    Two weeks of discovery: actual workflows, actual pain points, actual data flow. We left with a written architecture diff.

  2. ii.

    Service boundary first

    Reshape one boundary at a time. Old code keeps running. New code gets observable interfaces. No big-bang rewrite.

  3. iii.

    Retrieval as foundation

    Stand up the retrieval layer the AI roadmap needed. Once it existed, three planned features became weeks of work, not quarters.

  4. iv.

    Hand the keys back

    By month four, the client's team was making architecture decisions independently. We stayed on retainer for the hard ones.

04Outcome

AI features in production,
and trusted.

By month six, the team was shipping AI features their CTO had been promising for a year. Release cadence is back to weekly. Onboarding a new engineer takes a week, not a month.

The team got their evenings back. The roadmap stopped being a hostage to platform debt.

i
faster release cadence
ii
4 mo
rebuild duration (zero downtime)
iii
0
rollbacks since release
iv
100%
of AI calls eval-scored

Stack

Frontend

Next.jsReactTypeScript

Backend

NodePostgreSQLRedis

AI

OpenAIpgvectorEvals

Infra

AWSTerraformGitHub Actions
Djuradj and his agency were always our technical twin on eye level. They understood exactly what the business side needed and developed pragmatic, hands-on solutions. With the design of the mid-term architecture, they found a good way to help the team and external stakeholders understand where we wanted to go.
M.C.
M.C.
Head of Product · Swiss climate-tech platform
05Have a similar problem?

Tell us the constraint.
We'll tell you the shape.

30-minute discovery call. We'll be honest about whether we're the right team.