I build the automation that takes the operation off your plate — so the evenings, weekends, and white space come back. For your family. For the next venture. For whatever "free" means to you.
It's not one big thing.
It's the estimate that ate Sunday night. The dispatch call at 2 a.m. The marketing post that never went up. The vendor renewal you noticed a week late.
Every workflow that still needs you to run. That's the seam — where the hours you thought you'd stop paying keep quietly getting paid.
It's not one big fire.
The merger integration that pushed your support teams underwater. The AI vendor pitching your team while the toil that started it all stays untouched. The recurring incident nobody's had time to root-cause since Q2.
Every workflow that keeps escalating to the same three people. That's where the money goes.
Software fits the vendor's average customer, not your business. Consultants hand you advice and an invoice. Freelancers finish the job and move to the next client. Forward-deployed engineering is the model built for what's missing: one engineer embeds in your business, builds the fix, and stays accountable for it. You're not buying a deliverable. You're buying an outcome — backed by someone who doesn't get to walk away from it.
Right now, you are the forward-deployed engineer of your own business. Every exception, every judgment call, every "just let me handle it" runs through you — because you're the only one close enough to own it. That's the bottleneck, and it costs real money: every hour you spend running the business is an hour not spent growing it. The fix isn't more software. It's a second person who can own the problem the way you do.
Built for the vendor's average customer, not your business. You pay the license, then spend your own time working around what it can't do.
Bills you for the diagnosis, then leaves you to make it actually work. The risk is yours the moment they walk out the door.
Cheapest quote up front — until it breaks. Then you're paying someone new just to relearn your business from scratch.
One person, one relationship, accountable from the first conversation to the 2 a.m. fix. You never pay someone new to relearn what already works.
Every engagement starts by finding what's eating the owner's week. Every deliverable is a system that runs after I leave — because I don't leave.
The dispatch bottleneck. Every load, every reroute, every HOS check ran through one human — 15 minutes of clicks and lookups per decision. Late pickups and compliance violations were caught after the fact, sometimes at 2 a.m. Rebuilt the flow around an AI assignment engine that scores HOS, equipment, weather, and customer windows on every load, and flags exceptions before they escalate. Dispatch decisions now take seconds.
Estimates ate Sundays. Walking sites by day was fast; nights got burned on copy-pasting catalog SKUs, reconciling labor rates, formatting quotes. Customers waited days for proposals. Built a voice-first estimating system: dictate scope on-site, the system matches the QuickBooks catalog and labor rates, priced PDF lands in the customer's inbox before you're back in the truck.
Marketing was always "next week." Weekly posting matters for hires, buyers, and staying top-of-mind — but doing it meant becoming a part-time copywriter, designer, and scheduler. Built a publishing system that learns brand voice once, generates platform-specific content on a schedule, and asks for nothing more than a five-minute weekly approval.
A continuous loop, not a project handoff. Most automation projects die because the consultant ships and disappears. I run the system after launch — so it gets better while you sleep.
Walk the operation. Watch where hours go that shouldn't. Identify the friction point worth removing first.
Custom system designed around your actual workflow — not a template, not a SaaS subscription. Your data, your rules.
Monitoring, uptime, exception handling, vendor management. You don't inherit a maintenance burden — because I don't leave.
Watch the system in production. Spot the next friction point. Tighten the loop. Then back to Discover.
Most engagements combine two or three of these. Some start with a fractional seat and grow into a full rebuild.
I'm William Pimentel. By day I lead ITSM at Truist — a 160+ staff global Service Desk transformed through a major bank merger. Before that, five years of infrastructure leadership at Office Depot / CompuCom — 40+ staff, Fortune 500 SLAs, 15-minute MTTR on major incidents. Before that, PCI compliance remediation and self-service portal design at CompuCom.
Since 2019 I've been running TekOmni in parallel — as fractional CTO, director, and builder for SMB clients across finance, logistics, and engineering. That's where the enterprise discipline gets applied at SMB cost and speed. Microsoft 365 estates, Intune, Entra ID, DLP frameworks that pass IRS and DOT/FMCSA scrutiny — and custom AI systems that take the operation off the owner's plate. Bilingual EN/ES policies, SOPs, and driver-declaration forms when the workforce needs them.
The SMB owner's real objection isn't "can he build it?" — it's "can he run it when it breaks at 2 a.m.?" The answer is on my resume for the last decade.
Pick any open slot below. Calendar invite lands automatically. We'll spend 30 minutes on the part of your operation that's draining time — and whether it's worth automating.