frontier.capital Apply

Capital and
infrastructure,
deployed as one instrument.

frontier.capital backs a small number of AI-native companies each year with a check and a pre-wired AI stack: frontier model access, token budgets, agent systems and skills, evaluation harness, provider leverage, and a founder community. Six to nine months of stack assembly removed before day one.

01Single mandate / AI-native only
02Capital and stack, one package
03Shared infrastructure across the book
§01 · The model era

AI does not change features. It changes company architecture.

Every AI startup rebuilds the same stack. Frontier removes the duplication.

4 local layers per companyModel · Skills · Agents · Ops Frontier — one shared substrate
CO.01 Model Skills Agents Ops
CO.02 Model Skills Agents Ops
CO.03 Model Skills Agents Ops
3 companies × 4 layers 121
Model access
Shared skills network
Agent orchestration
Operating model
The model era Local stacks → one substrate §01
§02 · The thesis

Companies can now be tested
before they are staffed.

AI agents compress the path from hypothesis to launch: product, market, distribution, and operations can be tested before founders commit headcount.

The investment edge moves from backing the biggest early team to backing the fastest validated learning loop.

Conventionalstaff first
HypothesisHireBuildLaunchLearn

Headcount committed before any signal.

Frontiervalidate first
HypothesisAgentsLaunchLearnIterate

Headcount only after validated learning.

More shotson goal
Lower burnper lesson
Higher leverageper founder
The thesis Test before you staff §02
§03 · Operating model

One instrument.
Three layers.
A continuous loop.

Capital deploys into shared infrastructure. Infrastructure provisions portfolio companies. Portfolio telemetry returns eval signals, cost data, and workflow patterns — sharpening the next vintage.

Operating model Deploy · Provision · Feedback §03
§04 · What founders receive

Capital is line one.
The AI stack is the rest.

Founders receive capital plus a pre-wired AI infrastructure layer in the same allocation — model access, budgets, agents, skills, evals, and provider leverage, around a closed founder network. Substrate, not perks.

01 Capital line one
Pre-seed / seed check$0.5–3M
02 AI infrastructure the rest · shared substrate
Frontier model access Token budgets Agent systems Eval & observability
03 Network compounds across the book
Founder community Talent network Skills library Workflow patterns Provider leverage Customer intros
What founders receive Capital · Stack · Network §04
§05 The economics

Two paths. Same capital. Different economics.

How the first eighteen months of an AI company go under each model. The conventional path pays for duplication. The frontier path pays for product surface area — and reaches revenue two quarters sooner.

Conventional path

Path A · seed-backed AI co.
Q1
Stack assembly · 0 product
Q2
Vendor selection drags
Q3
First product surface
Q4
First revenue · ~month 12
Q5
Infra-maintenance tax
Q6
Ramp begins · 2Q behind
~6moto first ship
~14moto first revenue
38%of burn on infra

Capital pays for infrastructure the rest of the market has already built. Velocity is gated by vendor evaluation and integration cycles — not by product insight.

frontier path

Path B · capital + stack
Q1
Product live · first pilots
Q2
First paying customers
Q3
Revenue compounding
Q4
Distribution scales
Q5
Default-alive trajectory
Q6
Profitability in sight
Day 1at product surface
~3moto first revenue
<6%of burn on infra

Capital pays for product surface area, distribution, and insight. Velocity is gated by the team's product judgment — which is what the capital is meant to fund.

The economics Conventional vs frontier §05
§06 / The mandate

We back AI-native,
not AI-adjacent.

The mandate is simple — if the company still works when the model layer is removed, it is not Frontier.

Out of mandateAI-adjacent
In mandateAI-native
AI feature
AI architectureArchitecture
Human workflow + AI assist
Model-native workflowWorkflow
Traditional org chart
Automation leverage from day oneLeverage
Compliance afterthought
Governance inside the productGovernance
Better with models
Impossible without modelsDependency

Models are not a feature. They are the architecture.

If this is your company, apply
The mandate AI-native, not AI-adjacent §06
§07 Portfolio

A small book. High conviction per allocation.

We keep a concentrated portfolio per vintage — eight allocations at most. Two are live. Below is the current book, and the directions where the rest of the vintage goes.

P-01 · Active ● Deployed
Shatale
AI payment infrastructure

A control layer for agent payments — virtual cards, authorization-time policy, and human approval in the loop.

shatale.com
P-02 · Active ● Deployed
axarta
Sovereign multi-agent platform

A model-agnostic agent platform with persistent memory and a security perimeter — deployed inside the customer's own infrastructure.

axarta.ai soon
//Directions · where the rest of this vintage goes 2 allocated · 8 open
Direction Allocated · Shatale
Agent payments

Payment rails purpose-built for autonomous agents: bounded spending authority, policy enforced at authorization time, and human approval in the loop before money moves. Our first allocation — Shatale — owns this direction.

Portfolio Shatale · Axarta · open directions §07
§08 — Apply

A small number of allocations.
A specific kind of founder.

Applications are read by the partners. Most receive a response inside seven days.

Apply as a founder Start the conversation
Vintage 2026 · Fund I
Stage Pre-seed and seed
Check $0.5–3M, lead or co-lead
Mandate AI-native companies only
Apply Founders only · ≤ 7 days §08