18/05/2026
A client I've worked with for years sent me this on Thursday.
He wasn't briefing a new project.
He wanted to stop sending me projects altogether.
For years it was the same loop between us. He'd send a brief. We'd build the website. Invoice. Next one. It worked. Neither of us was unhappy with it.
Then we changed how DevHush runs.
Agencies get a plan, a queue, and a team that just handles the website work — instead of quoting it job by job.
He saw the new model and asked to start on the monthly plan. Then he came back and said he'd run it for 3 months.
I didn't pitch him that. He lived the project-based version for years and decided the queue made more sense than what he was already doing.
But the message that stuck with me was the one in between.
He has a client who is insisting on Wix instead of WordPress and won't change his mind. He didn't ask me "can you do Wix." He asked whether Wix was covered under the active tasks in the plan.
So let me clear this up for everyone reading, because it's a fair question.
WordPress is what we build. That's the core of DevHush and it's what the plans are built around.
But the website problem on an agency's desk is rarely just WordPress. Sometimes a client won't move off Wix. Sometimes it's Webflow. Sometimes Squarespace. We don't pretend those clients don't exist — when an agency on a plan has one, we handle it instead of sending them back to find someone else.
That's the actual shift in how he saw us.
He stopped thinking of us as the people who build the WordPress site.
He started thinking of us as the team that takes the website problem off his desk — including the client who won't budge on platform.
That's usually how this goes. Nobody gets argued out of project-based work. They quietly notice it's been costing them, and they move.
If you're still running website work one quote at a time, the question isn't whether the queue model is better.
It's how long the project-by-project version has been costing you without you noticing.
