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 two days.

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 is an in-person, two-day Full Build 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 two-day Full Build are handled through the application process so Obvious can align the team, scope, and pricing.

Frontier Dallas

Event details

Bring one roadmap priority. Leave with production-ready work built alongside the Obvious team.

Date: July 30–31, 2026

Location: Dallas, TX

Overview

Dallas

DALLAS

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

FULL BUILD EXPERIENCE

Ship 12 weeks of roadmap work in 48 hours.

Bring one roadmap priority. Leave with production-ready work built alongside the Obvious team.

Two focused days.

A two-day build sprint for specs, steering, review, and production hardening.

Apply to join the Dallas build room.

Format dossier

Texas

USA

Modern Event Space Outside of American Airlines Center

Oak Lawn, Dallas, TX

Expectations

Shipped Code: Work in your own codebase and leave with implementation, not notes.

AI by Builders: Learn how experienced builders apply AI to production work.

Real Systems: Tune specs, context, CI, and guardrails around production constraints.

Engineering Peers: Work beside CTOs and engineering leaders facing the same execution pressure.

Method

Obvious turns roadmap intent into a system the team can understand, steer, verify, and continue operating after Frontier.

System understanding: Read the codebase, patterns, specs, context, and production constraints before work moves.

Intent and reasoning: Translate roadmap intent into reviewable specs and decisions the engineering team can inspect.

Orchestration and feedback: Steer live runs, review output, and update context and guardrails as the system learns.

Verification and judgment: Use CI, review, underwriting, and engineering judgment to keep production work accountable.

Audience

CTO: Decide where AI can safely change engineering delivery.

VP Engineering: Turn roadmap pressure into operating loops your organization can sustain.

Head of Engineering: Improve throughput without giving up review, CI, or architectural judgment.

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

Format options

Full Build

Recommended

2 Days

Set unbelievable goals and move your baseline forever.

Day 1: Integration, roadmap review, first spec runs

Day 2: Full build sprint, steering, underwriting

Sprint

Lighter Option

1 Day

Get the essentials and ship something wildly impressive.

Day 1: A condensed build cycle in a single session

Agenda

10:00 AM — Doors Open

10:45 AM — Welcome & Round Table

11:00 AM — Learn Spec Design with David

1:00 PM — Lunch

1:30 PM — Work Session 2: Steering

5:00 PM — Pulse Check

5:30 PM — End of Day 1

10:30 AM — Welcome

10:35 AM — Obvious at Obvious

11:00 AM — Work Session 1: Underwriting

1:30 PM — Work Session 2: Shipping to Production

4:00 PM — Debrief

4:30 PM — Happy Hour

5:30 PM — End of Event

Agenda days

THURS · DAY 1

10:00 AM — Doors Open

10:45 AM — Welcome & Round Table

11:00 AM — Learn Spec Design with David

1:00 PM — Lunch

1:30 PM — Work Session 2: Steering

5:00 PM — Pulse Check

5:30 PM — End of Day 1

FRI · DAY 2

10:30 AM — Welcome

10:35 AM — Obvious at Obvious

11:00 AM — Work Session 1: Underwriting

1:30 PM — Work Session 2: Shipping to Production

4:00 PM — Debrief

4:30 PM — Happy Hour

5:30 PM — End of Event

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 connect the schedule to the production patterns behind Frontier: spec design, steering, underwriting, and review.

Prep

Laptop: Use the machine you normally ship from.

Codebase Access: Have repository, CI, product context, and permissions ready.

Roadmap Context: Choose one roadmap item ambitious enough to matter.

Room Logistics: Workspace, Wi-Fi, coffee, meals, and room flow are covered.

Venue

Modern Event Space Outside of American Airlines Center

Exact address shared after approval.

A modern private event space near American Airlines Center with an indoor lounge, glass-enclosed conference room, and outdoor networking area.

Notes: Indoor lounge; Glass-enclosed conference room; Outdoor networking area; Premium professional setting

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 two days.
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 is an in-person, two-day Full Build 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 two-day Full Build are handled through the application process so Obvious can align the team, scope, and pricing.