Night Owl IT began as one engineer's after-hours practice and is becoming a UK product business. This page is the whole of it: the story, the paperwork, the person, the principles, and the products.
Night Owl IT started the honest way: a Lead Salesforce Engineer with an enterprise day job, building carefully in the evenings. The name was never marketing. This is what gets made after dark, when the room is quiet and there's time to do things properly.
The practice grew a body of work that most small shops never attempt: a household voice assistant with a real threat model, a trading system with seven independent risk layers, multi-agent AI pipelines that commit to git like a disciplined colleague. Each one built with written scope, named threats, and a support story, because that's how enterprise engineering works and there was never a reason to do it worse at home.
Now the practice is becoming a product business. The first product to reach the public is WorkRecap, a private workday journal for Windows, and the discipline behind the consultancy carries straight over: software you can buy from a business that has terms you can read, a privacy policy that means something, and a human who answers email.
Night Owl IT founded as an after-hours engineering practice: bespoke systems, automation, and AI tooling, built to enterprise habits.
JEEVES, GoldBot, and the multi-agent author's studio take shape. Threat models, risk stacks, and productisation plans are written before launch plans.
WorkRecap opens its waitlist as the first commercial product. The company page, terms, and policies go up ahead of the first sale: trust before transactions.
If you're deciding whether to buy software from us, this is the part you're entitled to check. No hunting through footers.
The day job is enterprise Salesforce: integrations, AI tooling inside the platform, and long-running estate work where a sloppy decision costs months. That environment teaches habits that small software companies usually skip: threat models, rollback paths, written scope, restore drills. Night Owl IT exists to apply those habits to products normal people can buy.
Being a one-person company is a choice, not a stage. It means the person who designed the security model is the person who answers your support email. It also means the company is honest about limits: response times are stated in writing, and work isn't taken on unless it can be done properly.
If you need a script in a hurry, this isn't the right shop. If you want software and systems built by someone who thinks about your problem the way an engineer with an enterprise pager rotation thinks about their own, welcome.
A small set of principles, applied consistently. They protect the customer, the work, and the relationship, in that order.
Every system gets a written threat model before code is written. Step-up auth, signed artefacts, network segmentation, audit streams: these are baseline, not bonus.
Scope creep is how good projects fail. Every engagement comes with a written list of things explicitly not being built, and the conditions under which that might change.
Documentation, restore drills, rollback paths, and a written support model are part of every delivery. A system without a recovery story isn't finished.
Products are local-first wherever the problem allows it, telemetry is opt-in or absent, and the privacy policy describes what the software actually does, not what a lawyer hopes it might.
Terms you can read in one sitting, refund rules stated up front, and a company page that shows the registration details. Trust is engineered like everything else.
WorkRecap is what's for sale. JEEVES is what's being built. Both carry the same engineering standard: local-first architecture, written security models, and honesty about which stage they're at.
Your day, remembered.
A private, local-only workday journal for Windows. It remembers what you worked on, transcribes on your own machine, and writes a daily summary only you can read, encrypted to your login, summarised by an AI you choose, including one that never touches the internet. Reports to you, not your boss.
The household assistant that stays home.
A multi-room, locally-hosted voice assistant: a brain on your own PC, Raspberry Pi satellites, biometric step-up authentication, and a signed tool catalogue. Not a cloud service: your household's data never lives on our servers, because there aren't any. Still being built, and lived with, in the founder's own home. It goes on sale only if it earns its way out of the lab.
Whether you're buying a product licence or commissioning a build, the shape of the relationship is the same.
Scope, out-of-scope, support terms, response expectations, refund rules: written down before money moves, so there's nothing to argue about later.
There is no support tier, ticket triage, or offshore queue. The person who wrote the code reads your message and replies, typically within two working days.
A one-person company doesn't promise 24/7 SLAs, and won't pretend to. What it promises instead: stated response times, documented recovery paths, and no silent abandonment of shipped software.
Products are designed so that trusting us mostly isn't required: data stays on your hardware, encryption is bound to your own login, and the privacy policy documents the actual data flow.
Ask directly. Questions about the company, the products, or whether we're the right shop for your problem all land in the same inbox.