AI adoption score
Read your organization's AI adoption score and understand how it's calculated
The AI adoption score is a number from 0 to 100 that shows how often, how deeply and how broadly your organization uses Hull. Engineering leads use it to track rollout over time and spot where adoption is lagging.
Find the score
- Open your organization at app.withhull.com.
- Click Usage in the sidebar.
- The AI Adoption Score card sits at the top of the AI usage view.
The card shows the current score, the score for each dimension, and a Trend Over Time chart. The chart follows the Period you pick in the side panel. Click a dimension to open its detail panel with improvement tips.
The score appears when you're viewing a single organization, not the combined view across sub-organizations.
The three dimensions
| Dimension | Points | Question it answers |
|---|---|---|
| Frequency | 40 | How often do people use Hull? |
| Depth | 40 | How much is Hull part of real development work? |
| Coverage | 20 | How broadly is Hull used across tools and the week? |
Frequency (40 points)
Four signals, worth 10 points each:
| Signal | Full points at |
|---|---|
| Agent interactions per day | 10 |
| Accepted autocomplete suggestions per day | 20 |
| Cloud agent sessions per day | 1 |
| Code review runs per day | 1 |
Depth (40 points)
Three signals, worth about 13.3 points each:
| Signal | Full points at |
|---|---|
| Agent queries per hour worked (daily interactions over an 8-hour day) | 1 |
| Suggestion acceptance rate | 50% |
| Multi-agent chains: days where a person used the agent, a cloud agent and code review | 1 |
Suggestion acceptance currently uses a fixed estimate rather than measured data.
Coverage (20 points)
Four signals over the last 7 days, worth 5 points each:
- Share of days with any Hull activity
- Whether the person used at least 2 kinds of agent (agent, autocomplete, cloud agent, code review)
- Whether the person used all 4
- How many different weekdays had activity
How the score is calculated
- Each signal is scored per person and capped at its full-points value, so one heavy user can't inflate the score.
- The organization score for a day is the average across members who had any activity that day. Members with no activity that day don't count toward the average.
- Daily scores are plotted over the selected period.
Reading the score
- Watch the trend, not the number. Direction over weeks tells you more than a single day.
- Find the weak dimension. Low Frequency means Hull isn't a daily habit yet. Low Depth means people aren't chaining agents into real workflows. Low Coverage means people use only one tool or only some days.
- Expect normal dips around holidays, leave and new hires onboarding.
- Look at the spread. Where available, Individual User Scores show whether a few power users carry the average.
Use the score to guide enablement, not to evaluate individuals.