30-day company brain rollout plan
Week-by-week plan for pilots — or the same timeline with Morrow driving setup while your team stays on product.
Week 1 — Connect and scope
- Name pilot squad (5–15 people) and one executive sponsor.
- Connect chat, issue tracker, repo, and calendar.
- Define off-limits data (HR, M&A, etc.).
- Optional: Morrow-led working session instead of internal hack days.
Week 2 — Memory and permissions
- Create project rooms aligned to real initiatives.1
- Verify agents inherit correct visibility.
- Turn on morning report for the pilot channel.
Week 3 — Agents with guardrails
- Enable one or two roles (e.g. product + support).
- Run three approval workflows end-to-end.
- Collect friction log from pilot users.
Week 4 — Measure and decide
- Metrics: prep time for standups, repeated questions in Slack, ticket quality.
- Compare to McKinsey-style value levers for gen AI — focus on workflow time, not novelty.[[mckinseyGenAi2024]]
- Go/no-go for wider rollout or Enterprise hardening.
Want the plan executed, not just written? We run weeks 1–3 with your admin team and hand off a working brain in week 4.
Quick answers
- What is a realistic company brain pilot timeline?
- Four weeks: connect tools, configure memory, run agents with approvals, then measure and expand.
Sources
- 1.
- 2.The state of AI in early 2024: Gen AI adoption spikes and starts to generate value
McKinsey & Company, 2024.
