● About
I build software for specific people — not for a market.
Ryan Fox. Systems builder in Harleysville, PA. I make small, durable software for operators, creators, and tight-knit businesses whose real work has outgrown the tools around it — and I increasingly put AI to work inside those systems.
The short version
The work usually starts with a sentence like "right now I do all of this by hand." That's the buying signal. I map the workflow, decide whether it deserves custom software, and build the smallest complete system that makes the work easier to run.
Sometimes that's a public order page and a private dashboard. Sometimes it's a booking board, a native app, a catalog site, a client gallery platform, or a piece of off-the-shelf SaaS configured well enough to stay useful. And since this year, it's often AI operating inside the system — drafting follow-ups, chasing reviews, mining leads out of spam, pushing a morning briefing to your phone — always with a human approving what goes out.
I handle the full loop: discovery, scope, design, frontend, backend, database, payments, email, integrations, hosting, launch, and the operational cleanup that follows. The goal is never to invent a platform. The goal is a real system in production.
Working principles
- Workflow first.The interface is downstream of the job. I care about who does what, when money moves, where the data lives, and what has to be true after launch.
- Complete beats theatrical.A deployed tool with auth, database, email, docs, and handoff beats a polished demo nobody can use next week.
- Scope protects everybody.If the right answer is a $50/month SaaS, I will not sell you a custom build. If custom is right, we define the smallest version worth owning.
- You own the system.My clients own their code, data, database, domain, accounts, and URLs. No mystery platform, no hostage situation.
- Approval-first AI.Automation drafts; you send. Every agent action is logged, every access is revocable, and your industry's rules are checked before anything ships.
- Built around one operator.The user is usually one person with customers, clients, fans, or a small team around them. That constraint makes the product sharper.
Background
I spent the last decade-plus as a broadcast television engineer — field operations, live production, integration. The kind of work where the system has to function before the red light comes on. That instinct is the whole business: live beats perfect, and running beats planned.
In parallel I've been building software for friends, family, coworkers, and myself: order systems, dashboards, trackers, publishing sites, native apps, and weird little tools for weird little workflows. A couple dozen systems are in production right now — including the one that runs my own life, which briefs me every morning at 6 AM.
I'm also a partner in a food brand running pop-ups in upstate New York — I handle media and IT for that team. I am not a cook.
A bad fit, on purpose
- Open-ended retainers without a defined operating role
- Marketplace or "next big thing" builds with no real workflow underneath
- Agency subcontracting where I can't talk to the actual operator
- Custom builds where an existing SaaS is the honest answer
- AI for AI's sake — automation that nobody asked for and nobody approves
- Projects that need a team and venture math before they need working software
Send the messy version.
Describe the workflow the way it exists today. The rough version is more useful than a polished brief — and the teardown is free.
Elsewhere
REPLY IN < 48H · FREE ONE-PAGE SYSTEMS MAP
NO CALL REQUIRED · NO OBLIGATION