Question 1

Which event is for me?

Accepted Answer

Frontier Build is a one-day intensive: founders and technology leaders in one room, learning the new way of working with AI in their own codebase. You leave ready to execute on 12 weeks of roadmap in 2 days.

Frontier Tables are intimate dinners, twelve seats: conversations for founders and technology leaders on what it takes to build something durable.

Panels are public discussions: open conversations with practitioners building on the frontier, recorded and shared.

Speaking Events are talks and keynotes: presentations from leaders building on the frontier, hosted at partner conferences and events.

Question 2

Do we need a mature codebase?

Accepted Answer

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

Question 3

How technical do our engineers need to be?

Accepted Answer

They need to be comfortable reviewing PRs at release level, but they don't need prior experience with autonomous agents. Frontier is about evaluating whole capabilities rather than individual commits. We'll brief everyone on operating Obvious at the start of day one. The goal is that by the end of day two, your team can run it independently.

Question 4

What if our CI is slow or flaky?

Accepted Answer

Slow CI is something that we can work on as an outcome of Frontier. Flaky CI is harder; it creates noise that makes it difficult to distinguish agent errors from infrastructure errors. We ask teams to stabilize critical test paths before arriving.

Question 5

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

Accepted Answer

Remote participation significantly reduces what your team can get done. If your team can't send technical representatives, reach out directly and we'll discuss whether a future cohort works better for your schedule.

Question 6

How do we prepare before the sprint?

Accepted Answer

Once accepted, you'll get a prep guide. You'll connect your GitHub repo to Obvious. We'll teach you how to write a first spec. And we'll share more context on what to expect on day one. The most important preparation is identifying the specific roadmap target you want to ship because the teams that arrive with a clear spec get the most out of both days.

Question 7

What does it actually cost?

Accepted Answer

There is no ticket cost for Frontier.

Your spend is linked to your build. Frontier accelerates the work you're already doing with LLMs. So you can think of it as a transferred cost for work you've already planned.

A better question is, "What is the cost of this work outside of Frontier?" Paragon's CTO described the output as six months of their hardest engineering work.

Building on the frontier requires a whole new way of working.

Upcoming Builds

Build

Build

Build

Build

Build

All events

Find your event.

Table

RenderATL

Build

Table

Build

Table

Build

Table

See all events

Events will cover topics like

Writing specs for long-horizon tasks

Ship better, not just more

Autonomous runs

Agent teams and roles

Running work in parallel

Harness tuning and optimization

Managing the transition

Frequently asked questions

The Frontier is calling.