AI

90 days does not transform your company - it proves transformation is possible

Stop trying to complete AI transformation in 90 days. Use that time to prove it is worth doing. Here is how mid-size companies can run sprints that build momentum for lasting change.

Stop trying to complete AI transformation in 90 days. Use that time to prove it is worth doing. Here is how mid-size companies can run sprints that build momentum for lasting change.

Key takeaways

  • 90 days proves viability, not completion - Use sprints to validate transformation potential rather than rushing incomplete implementations
  • Mid-size companies have the right agility - 50-500 employee organizations can move faster than enterprises while maintaining structure for scaling learnings
  • Focus beats feature creep - Pick one high-impact use case with measurable outcomes rather than trying to transform everything at once
  • Momentum matters more than perfection - Build organizational confidence through visible wins that create appetite for continued investment

90 days won’t transform your company. Full stop. But it will tell you whether transformation is worth pursuing at all. That’s the real difference between a sprint and a slog - one proves value, the other assumes it.

We learned this at Tallyfy, and honestly, we learned it the embarrassing way. We pitched 12-month transformation roadmaps to clients. Week three brought the first crisis. Week six brought budget questions. By month three, the original vision was buried under “urgent” priorities nobody could quite define. Then we switched to 90-day pilots focused on proving specific value propositions. Renewals became automatic. Expansions became obvious. Proof beats promises. Every time.

The problem with how companies frame this

Research keeps showing less than 30% of transformations succeed. Look closer and you’ll find something interesting: the ones that work start with clear proof points, not grand visions. Current data on AI adoption shows the vast majority of organizations now use AI in at least one function. Only about 6% are generating value at scale. Everyone’s experimenting. Few are transforming.

The framing problem is this: companies treat 90 days as a compressed version of a multi-year transformation. They’re trying to finish something instead of prove something. Those are fundamentally different goals, and conflating them is why so many sprints collapse.

90 days is long enough to push past the honeymoon phase where everything seems possible. Short enough to maintain urgency without triggering change fatigue. Employees tend to hit peak resistance somewhere around the two-month mark of any major change, once the initial excitement fades and real friction sets in. HBR reported that employee willingness to support enterprise change collapsed from 74% to 43% between 2016 and 2022. By day 90, you’ve either pushed through or you haven’t. No ambiguity. Six months gives doubt too much room to grow. One month doesn’t produce real behavioral change. 90 days hits the sweet spot where iterations produce patterns - three full monthly cycles, each building on the last.

A Nigerian education pilot achieved two years of academic progress in six weeks. If that’s possible in education, one of the slowest-changing sectors, the real question isn’t whether 90 days is enough. It’s whether you’re asking the right question going in.

What you’re actually proving

Most companies think a 90-day sprint should deliver a mini-transformation. Wrong. You’re not building the future in 90 days. You’re proving it’s buildable.

Four things get tested simultaneously.

Your team’s ability to learn new tools without melting down. Prosci’s research shows 43% of AI adoption failures trace back to inadequate executive sponsorship, while 38% come from user proficiency gaps like learning curves and poor training. Together, people problems account for the majority of failures, outpacing technical issues by a wide margin. In 90 days, you’ll know if your people can adapt or if you need a different approach.

Your processes’ actual flexibility. Can existing workflows bend without snapping? Companies discover their “core processes” were really just habits nobody had questioned in years. 90 days forces those questions out into the open, which is uncomfortable but useful.

Your leadership’s commitment when things get genuinely hard. High-performing companies are 3x more likely to have senior leaders who demonstrate real ownership of AI work. Day 60 tells you everything about whether that’s real or just performative enthusiasm at kickoff meetings.

Your actual data readiness. Everyone thinks their data is “pretty good” until they try feeding it to AI. A full 57% of organizations estimate their data isn’t AI-ready, and data quality remains one of the top obstacles organizations face. Better to discover that in a sprint than mid-transformation.

The sprint framework that actually produces results

Forget complex methodologies. What actually drives results is simpler than most consultants will admit.

Days 1-30: Foundation without overthinking

Pick one use case. One. Not three with a backup. Inc.com’s analysis of enterprise AI data shows workflow redesign has the biggest effect on EBIT impact from AI, yet fewer than 20% of enterprises track defined KPIs for their AI work. Clarity beats coverage every time.

Get the right people involved from day one. Not a committee. One person owns it. They pull everyone else in. This isn’t democracy; it’s delivery. Set up basic measurement - not perfect dashboards, just enough to know if you’re winning or losing. You can refine the metrics later.

Days 31-60: Reality meets resistance

This is where most pilots die. The novelty wore off. Real problems surfaced. Change fatigue kicks in hard. If you can push through this phase, you’ve proved more than any presentation deck ever could. This is where you find out if your organization has the stomach for real change or just likes talking about it at off-sites.

Double down on what’s working. Kill what isn’t. No sentimentality. Done.

Days 61-90: Scaling signals emerge

Patterns are clear by now. You know what scales and what doesn’t. You’ve identified your champions and your skeptics. The compound effect starts showing.

Document everything that worked. Pull it out of people’s heads before they forget the details. Turn it into repeatable processes. This is your blueprint for the real transformation that follows.

Choosing where to run your first sprint

Pick wrong and you’ve wasted 90 days. Pick right and you’ve bought years of momentum. I think this choice matters more than most people realize.

Look for processes with measurable outcomes within 30 days, willing participants who won’t quietly undermine the work, enough complexity to be meaningful but not so much that it’s overwhelming, and clear before/after comparisons that you can show to skeptics.

I watched one company try to transform their entire customer service operation in 90 days. Failed spectacularly. Another focused only on routing tickets 20% faster. That 20% improvement bought them executive support for the next five sprints. The scope difference was the whole game.

Mid-size companies have real advantages here. You’re not fighting enterprise bureaucracy. You’re not constrained by startup chaos. You can pick a battlefield where winning is actually possible, which is probably more important than most guides acknowledge.

Converting sprint wins into lasting change

The majority of challenges in AI rollout relate to people and processes, not technical issues. Fewer than 20% of employees have heard from their direct manager about AI’s impact on their job. People arrive anxious and exhausted before you’ve even started. That’s the real environment you’re working in.

90 days works partly because it’s defined. There’s an end date. People can see the finish line. Set expectations early: this is about learning, not perfection. We’re testing feasibility, not delivering final products. Success means clear signals, not complete solutions.

Build in breather moments. Week 6 should be lighter. Week 11 should consolidate, not accelerate. Communicate progress weekly - not lengthy updates, just “this week we learned X, next week we’re testing Y.” Simple. Clear. Forward motion.

Most companies drop the ball right here. They run a successful 90-day sprint, celebrate, then nothing. Six months later they’re running another “pilot” because they never converted the first one into sustained change. Treat each sprint as a building block, not a standalone event. Your second sprint should build on the first. Your third should scale what the second proved.

Document patterns, not just outcomes. What worked and why? What failed and why? These patterns become your actual playbook. Build your coalition gradually. Each sprint should create more believers. By sprint three, you should have enough advocates that resistance becomes futile. Systematic strengthening beats random improvement.

One client ran four consecutive 90-day sprints, each building on the last. By month 12, they’d achieved more than the original 3-year plan had promised. They proved each step worked before taking the next one. That sequencing was everything.


90 days won’t transform your company. But it will tell you if transformation is possible, who will drive it, what will break, and what it’s actually worth.

In a world where 95% of GenAI pilots fail to deliver measurable returns and analysts predicted 30% of AI projects would be abandoned after proof of concept, intelligence beats ambition. Start your 90 days to prove something. Anything.

Because proof builds momentum. And momentum is what transforms companies.

About the Author

Amit Kothari is an experienced consultant, advisor, coach, and educator specializing in AI and operations for executives and their companies. With 25+ years of experience and as the founder of Tallyfy (raised $3.6m), he helps mid-size companies identify, plan, and implement practical AI solutions that actually work. Originally British and now based in St. Louis, MO, Amit combines deep technical expertise with real-world business understanding.

Disclaimer: The content in this article represents personal opinions based on extensive research and practical experience. While every effort has been made to ensure accuracy through data analysis and source verification, this should not be considered professional advice. Always consult with qualified professionals for decisions specific to your situation.