Enterprise tooling stack
Six studio tool layers with Runs, Install, and Bench tiers, plus selection criteria for instrumented, portable, gated tooling.
Exiid's studio tools are organized in six layers, not a flat logo list. Each entry is tier-labeled: Runs (live today), Install (default on Client Services), or Bench (evaluated fallback).
Who this is for
For: operators comparing Exiid to an agency tool dump or a single-vendor AI pitch.
Useful when: you need to know what we run, what we install, and what we chose not to default.
What must be true
Every tool category passes four selection tests:
- Instrumented: emits events we can warehouse and audit
- Gated: does not own the process (no lock-in traps)
- Portable: client can keep it if Exiid steps back
- Honest cost: priced for outcomes, not seat theater
Tools that fail Portable or Gated stay on Bench unless the engagement requires them.
Six layers
| Layer | Role | Phase |
|---|---|---|
| 01 Intelligence and research | Decode markets and jobs | RECON |
| 02 Product and platform | Ship instrumented products | RAID · Build |
| 03 Data and instrumentation | Cohort truth before automation | RAID · Launch/Scale |
| 04 Growth and GTM | Loops and lifecycle beyond SERP | RAID · Launch/Scale |
| 05 AI and orchestration | Agents on rails | RECON + RAID |
| 06 Ops, security, and delivery | Four-entity studio operations | Cross |
The live index with tier badges lives on Method.app.
Runs vs Install vs Bench
Runs means in production on Exiid or a live venture today, with a receipt (repo, venture, or memo).
Install means our default recommendation when we scope Client Services or a systems sprint.
Bench means evaluated and available, but not the default. Bench entries signal judgment, not gap.
Receipts
- Method.app: full tool grid with filters
- One operator, many agents: five-layer agent stack this taxonomy extends
- PostHog + wave3 bet: instrumentation on product decisions
- Brief Desk: Resend path and operator intake