The spreadsheet tax
AI gets you 80% of a working sheet. Then you change one column and every formula downstream breaks, and now you're debugging a spreadsheet instead of running your business. The 80% was never the hard part.
Operations systems for owner-operators
I build custom operations dashboards for owner-operators — the people running two locations, two jobs, and no ops team. Due dates, task capture, cash flow, recurring bills. One place. Built for you, not configured by you.
Working software in 14 days · fixed fee · you don't build a single spreadsheet
Why this keeps failing
Every project-management platform on the market assumes you have someone whose job is to run the project-management platform. You don't. You have a business to run.
AI gets you 80% of a working sheet. Then you change one column and every formula downstream breaks, and now you're debugging a spreadsheet instead of running your business. The 80% was never the hard part.
Sprints, epics, story points, workspaces, custom field dependencies. Consulting vocabulary invented for software teams, sold to people who make physical things. If you have to learn a new language to see your own numbers, the tool failed.
The platform is capable. It is also empty, and it stays empty, because populating it is a second job. Nobody tells you the license is the cheap part and the setup is the expensive part.
“For all the hype around these AI systems, I haven't been able to get anything functional out of any of them. I don't want to spend days trying to build something that is never going to work.”
— a small business owner, publicly, this month
What I build
Not a platform I resell. Not a template I recolour. A system built around how your business actually runs, using AI where it earns its place and boring reliable software everywhere else.
One screen. Everything with a deadline, everything with a dollar sign, across every location you operate.
The to-do that arrives while you're mid-shift with wet hands has to land somewhere in under five seconds, or the system is already dead.
Recurring obligations auto-populate themselves. You should never hand-enter the same bill twelve times a year.
The technical operations person you can't justify hiring full-time, for a fraction of the salary.
How it works
Your total time investment is about three hours. I do not send homework, I do not ask you to fill in a template, and I do not need you to "get your data ready" first. Messy is fine. Messy is expected.
We walk through how the business actually runs today — every recurring obligation, every deadline, every place a number currently lives. I map it. You keep the map whether or not you hire me.
This is the part that stops everyone else. You do not build the data structure — that's the actual work, and it's mine. I set up the underlying system, migrate what you already have, and wire the pieces together.
You get something clickable in the first week, not at the end. You will know whether this is going to work long before the money is fully spent — which is the entire point.
Real data, on your phone, in daily use. One walkthrough session. Plain language, no jargon, and written notes you can hand to a manager. Then you decide about ongoing support — with the thing already working.
Pricing
You should not have to sit through a discovery call to find out what something costs. Fixed fee, agreed before anything starts. No hourly billing, no scope surprises, no invoice you didn't see coming.
01 — Teardown
Free
45 minutes · no obligation
A working map of your operation and an honest answer about whether software would actually help.
02 — The build
$2,400 fixed
14 days · one working system
Your dashboard, your real data, live and in daily use inside two weeks.
03 — Standing
$850 / month
Optional · cancel anytime
I keep it alive and keep it useful as the business changes underneath it.
$1,200 to begin, $1,200 once the system is live and you've used it for a full week. If it isn't working by then, you don't owe the second half and you keep everything built so far. The risk of this not working is mine to carry, not yours.
Who you'd be working with
I'm an engineer who builds AI-driven software: multi-agent orchestration systems, voice-controlled desktop applications, and the connective tooling that lets AI models actually operate real software rather than just describe it. That's my day-to-day work, not a certificate I picked up.
Which is exactly why I'm cautious about it. I know precisely where these models are genuinely useful and where they quietly produce confident nonsense. In an operations system, AI belongs in a few specific places — reading messy input, sorting and categorising, drafting, catching what you'd miss. Everything else should be plain, predictable software that works the same way every single time. Most AI consultants have that backwards, which is why their builds fall over in month two.
I work with owner-operators: the people who are simultaneously the CEO, the ops manager, the bookkeeper and the person unlocking the door. You are not short on capability. You are short on hours and on someone who will do the unglamorous structural work for you.
Norok is my own practice, and I'm deliberately taking a small number of clients right now so each one gets built properly. If you're reading this, you're early — and priced accordingly.
Start here
Tell me what's currently living in your head, on a whiteboard, or in a spreadsheet you're afraid to touch. If I don't think software will help, I'll tell you that — it's a faster answer and a cheaper one.