Identity, infrastructure, AI, and the code between them.
I build all of it.
Four ways to hire me
What I do
- Microsoft 365 and Entra — Identity, Conditional Access, Intune, Exchange Online, tenant migrations.
- Systems and IT Administration — The whole estate: servers, networks, endpoints, backups, the lot.
- AI and Automation Engineering — Agents, infrastructure, and pipelines that remove the work people still do by hand, give you business insights, and opportunity intelligence.
- Integrations and Custom Apps — Two or more systems that need to talk to each other, or when a custom solution is needed.
- SaaS — Multi-tenant architecture, billing, onboarding, APIs, and the integrations your customers keep asking for.
- CMMC Remediation — NIST 800-171 controls actually implemented, not just documented.
- Fractional CTO / CIO — Architecture calls, vendor picks, whether an estimate is honest, and team management.
I know what works because I've built it, and what doesn't because I've fixed it.
Twenty years across Microsoft 365 and Entra, the server and network estate, custom apps and integrations, and the AI that removes work people still do by hand. Most companies staff that with three people and a vendor.
All four ways · no retainer · no minimum · no agency layer
Twenty minutes, no pitch. Tell me what's costing you the most money, time, or pain, and I'll tell you if I can fix it and roughly what it runs.
Four ways. Pick the one that sounds like you.
Same person, same rate, four different shapes. Most people know which one they are before they finish reading the first line.
On your payroll
Pick this if you want someone in house, not a consultant.
IT Administrator, Microsoft 365 Administrator, Systems Administrator, or AI Engineer. I work your hours, in your tools, on your team. Remote, Florida based, U.S. citizen.
- The tenant, the identity layer, the endpoints, and the automation nobody has had time to write
- AI built into how the company actually operates, same hire instead of a second one
- Available now, remote, and I can start inside a week
For the project you need finished
Pick this if you have a team already, and a job they cannot get to.
A defined deliverable with a start and an end. One week to one month is typical. Or somebody left and you need the work covered starting Monday.
- Connect two systems that should have been talking, or kill the daily copy-paste job
- Tenant migrations, Intune buildouts, or a stalled project taken over and landed
- Everything runs in your accounts and is documented as I go
For the decisions, not the tickets
Pick this if you are making technology calls with nobody senior to check them against.
A fractional engagement, about a week a month rather than full time. You get an opinion with a reason attached, every time, from someone who has built the thing being decided about.
- AI strategy that ends in working systems instead of a deck
- Build versus buy, vendor and quote review, infrastructure and scaling decisions
- Hiring developers and IT staff, then managing and overseeing them
Under your logo
Pick this if you run an MSP and a client is asking for something your bench does not cover.
I show up as your engineer. Your PSA, your documentation, your client, your invoice. Mark it up to whatever you bill it at.
- Entra ID, Conditional Access, Intune, tenant migrations, Exchange Online, GCC High
- CMMC and NIST 800-171 remediation, Graph and PowerShell automation
- I do not approach your clients, during an engagement or after one, unless you direct it
Same person in all four · no retainer · no minimum · no markup
One engineer, the whole thing.
Not a firm with a bench, and not a generalist either. The span is the point: the same person who runs the tenant writes the integration, and the one who picks the architecture is the one who has to live in it afterward.
7disciplines
One person
Identity and Entra, the server and network estate, AI automation, integrations and custom apps, SaaS platforms, CMMC, and the architecture calls. Most companies staff that with three people and a vendor.
1engineer
Scope to handover
Whoever scopes it is whoever builds it, documents it and hands it over. There is no second party to brief and no gap between them for the context to fall into.
0
Layers above the work
No account manager, no project manager, no bench billed alongside the engineer. You talk to me, and I am the one doing it.
Yours
Accounts, code and docs
It runs in your tenant, under your licenses, documented as I go. If I stop tomorrow you keep a working system and the notes to run it without me.
AI makes it fast. 20 yrs experience makes it right.
I won't sell you a chatbot or a strategy deck. I find the places in your business where a machine should be doing the work, and I build them. You see the first one running in week one.
Twenty years, and the part of it you actually need.
Eleven years in IT operations and managed services. Nine building SaaS and custom software. What follows is the overlap: the work companies are hiring for right now, and the proof I have already done it.
Replaced a Twilio dependency with an in-house service. Same functionality, one line item.
Built the internal platform that replaced them, carrying 19 live production integrations.
Built a CMMC Level 2 readiness platform for a client; the scoring engine covers every NIST 800-171 control and assessment objective on the DoD SPRS methodology, with a live read-only Microsoft Graph integration pulling tenant evidence behind the technical ones.
Led incident response on a live adversary-in-the-middle account takeover. Tokens revoked, tenant hardened, root cause written down.
Before that: managed services and hosting, development team management, senior technical project management, and four SaaS platforms including one acquired. A dozen IT environments. I have been the person who gets called at 2am, which is why I document everything.
One person. You talk to me. I do all the work.
Full-time, freelance, fractional CTO, white-label. Me in all four, working in your accounts and documenting as I go.
You get a scope and a number before anything starts. If it goes long you hear it before it does, not on the invoice. Everything runs in your accounts and is documented as I go, so nothing depends on me afterward.
The ones people actually ask.
Would you take a full-time role?
Yes. That is the first of the four ways to hire me, and it is a real option rather than a courtesy. IT Administrator, Microsoft 365 Administrator, Systems Administrator, or AI Engineer. Remote, U.S. citizen, available now. If you want to start as a contractor and convert, that works too.
How fast can you start?
Usually within a week, sometimes the same week. Ask about a specific week and you get a yes or a no in one reply. If I'm booked I will tell you rather than stringing it out.
What if I already have a development team or an IT provider?
Good, that is most of my work. I take the specific job they cannot get to, or the one that needs a developer rather than a technician. I work alongside them and I document everything so they can own it afterward. I am not there to replace anybody.
Is the AI work real, or is it a chatbot?
AI writes code fast; twenty years decides what should be built and verifies it is right. Anything touching money, permissions, or an audit trail gets validated by arithmetic and business rules rather than by a model's confidence, and anything that moves money gets a human approval gate. I will not sell you a chatbot or an AI strategy deck.
Do you work outside Florida?
Yes. Everything is remote and most of my clients are not in Florida. Florida based, U.S. citizen. Flexible hours across time zones.
I run an MSP. Will you approach my clients?
No. Not during an engagement and not after one. You own the relationship, I do the work under your brand, and I will sign whatever confirms that. Unless you direct it, I have no contact with them at all.
Tell me what's broken.
Twenty minutes, no pitch. Tell me what's costing you the most money, time, or pain, and I'll tell you if I can fix it and roughly what it runs.