A studio for engineering offsites · est. 2026

Offsites for engineering teams that don't suck.

We design two- and three-day offsites for engineering teams of 8–40. You get a sharp agenda, a facilitator guide, and the small rituals that turn a calendar block into a thing your team actually remembers. No trust falls. No vision quests.

One studio. One designer. Direct line. Drafted in a week.
SECTION 01 / PROBLEM

Why this exists

Most offsites are an awkward, expensive way to leave town for three days.

"

We flew 24 people to a beach house and somehow only made one decision. It was about lunch.

— Eng Manager, Series B SaaS

"

The agenda was a Notion doc that someone wrote at 11pm the night before. We winged it.

— Director of Engineering, fintech

"

Two icebreakers, four panels, zero follow-through. Three months later nothing had changed.

— Staff Engineer, healthtech

The pattern is depressingly consistent. Someone good at their actual job ends up moonlighting as an event planner. The schedule gets thin. The conversations stay shallow. The follow-through dies in a Slack thread by Wednesday. Then everyone agrees it was "a good time" and books the next one for Q4.

SECTION 02 / APPROACH

Three things, done well

We optimize for the things teams actually remember a month later.

01 / CLARITY

Clarity

Before we book a single hour, we get sharp on what the offsite is for. One outcome, written down. If we can't name it, we don't run it.

  • Pre-offsite interviews with leadership and ICs
  • One-page brief everyone signs off on
  • Hard "no" on scope creep at the door
02 / STRUCTURE

Structure

Engineers respond to good architecture. We block time the way you'd design a system: explicit interfaces, clean handoffs, room to breathe.

  • Hour-by-hour agenda with explicit goals
  • Workshop templates, not free-form "discussions"
  • Built-in slack — for actual rest, not panic-prep
03 / FOLLOW-THROUGH

Follow-through

The week after is where most offsites die. We design the artifacts, the owners, and the 30-day check-in before anyone gets on a plane home.

  • Decisions log shipped within 48 hours
  • Owner + due date on every action item
  • 30-day async retro to check what actually stuck
SECTION 03 / DELIVERABLES

What you actually get

Five documents. Designed to be read once, used hard, then archived.

  • 01

    Overview Doc

    The why, the who, the one outcome. The thing you forward to your VP so they stop asking.

    PDF · 2 PG
  • 02

    Detailed Agenda

    Hour by hour. Goals, owners, materials, transitions. Printed and pinned to the wall.

    PDF · 6 PG
  • 03

    Facilitator Guide

    What to say, when to interrupt, how to land each session. Designed for someone on your team to run it.

    PDF · 12 PG
  • 04

    Activity Templates

    Worksheets, board layouts, decision frameworks. Sized for whiteboards, FigJam, or paper.

    PDF + FIG
  • 05

    Follow-through Kit

    Decisions log template, action-tracker, 30-day async retro script. The part that prevents amnesia.

    DOCX + GS
Overview Doc
DELIVERABLE 01 · 2 PAGES
SAMPLE
SECTION 04 / PROCESS

How it works

Three steps. Two weeks. No status meetings.

01

Brief

30-minute call. We ask about the team, the moment, and what would make this offsite worth the airfare. You leave with a one-pager you can react to.

~ Day 0130 MIN
02

Draft

One week later, you get the full blueprint: agenda, facilitator guide, activities, the lot. We iterate over async comments — not meetings.

Day 02 — 091 REVISION
03

Run

Your team runs it. We're on Slack the whole time for live questions, and we ship the follow-through kit within 48 hours of close.

Offsite week+ 48H
SECTION 05 / PRICING

One scope, one price

Flat fee. No retainer. No "let's hop on a call about scope."

An offsite blueprint covers a team of up to 40 for a 1–3 day program. Travel, venues, and catering are on you — we don't markup logistics.

Standard
$1,000 / blueprint

For everyone after. Same deliverables, same timeline.

  • Discovery brief + one-page outcome doc
  • Hour-by-hour agenda (1–3 day program)
  • Facilitator guide written for your team
  • Activity templates (PDF + FigJam)
  • Follow-through kit + 48h decisions log
  • One revision round, async
Get a standard proposal →

Don't see your shape? Custom programs (50+ engineers, multi-track, leadership-only) — email and we'll quote it honestly or tell you we're not the right fit.

SECTION 06 / FAQ

Reasonable questions

Things engineering managers actually ask before signing.

No. We don't book hotels, hire caterers, or argue with the Airbnb host. We design the program — the agenda, sessions, and follow-through. The logistics are yours, and that's deliberate: it keeps the price honest and the scope sharp.
Not by default. The facilitator guide is written so a senior manager or staff engineer on your team can run it confidently. If you want a co-facilitator on site, we can quote that separately, but most teams don't need it.
Sweet spot is 8–40 engineers — one to four squads. Below 8 and you don't really need a blueprint, you need a long lunch. Above 40 and the dynamics change; we'll tell you honestly if we're a fit and quote a custom program if we are.
A template assumes a generic team. The blueprint is built around your specific team's moment — what's tense, what needs a decision, what's been deferred for two quarters. The pre-offsite interviews are most of the value. The PDFs are the artifact.
One full revision round is included, async — leave comments, we ship v2 within 48 hours. If you need more than that, something is probably wrong with the brief and we'll talk.
A small studio. One designer-operator with a decade of running engineering teams (Series A through public), plus a rotating bench of senior facilitators when a project calls for it. You'll always work directly with the principal — there is no account manager to triage you.