Score a team or company on the 10-line AI-native scorecard and get a 90-day plan. Each line is scored 0 to 3 by the user: a named AI owner with hours for it, department reps meeting every 2 weeks, a pinned 1-page AI policy, monthly live training on their own workflows, training in 3 tracks, a recorded session library checked monthly, a use-case list ranked by hours saved, wins posted company-wide, weekly blocked AI time, and hours saved measured and shown to leadership. Ask the user for each of the 10 scores first (the input schema says what 0, 1, 2 and 3 mean on each line); never guess one. Returns the total out of 30, the band (You bought seats, A start no engine, Almost there, AI native), the 3 first moves, a 90-day plan in 3 months with each step marked start, tighten or keep, the AI champion role card, and a share_url to a public result page. Nothing is stored; the link holds only the 10 numbers and the optional team name.
View input schema
{
"type": "object",
"properties": {
"scores": {
"type": "object",
"description": "The team's 0 to 3 score on each of the 10 lines. Ask the user for each line; never guess a score they did not give.",
"properties": {
"owner": {
"type": "integer",
"minimum": 0,
"maximum": 3,
"description": "One named person owns AI adoption, with hours for it in their week. 0: Nobody owns it. Whoever is keen helps when they can. 1: Someone is the go-to person, but it is a favour on top of their job. 2: A person is named, but the hours for it are not in their week. 3: A named owner has protected hours every week, and everyone knows who it is."
},
"reps": {
"type": "integer",
"minimum": 0,
"maximum": 3,
"description": "One person from each department meets every 2 weeks. 0: Departments do not talk about AI with each other. 1: People swap tips in a chat channel now and then. 2: There are department reps, but they meet when someone remembers. 3: Each department has a rep, and the reps meet every 2 weeks with notes."
},
"policy": {
"type": "integer",
"minimum": 0,
"maximum": 3,
"description": "A 1-page AI policy is pinned where people work. 0: There is no policy. People guess what is allowed. 1: There are rules, but they live in an email or in someone's head. 2: A policy exists, but it is long or hard to find. 3: One page says what data may go where and which tools are approved, and it is pinned in the main channel."
},
"training": {
"type": "integer",
"minimum": 0,
"maximum": 3,
"description": "Live training every month, on your own workflows. 0: No training. People learn from videos on their own. 1: There was a kickoff session, and nothing since. 2: Training happens a few times a year, or uses generic examples. 3: Every month there is a live session built on a real task from your own team."
},
"tracks": {
"type": "integer",
"minimum": 0,
"maximum": 3,
"description": "Training comes in 3 tracks: starters, daily users and builders. 0: Everyone gets the same thing, or nothing. 1: There is one level, pitched at beginners. 2: There are 2 levels, or the 3 tracks exist on paper only. 3: Starters, daily users and builders each have their own track and their own sessions."
},
"library": {
"type": "integer",
"minimum": 0,
"maximum": 3,
"description": "Sessions are recorded into a library that is checked every month. 0: Nothing is recorded. 1: Some recordings exist in someone's drive. 2: There is a shared library, but old or broken material stays in it. 3: Every session goes into one library, and each month someone removes what is out of date."
},
"backlog": {
"type": "integer",
"minimum": 0,
"maximum": 3,
"description": "A list of AI use cases, ranked by hours saved. 0: Ideas come and go in meetings. 1: There is a list, but nobody ranks it. 2: The list is ranked by gut feel or by who asked loudest. 3: Every idea has an hours-saved estimate, and the list is ranked by it every 2 weeks."
},
"wins": {
"type": "integer",
"minimum": 0,
"maximum": 3,
"description": "Wins are posted where the whole company sees them. 0: Wins stay inside the team that made them. 1: A win gets mentioned now and then in a meeting. 2: Wins are posted, but without the time saved or how it was done. 3: Each win is posted company-wide with the hours saved and the steps, so others can copy it."
},
"focus_time": {
"type": "integer",
"minimum": 0,
"maximum": 3,
"description": "Time for AI work is blocked in calendars every week. 0: AI work happens only when the day is quiet, which is never. 1: Some people block time for it on their own. 2: Blocked time is encouraged, but meetings take it back. 3: Everyone has a weekly block for AI work, and managers protect it."
},
"hours_saved": {
"type": "integer",
"minimum": 0,
"maximum": 3,
"description": "Hours saved are measured and shown to leadership. 0: Nobody knows what AI saves. 1: There are stories, but no numbers. 2: Some workflows are timed, but the numbers are not shown upward. 3: Hours saved are measured before and after, and leadership sees the total every month."
}
},
"required": [
"owner",
"reps",
"policy",
"training",
"tracks",
"library",
"backlog",
"wins",
"focus_time",
"hours_saved"
],
"additionalProperties": false
},
"team_name": {
"type": "string",
"maxLength": 60,
"description": "Optional team or company name shown on the result and in the share link. Leave it out to keep the link anonymous."
}
},
"required": [
"scores"
],
"additionalProperties": false
}