Start a conversation

Automation built to survive production

One engineer, accountable for the entire stack.

I design, build, and run enterprise IT for small and mid-sized businesses — Power Automate and Power Apps automation, Microsoft 365 and Azure, and the network engineering underneath them. Assessment, architecture, and hands-on delivery, owned end to end by the person you actually talk to.

Start a conversationSee what I do
  • 27 yrsAcross military, healthcare, and manufacturing IT
  • End to endAssessment, architecture, and hands-on delivery
  • Remote-firstAvailable wherever the work can be done remotely

01 · Services

The work that usually gets split across three vendors.

Strategy, architecture, and hands-on delivery as one engagement with one accountable engineer. Two ways to work together: full-stack delivery, where I design, build, and administer the solution directly, and guidance and leadership, where I advise, architect, or oversee without doing the hands-on build.

Full-stack deliveryDesigned, built, and administered directly

  • Lead offer

    Power Automate & Power Apps

    Business process automation — design and engineering, guidance, and leadership. This is the lead offer.

    • Flow design and build for approvals, notifications, and data sync across Microsoft 365 and line-of-business systems
    • Power Apps model-driven and canvas apps on Microsoft Dataverse
    • Custom connectors and API integrations for systems without native Power Platform support
    • DLP-policy-aware automation that survives a compliance review, not just a demo
    • Architecture review and platform leadership for existing Power Automate / Power Apps environments

  • Microsoft 365

    Full-stack design and engineering, guidance, and leadership.

    • Tenant migrations, including hybrid and cross-tenant deployments
    • Identity, access, and security — Entra ID, conditional access, MFA
    • Ongoing Microsoft 365 administration and support
    • Architecture review and leadership for an existing Microsoft 365 environment

  • Azure

    Full-stack design and engineering, guidance, and leadership.

    • Azure IaaS design and deployment, including hybrid and multi-location environments
    • Migration planning and execution — on-premise to Azure, cross-subscription, cross-tenant
    • Azure identity, access, and governance
    • Architecture review and leadership for an existing Azure environment

  • Network Engineering

    Full-stack network, virtualization, and storage — design, deployment, and administration.

    • LAN/WAN/SD-WAN design, VPN and site-to-site connectivity
    • Wireless deployment and site surveys (Aruba)
    • Hybrid-cloud connectivity between on-premise and Azure/Microsoft 365
    • Firewall configuration and management (Fortinet, SonicWall)
    • VMware and Hyper-V virtualization design and administration
    • Storage, backup, and disaster-recovery infrastructure (Veeam); Citrix application and desktop delivery

  • IT Leadership & Advisory

    For organizations without a full-time IT director, this is that role — scoped to what's actually needed.

    • IT strategy, budgeting, and vendor management
    • Security posture and compliance program development (including HIPAA)
    • Project and program management across concurrent initiatives
    • Fractional / advisory IT leadership on a retainer basis

Guidance & leadershipAdvise, architect, and oversee — not the day-to-day build

For these areas I bring the same 27 years of hands-on Microsoft-stack experience to advise, architect, and lead — I'm not the one doing the day-to-day build.

  • Dynamics 365 Business Central

    What I take on

    Strategy, architecture review, and implementation-partner oversight, plus Power Automate automation built around an existing Business Central environment.

    Out of scope

    Setup, configuration, and migration of Business Central itself.

  • Data platform & reporting

    What I take on

    Guidance on modernizing legacy reporting and a migration path to Power BI / Microsoft Fabric, including small hands-on Power BI builds, plus automation directly against SQL Server data through Power Platform.

    Out of scope

    Hands-on SQL Server schema/stored-procedure development and new SSRS/SSAS report builds.

Beyond this list

27 years across military, healthcare, and manufacturing IT means most things running on the Microsoft stack — even outside the categories above — I can assess and speak to credibly. If it's not listed here, ask; I'll tell you plainly whether it's something I build, something I advise on, or something outside my lane.

02 · Approach

Solo is the feature, not the constraint.

Every hand-off in an IT project is a place for context to go missing. A one-person practice removes them structurally — there is no boundary to lose anything across.

The hand-off model

  • A salesperson scopes the work, an architect designs it, and a delivery team you have not met builds it.
  • Context is re-explained at every boundary, and detail is lost at each one.
  • When something breaks in production, the question of who owns it is the first thing to resolve.

This one

  • The person who scopes the work is the person who architects it and the person who builds it.
  • Nothing is re-explained, because nothing changes hands.
  • When something breaks in production, there is one name on it.

27 years, one continuous thread.

Today I run IT for a Colorado family-owned manufacturer that has been in business since 1936 — the entire stack, plus a team of four, supporting marketing, sales, R&D, quality control, in-house manufacturing, packaging, and shipping.

The work there is the kind FullCircuit exists to do: a ground-up network build — including 26 wireless access points — when the company relocated to a new warehouse facility, a 20-year-old homegrown manufacturing system migrated onto Dynamics 365 Business Central, and Power Automate and Power Apps solutions built on top of it, from shop-floor scanning of finished goods to automated product-label printing. I manage the Microsoft 365 and Azure environment for 140 users, including identity, endpoint, and security posture. Strategy, architecture, and hands-on build, owned end to end.

That approach was set early. I started in IT in the U.S. Navy in 1999 as an Information Systems Technician, holding a TS/SCI clearance and running communications and information-systems support for a command of several hundred people — where the habit of owning a problem to completion, not handing it to the next desk, took hold. From there: SQL development and reporting, then seven years as Director of IT at a Denver community health center — a network overhaul for on-premise EMR, EDR, and digital x-ray spanning 200+ users across sites, an Exchange-to-Office-365 migration, a cloud VoIP cutover, and the budgeting, HIPAA compliance, and staff management that came with reporting to the COO. I have also carried up to eight concurrent client projects as a senior professional-services engineer: Azure IaaS for a five-location healthcare provider, an Aruba wireless deployment of 80+ access points, and Microsoft 365 migrations totaling 2,000+ mailboxes — alongside a multitenant datacenter serving 100+ clients on a high-availability VMware cluster.

03 · Engagement

Three ways to structure the work.

The right structure depends on how well the scope is understood before the work starts. If that is not clear yet, an hourly assessment is usually the cheapest way to find out.

Pricing depends on scope and is quoted per engagement. Remote-first — I take on work anywhere it can be delivered remotely, with on-site arranged where a project genuinely calls for it.

04 · Contact

Tell me what you are trying to fix.

A short description of the problem is enough to start. I will tell you whether it is something I can take on, and which engagement model fits — including when the answer is that you do not need me.

Principal
Sean Schodowski
Availability
Remote-first, US-wide

Opens your mail app with the message ready to send. Prefer to write it yourself? sean@fullcircuitit.com