Do we need a mature codebase?

No minimum maturity level is required, but Obvious works best when it can read your codebase and understand your patterns. Teams with at least six months of active development get the most out of the sprint. Greenfield projects can participate, but typically ship smaller scope in the one-day Sprint.

How technical do our engineers need to be?

Bring people who can make implementation and review decisions in the codebase. Frontier is hands-on, so the strongest teams include engineering leaders and builders who understand the roadmap, architecture, and tradeoffs.

What if our CI is slow or flaky?

Bring that context with you. Part of the work is identifying where tests, CI, review loops, and guardrails need to improve so the system can ship with confidence.

What if we can't send engineers on-site?

Frontier Miami is an in-person, one-day Sprint event. If travel is a constraint, raise it during application review so Kamp can clarify attendance requirements.

How do we prepare before Frontier?

Choose one roadmap priority, confirm repository and CI access, bring the hardware your team normally ships from, and make sure the people in the room can decide scope and review direction.

What does it actually cost?

Commercial details for the one-day Sprint are handled through the application process so Obvious can align the team, scope, and pricing.

Frontier Miami

Event details

Obvious is an applied AI research lab, closing the gap between what is possible and what is doable. Frontier is where we hand that system to other teams.

Date: August 14, 2026

Location: Miami, FL

Overview

Miami

MIAMI

FOR CTOs • VP ENGINEERING • HEADS OF ENGINEERING • TECHNICAL CO-FOUNDERS

1-DAY SPRINT

Build the fourth mode inside your own codebase.

Obvious is an applied AI research lab, closing the gap between what is possible and what is doable. Frontier is where we hand that system to other teams.

One focused day.

A factory running in the background while you do the work only you can do.

Apply to join the Miami build room.

THE DAY

Full Schedule

Doors at 10:00. Programming starts at 10:30. Wraps at 6:00. Happy hour and open build time after.

Every session pairs a teaching block with a working block. You learn the concept, then you use it — same day, same room, with help nearby.

Format dossier

Florida

USA

The LAB Miami

Wynwood, Miami, FL

Hero video

Frontier Miami title sequence over Art Deco buildings along the Miami shoreline

Expectations

A Working Factory: A factory that runs on your codebase, tuned by you, with merged PRs to prove it.

The Right Control: Look at bad agent output and know which control to reach for. This is the skill that keeps paying after the day ends.

Named Co-Managers: A named list of co-managers inside your company, plus a technique for turning your loudest skeptic into a reviewer with skin in the game.

A Four-Week Plan: A plan that takes you from a working factory to a factory that is simply how work flows through your team.

Method

Your week already has busy work, collaborative work, and deep work. Frontier builds the fourth mode: a factory running work in the background while you do the other three.

Specs and context: Point agents at real work — a bug backlog, a deferred improvement, a spec for something bigger — and give them enough context to produce.

QA and review: Catch bad output before it lands, and review larger change sets without losing fidelity.

Skills and loops: Turn what works into repeatable skills and loops the factory runs without you restating them.

Design systems and CI: Hold the guardrails that keep background work shippable against production constraints.

Audience

Technical Teams: Teams with at least one technical member who can build alongside us.

Non-Technical CEO: Welcome with a CTO or technical co-founder in the room.

CTO / VP Engineering: Decide where agent-scale delivery can safely change how your team ships.

Technical Co-Founder: Move product scope while defining the system your team will inherit.

Format options

Sprint

The Format

1 Day

Build the fourth mode and leave with merged PRs to prove it.

Day 1: A factory running by the first hour, then eight mechanisms to make it better

Agenda

10:00 AM — Doors Open

10:30 AM — Opening

10:45 AM — Session 1

11:15 AM — Working Block

12:15 PM — Lunch

12:30 PM — Session 2

1:00 PM — Working Block

2:00 PM — Break

2:15 PM — Session 3

2:45 PM — Working Block

3:45 PM — Break

4:00 PM — Session 4

4:30 PM — Working Block

5:30 PM — Closing

6:00 PM — Happy Hour

Agenda days

FRI · SPRINT

10:00 AM — Doors Open

10:30 AM — Opening

10:45 AM — Session 1

11:15 AM — Working Block

12:15 PM — Lunch

12:30 PM — Session 2

1:00 PM — Working Block

2:00 PM — Break

2:15 PM — Session 3

2:45 PM — Working Block

3:45 PM — Break

4:00 PM — Session 4

4:30 PM — Working Block

5:30 PM — Closing

6:00 PM — Happy Hour

Collaborators

Jon Bell — Co-Founder, Obvious at Obvious. Jon helps engineering leaders turn ambitious product intent into systems teams can actually ship.

David Boskovic — Co-Founder, Obvious at Obvious. David works across design, engineering, and AI systems to translate ambiguous roadmap work into executable specs.

Guided by the team operating the system.

Jon Bell and David Boskovic hand over the system Obvious runs on its own company, and the mechanisms that keep a factory producing work worth merging.

Prep

Laptop: Use the machine you normally ship from.

A Real Codebase: Access to a codebase you care about, with repository, CI, and permissions ready.

Fuel for the Morning: A bug backlog or a list of small improvements you have been meaning to make is ideal.

No Pre-Work: Nothing beyond signing up and following the onboarding steps in advance. Meals and snacks are provided.

Venue

The LAB Miami

2750 NW 3rd Ave #24, Miami, FL 33127

August 14, 2026

Frontier Miami is taking over The LAB Miami for one focused day of hands-on building, team review, and production work in Wynwood.

Notes: Wynwood location; Flexible event space; Collaborative workspace; Built for hands-on work

Sponsor line

Obvious

kamp

Testimonials

“Everything changed.” — Ishmael Samuel, CTO, Paragon

“You get instant results.” — Diptanu Gon Choudhury, CEO, Tensorlake

Frequently asked questions

Do we need a mature codebase?: No minimum maturity level is required, but Obvious works best when it can read your codebase and understand your patterns. Teams with at least six months of active development get the most out of the sprint. Greenfield projects can participate, but typically ship smaller scope in the one-day Sprint.
How technical do our engineers need to be?: Bring people who can make implementation and review decisions in the codebase. Frontier is hands-on, so the strongest teams include engineering leaders and builders who understand the roadmap, architecture, and tradeoffs.
What if our CI is slow or flaky?: Bring that context with you. Part of the work is identifying where tests, CI, review loops, and guardrails need to improve so the system can ship with confidence.
What if we can't send engineers on-site?: Frontier Miami is an in-person, one-day Sprint event. If travel is a constraint, raise it during application review so Kamp can clarify attendance requirements.
How do we prepare before Frontier?: Choose one roadmap priority, confirm repository and CI access, bring the hardware your team normally ships from, and make sure the people in the room can decide scope and review direction.
What does it actually cost?: Commercial details for the one-day Sprint are handled through the application process so Obvious can align the team, scope, and pricing.