When operations get messy, most teams respond the same way: they hire.
Another person will handle tickets, another manager will track follow-ups, and another body will patch the gaps between systems that don’t talk to each other.
But what if you didn’t need more people? What if the answer was connecting the systems you already have?
Tod Ellington, VP of Operations at Whitestone, shares how he built scalable, post-sales operations. Not by growing the team but by fixing handoffs, improving visibility, and rolling out tools that work together.
Most ops teams are stuck working around broken systems
Before Hiver, Asana, and Zoho Analytics, Whitestone’s support workflows were duct-taped together.
They were using shared email accounts with shared credentials. There was no ownership, tracking, or clear way to escalate issues, so important messages were slipping through. Support hours, often billable, were tracked manually in a Google Sheet.
“It wasn’t secure. It wasn’t efficient,” Tod says. “And no one really knew who was responsible for what.”
Instead of hiring someone to fix the mess, he cleaned up the foundation. He introduced shared inboxes, tagging, and real-time task tracking, making everything visible in one place.
Systems that hold everything together
Tod’s operational philosophy is simple: structure gives speed. You don’t scale by doing more. You scale by doing things better.
At Thumbprint, his previous company, Tod helped launch over 120 ecommerce stores and scaled the platform to 45,000+ active users, all without layering on extra teams.
What made it work wasn’t headcount. It was clarity.
“You can’t just throw more people at problems,” he says. “You need systems that allow you to scale.”
That mindset carried over to Whitestone. Even though nothing was broken, Tod focused on adding enough structure to support growth, without slowing people down.
Pilot. Measure. Scale. Then invite everyone in.
Tod doesn’t roll out tools company-wide on day one. He starts small.
Hiver was tested first with the support team. Asana was introduced with clearly defined SLAs. Each time, the approach was the same: pilot in one place, build a process around it, and let other teams opt in once the value was clear.
The result is buy-in without burnout, adoption without resistance.
“It’s not about pushing tools on people. It’s about giving them something that actually helps. Once they see that, they want in.”
Visibility is everything, especially when things get busy
As operations expanded, the payoff became clear.
Every client request, task, and email was tagged, tracked, and linked to metrics in Zoho Analytics. Teams could see exactly where things stood, by client, department, and request type, in real time.
For Tod, that visibility made support billable, repeatable, and scalable.
Change doesn’t need to be top-down. It needs to be proven.
That’s why every new system starts with a champion who can show it works before others are asked to follow.
“You need to move fast enough to avoid paralysis,” he says, “but not so fast that you miss input that matters.”
Where AI fits (and where it doesn’t)
AI is already making an impact across Tod’s workflows. It’s helping automate internal coding tasks, build faster proposals, and save time across internal ops. But he’s clear: tools only help when you give them the right inputs.
“AI still needs human context,” he says. “You have to frame the problem properly.”
Even with tools like Hiver, he sees the potential in AI-generated insights, but he also knows that accuracy and accountability matter more than speed.
You don’t need more people. You need connected systems.
The takeaway from Tod’s story is that scaling ops doesn’t mean hiring more. It can also mean tightening what already exists.
When teams work off the same system, see the same data, and move through shared workflows, there’s less confusion and chaos.
And that’s what connected ops means: better tools and a better way to work.