SABLE: the operating system we run the agency on

Indigo Trigger runs its own agency on software it built. SABLE is that system: an agency operating platform that holds project memory, answers scoped questions about the book of work, turns meetings into tracked commitments, and routes every outbound action through a person.

The problem

Agency delivery leaves its record in too many places. Decisions get made on a call, promises get made in email, tasks live in Asana, hours live in a timer, and the scope everyone agreed to lives in a document nobody reopens. By the time a project is visibly in trouble, the evidence that it was heading there has been scattered across five tools for weeks.

One owned record

SABLE is built on a single owned data model — clients, projects, people, sources, decisions, promises, tasks, documents, approvals, and an audit trail. Meeting transcripts and documents land there as sources with their provenance intact, so any answer can be traced back to the thing that said it. The record is the product; every screen is a view onto it.

The surfaces

A portfolio cockpit for status, delivery risk, promise load, and logged hours. A project hub for the decisions, promises, and context on a single engagement. A draft workbench, a document library, and a client portal that shows a client only what has been explicitly released to them. Ask SABLE answers questions across the record, cites the evidence it used, and is read-only by construction.

The Outcome Engine

The pricing and scoping surface takes the agency's own delivery history — comparable projects, logged hours, category, budget and margin — and returns an hours range, a duration, and a confidence level for new work, alongside the comparables it reasoned from. When the history to support an estimate is not there, it says so and shows an insufficient-data state rather than inventing a number that looks authoritative.

Nothing acts without approval

Proposed actions land in an approval queue and move through a defined lifecycle that a person drives. Only approved proposals execute, external writes sit behind explicit operator switches that stay off until someone turns them on, and every session leaves an audit record. Even changes to the agent's own instructions are a reviewed approval rather than a quiet edit.

Why it is here

SABLE is not a product for sale. It is the clearest example of how we think revenue and delivery systems should be built: one owned record, evidence attached to every claim, and a human on every action that leaves the building. It runs in production, and we are still refining it.