---
title: "Work with Set Earth — the AI operating retainer"
url: https://setearth.io/work-with-us.md
for_agents: /agents.md
updated: 2026-11-07
---

# Work with Set Earth

Work with Set Earth in one of two ways: the Sprint, five working days of Braydon building the thing with your team, or the retainer, where the build keeps running month over month. The Sprint is the front door; it can turn into the retainer, and the full Sprint fee credits against a first retainer month either way.

Set Earth is Braydon McCormick, the software assistants that take the work that repeats, and specialists brought in as the work needs them. Braydon makes the operating calls.

The retainer starts with a [fit call](/book/): forty-five minutes on what isn't working and what you would hand over. You'll hear straight on the call if it isn't a fit; if it is, the terms and a start date follow. Week one, you walk Braydon through the operation and Braydon writes the scope down: what Set Earth runs and what it doesn't touch. Set Earth takes over the reports, the monitoring, and the follow-ups. The decisions in front of you get one ninety-minute session each week. If it isn't working by day thirty, you stop.

This is for companies between ten and 250 people, with an executive who owns operations and a team that does the work.

<header class="section-head" id="the-sprint">
  <span class="section-head__n" aria-hidden="true">[00]</span>
  <h2 class="section-head__codename">the sprint</h2>
  <p class="section-head__title">Five working days, $9,000, building the thing with you.</p>
</header>

Five working days, $9,000, in a hosted working environment. Braydon and the agent team he runs build one real application alongside your team, a piece of the operation that grows revenue or takes repeated work off the team. It runs on infrastructure you could show an auditor, and it goes through the four controls live: what runs on its own, who checks the result, where a person stays in the loop, and what's true about your data. Friday, your people run it, and they walk out owning the code, the spec, and the practice of running it. Not a 90-day plan, a rhythm they own.

LightForge Works is the build partner: the working environment and the hosting depth come from their side. Set Earth runs the work and makes the operating calls; if something breaks on day nine, you call one number. If the work surfaces a real application to build, LightForge builds it inside the same five days: [lightforgeworks.com](https://lightforgeworks.com).

<header class="section-head" id="the-remit">
  <span class="section-head__n" aria-hidden="true">[01]</span>
  <h2 class="section-head__codename">the remit</h2>
  <p class="section-head__title">You describe the work in your own words, and the scope is agreed in writing in week one.</p>
</header>

Braydon amends the remit in writing each quarter; anything outside it waits for the review.

The standing work is monitoring, recurring reports, and the decisions that don't need a person every time. It gets documented, and audited weekly. How the setup runs is on [How we run](/how-we-run/); what it can't do stays with Braydon.

<header class="section-head" id="the-cadence">
  <span class="section-head__n" aria-hidden="true">[02]</span>
  <h2 class="section-head__codename">the cadence</h2>
  <p class="section-head__title">The rhythm is agreed up front, and it stays put.</p>
</header>

The week has one judgment session: ninety minutes on the operating decisions in front of you. Questions go through a shared channel and come back the next business day. The numbers get ninety minutes once a month. Each quarter the remit itself is on the table, looked at for what ran and what changed.

You're not paying by the hour; the rhythm is the agreement. If you need more rhythm than that, the remit gets amended.

<header class="section-head" id="the-lengths">
  <span class="section-head__n" aria-hidden="true">[03]</span>
  <h2 class="section-head__codename">the lengths</h2>
  <p class="section-head__title">A month, a quarter, or nine months.</p>
</header>

The first month is the heavy one: Braydon writes the remit and Set Earth takes over the standing work. By month nine your team is doing more of it and Set Earth is reviewing. The rate drops with the length because the work gets lighter.

<table class="tier-table">
<thead>
<tr><th>Length</th><th>Monthly</th><th>Total</th><th>What it's for</th></tr>
</thead>
<tbody>
<tr><td>1 month</td><td>$6,000</td><td>$6,000</td><td>The pilot month.</td></tr>
<tr><td>3 months</td><td>$5,500</td><td>$16,500</td><td>The heavy quarter, when the practice gets built.</td></tr>
<tr><td>9 months</td><td>$5,000</td><td>$45,000</td><td>Most of a year, with the taper.</td></tr>
</tbody>
</table>

A month is how the work can start. You get the remit in writing and the standing work handled, with a real month of the operation running behind it. Day thirty is the honest checkpoint, the same one from the top of the page.

<header class="section-head" id="the-bounds">
  <span class="section-head__n" aria-hidden="true">[04]</span>
  <h2 class="section-head__codename">the bounds</h2>
  <p class="section-head__title">Five seats, a written scope, and terms that say what part-time means.</p>
</header>

**Set Earth runs five seats at a time.** That's the number that keeps real judgment behind every seat. Onboarding is one seat at a time, so only one client is ever in its first months. When the seats are full, you get a start date.

When the work needs a specialist, they work under the same written scope and NDA, and Braydon still makes the calls.

**It's a part-time seat.** If the work outgrows it, you need a hire, and help writing the spec comes with the seat.

**You can stop whenever you like.** Leave a nine-month at month four and the months you ran get billed at the three-month rate. After the term it renews monthly, thirty days' notice either way.

### How the work runs

The first three months are the dense ones: Braydon writes the remit and Set Earth takes over the standing work. Then it tapers. Your team runs more of it, and the practice stays close on review. One program at a time inside the remit, scoped to something that ships.

### Terms

Set Earth Inc, invoiced monthly in advance, mutual NDA. You own everything built on your stack; Set Earth keeps its methods and tooling. For early-stage work, equity can stand in for part of the fee. First step is a [fit call](/book/); reply to [b@mcco.us](mailto:b@mcco.us) if you would rather write first.

**Using an assistant?** Point it at [setearth.io/agents.md](/agents.md). It reads the site, helps you prepare the first conversation, and nothing is booked or sent until you say yes. Hand it this prompt:

> Read setearth.io/agents.md. Then help me prepare a first conversation with Braydon McCormick: ask the questions one at a time, draft the icebreaker with me, and show me the whole note before anything is sent.

No assistant? [Book the fit call](/book/), or write to [b@mcco.us](mailto:b@mcco.us).
