Too many human-dependent steps
A single joiner or leaver touches identity, licensing, groups, mail, SaaS applications, tickets, and notifications—with completion living in someone’s memory.
Project-based IT automation consulting
Get repetitive IT work out of the backlog.
I help internal IT teams automate employee lifecycle, Microsoft 365, Entra ID, SaaS provisioning, and other repeatable operational workflows—without adding another full-time engineer.
- Fixed scope
- Built alongside your IT team
- Documented handoff
Example workflow
EMPLOYEE LIFECYCLE
TRIGGERHRIS or approved request
Received
AUTOMATIONValidate, map, orchestrate
Controlled
IDIdentityCreate + update
MMicrosoft 365License + groups
SSaaSProvision access
ITITSMUpdate + notify
Still seeing these in the queue?
Manual new-hire setup Multi-system offboarding Repeated access tickets Spreadsheet reconciliationProblems I solve
Documented does not mean automated.
If an administrator still has to copy values, click through the same screens, or reconcile the same systems every time, the process is still consuming scarce IT capacity.
The same request, handled again
Recurring access, account, SharePoint, or Microsoft 365 tasks keep arriving as tickets even though the decisions and execution pattern are largely repeatable.
Systems that do not stay aligned
HRIS, identity, ITSM, and SaaS data drift apart, leaving administrators to compare records and correct discrepancies by hand.
Capable team, no project capacity
Your team could build the automation eventually. Operational work keeps winning, so the project remains designed in theory and manual in production.
Core services
Defined automation projects for internal IT.
Each engagement is designed around your systems, approval model, security constraints, and exception paths—not a rigid software package.
01EMPLOYEE LIFECYCLE
Employee onboarding automation
Turn an approved HR or IT request into a controlled provisioning workflow that handles the repeatable work and surfaces exceptions.
- Account creation and attribute mapping
- License, group, and mailbox actions
- SaaS provisioning and ITSM updates
- Validation, logging, and failure handling
Request→Identity→M365 + SaaS
02ACCESS REMOVAL
Employee offboarding automation
Execute time-sensitive access-removal steps consistently and produce a visible record of what completed, failed, or needs review.
- Sign-in block and session revocation
- Account, license, group, and mailbox handling
- SaaS deprovisioning and notifications
- Completion reporting and audit logs
Approved exit→Revoke→Verify
03OPERATIONS
Custom IT operations automation
Automate a well-defined administrative workflow or integration outside the standard joiner/leaver path.
- Microsoft 365 and Entra ID workflows
- Jira-triggered and scheduled processes
- REST API and PowerShell automation
- Provisioning, synchronization, and reconciliation
Event→Rules→Systems
Relevant hands-on experience
Microsoft 365Entra IDMicrosoft GraphPowerShellJiraOktaIntuneREST APIs
Selected work
Proof from production environments.
Three anonymized engagements, condensed from completed case studies. Results are limited to what was measured and confirmed.
~60 minto1–2 min
Microsoft 365 onboarding became a supportable internal service.
Challenge
Administrators manually moved Jira request data through account, license, group, mailbox, and SaaS provisioning steps for 15–20 onboardings per month.
Solution
A centralized FastAPI service used Microsoft Graph and PowerShell to execute approved provisioning, log activity, and route failures back to IT for review.
Result
Provisioning fell from about one hour to 1–2 minutes. The service has operated for roughly three years and is supported by multiple administrators.
JiraEntra IDMicrosoft 365GraphPowerShellOkta + SaaS
90%installed within14 days
Windows updates moved faster through a controlled five-ring rollout.
Challenge
Roughly 450 endpoints took about 21 days to reach 90% installation, but a faster process still had to protect test and critical populations.
Solution
Five Intune Update Rings staged a test group, three dynamic waves, and a final critical group with defined deferrals, deadlines, and grace periods.
Result
The first production cycle reached 90% installed coverage within 14 days with no observed increase in support issues.
Evidence note First-cycle result; no sustained seven-day outcome is claimed.
40 userswith0 mail downtime
Google Workspace mail moved to Microsoft 365 without interrupting delivery.
Challenge
An acquired organization needed 200 GB of email—and a broader 200 GB Drive migration—moved while preserving business communication.
Solution
Staged synchronization kept Google MX active, then forwarding, aliases, and an after-hours MX cutover moved mail flow to Exchange.
Result
The mail cutover completed with no downtime. Drive migration also completed through a validated process shared with the delivery team.
Google WorkspaceMicrosoft 365ExchangeOneDrive
Why a specialist
Additional project capacity—not another IT provider.
Your IT team already knows the environment, stakeholders, and business constraints. I bring focused engineering time to map one process, build the automation, test it against real conditions, and hand it back in an operable state.
That makes the engagement useful when the work is important enough to finish, but not broad enough to justify another permanent hire.
Discuss what is stuck
Good fit
Defined systems problem
- Clear workflow or operational pain
- Known systems and stakeholders
- Internal technical owner
- Measurable acceptance criteria
- Documentation and handoff expected
Not offered
General managed IT
- End-user helpdesk
- Broad break/fix support
- Device or printer repair
- On-site support
- 24/7 outsourced IT management
Engagement model
Scoped before it is built.
The process makes responsibilities, dependencies, failure conditions, and “done” explicit before implementation begins. Most projects are then quoted at a fixed price.
-
01
Discovery
Map the trigger, current steps, systems, owners, decisions, edge cases, permissions, and security constraints.
-
02
Scope
Define included systems, deliverables, exclusions, dependencies, responsibilities, and acceptance criteria.
-
03
Build
Implement the workflow, integrations, authentication, validation, logging, and operational controls.
-
04
Test
Exercise expected paths, permissions, retries, failure states, edge cases, and idempotency where relevant.
-
05
Handoff
Deliver appropriate documentation, explain operation and exception handling, and validate acceptance criteria.
-
06
Optional support
Keep the implemented automation healthy under a narrowly defined maintenance agreement if needed.
Who this is for
Internal IT teams with more automation demand than delivery capacity.
75–500employee target environment
1–8internal IT staff, typically
These ranges describe the intended customer profile, not past customer counts or engagement limits.
You likely already have:
- 01An internal IT owner
An IT Manager, Director, Systems Manager, or Infrastructure lead who can make workflow and access decisions.
- 02A Microsoft and SaaS environment
Microsoft 365, Entra ID, multiple SaaS applications, and meaningful joiner/leaver volume.
- 03A specific backlog item
A recurring process everyone agrees should be automated, but nobody has uninterrupted time to finish.
After the handoff
Keep the automation maintained—without turning it into general IT support.
Optional maintenance can include
- Monitoring the implemented solution
- Troubleshooting automation failures
- API and authentication changes
- Minor workflow adjustments
- Periodic automation health checks
Scope boundary
New automations, major redesigns, added integrations, and unrelated IT work are scoped as separate projects.
Practical questions
Before we talk.
Clear boundaries make a better technical engagement. If your question is not covered here, bring it to discovery.
Ask a project questionDo you provide general IT support?
No. This is project-based automation consulting—not helpdesk, desktop support, break/fix service, on-site support, or outsourced IT management.
Can you work alongside our existing IT team?
Yes. That is the intended model. Your team supplies environment context, decisions, access, and an internal owner; I provide focused capacity to scope and execute the automation project.
Are engagements remote?
Yes. Engagements are designed to be delivered remotely with defined access, communication, testing, and handoff expectations.
Do you work with Microsoft 365 and Entra ID?
Yes. Relevant project work includes Microsoft 365, Entra ID, Microsoft Graph, PowerShell, Jira, Okta, Intune, and SaaS provisioning. The exact scope depends on your environment and required workflow.
Can you integrate with our HRIS or SaaS platforms?
Potentially. Discovery confirms whether the systems expose suitable APIs, events, authentication methods, and permissions. I do not claim blanket support for every HRIS or SaaS product.
How are projects priced?
Projects are normally scoped first, then quoted as fixed-scope, fixed-price engagements. Dependencies, exclusions, responsibilities, and acceptance criteria are documented before the build begins.
What happens after the project?
You receive an appropriate handoff and documentation so your team can operate the solution. If you prefer not to own maintenance, a defined support agreement may be available.
Do you offer ongoing support?
Only for implemented automations and integrations. It can cover monitoring, failure troubleshooting, API or authentication changes, small workflow modifications, and health checks—not general IT support.
Start with the workflow
What is sitting in your automation backlog?
Bring one repetitive process, the systems it touches, and what a reliable outcome should look like. The first conversation is a technical fit check—not a general IT sales pitch.
Prefer email?
CONTACT_EMAIL