Basenull AI Ops · Workforce AI Literacy

AI literacy, measured.
Across every role in your company.

Role-tailored AI skills assessments. Eight axes across three domains — Execution, Cognitive, Governance. A team spider chart your CHRO can put in front of the board.

Sample team aggregate · Sales department
Prompting71/100Tools64/100Workflow58/100Leverage41/100Framing49/100Evaluation53/100Hygiene28/100Judgment56/100
Sales scores 28/100 on Data Hygiene — your reps are pasting customer data into a public web chatbot. The kind of signal you want to see before AppSec does.

What we measure

Eight axes grouped into three domains — Execution, Cognitive, Governance. Calibrated for the way AI fluency actually differentiates strong operators from heavy users.

Execution
4 axes

What you do with AI day-to-day — how cleanly you communicate, which tools you reach for, how deeply AI is woven into your work, and whether you turn one-off use into reusable assets your teammates can adopt.

Prompting & Context

How clearly you communicate intent, and what context (files, examples, constraints) you put in front of the model.

Tool & Agent Use

How well you choose between an inline assistant, a chat, an agent that can run unattended, and combinations of these for the task at hand.

Workflow Integration

How thoroughly AI is woven into your day-to-day work — and whether the resulting output is good, not just abundant.

Leverage & Reusability

Whether your AI work multiplies — reusable prompts, templates, agents, snippets, internal docs that uplift teammates and compound over time.

Cognitive
2 axes

How you think about AI as a system — recognizing which problems suit AI in the first place, decomposing them well, and rigorously verifying outputs before acting on them.

Problem Framing

Whether you can identify which problems are AI-appropriate, decompose ambiguous work, and structure tasks for augmentation rather than replacement.

Evaluation & Verification

How well you spot-check individual outputs and — at higher levels — build systematic evals/regressions for repeated AI workflows.

Governance
2 axes

What keeps you and your company safe — handling data correctly when you do use AI, and exercising judgment about when AI is the wrong tool entirely.

Data Hygiene

How safely you handle data when you do use AI — what you redact, which deployment you choose, what trains on your inputs.

Human Judgment

Whether you know when NOT to use AI — when escalation, expert review, or human accountability is non-negotiable, even when AI could produce something plausible.

How it works

Step 1
Take the assessment

Pick a role. Answer 11 questions — multiple-choice, short-form, and one longer scenario — across 8 axes. Designed to feel like a thoughtful coaching session, not a gotcha test.

Step 2
See your spider chart

Per-axis scores, an overall number, and 3 paragraphs of personalized feedback grounded in your actual answers. Shareable result URL.

Step 3
Deploy to your team

Subscribe → invite your team via one link → see a team aggregate spider chart with role breakdowns. The artifact your CHRO walks into the board meeting with.

Pricing

Free
$0
forever
  • · Individual self-assessment
  • · All 3 roles
  • · Spider chart + 3-paragraph feedback
  • · Shareable result URL
  • · Basenull-branded results
Take the assessment
Pro
$99
per month
  • · Up to 25 employees
  • · Team dashboard with aggregate spider chart
  • · Per-role breakdowns
  • · Roster + history
  • · Unbranded results
  • · CSV export
Subscribe Pro
Enterprise
Talk to sales
100+ employees
  • · Unlimited employees
  • · SAML / SSO
  • · Custom roles & axes
  • · Audit log
  • · Dedicated CSM
  • · DPA / BAA available
Talk to sales

Why measurement, not training?

Pluralsight, O'Reilly, LinkedIn Learning, Coursera all sell training. Your L&D team needs both — but measurement is the gap. Without it, "AI literacy" on the corporate scorecard is vibes. With it, it's a board-grade artifact you can update quarter-over-quarter.

Why role-tailored?

A sales rep's AI workflow is fundamentally different from a software engineer's. Asking a CS manager about transformer architecture is asking the wrong question. Asking a developer about cold-email frameworks is the wrong question. Each role's assessment is tuned for that workflow.

Why a spider chart?

Eight axes grouped into three domains. Execution (Prompting & Context, Tool & Agent Use, Workflow Integration, Leverage & Reusability) is what you do day-to-day. Cognitive (Problem Framing, Evaluation & Verification) is how you think about AI as a system. Governance (Data Hygiene, Human Judgment) is what keeps you safe. The shape of the chart tells the story before any number does.