The same person, from first call to fix

Why we exist

Why we work this way

One Degree AI is run by Nick, from Singapore.

I started it after seeing the same pattern too many times. A small business either has no IT support at all, or it has a vendor who set something up once, disappeared, and reappears only to invoice. Either way nobody owns the basics — and nobody notices until something breaks.

Meanwhile someone on the staff has quietly become "the computer person" on top of their actual job, and nobody has looked at the backups in two years.

So this practice is deliberately small and deliberately senior. No sales team, no account managers, no layer of junior staff billed at senior rates. The person who scopes your work is the person who does it, and who already knows your setup without reading back through a ticket history.

That has real trade-offs, so here they are. You get someone who answers directly and has no incentive to sell you work you don't need. What you don't get is a 24-hour staffed operations centre or capacity for a 500-person rollout. If that's what you need, I'll say so on the first call and point you somewhere better.

I came at this from security first — from breaking into companies for a living. What became obvious was that most of what I found wasn't clever attacks. It was basic IT hygiene nobody owned: shared passwords, no MFA, ex-staff accounts still live, a server everyone had forgotten was on the internet.

You can't fix that by selling a security report to a business that has no IT function. You fix it by being the IT function, and building it properly from the start. That's why security is included in the plans rather than quoted as an upgrade — and why the AI work sits on top of a foundation that actually holds.

The name comes from how the work goes. A single degree of course correction is invisible on the day and decisive over a year. One automation that removes four hours a week. One backup that gets restore-tested. Small, finishable changes that compound — rather than a transformation programme that dies in week three.

Scope & ethics

What we will and won't do

We hold administrative access to our clients' businesses. That deserves explicit boundaries rather than assumed goodwill.

• We access client systems only for agreed support and maintenance purposes, and our access is logged.
• Security testing happens only on systems you own or are contractually authorised to have tested, confirmed in writing before we begin.
• Every testing engagement runs under a signed rules-of-engagement document covering scope, timing, exclusions and emergency contacts.
• We take the minimum evidence needed to prove a finding. We don't extract data to make a point.
• Your data is not used to train anything, and testing is never subcontracted offshore.
• We won't monitor your staff's personal activity, and we'll push back if asked to.
• We decline work aimed at surveilling individuals or touching systems the client doesn't control.