You Don’t Need a Dev Team Anymore—You Need Dev Literacy

I’ve been building websites since I was in college, back when you had to hand-code everything and pray your CSS worked in Internet Explorer. For years, the ability to write code was a moat: if you could build software, you had leverage other knowledge workers didn’t. That moat just evaporated.

AI coding assistants like Claude and GitHub Copilot aren’t just making developers faster. They’re turning domain experts into builders. Marketing directors are shipping custom content management systems. Healthcare administrators are prototyping patient engagement tools. Financial analysts are building data pipelines that used to require engineering sprints.

The competitive advantage isn’t access to developers anymore. It’s knowing what to build and having the literacy to direct AI tools to build it. That’s a fundamentally different skill set, and most organizations haven’t figured out what it means yet.

From Copy-Paste Tax to Infrastructure Thinking

Mike Bayly’s recent post nailed something I’ve been seeing in my own workflow: the shift from one-off solutions to reusable systems. He’s talking about work that used to take days now taking under an hour—not because the AI writes code faster, but because it enables you to think in systems rather than tasks.

Here’s what that looks like in practice. A marketing director at one of our clients used to manually export campaign data from three platforms, merge it in Excel, format it for their monthly board deck, then repeat the whole process next month. Classic copy-paste tax. Now she’s built a custom data pipeline that pulls everything automatically, formats it to their brand standards and outputs a presentation-ready report. She didn’t hire a developer. She spent two afternoons with Claude, explaining what she needed in plain English.

The tool she built isn’t just faster—it’s infrastructure. It compounds. Every month, she gets those hours back. Every time the board asks a new question about campaign performance, she modifies the system rather than starting from scratch. She’s thinking like a developer now, even though she’s never written production code.

That’s the shift. Knowledge workers who learn to build reusable systems rather than executing repetitive tasks create leverage that accumulates. The ones still doing things manually are falling behind, not because they’re less smart, but because they’re playing a different game.

What Dev Literacy Actually Means

You don’t need to become a software engineer. But you do need to understand how software thinks. That means:

• Recognizing when a workflow should be automated versus executed manually
• Breaking complex processes into discrete, repeatable steps
• Understanding data structures well enough to explain what you need
• Knowing when to build custom versus when to integrate existing tools
• Testing and iterating on systems rather than expecting perfection on the first try

This isn’t coding literacy—it’s systems literacy. The AI handles the syntax. You handle the architecture. You’re the one who knows that your content approval process has seven steps, three stakeholders and two systems that don’t talk to each other. The AI can’t intuit that. But once you explain it, it can build the connective tissue.

I’ve watched developers land 259 pull requests in 30 days by running 15+ Claude sessions in parallel. That’s not sustainable for non-developers, and it’s not the point. The point is that individual knowledge workers can now build the specific infrastructure they need for their specific workflows, without waiting for IT roadmaps or agency timelines.

What This Means for Organizations

If you’re hiring marketing directors, ask them about the last system they built. If you’re evaluating agencies, ask how they’re enabling client teams to build their own tools. If you’re setting training budgets, invest in AI tool proficiency before you invest in more software licenses.

The organizations winning right now aren’t the ones with the biggest development teams. They’re the ones where domain experts have permission and capability to build solutions to their own problems. That requires a culture shift—from “submit a ticket and wait” to “prototype it yourself and we’ll help you productionize it.”

At Jigsaw, we’re seeing this play out in real time. Clients who used to ask us to build custom reporting dashboards are now building first drafts themselves and asking us to refine them. That’s not threatening our business—it’s making our partnerships more productive. We spend less time translating requirements and more time solving actual strategic problems.

But here’s the tension: this only works if you invest in building that capability. Buying everyone a Claude subscription doesn’t create dev literacy any more than buying everyone running shoes makes them marathoners. You need training, you need cultural permission to experiment and you need leaders who understand what good infrastructure looks like.

The Compounding Advantage

The real competitive advantage isn’t the tools you build this quarter. It’s the organizational muscle memory you develop around building tools. Teams that get good at translating domain expertise into software infrastructure create compounding productivity gains. They solve problems faster, they adapt to change more fluidly and they stop being bottlenecked by development resources.

This shift expands who gets to build. The marketing director who builds her own content system still needs developers for security, scalability and integration with enterprise systems. But she’s not waiting three months for a discovery process to explain what she already knows she needs.

The knowledge workers who figure this out first—who invest in learning how to direct AI tools to build their personal infrastructure—will have a productivity advantage that looks like magic to everyone else. It’s not magic. It’s just leverage. And leverage, compounded over time, is what separates organizations that grow from organizations that grind.

So here’s the question: are you building systems or are you still paying the copy-paste tax?