Guide ยท Columbus, Ohio

Your team has Claude licenses and nobody uses them. Why, and what fixes it?

Licenses go unused when people are handed a tool but not a task. They open a blank chat, don't know what to ask, can't connect Claude to the systems they work in, and go back to what they know. The fix is to choose one workflow, set Claude up around it for the people who do that work, and name someone to own it.

Claude Desktop Enablement

What does an unused license usually mean?

Rarely that people are resistant. More often, one or more of four things is missing:

  • A starting point. Nobody said which task to try first, so people try something vague, get a vague answer, and stop.
  • Reference material. Claude doesn't know your terminology, your templates or how your team does things unless it has been given them.
  • A connection to the systems where the work happens. If people have to copy and paste between Claude and everything else, it's easier not to bother.
  • An owner. Nobody is responsible for keeping the setup current, so even a good start drifts.

Is it a training problem?

Partly. Training teaches people how to use a tool, but a general session on writing prompts doesn't change what Claude knows about your work. It helps most when it's role-based and built on a setup made for that role, so people practice on the thing they'll actually use.

That's why we treat training as one part of a rollout instead of the whole of it.

How do we pick the first workflow?

Look for work that is repetitive, painful for a specific team, and easy to recognize as done well. Ask the people who do the work, not only their managers, because they know where the time goes.

If you have several candidates and no clear winner, the AI Audit & Roadmap has the owners of each workflow score every opportunity on value and feasibility, then sequences the results into a quarterly roadmap.

What should a first setup include?

For one workflow and the people who do it, a first setup covers five things:

  • Claude Desktop configured consistently for the people in scope, agreed with your IT team.
  • A project per team or role that holds the instructions and reference material they need, so good context stops living in one person's chat history.
  • Custom skills, which are saved instructions for the tasks a role repeats, written with the people who do the job.
  • Connections to your systems through MCP (Model Context Protocol), an open standard for linking AI tools to other software, limited to what the workflow needs.
  • A short data-handling guide saying what can go into Claude, what can't, and who to ask when unsure.

Who should own it afterward?

A named person inside your organization, with documentation and training so they can keep it running without outside help. A setup nobody owns slowly goes stale, and people quietly stop using it.

If you want hands-on help with the next workflows as well, an Enablement Partner retainer covers that.

What if we don't know where to start?

Try the self-assessment on the homepage to see which of these problems sound familiar, or begin with a Half-Day Strategy Workshop to choose the first workflow with the people who'll use it. If you'd rather talk it through, start a conversation and you'll get an honest read on whether we're the right fit.

Keep reading

Claude Desktop Enablement

How we set Claude up around one workflow and hand it to an internal owner.

How to roll out Claude to a team

One team, one workflow, a real pilot, and a named owner.

Start with one win. Build a capability that lasts.

Describe what you're trying to figure out. You'll get an honest read on whether this is the right fit, and if it isn't, a pointer to who is.

Prefer email? hello@sunburydigital.com

Takes about two minutes. No pitch deck, no sales sequence.

Replies within one business day. The first conversation is a call, not a pitch.