The room where the things that matter happen.
Paper, marker, decent coffee, an outside facilitator. No screens, no slides, no "team building". In 48 hours your team leaves with three named blockers, three concrete moves, and a one-page memo you can take to the next board meeting without apologizing.
Boring is the feature.
The name isn't ironic. Most technical offsites end in escape rooms, colored sticky-note exercises, or a coach telling everyone to "vibe together". You come back Monday and nothing has changed.
None of that here. A room, a table, paper, and the questions your team has been ducking for six months. When someone says them out loud and no one can look at their phone — something else happens.
Read the manifesto "Your startup doesn't need more engineers" →
Two days. One room. Your team and me.
Day 1 · Morning
Map
Where the team is today. What it ships, what it promises, what it costs. Numbers on the table.
Day 1 · Afternoon
Blockers
The three things actually stopping progress. Not the ones from a retro six sprints ago — the ones no one names.
Day 2 · Morning
Moves
Three concrete things the team decides to do (and two it explicitly decides NOT to do).
Day 2 · Afternoon
Memo
One page. Defendable to the board without glossary. The team drafts it; I edit.
Five to ten people. Your team, not mine.
The full engineering team if you're under ten. If more, the decision core: CTO/VP Eng, two or three tech leads, a PM if you have one. The board doesn't come. No consultants. No agencies.
Whether the non-technical CEO joins, we discuss in discovery — sometimes it helps, sometimes it gets in the way. Depends on the team.
Three artifacts. Zero PowerPoints.
- Top-3 named blockers — the real ones, with owner and date.
- Top-3 concrete moves — what to start, what to stop, what to protect.
- One-page memo — written in board language, defendable the next day.
Three reasons not to do it.
- If your team needs someone to write the code — that's not me, I'll send contacts.
- If you need Scrum / SAFe / ICAgile certification — I don't certify, and don't want to.
- If you're trying to validate a pre-PMF idea — the Boring Room is for teams that built something and lost the plot, not teams still looking for what to build.
What's happened in rooms like this.
ClicOh · 2021–22
As DevOp, not an external facilitator. By session five the devs asked to implement QA on their own. 18 months later, the culture still holds.
GoJiraf · 2022–23
As Senior DevOps Manager. Infra went from USD 1.5K/mo at 1K users to USD 2.5K/mo at 50K users. 50× scale at 1.6× cost.
Hubbing LATAM · 2021–24 · Senior DevOps Consultant
A B2B startup in LatAm extended runway by +8 months through cost-aware DevOps decisions.
These engagements were done from inside the team as DevOps or Solutions Architect. The Boring Room is the short format that distills eight years in rooms like these — same decisions, condensed into two days.
30 minutes. No pitch. No slides.
You bring the decision you're weighing or the pain that won't go away. I bring eight years of pattern-matching from rooms like this. If there's no fit by the end of the call, I'll say so. If there is, we talk about what a Boring Room looks like for your team.
Or email [email protected].
Pricing discussed in discovery. The number depends on team size, format (on-site vs remote), and travel.