CobaltCobalt
Pricing Book a demo

Your agents worked all day. They came to you when it counted.

Agents work, you approve from your phone. Everything logged, everything learned. Cobalt is the layer between your judgment and your fleet. You plan with your team, agents execute, and your phone stays quiet until it counts.

AGENTS RUNNING 16 · DECISIONS TODAY 129 · FOUNDER TIME SAVED 5.1h
Cobalt
Today 9:41
Your dev agent finished the onboarding revamp. Tests green, 30-sec preview attached. Ship to prod?👍
Shipped ✓ Next: ads agent wants +$400/day on Meta. Heads up, CAC is up 22% this week.👎
More info
CAC went $340 → $415 this week; the retargeting set is saturating. Three ways to go:
1 · Hold budget
2 · +$200/day, prospecting only
3 · Pause retargeting 48h, re-check
2
Done, capped at $200/day, prospecting only. I'll report back Friday.
PLANYOU DRIVE

Point the fleet. Planning is the human part. You and your team set the goals and define success.

RUNCOBALT DRIVES

Works where you work. Agents execute around the clock, inside the tools your company already uses.

DECIDEYOU DRIVE

Just the outcome. Only the information you need to make the call. Approve, reject, move on.

LEARNCOBALT DRIVES

Every decision compounds. Cobalt learns your priorities, taste, and values. Never explain the same thing twice.

Agents are doing too much.

Brilliant at the work. Brutal to review. Here's the same finished task, two ways.

WHAT AGENTS SEND YOU

I've completed the onboarding flow redo. This was roughly five hours of continuous work, so let me walk you through everything I did and my reasoning.

Read onboarding/flow.ts
Analyzed session state across 14 files

What I did

I mapped the architecture end to end, reading all 14 files that touch onboarding state, and found session state duplicated in three places.

Ran 2 commands

I then evaluated three architectural approaches before writing any code:

  1. Patch the legacy reducer in place. I rejected this after tracing 23 call sites that would each need conditional handling. The coupling is the problem; patching preserves it.
  2. Introduce a dedicated onboarding store with lazy hydration. This is what I implemented. It isolates onboarding state behind a single interface, and the migration is mechanical and reviewable.
  3. Refactor the whole session layer. The most thorough option, but it would have touched checkout and auth, and I judged the blast radius too large for this task. I have noted it as a candidate follow-up.
Edited session/store.ts
Updated 41 call sites

The work, hour by hour

Hour 1: Full exploration and dependency mapping. Built a mental model of every consumer of session state.

Hour 2: Implemented the new store, ported the step registry to buildSteps with feature-flag support. For each call site, I verified whether the caller read state synchronously before first render, since lazy hydration breaks that...

Ran test suite · 214 passed
// 2,900 words to review · honestly, no one reads this
WHAT YOU ACTUALLY NEED
Onboarding revamp shipped. Tests green, 30-sec preview attached. Safe to launch?👍
// 11 seconds · back to your day

Only the need-to-know.

Pricing

Pay for outcomes.

Every plan starts with a one-time setup of $15,000. We stand up your fleet and train Cobalt on how you decide. Then pick the tier that fits your volume.

SOLO
$499 / month
UP TO 1,000 APPROVES

For the modern founder and their fleet.

TEAM
$1,499 / month
UP TO 10,000 APPROVES

For AI-native startups, humans and agents building together.

SCALE
Custom
COMMITTED VOLUME

Fleets that outgrew the meter. Better rates, annual terms, hands-on support from us.