TL;DR: The expansion motion: a 5–50 person team accumulates a shelf of bespoke tools — each with a different handful of users — and pays one consumption bill plus a flat org plan instead of twenty seat-licenses and two stitched vendors. The metric that matters: cells shared with ≥1 other person, and weekly actives who didn’t build the cell.
A week in the life
- Monday: Ops opens the invoice reconciler (FastAPI, built by an analyst + agent). Three users. Slept all weekend; woke in time for the click.
- Tuesday: Growth demos a prototype to three colleagues. Link, work login, clicks. No staging environment was harmed.
- Wednesday: Finance checks the one-metric dashboard. Data owns the cell; finance just opens it — weekly actives who didn’t build the cell, the thesis working.
- Thursday: The sprint tracker shaped like this team’s sprints (not Jira’s) gets shared with two new joiners — a group-membership change, not a provisioning ticket.
- Friday: Nobody thinks about any of this. That’s the product.
Why this team converts (the money question, answered)
Consumption is the on-ramp and the floor; the org plan carries revenue. This team buys: org SSO (SAML/OIDC), group-based sharing, per-cell access logs, custom base images with private packages, internal network reachability. Flat fee, because metering their tiny compute would price the plan below its value — small software is by definition low-consumption, and we’re honest about that. If teams won’t pay a flat org fee for identity and environment, this is a small business; design partnerships test exactly that.
What IT needs to say yes
Shadow IT at 30–40% of enterprise spend (Gartner) is largely this team, moving faster than tickets allow. Sanction beats prohibition when the platform offers: SSO enforcement with SCIM-shaped deprovisioning (leaver loses all twenty tools at once), per-cell access logs (who opened what, when), egress rules and spend caps per cell, ownership transfer so tools survive authors, and region choice for residency posture. The membrane and front door pages are the technical companions to this conversation.
Scenarios by function
| Team | Tool | Shared with | Why AgentCell fits |
|---|---|---|---|
| Ops | Invoice reconciler | 3 analysts | Private packages, internal DB egress, asleep weekends |
| Product | Sprint tracker | 8 + joiners via group | Group sharing, survives author leaving |
| Finance | Metric dashboard | 4 execs | Access log for the “who saw revenue” question |
| Growth | Click-through prototype | 3 colleagues | Sleep/wake, public-link-or-org choice |
| Data | Streamlit explorer | 5 stakeholders | Python cell, per-cell datastore |
Explicit non-fits (say them early)
Consumer apps with real user bases, horizontal-scale needs, regulated production workloads, government/PSU, own-metal self-host. If that’s the workload, dedicated platforms win and we say so — credibility with IT starts with knowing what we’re not.
FAQ
Who holds the card — individual, team lead, procurement? Unknown industry-wide; our sequencing assumes personal card → team card → platform deal as sprawl accumulates. Discovery tests it.
How do we migrate twenty tools?
Audience order: shared-daily first, monthly second, dormant last (or let them go — deploys alone are vanity). Folder → deploy → re-share per tool; see the Firebase migration playbook for the shape.
What proves it’s working? Not deploy counts: cells shared with ≥1 other person, and weekly active users who didn’t build the cell.
Running the team on bespoke tools already? Give them a permanent home. Deploy now.