Decision inputs for how enterprises begin with AI Fabrix — company size, systems, business problem, first assistant, expected outcomes, and time to first value. No technology dump; link persona paths for install and build.
Company size → typical first scope
| Size | Typical first scope | Governance note |
|---|---|---|
| Mid-market (hundreds of employees) | One Role Assistant, 2–3 systems, one business unit | Single certification track; executive sponsor + one integrator |
| Enterprise (multi-BU, multi-region) | One pilot BU, 3–5 systems, one role family | Dimensions and protection early; avoid global rollout day one |
| Group / multi-entity | Shared pattern on one entity, then template | Separate tenant or environment per entity where policy requires |
Systems in place → connect order
Connect systems in business-value order, not alphabetically:
| Priority | System type | Why first |
|---|---|---|
| 1 | System of record for pilot role | CRM for Sales Assistant; ERP/finance for Finance Assistant |
| 2 | Documents tied to that record | Contracts, proposals, policies linked via cross-system relationships |
| 3 | Identity and roles source | Align business roles and test subjects for governance verification |
| 4 | Adjacent systems | Ticketing, HR, or data warehouse — after first assistant proves value |
Integrators follow Create enterprise external system. Business readers link this page only as proof that an integrator path exists.
Business problem → recommended first assistant
| Business problem | Recommended first assistant | Proof in 30 days |
|---|---|---|
| Pipeline and CRM quality | Sales Assistant | Cleaner records; faster pipeline review |
| Proposal and delivery speed | Proposal or Project Assistant | Shorter cycle; visible risks |
| Invoice and spend control | Finance Assistant | Fewer validation exceptions |
| Customer retention risk | Customer Success Assistant | Health review with evidence |
| Master data drift | Data Quality Assistant | Stewardship tasks with audit trail |
| Compliance documentation | Compliance Assistant | Audit-ready artifact set |
See Best first use cases for industry defaults.
Expected outcomes → outcome library
Map each pilot to one primary outcome row in the Business outcome library. Avoid measuring everything in the first 30 days.
Time to first value → 30-day framing
Typical 30-day pilot shape (illustrative):
| Week | Focus |
|---|---|
| 1–2 | Tenant active; priority systems modeled; credentials and validation green |
| 2–3 | Protection and governance verification for pilot role scope |
| 3–4 | One Role Assistant in channel; operators run tasks with evidence |
| 4 | Review outcome KPIs; decide expand, adjust, or pause |
Human procurement POC detail: Proof-of-concept framework.
Persona paths after fit
| Persona | Where to go |
|---|---|
| Platform admin | Installation and onboarding → Foundation admin guides |
| Integrator / developer | Developer workstation setup |
| Executive sponsor | Adoption roadmap |
Suitable when (start pattern)
- One measurable outcome is named before integration starts
- Executive sponsor and integrator capacity are assigned
- Pilot scope fits one role family and certified data boundaries
Not suitable when (start pattern)
- "Connect everything" before any assistant is defined
- No operator to accept or correct task outcomes during pilot
- Success criteria are only user satisfaction scores with no business KPI
Limits
Timelines depend on system count, certification depth, and channel readiness. Tables above are planning frames, not implementation guarantees.