Carbonoodle’s enterprise bet is paying off: Atlas Manufacturing signed in April and
Sales has been on a tear. That same surge strained the platform — a mid-May outage
briefly pulled Engineering, Product and Support into the red before Support clawed back.
The headline numbers climb the right way; European expansion is our one stubborn red.
The whole company, on one screen
OKRnest › Explore › Table
Two cycles, six teams, one glance: the annual plan is pacing steadily and the quarter is
tracking well ahead of halfway. The more honest picture is the trend — are we climbing fast
enough to finish the cycle?
OKRnest › Explore › Timeline
The dotted line is the pace we’d need; the dots are where we actually were each week. The
mid-May flat spot on the lower curve is the incident, visible from orbit — and so is the
recovery that followed it.
Leadership — the annual scorecard
OKRnest › Teams › Leadership › Status
The headline metrics are all pointed the right way: ARR climbing toward the €5M goal,
enterprise logos marching toward 120, hiring roughly halfway up the mountain. One bar
refuses to turn green — European expansion — and Erik would like the room to look at it.
OKRnest › Key Result sheet — “Launch platform in 3 new European countries”
This is the story in one chart: we launched the first new country, then the line went flat.
The CSRD Omnibus rollback put a question mark over mid-market demand across Europe, and the
next two launches are waiting on that uncertainty to clear rather than on us.
Featured team: Engineering — held the line, honestly
Every month we put one team under the spotlight. This time it has to be Engineering, because
the most interesting thing about the period isn’t a number — it’s a dip.
OKRnest › Teams › Engineering › Status
Data volume rode the enterprise wave almost all the way to target and accuracy held steady.
Where the month bit back was reliability: uptime and incident-recovery both sit Behind,
and that’s not a rounding error — it’s the May incident, written down where everyone can see it.
OKRnest › Key Result sheet — “Achieve 99.99% platform uptime SLA”
The shape tells it better than we could: a steady green run, a hard fall on 14 May when the
big-account volume outran our capacity, then a week-by-week climb back toward the line. Johan
was the one paged at 02:00; he and the squad rebuilt the ingestion path under fire. The last
status note says it plainly — recovered, but the quarter’s target is out of reach. We’d
rather log that honestly than dress it up.
The people moment
Numbers are people in a trench coat. Engineering had the hardest month and the best story:
Johan, who owns the uptime number like a personality trait, was the one paged at 02:00 on 14
May, and he and the squad more or less moved into the office until the ingestion path stopped
buckling — they came out with a haunted look and a much better runbook. A few desks over,
Marketing’s Lisa saw the mid-market collapse three days before anyone said it out loud and
quietly rerouted the spend toward enterprise. David in Customer Success spent the incident
turning three furious escalations into renewals through sheer relentless niceness. And
Niklas, who landed Atlas, has now told that story to everyone in the building, including the
facilities manager — which is fine, because that one logo is doing a lot of heavy lifting.
Everything in this report is live in OKRnest. Want to drill into any number — happy to share
the workspace view in the meeting.