DEV Community: Todd 🌐 Fractional CTO

Are Your AI Adoption Numbers Wrong?

Todd 🌐 Fractional CTO — Tue, 22 Sep 2026 14:00:00 +0000

Why license dashboards hide what your team is really doing with AI

A team lead checks the dashboard, sees that 40 percent of seats are active, and calls that the adoption number. It feels precise. It usually is not.

Here is what the seat count cannot see. Shadow AI research in 2026 found that 65 percent of employees reach for public AI tools instead of the ones their company approved. Plenty of them are loading real work into those tools, including customer records, financial details, and internal strategy documents. The official dashboard registers none of it.

So the 40 percent is wrong in two directions at once. Some of those active seats belong to people who open the tool, poke around, and accomplish almost nothing. Meanwhile, a chunk of the people counted as non-adopters are running careful, repeatable workflows on personal accounts you cannot audit. Real usage is higher than you think and messier than you hoped.

What the dashboard actually measures

License activity tells you who logged in. It says nothing about who built something useful.

That gap matters because the two groups need opposite things. The person with an active seat and no output needs help finding a first real use. The person running a private workflow on a personal account needs that work brought into the open before it creates a problem. Treat them as one number and you serve neither.

The legal and reputational exposure sits with the second group. When someone pastes a client contract into a consumer chatbot, the data leaves your control and the record of it leaving never reaches you. You find out when something breaks, not before.

Why the security conversation stalls

The usual response is a policy memo. Stop using unapproved tools. Stick to the approved stack. Compliance signs off, the memo goes out, and very little changes.

It stalls because the memo asks people to give up something that works without handing them anything better. The marketer drafting campaigns in a personal account is faster with it than without. Telling that person to stop, with no replacement, asks them to choose between the rule and their own output. Most people just choose their output.

This is where I see leaders lose the thread. They frame a workflow problem as a discipline problem. Discipline problems get solved with rules. Workflow problems get solved with better workflows.

The real issue is consistency

Picture ten people on a team, each running a separate unofficial AI setup. Different tools, different prompts, and different standards for what good looks like. Nobody can see anyone else’s process, so nobody can borrow it.

That fragmentation costs more than any single data leak. There is no shared quality bar, so output swings wildly between people. There is no repeatable system, so a strong method one person discovers stays trapped with that person. There is nothing common to improve on, which means none of the private wins ever compound. You have ten experiments and zero shared progress.

A team that shares one workflow gets the opposite. A prompt that works gets refined by the next person who uses it. A weak output gets caught against a known standard. The system improves because everyone feeds the same system.

Build the version worth switching to

The fix starts by accepting what the data already shows. People want these tools and will use them with or without permission. The job is to make the sanctioned path the obvious choice.

That means building an official workflow that beats the personal one on the merits. It should run faster on the tasks people actually do, come stocked with prompts and templates tuned to your work rather than generic ones, and connect to your real context so the output needs less cleanup. When the approved option genuinely wins, the personal accounts empty out on their own, and the data risk drops as a side effect rather than a fight.

Start by finding the people already running good private workflows. They have done the hard part for you. Ask what they built, why it works, and what made them skip the approved tool. Their answers are the spec for the system everyone should be using.

The number on your dashboard was never the real story. The real story is whether your team shares a way of working that gets sharper every week, or ten separate ones that go nowhere. One of those scales, and you get to decide which.

. . .

Want to save hours each week by turning work into repeatable AI workflows?

The Fortune 100 AI Skills Library™ includes plug-and-play prompts built to save leaders time and money. Copy, paste, and edit in 60 seconds, then apply them across planning, execution, and reporting.

How to Decide Which AI Platform Gets Which Creative Work

Todd 🌐 Fractional CTO — Tue, 15 Sep 2026 14:00:00 +0000

A decision method for marketing teams who keep buying tools instead of making the call

You already pay for three AI platforms. One of them is open in a tab right now, and that tab is about to catch the next campaign brief for no reason other than it was closest. Nobody chose it. Proximity chose it.

Do that a few dozen times a week across a team and you get exactly what you’d expect. Output that swings in quality, a vague sense that the tools are inconsistent, and a running argument about whether to buy a better one. Skip that argument. Decide which tool you already own does which job, and write it down where everyone can see it.

You see it in the work. A landing page that reads sharp one week and flat the next, same writer, same brief, different tool. A deck that looks polished until someone clicks through and half the structure doesn’t hold. The team chalks it up to the AI being unreliable. The AI was fine. The routing was random.

Stop asking what each platform is good at

The marketing pages already answered that, and the answer is “everything.” More useful is knowing how each one fails, because failure is consistent and you can build around it.

Run one real task through all three and the differences land fast. Claude produces visually complete work with genuine design instinct, and will happily overcook something you wanted fast and rough. ChatGPT reaches for the generic and hands back pieces that look right and don’t actually function. Gemini gets it done and stops at functional, skipping the refinement that makes work feel finished.

None of that stays in the design lane. The platform that over-polishes a logo over-polishes your positioning. The one defaulting to generic layouts defaults to generic copy. Ask the generic one for a competitor teardown and you get a tidy summary with no teeth. Ask the one with instinct and you get a read you can actually use, or argue with. Pick the strength you want and you inherit the blind spot attached to it.

Decide which failure you can eat

Here’s the whole method. Take the work your team does most, and ask which failure you can live with on it.

High-volume social copy? A generic first draft is fine, because someone edits it anyway, and speed beats polish. Client-facing campaign concepts? You can’t ship something that looks right and breaks on contact, so you pay for the stronger instinct even when it runs slower. The middle stuff, research synthesis, recaps, drafts you’ll rewrite regardless, goes wherever, because your edit covers the gap.

Put it on one page

The map is boring to look at, which is the point. Concepts, mockups, and positioning go to the platform with instinct. Volume copy, recaps, and first drafts go to the fast one. Everything you rework anyway goes wherever’s convenient. One page, listing the work, the tool, and the reason, because the reason is what lets the next person fix the map when a model changes under them.

What you get for the trouble

Better output from the same people, the same subscriptions, the same prompts, because each task lands on the tool least likely to wreck it. The weekly tool argument dies, since the call already lives on the page. New hires inherit it on day one instead of learning it the hard way over a quarter.

That’s the trade. Ten minutes of testing and one page against a quarter of uneven work and a subscription you were about to buy for no reason. Make the call once. Then go do the work.

. . .

Want to save hours each week by turning work into repeatable AI workflows?

4 Ways Team Leads Can Model AI Use to Drive Adoption

Todd 🌐 Fractional CTO — Tue, 08 Sep 2026 14:00:00 +0000

The visible habits that drive AI adoption faster than any all-hands announcement

When managers actively model AI use, their teams report a 17-point lift in how much they value AI, a 22-point lift in critical thinking about it, and a 30-point lift in trust in agentic systems. Those figures come from a Microsoft People Science study of 1,800 workers, cited in the 2026 Work Trend Index. The same report found only one in four employees say their leadership is clearly and consistently aligned on AI.

Most team leads have already done the obvious work. They approved the tools. They sat through the kickoff and sent the all-hands update. What they have not done is change how they work in front of the people watching them.

Executive sponsorship tells a team that AI matters. Modeling shows them what working that way looks like at their own level. That gap is most of what separates real AI adoption from a stalled rollout. Here are four habits that make your AI use visible without a single announcement.

1. Run Your Briefings With AI in the Room

Most leads prepare the summary, the analysis, or the plan in advance, then walk in with a clean result. The team sees the output and learns nothing about how it came together.

Open the tool live instead. Start the briefing by building the first pass while everyone watches. Type the prompt in front of them. Let the draft come back rough, then refine it on the screen.

What the team picks up is the part that usually stays hidden. They see how you frame a question, where you push back on the model, and how many passes a decent answer actually takes. That is the reference point they have been missing.

Pick a recurring, low-stakes briefing to start. A weekly status roundup or a project recap works well, since the cost of a clumsy first attempt is close to zero. Once the rhythm feels natural, bring it into higher-stakes rooms where the modeling matters more.

2. Share the Prompt and First Output on High-Stakes Work

When you send around a polished deliverable, you teach the team that good AI work arrives finished. They have no idea what it took to get there, so they assume their own messy drafts mean they are doing it wrong.

Attach the prompt and the raw first output next to the final version. A short note is enough. Show what you asked for, what the model gave back, and what you changed before it was ready to ship.

That mirrors how careful AI users already work. In the Work Trend Index, 86% said they treat AI output as a starting point and stay responsible for the thinking. Sharing your own process gives the team a working template they can copy on their own deliverables.

Save this habit for work that carries real weight. A board summary, a customer proposal, a technical decision document. The higher the stakes, the more your visible process reassures people.

3. Say It Out Loud When AI Gets Something Wrong

The instinct is to fix a bad AI answer without comment and move on. That habit hides the single most valuable skill you can model, which is judgment.

When the model invents a number, misreads the context, or confidently produces something off, name it in the moment. Tell the team what looked wrong and how you caught it. Walk them through the check you ran before you trusted the output.

Doing this in the open reframes what competence with AI means, away from clean first-try answers and toward knowing when to push back. Your team learns that catching the model’s mistakes is the job, and that the people who do it well are the ones worth following.

Quality control of AI output and critical thinking now rank as the two human skills professionals say matter most as AI takes on more work. You cannot lecture those skills into a team. You can show them every time you question an answer out loud.

4. Use AI Live During Team Reviews

Plenty of leads use AI heavily and still do all of it offstage. The team never sees the tool touch the work that gets reviewed, so they file it under personal productivity rather than real decision-making.

Bring it into the review itself. During a roadmap discussion or a design critique, pull up the model and pressure-test an assumption in front of everyone. Ask it to argue the opposite case. Have it surface the risks nobody in the room has raised yet.

You want AI participating in the decisions that count, while a group of people watch and weigh in. That positions the tool as something you reason with, rather than a shortcut you hide. Used this way, it raises the quality of the conversation instead of replacing it.

Start with reviews where the team already trusts your judgment. When they see you treat AI as another voice in the room, one you still overrule when it earns it, they start doing the same in their own work.

The Reference Point Only You Can Set

Every one of these habits does the same work. It gives your team a picture of what working with AI looks like at their level, performed by someone whose judgment they already respect.

Tools and training tell people AI is available. Your behavior tells them it is safe, expected, and worth getting good at. That signal carries further than any policy, because people copy what their lead does long before they act on what their lead says.

You do not need a new initiative to start. Pick one of these four for next week and let the team watch you work. The lift in trust, thinking, and value comes from watching you do the work, which lands harder than anything you could announce.

. . .

Want to save hours each week by turning work into repeatable AI workflows?

Why You Should Stop Trying to Be a Better Prompter

Todd 🌐 Fractional CTO — Tue, 01 Sep 2026 14:00:00 +0000

Framing the problem now matters more than crafting the prompt

In 2024, the person on your team who wrote the cleanest prompts got the best output. They knew the role-play openers, the few-shot examples, the formatting tricks that nudged a model toward a usable answer. But those tricks eventually stopped working because the models got better at the thing the tricks were compensating for.

For example, “think step by step” gave older models a measurable bump because their default reasoning ran shallow. Today’s reasoning models do that work internally whether you ask for it or not.

Andrej Karpathy started using “context engineering” in place of “prompt engineering,” and the change in language tracks a real change in where the value sits. Here is where most teams are stuck. They are still running training built for the 2024 version of the problem, the prompt libraries and magic-phrase cheat sheets and internal workshops on how to talk to ChatGPT. All of it sharpens a skill whose return shrinks every quarter.

The question worth handing AI

The more productive structure in 2026 reads less like an instruction and more like a brief. How might we achieve this objective, given these constraints?

That framing does three things a polished prompt does not.

1) It generates options rather than one rigid answer. Ask for the answer and you get the answer. Ask how you might get there and you get three or four routes worth comparing, which is what you actually want when the path is not obvious yet.

2) It forces real constraints into the room. Budget, timeline, the headcount you actually have rather than the one you’d staff in a perfect world. A prompt tuned for the cleanest possible output tends to assume that perfect world exists. A well-framed problem carries the friction with it.

3) It keeps AI in strategist mode before it drops into executor mode. The fastest way to get a confident, wrong answer is to hand a model a task before anyone has agreed on the objective. Framing first, execution second. The order matters more than the wording ever did.

What this changes for a team lead

If you run a function, the implication lands close to home. A team of skilled prompters scales only as far as its most patient member can sustain. Real leverage shows up when the whole team can hand AI a well-framed problem and judge what comes back.

Those are two separate skills, and the second is the rarer one. Framing a problem well means stating the objective plainly and naming the constraints honestly. Evaluating the output means knowing enough about the domain to catch where the model is confidently off. Neither skill lives in a prompt library. Both of them carry across every model you will ever use, which is the part that makes them worth building.

I have watched capable teams pour months into prompt training and come out with people who can coax a decent paragraph out of a chatbot. Useful, briefly. Then the model updates, the old tricks stop landing, and the training starts over. The teams that invested in problem-framing and output evaluation never had to rerun anything. Their skill survived the version bump.

Make it the default, not a personal habit

Most people reading this already frame problems this way on their best days. The work now is moving it from a personal habit to the team’s default.

That shows up in what you ask for in a meeting. When someone brings you an AI result, the question to ask is what objective and constraints they handed the model, and how they checked what came back. Ask that consistently and people start framing before they type, because they know the framing is what you will inspect.

Prompt skill was always going to be temporary. It was a feature of one particular moment in the technology, and that moment is closing. The skill underneath it, defining a problem clearly enough that a capable system can solve it, has been valuable for as long as people have delegated work. AI just raised the price of doing it badly.

. . .

Want to save hours each week by turning work into repeatable AI workflows?

More Connections Won’t Make Your AI Smarter

Todd 🌐 Fractional CTO — Tue, 25 Aug 2026 14:00:00 +0000

Why a leaner tool stack outperforms a maximally connected one, and how to trim yours

In June, David Cramer did something that looks like a mistake. He nearly halved the number of tools his company’s AI could see at once.

Sentry’s AI agent used to see 14 tools every time it ran. Cramer’s team cut that default down to 8 and tucked the rest behind a layer the agent only reaches for when a task actually needs them.

The agent did not get weaker. It got sharper, with fewer wrong calls, faster responses, and more reliable output.

Most mid-market teams are running in the opposite direction. Marketing and ops leads are wiring their AI into Salesforce, HubSpot, Slack, the CMS, the analytics dashboard, and the project tracker, working from the idea that more connections means more capability. The research keeps landing on the other side of that bet.

Why more tools make your AI worse

The numbers are blunt. Independent analyses of production agents point the same way. They run best with three to five tools, and quality drops sharply once the count passes twenty. A separate test watched accuracy fall off a cliff rather than slide down a ramp, holding strong at ten and twenty tools, then collapsing around a hundred. In one experiment, a strong model’s accuracy on a scheduling task dropped from 43 percent with four tools to 2 percent once the count climbed past fifty. Somewhere along that curve, adding capability stopped helping and started breaking the thing you built.

Picture a sharp new hire on their first day. Give them one clear task and the two tools they need, and they move fast. Hand them that same task plus a hundred-page binder describing ninety other tools they could theoretically use, and watch them slow down. They read the binder. They second-guess. They reach for the wrong thing. Your AI behaves the same way. Every connection you add is another page in the binder it has to consider on every single request.

So the real question for a team lead stopped being how much you can connect. The better question is which connections actually carry weight in the work you do. That sounds abstract until you run the audit.

Run the audit before you add anything else

Open a document and list every AI integration you currently have live. Next to each one, write the specific task it performed in a real workflow this week. Real tasks only. “Pulls the deal stage from Salesforce into the Monday pipeline summary” counts. “Connected to HubSpot” just tells you a wire is live somewhere in your account.

Most teams find half their list falls into that second group. The connection exists because it was available and easy to switch on, never because a repeatable workflow leans on it.

Decide what is load-bearing

A load-bearing integration is one where a real process breaks if you remove it this week. That is the whole test, and you run every item through it.

If pulling an integration would stop a report from generating, block a handoff, or leave a customer waiting, it stays. If pulling it would change nothing you would notice by Friday, it goes on the cut list. Be honest about the gap between a connection you use and a connection you simply like having around. Your AI does not care that the Slack integration feels modern. It sees one more option competing for attention every time you ask it to do something.

Most stacks have three to six integrations doing genuine work, plus a long tail doing nothing but adding noise.

Trim, then retest

Turn off everything that failed the load-bearing test. Do it in one pass rather than gradually, so the difference is easy to feel. Then run your normal tasks for a week and watch response speed and error rate. Both should improve. If some workflow you forgot about does break, you have just learned that integration was load-bearing after all, and you switch it back on with evidence instead of habit.

Cramer’s team did not guess their way to a leaner setup. They measured, cut back what the agent had to weigh, and watched the output improve. You have the same option, and it costs you nothing beyond the comfort of a long integration list.

The instinct to connect everything comes from a good place. You are trying to build leverage, to get the AI doing more of the work so you can do less of it. A bloated stack hands you the feeling of leverage while taxing every output behind the scenes. A lean one hands you the real thing. The fastest, most reliable AI setup in your business is almost certainly smaller than the one you are running today, and getting there is mostly a matter of deleting.

. . .

Want to save hours each week by turning work into repeatable AI workflows?

Why Your AI Output Sounds Like Everyone Else’s

Todd 🌐 Fractional CTO — Tue, 18 Aug 2026 14:00:00 +0000

Building the AI context layer that turns generic answers into brand-specific work

Most teams that bought AI tools this year came away disappointed. The 2026 State of AI for GTM report, where Kyle Poyar and Maja Voje interviewed thirty leaders and collected forty working plays, put a number on it. Fifty-three percent of go-to-market leaders said AI delivered little to no impact. Only 24 percent reported real returns.

Read that again. Three out of four teams spent money and saw nothing move.

Here is the part that should bother you. Everyone in that survey had access to the same models. Same ChatGPT, same Claude, same Gemini. The teams seeing returns and the teams seeing nothing were typing into identical tools. So the gap was never about who had the better software.

What “generic” actually means

Open your last AI-written email or landing page. Read it as if a competitor sent it. Would you know the difference?

For most teams, the honest answer is no. The output reads like it could have come from any company in the category, because it was built from the same raw material every other company is using. A request goes in, a general answer comes back, someone polishes the surface, and it ships.

That output is the average of the internet on your topic. It is competent. It is also indistinguishable from what the team across the street produced the same morning.

When you swap tools and tighten your prompts and still get bland, interchangeable copy, the tool is doing its job. You handed it generic inputs and it gave you generic results. The machine is a mirror.

The teams getting real work out of AI feed it something different

The 24 percent are not better at writing prompts. They have built a habit the other teams skipped. Before they ask AI to produce anything, they make sure it already knows the business.

Kieran Flanagan at HubSpot described his version of this. He built what he calls a customer digital twin, a model he tests campaigns against before launch. It runs on real sales call transcripts, real G2 reviews, real objection notes from the CRM. His warning was blunt. Synthetic data in, synthetic insights out. The twin is only as sharp as the voice-of-customer you train it on.

That principle holds for everything, not just customer simulations. The AI writing your outbound, your blog drafts, your positioning, all of it inherits the quality of what you put in front of it. Feed it your actual customer language and it writes in your customer’s voice. Feed it nothing and it writes in the voice of the average.

A context layer is a curation job, not a coding job

This is where teams talk themselves out of the fix. They assume building this kind of system means a technical project, a data engineer, a six-month integration.

It does not. The report’s own conclusion was that you do not need to be an AI expert or a software engineer to start seeing value. The highest-leverage move a functional team can make is a documentation project. You decide what the AI needs to know, gather it, and write it down in a form the model can read. Most of that work is judgment, and your team already has the judgment. They just have it scattered across people’s heads, old decks, and a hundred Slack threads.

Maja Voje described the simplest version of this in the report. She has the teams she works with build a content assistant inside a single AI project. They upload their messaging and brand guidelines, a knowledge base describing the company, and examples of their best-performing content. Then they write instructions that define the voice and spell out what to do and what to avoid. That is the whole setup. No special platform, no engineering ticket.

What goes into the layer

Build it from the intelligence you already own:

Your ICP, written down. Not the aspirational version on the website. The real one, including the segments that close fast and the ones that waste your time.

Real customer language. Pull exact phrases from call transcripts, reviews, and support tickets. The words your buyers use to describe the problem, copied verbatim.

Your best work. Three to five examples of copy, posts, or pages you were proud of. The model learns your voice from samples, not adjectives.

What has failed. The campaigns that flopped, the messaging that confused people, the angles that never landed in your market. Telling AI what to avoid is as valuable as telling it what to chase.

Your market position. How you differ from the obvious alternatives, in one honest paragraph.

Once it exists, the same prompt behaves completely differently. The request that produced generic filler last week now produces something that sounds like you, references your customers correctly, and reflects how you actually win. You did not get better at prompting. You gave the model a memory.

Start with one workflow

You do not need to document the entire company before you see a return. Pick the one task your team runs most often. Outbound email, social posts, first-draft blogs, whatever eats the most hours.

Joey Maddox at Verisoul makes the case for this with meeting prep. His team loads prior transcripts, email threads, and CRM history into a custom GPT before every call, and his takeaway was simple. The more relevant data the AI can reach, the more useful it gets. Start there. Gather the context for one workflow, load it into a project, and run your normal prompt against it. Compare the two outputs side by side. The difference is usually obvious enough to settle whether this is worth your time.

Then do the next workflow. The layer compounds. Every document you add makes every future task sharper, and you build it once.

The teams in that report who saw nothing are still treating AI like a search engine, asking strangers for answers and accepting whatever comes back. The teams seeing returns gave their AI a home, a memory, and a clear picture of the business it works for. The tool was never the variable. What it knew was.

. . .

Want to save hours each week by turning work into repeatable AI workflows?

Your Best AI User Says the Least

Todd 🌐 Fractional CTO — Tue, 11 Aug 2026 14:00:00 +0000

How to find the people rebuilding their work around AI

On most teams, the loudest voice about AI and the most valuable person using it are rarely the same human.

One demos a new tool in every standup. They ask for more licenses, forward the latest model announcement, and bring AI up in every meeting. They’re easy to spot, which is exactly why they end up with the training budget and the leadership attention.

The other person says almost nothing. They quietly turned a two-day task into a four-hour one and moved on to the next thing. You’d never know unless you went looking at what they actually shipped.

When the time comes to scale AI across the team, most leads fund the first person. That’s the expensive mistake.

Enthusiasm is loud. Output is quiet.

The numbers make the gap obvious. One analysis of more than 400 companies found AI tool usage climbed 65 percent while median pull request throughput rose only about 8 percent. A lot of motion, very little progress.

That disconnect is the whole story. Most teams measure who talks about AI, not who has been changed by it. Training flows toward the vocal users. Budget follows enthusiasm. The people who genuinely rebuilt their workflows stay invisible the entire time, because real change rarely announces itself in a standup.

A vocal user adopts the tool. A real contributor redesigns the work around it. Only one of those compounds when you scale it.

Output reveals what behavior hides

You’ll find the signal in the work itself. Standups won’t hand it to you.

Pull the last quarter of output and look for the curves that bent. Find the person whose turnaround time dropped with no loss in quality, whose revision counts keep falling, who now ships the same volume in half the hours or double the volume in the same time. That person changed something structural about how the work happens.

Someone who compressed a multi-day process into an afternoon has built something you can study and reuse. Someone who gives a polished demo has built a presentation. For a scaling strategy, the first is worth ten of the second.

Interview the workflow itself

Once you’ve found them, resist the urge to ask which tools they like. That question gets you a product review and nothing more.

Ask how they actually do the work now. Walk me through the last time you ran this end to end. Where does AI come in, and where do you still work by hand? What did you stop doing completely, and what broke before you got it right?

You’re after the sequence, the judgment calls, and the small corrections they’ve stopped noticing they make. Most people who have rebuilt a workflow can’t explain it cold, because it has turned into instinct. Your job is to slow them down until the instinct becomes steps again. Record the conversation. The throwaway comments are usually where the real method hides.

Extract it before it lives in one head forever

A redesigned workflow that exists only in one person’s head is a liability. They take two weeks off and the speed leaves with them.

Document it while you’re still in the room. Capture the prompts they reuse word for word, the order they work in, the checks they run before anything ships, and the moments where they override what the AI suggests. Write down the failure modes too, because half the value sits in what they have learned not to trust. Keep all of it concrete enough that someone else could follow it next Monday without coming back with a single question.

Turn one person’s process into a system

A personal workflow becomes leverage the moment it survives a handoff.

Give it to one other person first and watch where they get stuck. Their confusion will expose the steps the original owner skipped, the ones so obvious to them they forgot anyone would need them spelled out. Fix those gaps, then widen the circle. Fold the prompts into shared templates. Wire the quality checks into your existing review process so standards hold steady as more people run the same play.

Do this well and the four-hour workflow quietly becomes the team default. The person who built it finally gets credit for the thing that moved the needle, rather than the colleague who demoed the most tools.

That’s how AI workflows actually scale. You find the quiet ones who already cracked it, then make their work repeatable for everyone else. Your most valuable AI user has probably already transformed how they work and never mentioned it. Look at what shipped, and you’ll see them.

. . .

Want to save hours each week by turning work into repeatable AI workflows?

3 AI ROI Metrics Executives Keep Getting Wrong

Todd 🌐 Fractional CTO — Tue, 04 Aug 2026 14:00:00 +0000

The measurement frameworks built for SaaS produce misleading signals when applied to AI investments

Executives are bullish on AI. They’re spending more, reporting business value, and telling boards the investment is paying off.

Harvard Business Review’s executive benchmark survey confirms the optimism, while noting that organizations still struggle to demonstrate ROI. The researchers attribute the gap to change and human and organizational readiness rather than the technology itself.

That diagnosis is useful. It’s also incomplete. Before readiness becomes the answer, there’s a measurement problem worth examining.

Most organizations are reporting AI ROI on metrics built for a different category of investment. Those metrics worked for SaaS rollouts, headcount decisions, and infrastructure spend. They produce signals that look like progress while obscuring what’s actually working. Let’s dive into why these metrics are failing, and what they are truly hiding.

1. Time Saved Per Employee Hides Quality Degradation

Time saved tells you how fast something got done. But it says almost nothing about whether the output held up.

A marketer who used to write a brief in 90 minutes and now writes one in 20 has saved real time on paper. If that brief comes back for revision twice and pulls additional reviewers into the loop, the savings evaporate and the surrounding work absorbs the cost. The metric doesn’t capture that loop.

A more useful measurement looks at completed quality. Track end-to-end cycle time on work that meets the same quality bar as before, measured against your previous baseline. If a deliverable used to require one round of review and now requires two, the time simply moved further down the pipeline. The signal worth reporting is the time from task start to task accepted by the next downstream owner, including all revisions.

This takes more work to instrument. It requires defining what “accepted” means for each workflow and tracking handoffs across teams. Most organizations skip that effort and report the easy number. The result is a confident chart in the board deck and a slower, lower-quality operation underneath.

2. Adoption Rate Mistakes Access for Value

Adoption rate is a metric showing up in nearly every executive update. You count licenses issued, divide by active users, and call that percentage your AI maturity score. Some companies pair it with usage frequency. Most stop there.

The number tells you whether people opened the tool. It says almost nothing about whether the tool changed their work in a way that produced business value.

Adoption became the proxy for transformation in most organizations, which is how the metric ended up so prominent. Procurement bought seats, IT deployed them, change management sent training emails, and the dashboard turned green. Leadership reported success on a metric that captures activity at the entry point while saying nothing about outcomes downstream.

A better measurement asks what shifted because of the tool. Pick three to five workflows where AI was supposed to change the work. Define what success looks like in each one before you start, with a baseline metric tied to revenue, cost, cycle time, or customer outcome. Then track whether that metric moved after deployment.

3. Cost Per Task Automated Misses the Cost of the System

A task automated by AI rarely sits alone. It connects to upstream inputs, downstream consumers, monitoring, error handling, exception escalation, model updates, and prompt management. Each of those activities carries a cost. Some are obvious, like the engineer maintaining the integration. Others stay hidden, like the senior reviewer who now spot-checks output, the team that built a fallback process for when the model fails, or the compliance review added when an audit flagged the workflow.

A more useful measurement is total cost to deliver the outcome. Define the business outcome the AI is supposed to produce, then sum every cost required to produce it reliably at the quality level your customers expect. Compare that total against the previous total. If the new number is lower, you have a real efficiency gain. If it’s higher or flat, you’ve built a more sophisticated machine that costs the same to operate.

The Measurement That Actually Earns Trust

Time saved per employee, adoption rate, and cost per task automated produce defensible numbers from data your systems already capture. They also produce a story that’s less accurate than executives believe.

The harder measurements force a definition of outcome before deployment starts. They require connecting AI to a business result, instrumenting the workflow end-to-end, and accepting that some investments will show no return. The same measurement that confirms a deployment is working flags the failing ones for redesign or retirement. That symmetry is the point.

Boards will start asking for it. The executives ready with an answer will be the ones who measured the right thing from the start.

. . .

Want to save hours each week by turning work into repeatable AI workflows?

The AI Skills Gap Is Harder to Fix Than You Think

Todd 🌐 Fractional CTO — Wed, 17 Jun 2026 13:27:44 +0000

Why Most Upskilling Initiatives Fail Before They Start

You bought the licenses, shared the training links, and gave the team time to learn. Six weeks later, almost nobody had changed how they work.

This is one of the most common frustrations I hear from leaders trying to build AI capability inside their organizations. They invest in upskilling, see polite participation, and then watch everything snap back to the old workflow within a month.

The instinct is to blame motivation or resistance, but the real issue is usually simpler and harder to see.

The Perception Problem

Research published by the World Economic Forum in early 2026 found that workers across multiple economies recognize AI as a disruptive force but consistently underestimate its impact on their own roles. The contrast was especially sharp in the UK, where 70% of workers expressed concern about AI’s broader economic impact while only 39% believed their own jobs were at risk.

Psychologists call this optimism bias, and it shows up everywhere. But it’s especially damaging in the context of AI upskilling for teams because it makes the problem invisible to the very people who need to act on it.

If someone believes their role is safe, they treat training as optional. They’ll attend the workshop and nod along, but they won’t change a single workflow because in their mind there’s nothing that needs fixing.

Training Fails When People Can’t See the Gap

Think about the last time your organization rolled out a new capability-building initiative. Chances are, someone built a curriculum, picked a platform, and scheduled sessions.

The assumption behind that entire sequence is that people already understand why they need to learn, and for AI upskilling, that assumption falls apart almost immediately.

Stanford’s AI Index Report found that 78% of organizations reported using AI in 2024, up from 55% the prior year, yet only 20 to 40% of workers were actually applying AI in their day-to-day work despite widespread organizational investment. The tools are available, but the people aren’t engaging with them in any meaningful way, and the reason has very little to do with access or willingness.

A study by KPMG and the University of Melbourne found that 83% of people are interested in learning more about AI. While interest in AI is high, the report highlights that urgency around training, education, and organizational preparedness remains relatively low.

Diagnosis Before Curriculum

If you’re leading AI upskilling for a team or an organization, the first move should never be a training plan. It should be a clarity exercise that helps people see, specifically, where AI intersects with their actual responsibilities.

One approach that works well is asking each team member to document their top ten recurring tasks over two weeks, then sitting down together to identify which of those tasks have viable AI-assisted alternatives right now.

The conversation shifts immediately when you go from “AI is important” to “AI can handle 30% of what I spend my week on.” That’s when attention sharpens and people start engaging with the idea of change on personal terms.

Build the Upskilling Around the Diagnosis

Once people see where AI touches their work, training has somewhere to land. The design of the program matters, but it matters less than the sequencing. Diagnosis first, then curriculum.

A few principles hold up consistently across the organizations I’ve worked with:

Start with the workflow, not the tool. Show someone how AI fits into a process they already run every week rather than leading with what the technology can do in the abstract. When the entry point is familiar, adoption follows more naturally.

Make the first win small and visible. One automated report, one faster research cycle, or one draft that used to take two hours and now takes twenty minutes. Early proof compounds quickly and builds momentum that generic training sessions rarely generate.

Let the confident users teach. Every team has one or two people who are already using AI effectively, and giving them a role in the training process accelerates adoption faster than any external course. Peer credibility carries weight that outside expertise often can’t match.

Measure behavior, not completion. Track whether people actually changed their workflow after training rather than whether they finished the course. Completion rates are vanity metrics when it comes to AI upskilling, and they tell you almost nothing about whether the investment produced real capability.

The Real Cost of Skipping This Step

Teams that don’t build AI capability fall behind on efficiency, and consultants or founders who skip the diagnostic step with their clients lose credibility when the training investment doesn’t translate into changed behavior. Organizations that keep funding generic programs quarter after quarter wonder why adoption stays flat while their competitors pull ahead.

The fix is rarely more training. It’s a better diagnosis. Help people see the specific gap between where they are and where AI could take their output, then give them something targeted to close it. That sequence, diagnosis before curriculum, is the one that actually produces results.

. . .

Want to save hours each week by turning work into repeatable AI workflows?

How to Review AI Accuracy Before It Costs You

Todd 🌐 Fractional CTO — Tue, 09 Jun 2026 12:56:48 +0000

A 15-Minute Review Habit That Protects Your Reputation and Your Revenue

Last year, Deloitte Australia refunded nearly AU$440,000 to the Australian government. A university researcher had discovered that their 237-page consulting report contained fabricated academic citations, references to nonexistent research papers, and a made-up quote attributed to a federal court judge. All generated by AI. All missed in review.

If Deloitte, with hundreds of reviewers and formal QA processes, shipped a deliverable full of AI-invented references, the odds that your business catches every error on a Tuesday afternoon are slim.

And that’s the specific problem worth solving. Most business leaders using AI aren’t worried about whether the grammar is right. They’re worried about whether the substance holds up when someone starts asking follow-up questions.

Where AI Fails in Creating Deliverables

AI failures that occur in key deliverables differ from AI failures in a blog post or marketing email.

Three patterns show up repeatedly, and they’re all hard to catch because the output reads well:

Wrong synthesis. AI pulls from multiple inputs and draws a conclusion that sounds logical but doesn’t actually follow from the evidence. You gave it five data points. It connected two of them in a way that would fall apart under scrutiny. The sentence is clean. The reasoning is wrong.

Invented specifics. OpenAI’s own research confirmed that language models are structurally incentivized to guess rather than admit uncertainty. The training and evaluation systems reward confident answers over honest ones, which means the model sounds most authoritative precisely when it has the least basis for what it’s saying. In creating key deliverables, this shows up as statistics that feel precise, studies that sound real, and quotes that seem properly attributed. But none of them actually exist.

Conclusions without support. AI is a pattern-matching engine, and it defaults to tidy summaries. Hand it messy qualitative data (client interviews, survey responses, market feedback) and it will smooth over contradictions, ignore outliers, and hand you a neat narrative. Caitlin Sullivan, a user-research veteran who has trained hundreds of product and research professionals on AI-assisted analysis, documented this problem in detail: AI cherry-picks supporting evidence, skips contradictions, and produces conclusions that look persuasive but don’t represent the full dataset.

Each of these failures has the same surface appearance: polished, professional, ready to ship. Every sentence arrives with the same structural confidence whether it’s accurate or completely fabricated.

Building a Review Habit That Actually Works

The goal here is a review process that catches real errors without eating the time savings AI provided in the first place. A 90-minute AI draft that requires 90 minutes of review is a net-zero outcome.

Check the claims, not the prose. Read through the deliverable and highlight every factual claim, statistic, attributed quote, and causal statement. Ignore the writing quality entirely on this pass. You’re looking for anything that would embarrass you if someone else verified it independently. This is the highest-leverage 15 minutes you’ll spend.

Stress-test the synthesis. For any section where AI combined multiple sources into a conclusion, go back to the original inputs. Does the conclusion actually follow? AI is very good at making two unrelated ideas sound connected. Read the source material yourself and see if you’d draw the same line between them.

Run the “follow-up question” test. Before you send anything, pick the three most important claims in the deliverable and ask yourself: if my someone asks me to explain the reasoning behind this claim in a live meeting, can I do it without looking at my notes? If the answer is no, you don’t understand the output well enough to ship it.

What a Trustworthy AI-Assisted Deliverable Looks Like

Structure matters here. A deliverable you can stand behind has a few consistent features.

Every claim traces back to a source you’ve verified. If AI generated a statistic, you’ve confirmed it exists. If it synthesized a conclusion, you’ve checked the logic against the inputs. Nothing goes out with “AI said so” as the only supporting evidence.

The speed AI gives you is real. A first draft in 30 minutes that used to take three hours is a genuine advantage. But the value only holds if what you deliver is accurate enough to build decisions on. Your review process is what makes the difference between using AI as a competitive edge and using it as a liability you haven’t discovered yet.

. . .

Want to save hours each week by turning work into repeatable AI workflows?

Why Solopreneurs Are Beating Agencies in 2026

Todd 🌐 Fractional CTO — Wed, 03 Jun 2026 12:57:29 +0000

The structural advantages solo consultants have right now, and how to use them

A solo consultant with a laptop and a $500/month tool stack can now research, strategize, produce, and deliver at the level of a small agency.
Two years ago, that sentence would have been aspirational. In 2026, it's an ordinary week.

Nearly 30 million solopreneurs in the US are generating $1.7 trillion in revenue, and the fastest-growing segment within that number is service providers and consultants doing the strategy, advisory, and implementation work that used to require a team of five.

Something structural shifted, and it happened quicker than most people in the agency world expected.

The Operational Gap Closed Fast

For years, agencies held real structural advantages over independent practitioners. They could produce faster, cover more skill sets, and maintain a level of output quality that a single person couldn't match. Those advantages justified premium retainers and multi-month contracts.

That math has changed. AI tools have quietly handed solopreneurs capabilities that used to require entire departments, and the speed of that shift caught most agencies off guard. A solo consultant can now research a client's competitive landscape, draft a strategic brief, build a presentation, and prep follow-up materials in the time it takes most agencies to schedule an internal kick-off call.

This goes beyond just writing faster or generating slides. The tools now handle competitive analysis, financial modeling, document review, and content production at a quality level that passes professional scrutiny. A consultant who knows how to direct these tools well produces output that looks and feels like it came from a well-staffed firm. The difference is that the strategic thinking behind it belongs to one person with deep context on the client, rather than a team piecing things together from a brief.

The solopreneur tech stack in 2026 runs between $3,000 and $12,000 a year, which represents a 95 to 98 percent reduction in operating costs compared to a traditional team setup. When your infrastructure costs drop by that much, your margins don't just improve, your entire business model changes.

Solo practitioners regularly operate at 60 percent margins or higher, while most agencies run between 20 and 40 percent. That gap gives independents room to invest in better tools, spend more time on strategy, and still take home more per project than an agency consultant billing at a higher rate.

Why Clients Are Choosing the Solo Expert

There's a growing frustration among buyers who feel like they're being passed around. They sign a deal because of the senior partner in the pitch meeting, then spend six months working with a rotating cast of junior staff who need to be brought up to speed every other week.

Solo consultants don't have that problem, because the person in the pitch is the person doing the work. Clients get direct access to senior thinking on every call, every deliverable, and every decision, and that consistency builds trust faster and produces better outcomes.

Speed compounds differently when one person owns the entire engagement. A solopreneur can respond to a client question, adjust a strategy, or pivot an approach in minutes, without internal sign-offs, committee reviews, or waiting for the account manager to loop in the creative director before anything moves.

When you combine that speed with AI tools that handle research, drafting, and production, something interesting happens. The solo consultant arrives at meetings more prepared, turns around deliverables faster, and maintains a level of strategic depth that larger teams struggle to match because their attention is always split across accounts.

There's also a quality dynamic at play. When one person owns the entire engagement, the work has a coherent point of view and every deliverable connects to the same strategic thread. Agencies often produce work that feels disjointed because different people touch different pieces, and the hand-offs introduce friction that shows up in the final product. Clients who've experienced both can feel the difference immediately.

The Structural Math Has Changed Permanently

The shift toward solopreneurs isn't happening because agencies suddenly got worse at their jobs. Agencies still do certain things well, especially large-scale, multi-channel campaigns that require significant coordination across dozens of stakeholders.

But for the kind of work that most consultants and knowledge-based service providers do (strategy, advisory, implementation, coaching) the structural math now favors the individual. A one-person practice with good tools, a clear niche, and a repeatable delivery system can match or exceed the output quality of a small agency while operating at a fraction of the cost.

The solopreneur economy backs this up at scale. Services and done-for-you work still rank as the top revenue sources for solo practitioners, ahead of digital products and courses, and the clients hiring them are choosing solo expertise deliberately rather than settling for it.

The AI adoption curve is accelerating the advantage even further. Early adopters are seeing AI automate 70 to 80 percent of operational tasks, recovering roughly 10 hours per client per week, which translates to 150 to 300 percent productivity gains. That's one person producing at the level of a small team with none of the coordination overhead.

What This Means for Positioning and Pricing

If you're running a solo practice right now, the worst thing you can do is try to look like an agency. The clients who are choosing solopreneurs over agencies are doing so precisely because they want what you offer, which is direct access, speed, consistency, and focused expertise.

Three shifts are worth making if you want to capitalize on this moment.
First, niche tighter than feels comfortable. Generalist agencies cast wide nets, but specialist solopreneurs become the only logical choice for the right client. The more specific you are about who you help and what outcome you deliver, the less you compete on price and the more you compete on fit.

Second, price on value rather than hours. If AI lets you complete ten hours of work in two, charging hourly punishes you for being efficient. Your clients pay for the outcome and the thinking, not the time it takes you to produce it, so structure your engagements around deliverables, phases, or retained access to your expertise.

Third, invest in your delivery system. The consultants winning right now aren't just skilled at their craft. They've built repeatable processes that let them onboard clients smoothly, deliver consistently, and follow up without manual effort. Your system is effectively your team, and it deserves the same attention you'd give to hiring and training real people.

The Window Is Real, But It Won't Stay Open Forever

Right now, most agencies haven't adapted to this shift. Their cost structures, hiring models, and delivery processes were built for a world where scale required headcount. That world is ending, and the transition is creating a window where well-positioned solopreneurs can capture work and build client relationships that will be hard to displace later.

The solo consultants who recognize this moment for what it is aren't trying to become agencies. They're building something better. Lean practices with high margins, deep client relationships, and the operational capacity to deliver at a level that would have been impossible three years ago.

They're also building something more resilient. When your overhead is low, a slow quarter doesn't threaten the business. When your client relationships are direct, you don't lose accounts because someone else on the team dropped the ball. And when your delivery system runs on tools you control, you can adapt to new client needs in days instead of months.

Being a one-person practice is the advantage right now, and the solopreneurs who understand that are building businesses that will be very hard to catch.

. . .

Want to save hours each week by turning work into repeatable AI workflows?

How to Leverage Claude Skills When You're Not a Developer

Todd 🌐 Fractional CTO — Tue, 26 May 2026 14:28:54 +0000

Three setup decisions that separate useful AI output from generic first drafts

Claude Skills have become one of the most talked-about features in AI productivity circles this year, and for good reason. A well-built skill turns Claude from a general-purpose chatbot into something that consistently produces work you can actually use, formatted the way you want it, in the voice you need, every single time.

If you're a consultant, a business leader, or a founder, you probably don't have a command-line workflow, and you don't think in YAML front matter. So how can you leverage what appears to be a highly technical tool?

The truth is Claude Skills were built for users just like you. You don’t need to be technical at all to leverage them. You just need a different starting point than the one Anthropic's docs give you.

What a Skill Actually Is (Without the Technical Jargon)

A Skill is a set of saved instructions that Claude reads automatically when it recognizes a matching task. You don't paste them in every time or type a special command. You just describe what you need, and Claude pulls in the right skill on its own.

Think of it like onboarding a new contractor. You hand them your brand guide, your formatting preferences, your examples of good work, and your list of things to avoid, except you only do it once. Every future conversation where that task comes up, Claude already knows the playbook.

The Skill itself lives in a simple text file with a short block at the top containing a name and description, followed by your actual instructions underneath. The description is what Claude reads on every message to decide whether the Skill is relevant, and the full instructions only get loaded when Claude decides it needs them.

That description block is where the first critical decision happens.

How to Write a Description That Actually Triggers

The most common reason a Skill misfires, or never fires at all, is a vague description. Claude uses that short text to match your request against every available Skill, so if the description is too broad, the Skill activates when you don't want it. Too narrow, and it sits there unused while you wonder why nothing happened.

Here's a practical example. Say you build a Skill for writing LinkedIn posts. If your description says "Use for social media content," Claude might trigger it when you ask for a tweet thread, an Instagram caption, or a content calendar. That's far too broad for what you actually need.

A better description would read something like this. "Use when writing LinkedIn posts for professional audiences. Applies brand voice guidelines, formatting preferences, and hook structures for single-image or text-only LinkedIn posts."

That version is specific enough to trigger correctly and narrow enough to stay out of unrelated tasks. The difference between these two descriptions is the difference between a Skill that helps and one that gets in the way.

Add Negative Boundaries Before They Become a Problem

Even with a well-written description, Skills can still hijack conversations they shouldn't touch because Claude errs on the side of helpfulness. If your request looks even loosely related to a Skill, Claude might load it, and suddenly your LinkedIn formatting is showing up in email drafts.

The fix is straightforward. Add negative boundaries, which are explicit lines in your Skill description that tell Claude when NOT to use it.
For that LinkedIn post Skill, you'd add something like this. "Do NOT use for blog articles, email sequences, newsletters, social media content other than LinkedIn, or general writing tasks."

That single addition prevents a whole category of misfires and draws a clean line between tasks that would otherwise blur together.

Ruben Hassid, who has written extensively about Claude for non-technical users, calls this one of the most overlooked steps in Skill setup. And it makes sense. When you're building the Skill, you're focused on what it should do, and you're rarely thinking about all the situations where it shouldn't activate. But Claude doesn't have that context unless you explicitly provide it.

A good rule of thumb is to spend two minutes listing three to five tasks where each new Skill should NOT fire, then add those as explicit exclusions in the description. You'll avoid the most common frustration new Skill builders hit, which is a Skill that works perfectly on the intended task but creates problems everywhere else.

Choose What to Automate (and What to Leave Alone)

Not every task needs a Skill, and building Skills for the wrong things creates more complexity than it solves.

The best candidates share three characteristics:

You do the task repeatedly, at least a few times per week.
The output follows a consistent structure or set of rules.
You find yourself re-explaining the same preferences to Claude every time you start a new conversation.

The question to ask yourself is simple. "Am I currently pasting the same instructions into Claude more than twice a month?" If the answer is yes, that's a Skill waiting to be built.

Pick the task you do most frequently where the output needs to follow specific rules. Build that single Skill, test it for a week, and refine based on where it falls short. A Skill doesn't produce perfection on the first try, but it does produce a consistent starting point that gets you roughly 80% of the way there, every time, instead of starting from zero.

One more thing worth noting is that Skills still consume your usage and don't magically reduce token costs. A complex Skill with long instructions will actually use more tokens per conversation than a simple prompt, because the efficiency gain comes from time saved and output consistency rather than lower AI costs. If you're using Claude daily with multiple Skills active, the Max plan at $100 per month starts making more financial sense than constantly bumping into usage limits on the Pro tier.

The Practical Path Forward

The people who get the most value from Claude aren't the ones with the most Skills. They're the ones who built a few Skills well, with clear descriptions, strong boundaries, and a focused scope. Those three or four Skills handle 80% of their recurring AI work, and everything else stays a normal conversation.

Skills aren't a power-user feature locked behind technical knowledge. They're a systems feature, and if you've built systems in your business before, whether processes, templates, or SOPs, you already understand the thinking that makes a good Skill. The interface is just different.

. . .

Want to save hours each week by turning work into repeatable AI workflows?