Building the internal business case for a digital overhaul
By Sarah Leeth with Insights from Creed’s CTO, Clark Engblom
You know something needs to change. Maybe your team is duct-taping three disconnected systems together just to produce a weekly report. Maybe your website is bleeding leads. You’ve done the research, maybe even gotten a proposal you were excited about, and then you took it upstairs and watched the momentum drain out of the room.
“Can we do this next fiscal year?” “What’s the ROI on this, exactly?”
In our experience at Creed, the most common reason a digital project stalls isn’t budget. It’s that the champion, often the Marketing Manager, IT Director, or Digital Lead who sees the problem most clearly, doesn’t yet have the language to make it land with the people who hold the keys.
This isn’t uncommon, but can prove challenging. So, we spoke with a few of our most successful client partners who offered the following tips to help change the conversation.
Translate symptoms into business outcomes
Executives aren’t thinking about symptoms. They’re thinking about risk, return, and strategic priority. So before you build a single slide, run every problem through this exercise: ask “so what?” until you reach a business outcome.
- Our website is outdated. → Visitors leave before converting. → We’re losing qualified leads to competitors. → Preventable revenue loss.
- Our portal is clunky. → Members call support instead of self-serving. → Cost-to-serve is inflated and retention is at risk. → Excess operational cost.
- Our systems don’t integrate. → Staff spend hours on manual data entry. → That’s headcount cost with no strategic return. → Unnecessary labor and a team operating below its potential.
This reframe alone will change how the conversation goes.
Build the ROI on four levers
You don’t need a finance degree. You need a structure. When we help clients think through a digital investment, we use four value levers:
- Revenue Growth. What’s a 15% improvement in lead conversion worth at your average deal size? Run the math conservatively.
- Cost Reduction. If your team spends 10 hours/week on manual workarounds at a $75 fully loaded hourly rate, that’s $39,000/year in labor you’re paying for inefficiency. Name it.
- Risk Mitigation. ADA litigation, HIPAA exposure, security vulnerabilities in legacy platforms; these aren’t hypothetical. Put a rough dollar range on your organization’s actual exposure.
- Strategic Enablement. What becomes possible once the foundation is rebuilt? Faster service launches, better data for decisions, a distributed workforce. These multipliers belong in the conversation.
Insight from Creed’s CTO: Most organizations dramatically underestimate what their current broken system is already costing them. This can be in developer time, workarounds, support overhead, and delayed decisions. When you add that up honestly, the investment in a modern solution often looks very different.
Frame it as investment, not expense
Language matters. “Cost” implies something taken away; “investment” implies something built. The difference isn’t spin. It’s accuracy.
| Instead of this… | Say this: |
| “This will cost $150,000.” | “This is a $150,000 investment with an estimated 18-month payback.” |
| “We need to redo the website.” | “We’re building a lead-generation asset that will serve us for 5+ years.” |
| “Our portal isn’t working well.” | “We can reduce support volume ~30% and improve retention through better UX.” |
Know your audience
- CFO: Show conservative math, acknowledge uncertainty with a range, and make the cost of inaction explicit. Waiting isn’t neutral, it’s a choice with a price tag.
- CEO / Executive Director: Connect the investment to where the organization is going. What does this enable? What does it protect?
- IT Leader: Bring them in early. Show that integration complexity and delivery risk have been considered. An IT leader who feels heard is an ally; one who feels steamrolled is an obstacle.
You don’t need another proposal. You need a partner.
If you’ve made it this far, you probably already know what needs to change. The harder part is getting everyone else to see it.
That’s where the right digital partner can make a meaningful difference.
A good partner should do more than estimate hours and hand you a scope of work. They should ask hard questions about the problem you’re solving, help you quantify the opportunity, identify risks you may not have considered, and translate technical decisions into language your leadership team can act on.
They should also be willing to tell you when a $150,000 project isn’t the right answer.
Because digital transformation isn’t about buying technology. It’s about improving how your organization operates, serves its customers, and grows. The technology is simply the means to get there.
So when you’re evaluating partners, don’t just ask, “Can they build it?” Ask, “Can they help us make the case for why we should build it?”
That’s the kind of partnership that turns a stalled idea into meaningful change.
If you’re struggling to get a digital initiative off the ground, we’d be happy to talk it through. Contact Creed to start the conversation.