Mutual action plan — SheetSpeed team pilot
Shared document. Short rows, not a narrative. Fill names and dates before day one. Security and legal run in parallel with the pilot, not after it. Prepared with the SheetSpeed trust pack.
Working title: [Company] × SheetSpeed pilot
Economic buyer: [name, role]
Champion: [name]
SheetSpeed contact: jarvis@agi-jarvis.com (Philip Dressler, Dressler Labs)
Pilot window: [start] to [end] — clock starts after install works, not on the day the idea is approved
Go/no-go meeting: [date] with [economic buyer]
Written success criteria (agree two or three before day one)
| # | Measure | Baseline (before start) | Target by go/no-go | How we will know |
|---|---|---|---|---|
| 1 | [e.g. At least X of Y pilots use it in a typical work week] | |||
| 2 | [e.g. Named workflow — close / forecast / deck — completed with shortcuts] | |||
| 3 | [e.g. IT signs off that permissions and rollback are acceptable] |
Track A — Pilot use
| Step | Owner (buyer) | Owner (SheetSpeed) | Date | Done? |
|---|---|---|---|---|
| Install works for the pilot group (allowlist or force-install on a small OU) | ||||
| Day-1 note sent to teammates | Champion | — | ||
| Weekly 30-minute check-in | Champion | SheetSpeed | weekly | |
| One-page weekly summary (what was tested, result, next week) | Champion | — | weekly | |
| Midpoint: criteria on track? If already met, do not wait out the clock | Both | Both |
Track B — Security, legal, procurement (start now)
| Step | Owner (buyer) | Owner (SheetSpeed) | Date | Done? |
|---|---|---|---|---|
| Trust pack sent (https://sheetspeed.agi-jarvis.com/trust/) | Champion | — | ||
| IT / security review; questions answered | IT | SheetSpeed | ||
| DPA / privacy / terms review if required | Legal | SheetSpeed | ||
| W-9 or vendor setup if required | Procurement | SheetSpeed | ||
| Confirm the buyer’s software-request path for a purchase of this size | Champion | — |
Track C — Decision
| Step | Owner | Date | Done? |
|---|---|---|---|
| Commercial next step drafted (even if the answer may be “stay on free Core / wait for billing”) | Both | before go/no-go | |
| Formal go/no-go against the written criteria | Economic buyer | ||
| If go: rollout plan and (when billing is open) commercial terms | Both | ||
| If no-go or pause: rollback (Block / remove force-install) and note why | IT + champion |
Stall red flags
Treat these as a prompt to ask, not as an automatic cancellation:
- No economic buyer named, or “I will forward this to my team” with no evidence it was sent
- Security pack not opened; questionnaire requested but the public pack was not read first
- Weekly check-in skipped twice, or no one in the pilot group has installed it after setup was confirmed
- Legal or procurement left until the last week of the pilot
- Success criteria still unwritten after day one
If engagement drops, ask once whether this is still a priority. Pause rather than chase a dead pilot.
Last updated 10 November 2026.