# Mutechs: Workforce Intelligence in Practice

> An illustrative Workforce Intelligence assessment, told as a story: what it saw in the security organization of Mutechs, a fictional composite, and what it handed leadership.

**Illustrative example. Mutechs is a fictional composite, and every figure on this page is built from it.**

This is the Markdown version of [the Mutechs case study](https://cybersn.com/case-studies/mutechs) on cybersn.com, written by CyberSN. On the page the story is told by scrolling, over an illustrative field of one dot per teammate.

## Mutechs had a roadmap, a security team of 31, and a question nobody could answer.

This is the story of one Workforce Intelligence assessment: what it saw, what it changed, and what it handed leadership.

## Part one: the Mutechs workforce

### The company: A SaaS company moving upmarket, fast.

Mutechs runs a multi-tenant platform that enterprise customers trust with sensitive data. It grew organically and by acquiring Lumify, whose cloud and identity stacks are still being folded in.

For its buyers, security stopped being a back-office concern. It became a condition of the deal.

### What leadership could see: Seven teams. On the org chart, every function had an owner.

Leadership, product security, cloud, detection and response, identity, GRC and security engineering. Reporting lines were clear and the headcount was approved.

### The workforce: 22 permanent employees and 9 contractors from 3 providers.

Workforce means everyone and everything doing the work: permanent employees, contractors, consultants, interns, service providers and AI agents.

At Mutechs, 29% of the security team came through providers.

### The question: The roadmap had seven priorities. Could this workforce execute them?

The CISO could feel the risk but could not see it precisely. Headcount and titles do not say who does which tasks, how deep that coverage goes, or where it stops matching the plan.

### The Workforce Intelligence view: The same 31 people, sorted by the work they actually do.

The assessment started from the work, not the titles. CyberSN recorded the tasks each person actually does and placed their time against the capabilities the roadmap needs.

### What it found: Six capabilities the roadmap depends on had low coverage.

Detection engineering, cloud guardrails, identity architecture, audit readiness, vulnerability management and acquisition integration.

The capability was real in every case. The depth behind its tasks was not.

### Who carries the work: Identity, the control plane for every system, ran almost entirely through one provider.

Three of the four people on the identity team came from a single provider, and the architect seat was empty. Nothing on the org chart showed it.

### How the team felt: The team trusted each other. They were less sure about the plan above them.

In the anonymous survey, team culture scored 4.4 out of 5 and company culture 3.3. Job satisfaction was lowest on the teams carrying the capabilities with the lowest coverage.

> "We hold it together ourselves; nobody is really planning for how long that lasts."
>
> Survey response (illustrative)

## Part two: from picture to plan

### The org chart, redrawn: The same org chart, with the work inside every box.

Each team's time by capability, with permanent employees and each provider's contractors side by side. The reporting structure had not changed. Now it showed the work.

Shown on the page: The org chart, with the work inside.

From the deliverable: [Workforce Intelligence Report](https://cybersn.com/case-studies/mutechs/deck-wi.html#capabilities).

### The record: Behind every box, the tasks each person actually does.

CyberSN recorded all 31 against its taxonomy. One of them, opened up: how the role's time splits across capabilities, then the responsibilities and tasks inside each.

Tasks are where gaps hide, and where AI changes the work.

Shown on the page: One teammate's job description.

### Strategy alignment: None of the seven priorities was fully supported by the workforce behind it.

Four were partly supported and three not yet. The strategy was sound; ownership and structure held it back. Each priority was rated on people (workforce) coverage, process, technology and metrics.

Shown on the page: Roadmap alignment.

From the deliverable: [Workforce Intelligence Report](https://cybersn.com/case-studies/mutechs/deck-wi.html#alignment).

### In the business's language: Every finding tied to an objective leadership already runs the business on.

Deal velocity, audit readiness, uptime and safe acquisitions. Nobody had to learn a new vocabulary to act on what the assessment found.

Shown on the page: Business objectives and the workforce signal behind each.

From the deliverable: [Workforce Intelligence Report](https://cybersn.com/case-studies/mutechs/deck-wi.html#business-objectives).

### Workforce risk: Fifteen workforce risks, named, ranked, and tied to the actions that retire them.

Ranked two critical, eight high and five medium in priority, each rated for severity and likelihood, with the places where one risk amplifies another called out.

Shown on the page: Fifteen risks by severity and likelihood.

From the deliverable: [Workforce Risk Table](https://cybersn.com/case-studies/mutechs/deck-risk.html#severity-likelihood).

### The plan: Seventeen recommendations, in order. Three start now.

Each one names the priority it serves, the risk it retires and the window it lands in. Two were already under way by the time the report was delivered.

Two of them automate work done by hand today: answering customer security questionnaires, and validating detections.

Shown on the page: Recommendations by horizon.

From the deliverable: [Workforce Intelligence Report](https://cybersn.com/case-studies/mutechs/deck-wi.html#recommendations).

### Funding the plan: Most of it needed no new budget.

Five of the eight funding paths needed no net-new budget: existing leadership time, contractor-to-permanent swaps, codified knowledge, a charter change and a renegotiated contract.

Each funding path arrived with its approval case already drafted.

Shown on the page: Each move's path through the funding gate.

From the deliverable: [Workforce Intelligence Report](https://cybersn.com/case-studies/mutechs/deck-wi.html#funding).

### The people: Every teammate got a growth path, and the organization got depth.

Only 19% of surveyed employees had a written career plan. Every teammate now has a one to three year plan, and read together the plans are one cross-training program behind the capabilities with low coverage.

Shown on the page: One teammate's plan, by role.

From the deliverable: [Training Plans](https://cybersn.com/case-studies/mutechs/deck-training.html#plan-customer-trust).

## So, what is Workforce Intelligence?

Mutechs' assessment covered security. The same method covers IT, because security depends on functions that sit inside IT and risk crosses between them.

Your strategy runs on tasks. Workforce Intelligence shows which cybersecurity and IT tasks it depends on, who and what is doing each one, and which have no coverage.

### Why now

Org charts and headcount reports count people, not tasks. AI changes work one task at a time, where they cannot see.

Capability coverage gaps (52%) outpace headcount gaps (48%). Source: [2026 SANS Cybersecurity Workforce Study](https://cybersn.com/resources/podcasts-and-videos/sans-2026-workforce-study).

### The value

- Find tasks with low or no coverage before an incident does.
- Tie each workforce move to a business metric.
- Walk into budget with a funding path, not a request.
- Decide where AI should take on work, task by task.

Start with a single assessment. Refresh it on your schedule.

## A real CISO, on the same work

> "[CyberSN] allowed me to show the gaps and unmet capability requirements in a way I simply couldn't before, while clearly representing what our talent was currently responsible for."
>
> Carraig Stanwyck, Fortune 200 CISO

[Read the Fortune 200 case study](https://cybersn.com/case-studies/fortune-200-ciso-workforce-transformation)

## The questions it answers

- Which tasks does our strategy depend on, and who and what is doing each one today?
- Which tasks have low or no coverage, and which business objective does that put at risk?
- What should change first, and how is each move funded?

The plan: 17 sequenced recommendations. Five of the eight funding paths needed no net-new budget: existing leadership time, contractor-to-permanent swaps, codified knowledge, a charter change and a renegotiated vendor contract.

## Is your team a Mutechs?

The page carries a six-question self-check for the reader's own team. Nothing is stored or sent anywhere.

1. Which capabilities does your roadmap depend on most? Pick up to eight. Cybersecurity: Security Operations, Incident Response, Security Analysis, Threat Intel, Cloud Security Engineering, Identity and Access Management (IAM), Application Security, DevSecOps, Vulnerability Threat Management, Security Engineering, Architecture and Design, Penetration Testing, Compliance, Risk, Privacy Analysis, Data Loss Prevention. IT: Infrastructure and Operations, Help Desk, Enterprise Architecture, Cloud Computing, Emerging Technology, IT Service Management, Solution Engineering, IT Compliance, Telecommunications. IT areas from the CyberSN taxonomy, and more.
2. How is each one covered? (Well covered, with room; Low coverage; Mostly contractors or providers; No coverage; Not sure)
3. How much of the work runs through contractors and providers? (Almost none; Under a quarter; A quarter to a half; More than half; Not sure)
4. Could you show which roadmap priority each team's work supports? (Yes, it's written down; Roughly; Not really; Not sure)
5. Is AI already doing part of this work? (Yes, and we know which tasks; Yes, but we could not say which tasks; Not yet; Not sure)
6. How many people on the team have a written career plan? (Most; Some; Few or none; Not sure)

This runs on what you believe. An assessment builds the same picture from the tasks your workforce actually does.

## The four deliverables, for when you want the detail

Everything in the story came from these. Open any of them, or skip them.

- [Workforce Intelligence Report](https://cybersn.com/case-studies/mutechs/deck-wi.html): Capabilities, roadmap alignment, sequenced recommendations and a funding path for each.
- [Workforce Risk Table](https://cybersn.com/case-studies/mutechs/deck-risk.html): Each workforce risk, rated and tied to the actions that retire it.
- [Workforce Happiness Survey](https://cybersn.com/case-studies/mutechs/deck-happiness.html): The anonymous retention signal beneath the org chart.
- [Individual Training Plans](https://cybersn.com/case-studies/mutechs/deck-training.html): A one to three year growth plan for every teammate.

Illustrative. Mutechs is a fictional composite.

## What would an assessment show about your team?

Talk through the tasks behind your priorities, no spreadsheets required.

[Book a 30-minute Discovery Call](https://cybersn.com/capability-mapping-and-workforce-intelligence#talk). Start with a single assessment, no long-term commitment required.

[Read how Workforce Intelligence works](https://cybersn.com/capability-mapping-and-workforce-intelligence)

---

Mutechs is a fictional composite. All Mutechs names, data and findings are illustrative.
