Innovation Overview
What leadership sees: who is building, what gets approved, and whether shared tools track with better results by role.
Vision preview — every number on this page is illustrative until tools exist and metrics are wired up
People on the platform
412
BC 96 · SAM 118 · SBA 84 · SBC 72 · STC 42
Active builders
131
32% of staff · most tools stay private
Tools created
318
201 private · 75 team · 42 submitted
Approved & shared
17
3 flagged as product candidates
From private tool to company product
Tools built318
Submitted for approval42
Approved & shared17
Product candidates3
Private and team tools are not counted as "lost" — keeping a tool private is a valid outcome.
Results by role: average lift after adopting a shared tool
| Role | Headline KPI | Avg change since adoption | Matched peers, no tool |
|---|---|---|---|
| BC | Sit rate | +4 pts | +1 pt |
| SAM | 44s per 10 SITs | +0.5 | +0.1 |
| SBA | Go rate | +5 pts | +1 pt |
| SBC | Job Billing Average | +14 hrs | +3 hrs |
| STC | Illustration turnaround | −0.7 days | −0.1 days |
Each user compared with peers who started at a similar level. Tools appear only after 10+ users and 2+ periods. Correlation, not proof.
Build Credits issued
184,500
Platform resources only · no cash value
Client financials in the Vault
1,204
All inside ISI · zero external uploads
Competing tools for the same job
6 pairs
Users choose · builders ranked on adoption, not outcomes
How results are measured
Lift, not levels
A tool is credited with how much its users improve on their own baseline, so a struggling colleague who improves helps the tool's number. No tool ever shows a raw performance level.
Matched peers
Each user is compared with peers who started at a similar level. Attracting strong or weak users doesn't move a tool's result.
Minimum cohort
Nothing is shown until a tool has 10+ active users and 2+ periods of data. One person's bad month cannot define a tool.
Builders see counts only
Builders see how many use their tool and the average lift. Who uses it, and how they perform, stays with the user and their director.
Recognition on adoption
Top Builders and builder credits are based on how many colleagues use a tool and keep using it, never on those colleagues' results.
Your result is yours
A KPI belongs to the person, not the app. Improving your own numbers earns credits, whichever tool you use or none at all.
Creativity at the Edge.
Control at the Core.
Every role can experiment freely, privately, on their own results. ISI controls the environment everything runs in.
ISI controls
- Identity
- Data access
- AI models
- Production deployment
- Security
- Application distribution
- Company intellectual property
- Client financial data (Vault)