Stefo Tech

Selected work

Different industries, the same job: make it reliable and write it down.

A few representative engagements. Clients are anonymized on purpose. Sensitive environments stay confidential, which is part of how I work.

Small business and professional services Recurring

A small office that needed one accountable person for all of its IT

The situation

A small team with no internal IT, juggling accounts, devices, backups, and vendors in their spare time, with no clear owner when something broke.

What I did

Took ownership of identity and endpoints, set sane security and backup baselines, handled vendor coordination and escalations, and documented the environment end to end.

The result

One number to call, predictable support, and an environment where the lights stay on without anyone on the team having to become the accidental IT person.

Churches, schools, non-profits Project plus ongoing support

A church and school that needed a managed device fleet and a real network

The situation

A faith-based organization running a fleet of tablets for classroom and ministry use, on a network that grew without a plan. Lean budget, no internal IT, and a need for things to simply work without babysitting.

What I did

Centralized device management with zero-touch enrollment for the classroom tablet fleet, then redesigned and installed the network with proper segmentation and reliable Wi-Fi across the building.

The result

Devices that configure and recover themselves, a network that holds up under real use, and documentation so volunteers and staff are not stuck when something needs attention.

Claude Setup My own practice, daily

A one-person practice I use Claude to run every day

The situation

One operator carrying a retainer client, a steady stream of tickets, statements of work, invoices, and time tracking. Too much context to hold in one head, and all of it has to be written down anyway.

What I did

Gave Claude the standing context the business runs on: clients, rates, contract rules, house style. Built workflows for ticket intake, reply drafts, time capture, and statement-of-work drafting. Wrote the rules down, including what never goes in, starting with protected health data.

The result

Every ticket gets a worklog and a time entry before the session ends. Client replies start as drafts in my voice that I approve before anything is sent. It is the same setup a Claude Setup client gets, sized to their business.

Healthcare revenue cycle Ongoing engagement

A behavioral-health RCM firm that needed an IT backbone and better tools

The situation

A small revenue-cycle advisory firm serving multiple behavioral-health clients. Sensitive files moving by email and spreadsheet, a help desk that needed structure, and recurring file workflows eating staff hours.

What I did

Administered identity, email, devices, and calling across five behavioral-health client projects. Stood up a ticketed help desk. Built five production browser-only tools for remittance conversion, file validation, roster matching, exclusion screening, and provider directory search, so protected data never leaves the firm.

The result

Remittance files become a clean three-sheet Excel workbook in seconds. Roster cross-references that took hours finish in minutes with a documented diagnostic. Exclusion screening runs against seven public sources, more than eight million records, with an exportable audit trail. Monthly deliverables are now repeatable instead of heroic.

Your situation is probably on this list, even if your industry is not.

The common thread is not the vertical. It is a team that needs its systems owned, made reliable, and documented. If that is you, tell me about it.