I spent 14 years keeping business systems running. Now I use that background to build better workflows with AI.
Michael Charles
I work with service businesses that already have solid tools in place but still lose time to repeat work, messy handoffs, and manual reporting. My job is to clean that up and build something the team will actually use.
Before starting ZDIT, I spent 14 years in enterprise IT infrastructure. That meant Microsoft 365 and Google Workspace administration, security and compliance work, networking, migrations, and the day-to-day responsibility of keeping systems stable for real teams.
That background matters because most workflow projects do not fail on the demo. They fail in the details: bad permissions, messy source data, broken handoffs, and a team that was never brought along.
I have been inside those systems for a long time. So when I say I can connect AI to the way your business already works, I mean the actual data layer, approvals, ownership, and operational reality, not just the flashy part.
Why ZDIT exists
I kept seeing the same gap: companies were being sold big AI language, but nobody was taking responsibility for the boring, necessary work of fitting it into real operations. ZDIT exists to close that gap.
How I actually build
A typical build might use Claude or OpenAI for reasoning tasks, n8n or Make for orchestration, and direct API connections into systems like HubSpot, QuickBooks, Microsoft 365, Google Workspace, or your CRM and ERP. If the off-the-shelf tools are not enough, I write code.
The engagements are fixed-scope and fixed-price. I map the work, rank the best opportunities, build inside your stack, and hand over documentation and training before I step out.
Fixed scope
You know what is being built, how long it should take, and what the decision points are before work starts.
Straight answers
If the process is too messy or the value is too thin, I will say that early.
Handoff built in
Documentation, training, and ownership transfer are part of the job, not an afterthought.
I stay close to the work.
The person you talk to is the person building the system and handling rollout.
The point is adoption, not a deck.
A clean recommendation is useful only if it can survive contact with your real tools and real team.
I start with the stack you already have.
Most teams do not need a new platform. They need the current process tightened up and connected properly.
I would rather lose a deal than force a weak project.
If I cannot make a credible case for the work, I will tell you that before you sign anything.
What to expect
Response time
I respond to inquiries within 24 hours. During active work, I reply within one business day.
Communication style
Direct and plain. Short updates, clear decisions, and no consultant theater.
Week by week
Discovery is usually 1-2 weeks. Build work runs on a defined cadence with weekly checkpoints. Outcomes get measured against the baseline we agreed on at the start.