"It works fine next to the router and nowhere else."
Details →What a project
actually looks like
Seven situations I'm set up to handle, start to finish. Open any one for the full scope. These are illustrative scopes, not a menu. Most real jobs are some combination, and every one starts with a look at what you actually have.
"We need a website, but the quotes are all for a brochure we could have made ourselves."
Details →"A guest is texting me about the wifi and I'm an hour away."
Details →"Every new hire costs us a day of clicking through setup screens."
Details →"We're paying monthly, per person, forever, for things we could just run."
Details →"We'd use AI if we were allowed to upload anything to it."
Details →"It grew one device at a time and nobody planned any of it."
Details →Home network that actually covers the house
Dead zones upstairs, video calls dropping, one ISP box trying to be a modem, router, firewall, and access point at once, and no idea what's actually connected.
What I do
- Walk the house and survey actual signal, not guesswork
- Run wire where it matters, so access points are fed properly
- Place real APs for coverage instead of chaining extenders
- Separate guest and IoT traffic from the machines you care about
- Replace the ISP box's firewall with something you control
- Label the rack, the runs, and the panel
What you end up with
- Coverage in every room, including the ones that never worked
- Guests and smart devices walled off from your own
- A written map of what's on the network and where it runs
- Someone to call who already knows the layout
Short-term rental you can manage from anywhere
Guests on the same network as your own devices, a router nobody can reset remotely, and no way to tell whether the problem is the ISP or the access point without driving out.
What I do
- Guest network fully isolated from anything you own
- Hardware that survives constant turnover and nightly reconnects
- Remote management, so most problems get fixed without a drive
- Monitoring that tells you the internet is down before a guest does
- Exterior cameras and smart locks, disclosed and within platform rules
- Apple TVs and tablets locked down, so guests can't leave accounts signed in
- A one-page sheet for guests and one for you
What you end up with
- Wifi that stops generating messages at 9pm
- Your own network private, even with strangers in the house
- Remote eyes on whether the place is actually online
- The same setup repeatable across additional properties
Small business IT foundation
One flat network where everything can reach everything, backups nobody has ever restored from, and remote access set up years ago by someone who left.
What I do
- Firewall policy and segmentation so a bad laptop isn't a bad day
- Sort out who has access to what, and remove what's stale
- Backups with a restore actually tested in front of you
- Replace ad-hoc remote access with something scoped and current
- Runbooks, diagrams, and credentials handed over properly
What you end up with
- A known-good baseline instead of accumulated history
- Proof your backups work, not an assumption
- Documentation any technician can pick up
- A clear picture of what's exposed and what isn't
Company devices that set themselves up
A mix of Macs and Windows machines configured by hand and never quite the same twice, apps installed ad hoc, no way to wipe a laptop that walked out the door, and no honest answer to which devices are actually up to date.
What I do
- Enroll the business in Apple Business Manager or Microsoft Intune, so devices belong to the company rather than to whoever set them up
- Zero-touch deployment: a new machine configures itself out of the box, before anyone hands it over
- Push apps, wifi, and security policy centrally instead of device by device
- Tie device access to identity in Entra ID, so disabling an account cuts off the device with it
- Remote lock and wipe for lost hardware or departing staff
- Enforce updates and disk encryption, with visibility into what's actually compliant
- Lock shared or public-facing devices into a single app
What you end up with
- New hires working on day one instead of day two
- A lost laptop that's an inconvenience, not an incident
- Every device on a known, repeatable configuration
- One way of working across Mac, Windows, and mobile
- Hardware that stays company property through turnover
Replacing subscriptions with hardware you own
File storage, notes, passwords, and media all rented from vendors who raise prices annually and hold your data on their terms.
What I do
- Work out what's genuinely worth self-hosting and what isn't
- Spec and build the server, sized to what you actually use
- Deploy the replacements and migrate the data across
- Secure remote access so it works off-site too
- Backups, monitoring, and a handover doc
What you end up with
- A fixed hardware cost instead of a growing monthly one
- Your data on equipment you control
- No per-seat penalty for hiring people
- An honest list of what stayed in the cloud, and why
Private AI on your own hardware
The useful documents are the confidential ones, and policy, contracts, or a compliance obligation rule out sending them to a third-party service.
What I do
- Spec and build the GPU host, sized to the models you need
- Run inference behind your firewall, nothing leaving the building
- Index your documents so answers cite the file they came from
- Connect it to the tools people already work in
- Sit with the team until they trust the answers
What you end up with
- An assistant that knows your business and cites its sources
- No customer or contract data leaving your control
- No per-seat AI subscription
- A straight answer on where it should not be trusted
A website that actually does something
Plenty of people will sell you a template with your logo on it. The harder question is whether you need a page that describes your business, or a tool that runs part of it, such as a booking form, a customer portal, a dashboard, or a place for staff to log something. Those are different builds, and being sold the wrong one is expensive.
What I do
- Work out first whether you need a site, an application, or a site with one feature that matters
- Build it to load fast and work properly on a phone, because that's where it'll be opened
- Wire in the function: forms, bookings, logins, portals, dashboards, or a feed from a system you already use
- Set up the domain, certificates, and email routing so it all points where it should
- Host it somewhere with a cost you can predict, self-hosted or cloud
- Hand over documentation so you can change the words without calling me
What you end up with
- A site that loads instantly and looks right on every screen
- The one thing you actually needed it to do, working
- Hosting and renewal costs you understand ahead of time
- No monthly platform fee for a page that rarely changes
- Someone to call when it needs to grow
Keeping it running afterward
Every one of these can end at handover, with documentation good enough for you or another technician to take it from there. If you'd rather not, ongoing support is available monthly and is usually the better deal for rentals and businesses without their own IT.
- Remote monitoring and alerting
- Firmware and patching kept current
- Priority response when something breaks
- Backups verified, not assumed
- Quarterly review of what changed
- Changes and additions as you grow
Not sure which one you are?
Most jobs are a mix. Tell me what's broken and I'll tell you what it takes.