In my years of helping businesses implement automation, I’ve watched the same tragedy unfold many of times: smart people buying software they’ll never properly use, then blaming themselves when it doesn’t work.
You know the drill. You saw the demo, loved the promise, signed the contract. Six months later, you’re paying $500/month for what’s essentially become the world’s most expensive digital paperweight.
Here’s what I’ve learned: The $5 trillion we spent on IT in 2024 isn’t failing because the tools are bad—it’s failing because we’ve been sold a fundamental lie about how business automation actually works.
Today I’m sharing the methodology I’ve developed after watching large-scale tech programs crash and burn. It’s not about finding better software or bigger budgets. It’s about understanding why most automation feels like it’s being done to you instead of with you.
What I Mean by Done-FOR-You vs. Done-WITH-You
Done-with-you consulting means you learn the system while we build it together, instead of having someone hand you a black box and hope for the best.
Most of my competitors operate on what I call the “magic wand” model: they analyze your business, recommend solutions, implement systems, provide some training, then disappear. You’re left holding a sophisticated tool you don’t really understand, hoping it keeps working.
I learned the hard way that this approach creates expensive dependencies. When something breaks (and it always does), you’re back to square one—calling consultants, paying for fixes, feeling helpless.
The done-WITH-you approach means we build your solution together. You’re not watching from the sidelines; you’re learning why every configuration choice matters. By the time I’m done, you understand your system well enough to modify it as your business evolves.
It’s like the difference between having someone cook for you every night versus learning to cook yourself. Both solve the immediate hunger problem, but only one gives you long-term capability.
Why Everyone Falls Into the Done-FOR-You Trap
I get it. When some consultant promises to “handle everything,” it sounds perfect. You’re already wearing twelve hats—who has time to become a software expert too?
But I’ve seen what those promises actually cost.
The Three Deadly Assumptions
Every done-for-you vendor makes assumptions that kill projects:
Assumption #1: Your business works like their last client’s business. I can’t tell you how many times I’ve been called in to fix a CRM that was configured for a tech startup when the client runs a consulting firm. Different industries, different sales cycles, completely different needs.
Assumption #2: Your team will naturally adapt to new systems. In my experience, if you didn’t involve people in choosing and configuring the system, they’ll find creative ways to avoid using it. I’ve seen teams maintain shadow spreadsheets rather than use the “perfect” system someone else built for them.
Assumption #3: Your processes are automation-ready. This is the big one. Most businesses try to automate broken workflows. I’ve learned you can’t put lipstick on a pig (oh my favorite phrase)—if your process doesn’t work manually, automating it just makes it fail faster.
Hold Up—Which Camp Are You In?
Right about now, you might be thinking, “Okay, but my vendor seems different. They really listen to us.”
Sure they do. Just like they listened to their last ten clients who are now maintaining shadow spreadsheets and cursing under their breath every Monday morning.
Before you convince yourself you’re the exception, I’ve got a 2-minute reality check that’ll show you exactly where you stand. No fluff, no “enterprise-grade” BS—just straight answers about whether you’re building automation that sticks or heading for the digital graveyard.
Find Out If You’re Setting Money on Fire →
(No email required. I’m not that desperate for leads.)
The Waste I See Everywhere
Here’s the data that keeps me up at night: Companies waste 37% of their software spending, which adds up to $30 billion annually in the US alone.
In my consulting work, I regularly find:
- 30% of applications that go completely unused
- 53% of licenses sitting idle in any 30-day period
- Millions in “productivity” tools that make teams less productive
A good example of this: paying $50,000/year for marketing automation used to send exactly one monthly newsletter. The vendor had convinced them they needed “enterprise-grade capabilities.” They needed a $50/month email tool.
If you took that assessment earlier and discovered you’re deep in done-for-you territory, you’re probably feeling a mix of vindication and dread right now. Vindication because you knew something was off. Dread because, well, you’re still paying for it.
The good news? You’re not stuck there.
How My Done-WITH-You Approach Actually Works
My philosophy: You should understand your business systems well enough to explain them to a new employee without calling me.
Instead of building something for you, I build something with you. Every decision gets explained, every configuration gets documented, every integration gets understood.
Why I Believe Collaboration Trumps Everything
The industry data backs up what I’ve experienced: 75% of executives want consultants who deliver value through collaboration, and two-thirds will fire consultants who don’t work this way.
More importantly, I’ve seen the results. Clients who understand their systems don’t panic when something breaks. They don’t need me on retainer. They don’t get stuck when their business model evolves.
You know your business better than I ever will. You know which features matter, which workarounds exist for good reasons, and which solutions your team will actually adopt. I know how to implement technology and avoid common pitfalls.
When we combine your business knowledge with my technical experience, we build something neither of us could create alone.
My Three-Phase Process
Phase 1: Discovery (Together) I don’t audit your business and deliver a report. We map your processes together, identify bottlenecks together, and prioritize solutions together. You’re involved in every decision because you’re the one who has to live with the consequences.
Phase 2: Implementation (Side-by-Side) While I’m configuring workflows and building integrations, you’re learning how everything connects. When we hit roadblocks (and we always do), we solve them together. By the end, you don’t just have a working system—you understand why it works.
Phase 3: Optimization (With Training Wheels Off) I document everything we’ve built, train your team on advanced features, then gradually reduce my involvement as your capability grows. The goal is making myself unnecessary, not indispensable.
Why Most Automation Projects Crash and Burn
In my experience, automation fails because companies buy tools instead of building capabilities.
The failure rates I see are staggering: 31% of software projects get canceled entirely, 53% exceed their budgets by nearly 200%, and 70-80% of enterprise implementations fail outright.
But here’s what really gets me: 78% of organizations claim they use AI, but only 1% feel they’re actually good at it. We’re spending trillions while admitting we don’t know what we’re doing.
The Vendor Dirty Secret I’ve Discovered
Software companies have turned the implementation gap into a profit center. They sell you the tool, then sell you training, then sell you consulting, then sell you ongoing support. Each failure becomes another revenue opportunity.
Those “customer success” teams every SaaS company brags about? They exist because customers can’t succeed on their own. If the software actually worked as advertised, customer success would be redundant.
I’ve seen vendors deliberately make their systems complex to create consulting dependencies. It’s more profitable to sell you a solution you can’t fully use than one you can master.
The “Pilot Purgatory” I Keep Encountering
Most of my new clients are stuck in what I call pilot purgatory—they’ve deployed tools and run experiments, but they can’t scale anything because they don’t understand how it all fits together.
They have marketing automation that doesn’t talk to their CRM. They have project management tools that duplicate their accounting system. They have AI pilots that impressed the C-suite but confused everyone else.
Reality check: Your job is running your business, not becoming a software archaeologist. But someone needs to understand how your systems work, or you’ll be forever dependent on vendors who may not care about your long-term success.
When I Recommend Each Approach
Not every situation needs my done-with-you treatment. Here’s how I help clients decide.
When Done-FOR-You Makes Sense
I tell clients to go with done-for-you when:
- You need a commodity solution with zero customization (basic bookkeeping, simple scheduling)
- It’s a temporary fix while you focus on bigger priorities
- The system is truly plug-and-play and won’t need modification
Honest assessment: Sometimes you just need something working fast, and learning can wait.
When I Insist on Done-WITH-You
I push for my collaborative approach when:
- The system affects your core business processes
- You’ll need to modify the solution as you grow
- Team adoption is critical for success
- You want to reduce long-term vendor dependencies
The deciding factor: If it’s important enough to do right, it’s important enough to understand.
The Investment Reality
Done-for-you costs less upfront but creates expensive dependencies. Done-with-you requires more initial investment but builds lasting capability.
My ROI promise: You’ll save more in year two than the extra you spend in year one.
What I See Coming Next
The automation industry is slowly catching on. 94% of companies get real value from automation, but only when they actually implement it properly.
Smart businesses are choosing capability over convenience. They’re recognizing that in a world where technology changes constantly, understanding your systems matters more than having perfect systems.
The best automation feels invisible because it fits your business perfectly. That only happens when you help build it.
Ready to Stop Renting Expertise and Start Owning It?
We need to talk if:
- You’re tired of calling consultants every time something breaks
- That assessment score made you wince
- You’ve got a sneaking suspicion your team maintains shadow spreadsheets
- You’re ready to actually understand what you’re building
Ready to fix this? Book a 30-minute reality check where I’ll map out exactly how to transform your current mess into something you actually control. Fair warning: I might tell you some tools need to go. Grab your spot →
Sources Directly Cited in the Blog:
- BCG (2025). “Most Large-Scale Tech Programs Fail—Here’s How to Succeed“
- Flexera (2024). “2024 State of IT Report“
- Apty (2024). “Why Enterprises are Prioritizing Software Adoption in 2024“
- McKinsey & Company (2025). “Superagency in the workplace: Empowering people to unlock AI’s full potential at work“
- McKinsey & Company (2025). “The state of AI: How organizations are rewiring to capture value”
- IBM Institute for Business Value (2024). “Consulting reimagined, powered by AI“
- Beta Breakers (2024). “Software Survival in 2024: 2023 Statistics and Quality Assurance“
- IT Jungle (2024). “Gird Yourself for Digital Transformation Failures in 2024“
- Matrix Venture Studio (2024). “Top 10 Business Consulting Trends for 2024“
- Harvard Business Review (2023). “The Best Consultants Do More Than Deliver Solutions“
Additional Supporting Sources:
- McKinsey & Company (2023). “Delivering large-scale IT projects on time, on budget, and on value“
- Gartner (2024). “How to Optimize Software Spending“
- Deloitte (2024). “The Future of Consulting – From Value to Values“



