commitops

Docs

Guides

Each guide names the buttons as the screen labels them, says what success looks like, and lists the fixes for what goes wrong. Each one has a 30-second video made from its own steps.

Product tour

Transcript, 2 minutes

Your team makes promises to customers every day. CommitOps keeps the ledger.

Setup has five steps, and each one ticks only when the data is there.

Connect one mailbox, read-only, and we read 90 days of customer threads.

Or paste one call. Every quote is checked word for word against the text.

Each candidate shows the exact sentence. A person keeps it or discards it.

Five minutes a day keeps the queue at zero.

The ledger holds every kept promise, with its owner, its work and its due date.

Gaps shows promises with no work started, ranked by the deals waiting on them.

When the work ships, a draft lands in your own Gmail, checked against the code.

On Monday the week is assembled for you: promised, shipped, told and slipped.

Mark the promises that block a deal, and each deal counts once.

Delivery lists what every new customer was promised before they signed.

Asks gathers the same request across every wording, ranked by the money it blocks.

The claim register keeps every public claim next to a dated check.

Entitlements sets each contract beside what your system grants.

Every row shows the sentence it came from. Start with one mailbox at commitops.ai.

Captions on by default. Made from this page’s steps, with demo data only.

Get started

Your first ledger in ten minutesConnect one mailbox, keep the candidates that are real, and link one repository, so you see what your team promised and whether it shipped.10 minutesConnect Gmail or OutlookGive CommitOps read access to one mailbox and its calendar, see exactly what it reads, and know what disconnecting deletes.3 minutesPaste a call or a threadRead one call transcript or email thread with no connection at all, and get its promises as candidates in the inbox.2 minutesKeep or discard a candidateDecide whether a sentence is a real promise: keep it, edit it first, or discard it with a reason that teaches the queue.2 minutesTwo-factor and recoveryTurn on two-factor sign-in with an authenticator app, keep your recovery codes, and sign out a lost device.

Daily use

Work the inboxClear the queue of candidates each day with filters, the keyboard and Keep all firm, so the ledger stays current.5 minutes a dayRead the gapsAct on the two lists that cost money: promises with no work started, and work that shipped without anyone telling the customer.5 minutesTell the customer it shippedTurn merged work into a draft in your own Gmail, checked against the code, and let the told sweep notice when the news went out.3 minutesRead the ledgerFind any kept promise, filter to what is late or blocking, and open one to link work, move its date or withdraw it.4 minutesThe Monday reviewRead the page the Sunday sweep assembles from the week: what was promised, shipped, told and slipped, and who carries what.10 minutes a week

Revenue

Blocking dealsMark which promises hold up a deal, so the ledger and gaps rank work by the pipeline waiting on it, each deal counted once.4 minutesDelivery after the signatureSee what each new customer was promised during the sale, who owns each promise, and send them a status in one draft.4 minutesWhat customers asked forGroup the same request across every wording and account, ranked by the pipeline it alone blocks, and send it to Linear.5 minutesOutcomesCompare closed deals whose promises were kept with deals whose promises were not, at the moment each deal closed.4 minutesRenewalsSee every account renewing in the next 90 or 180 days, ranked by the revenue renewing, with the promises due before each date.4 minutes

Truth

The claim registerKeep every public claim about your product next to a dated check, so nothing false stays published and nothing true goes stale.6 minutesEntitlementsCompare what each customer's contract says against what your system grants, led by customers who get less than they paid for.4 minutes

Agents and API

Connect an agentConnect Claude Code, Claude Desktop, Cursor or claude.ai over MCP or HTTP, with every tool and the rules agents follow.The check_claim contractA versioned route that answers verified, false or unverified with the date a claim was last checked, and fails open.Set up a product's agentOne workspace per product, an agent principal in each, a propose-only key, check_claim before a capability.The sibling feed contractHow RepoOps and SalesAsCode push work, spend and deals to CommitOps as agent principals, and what is never asked for.