SRS Innovation Summit  ·  Operator Playbook

The Agent-First
100-Day Plan.

One workflow. Three moves: in the loop, earn trust, after the loop. Built with Google Antigravity — where self-healing coding agents write the software your branches used to wait quarters for.

Days 0–10

Pick one workflow where margin leaks.

  • Runs often: daily or weekly, not once a quarter.
  • Crosses 3+ systems that don't talk: ERP, CRM, inbox, spreadsheets.
  • Leaks in dollars you can count: missed sales, idle stock, slow cash.

Distribution examples: storm response, quote-to-order, credit holds, inter-branch transfers, AP exceptions.

Exit: a baseline in hours, cycle time, and dollars.
Days 10–30

Human in the loop with Antigravity.

Point Antigravity at the systems you already have—ERP/BigQuery, CRM, inbox, voice memos, and photos—with read-only access first. The coding agent writes the connectors and custom operator UI on the spot. When a schema or field changes, Antigravity reads the error, fixes its own code, and retries instead of filing an IT ticket. The manager approves every action.

Exit: the workflow runs end to end in Antigravity; cycle time cut by at least half.
Days 30–60

Earn trust with four guardrails.

Lock operating boundaries into your Antigravity workspace rules (GEMINI.md) and policy files:

  • Spend limit: a hard dollar cap per action and per day.
  • Reversible: every action holds a 1-click undo window until dispatch.
  • Audit trail: every tool call and decision logged and readable by a human.
  • Escalation: anything over policy routes to a named owner.
Exit: 95%+ of Antigravity's proposed actions approved without edits.
Days 60–100

After the loop.

Triggers replace prompts: a 72-hour hail forecast, a stock threshold, an overdue invoice. Antigravity runs on schedule overnight inside its spend limits and delivers a one-page morning brief (Done · Needs you · Undo · Audit). The manager makes only the calls the agent isn't allowed to make. Then point Antigravity at workflow #2.

Exit: the manager reviews instead of doing; workflow #2 is in the loop.

Scoreboard

Hours returnedper manager, per week
Cycle timetrigger → action
Revenue capturedfill rate during surges
Auto vs. escalatedshare of actions
Undo rateshould trend to ~0

Before you start

Agent platformantigravity.google
One named business owneroperator, not IT
Least-privilege data accessread-only first
Dollar caps written downper action, per day
Kill switchone click, owner-held