Home / Services
What the work actually involves
Six areas. They overlap on purpose — most real jobs touch three of them, and that's exactly the part other people can't quote for.
Websites & web applications
Sites that load fast, are easy to change, and don't quietly break. New builds, rescues of sites nobody has touched in three years, and the applications sitting behind them.
Delivered as a running system on real hosting — the certificate, the DNS and the mail path included — not a folder of files handed over.
Typical work: A full build · a rebuild of a site that has outgrown its shape · taking over a site nobody currently owns.
IT & technology management
Support for you and your staff, vendor wrangling, email and domains, accounts and access, and backups you can actually restore from.
This is a hurricane coast, so recovery is not an abstraction here. A backup that has never been restored is not a backup, and testing that is part of the job rather than an upsell.
Typical work: Standing support · taking over an estate nobody owns · getting backup and recovery to a state you'd bet the business on.
Data & reporting
The numbers your business already produces, pulled into one place and made readable. Dashboards, recurring reports, and integrations between the tools you're stuck with.
Most businesses don't have a data problem. They have six systems and no way to ask them a question at the same time.
Typical work: One dashboard that replaces a monthly spreadsheet ritual · joining two systems that were never meant to meet.
Automation
Small, specific, boring wins: reading documents so a person doesn't have to, routing intake, drafting follow-ups, killing recurring manual work.
Not a transformation programme. A shorter Tuesday. The right size for this is usually one annoying task, done properly, that never comes back.
Typical work: Intake that reads the PDF · a report that builds itself · the Friday retyping job, deleted.
Custom software
When there is no product to buy, it gets built. Line-of-business applications, integrations between systems that have no integration, and the interfaces your people actually touch.
This includes the deep end — machine learning, model training and evaluation — when the problem genuinely needs it. Most don't, and you'll be told so.
Typical work: A system that doesn't exist yet · replacing a spreadsheet that has become load-bearing.
Architecture & technical leadership
Deciding what to build, what to buy, and what to stop paying for. Fractional CTO and IT director work for businesses too small to need one full time and too complex to guess.
Often the most valuable thing that happens in the first month is that something gets cancelled.
Typical work: A second opinion before a big purchase · a plan for the next two years · owning the technical decisions outright.
Then describe the symptom, not the category
Half the jobs here don't fit one heading. Tell us what's annoying you and you'll get a straight answer on which of these it is — or that it's none of them.