AASSCC is one senior pair of hands across the bits of your business that quietly keep it running. AI integration and team training, websites, Google Workspace and Microsoft 365, email and DNS, cyber security, and the Apple and Windows machines your team works on. One person, joined up, on retainer.
AASSCC /ɑːsk/
verb. to put a question, to seek help,
to get the broken thing fixed today.
Also: the initials of my kids,
put together. I’m nostalgic like that.
Seven services, one person across all of them. The work is joined up on purpose: an email problem gets fixed in a way that also tidies the DNS, an AI training session gets built around how your team actually works, and a website rescue leaves the rest of the stack in better shape than it found it.
For teams using AI in theory but not yet in practice.
Three ways in: a training session built around how your team actually works, an infrastructure audit to find where AI genuinely fits your workflow, or a pilot project to prove the value before committing. The goal is AI as something your team reaches for every day, not a tab nobody opens.
The day-to-day running of your technical stack.
The fiddly infrastructure work a growing business needs but cannot justify a full-time head of IT for. On retainer, quietly, so your team can get on with the actual work.
WordPress, custom builds, and the stack that faces the public.
WordPress recovery, performance, and maintenance are the bread and butter. Custom and static sites where they are the better fit. The hosting choices that make everything else easier, and a handover that means your team can actually use what we build.
Setup, admin, and the quiet tidying that keeps accounts sane.
Tenant setup, joiners and leavers, shared drives that don’t turn into swamps, MFA rolled out without a revolt, and the sensible security posture underneath it all.
Deliverability that just works, and the awkward moves that don’t.
SPF, DKIM, DMARC, domain transfers, the emails that mysteriously stopped arriving, and a DNS zone that finally reads like it was written by one person rather than six.
Sensible hardening for teams without a security department.
Good security is mostly unglamorous habits done consistently. Practical policies, proper backups, sane access controls, and an honest conversation about what you actually need to protect.
Apple-heavy fleets, mixed estates, and launch-day laptops.
Procurement, provisioning, MDM, and the quiet rebuild when something goes wrong on the Monday of a launch. Cross-platform when it has to be, opinionated when it helps.
A few things people have said on the first call this year. If any of them sound close to home, the fix is usually less dramatic than it feels.
The site’s down and nobody knows why.
We bought Copilot licences for everyone and nobody really knows what to do with them.
Our emails aren’t arriving and a client is getting annoyed.
DNS and email got set up by three different people over six years and now nothing quite makes sense.
Half the team is using AI and the other half thinks it’s cheating. I don’t know what to tell either of them.
We think someone in the team was phished. What do we do now?
We know we need proper security, we just don’t know where to start.
I can see AI should be saving us time. I just can’t work out where to start or who to trust to set it up properly.
The WordPress site has been nearly fine for a year and it’s getting worse.
The person who set everything up has left and nobody has the passwords.
We tried an AI workshop. Came out more confused than when we went in.
We’re moving to Google Workspace on Friday and it is not going well.
Any of these? Ask.
Start a conversation →Four ideas that shape every engagement. Expect the first to come up on the first call, and the rest to be quietly doing the work in the background once we’ve started.
Most of the expensive problems in a small business sit in the gaps between web, IT, security, and operations. Having one person who sees the whole picture means the fix lands in the right place, not the nearest one.
In practice: an email deliverability rescue that also tidies your DNS and hardens the domain, in one engagement.
Sites down, accounts locked, inboxes dark, failed migrations, ransomware scares. The tone on the other end of the phone is part of what you’re paying for. Competent, unhurried, honest about what we know and don’t.
In practice: a real assessment inside the hour, and a clear plan before anything gets changed.
Break-fix is expensive and stressful for everyone. Retained support costs less over a year, catches problems earlier, and means the person on the other end already knows how your stack is wired when something does go wrong.
In practice: monthly retainers with a small standing allocation and a clear runway for the bigger pieces of work.
Technical decisions framed as business decisions: what’s the risk, what does it cost, what does it buy you back. No fear-based upselling. No vague invoices. No phrases that read like they were written by a committee.
In practice: short emails, itemised quotes, and an honest no when something isn’t worth doing.
Three recent engagements, presented as brief case notes rather than portfolio shots. Two are client-facing websites. The third is the kind of operations work that never shows up in a portfolio.
Two clients, both on retainer for more than five years. A third slot is held open for a newer engagement once the work has settled.
I couldn’t manage my digital life without you.
I appreciate you every day.
AASSCC is run by one person. A short biography is usually more useful than a long one, so here is the short version.
I’ve spent the last twelve years being the person small businesses call when the digital stack quietly stops making sense.
Before that, a decade inside agencies and in-house teams looking after websites, email, cloud platforms, and the mixed fleets of laptops that the people running the business actually use. The work has always sat across disciplines. I kept noticing that the expensive problems lived in the gaps, so I built a practice around closing them.
I work this way because it’s the kind of support I wish my own businesses had been able to buy when I was younger. One competent person, paid fairly, there for long enough to understand how things are wired, trusted to make sensible calls without a meeting. That’s it.
In practice, working with me feels like a quiet, responsive email thread with someone who already knows your setup. Short messages. Itemised quotes. A phone call when something is on fire, and a plan before anything gets changed. If that sounds useful, the easiest next step is a thirty-minute conversation.
A real human reads every message. Replies typically land within a few working hours, or sooner if you tick the urgent box.