About
I build custom software for specific people.
Ryan Fox. Systems engineer in Harleysville, PA. I build small, durable software for operators, creators, service businesses, and tight-knit groups whose real work has outgrown the tools around it.
The work usually starts with a sentence like, "Right now I do all of this by hand." That is 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.
Short version
Product partner, not template vendor.
I build business software around the way a specific person actually works. Sometimes that means a public order page and a private dashboard. Sometimes it means a booking board, a native app, a catalog site, a live tracker, an email system, or a piece of SaaS configured properly enough to stay useful.
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 not to invent a platform. The goal is to get a real system into production.
Working principles
The rules that keep the work useful.
Workflow first.
The interface is downstream of the job. I care about who does what, when money moves, where the data lives, what breaks, 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 that 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 the right answer is custom, 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 hidden dependency, no hostage situation.
Built around one operator.
The user is usually one person with customers, clients, fans, participants, or a small team around them. That constraint makes the product sharper.
Background
Live production trained the instinct.
I spent the last decade-plus as a broadcast television engineer: field operations, live production, integration, and the kind of work where the system needs to function before the red light comes on.
In parallel, I have been building software for friends, family, coworkers, collaborators, and myself: order systems, dashboards, trackers, internal CMSes, native apps, publishing sites, and weird little tools for weird little workflows. A couple dozen systems are live in production right now.
I am also a partner in a food brand launching upstate New York pop-ups in May 2026. I handle media and IT for that team. I am not a cook.
What I do not do
Some work is a bad fit on purpose.
- Open-ended retainers without a defined operating role
- Marketplace, platform, or "next big thing" builds with no real workflow underneath
- Agency subcontracting where I cannot talk to the actual operator
- Custom builds where an existing SaaS is the honest answer
- Projects that need a team, a roadmap, and venture math before they need working software
Where to start
Send the messy version.
Describe the workflow the way it exists today. The rough version is more useful than a polished brief.