I don’t just design the front end. I build the machine underneath it.
About · Timmothy Jones
I build differentlybecause I think like an owner first.
Some of what I’ve built runs businesses I own. I’ve been the one answering the phone at 7pm, chasing the deposit and writing the same job down twice — so I don’t build pages that only look good. I build the system the business actually runs on.
How customers find you, trust you, book you and pay you, how your staff work, and what happens after the sale — designed as one thing.
- Based in
- Dallas–Fort Worth, Texas
- Working with
- DFW and remote, US-wide
- Currently
- 15 systems live
- hello@sitesbynu.com
How I think about it
Every business problem has a system behind it.
A customer asking for a quote looks like one message. It's really the start of six things that all have to go right — and most of them happen after the website.
Business problem
Digital solution
Operational system
Business problem
A customer needs a quote
They shouldn't have to call during business hours just to ask.
Digital solution
Website intake
A guided request asks what the job actually needs — photos included.
Digital solution
Booking
Real availability, so the time they pick is a time you can do.
Digital solution
Payment
A deposit holds the slot and is recorded against the job.
Operational system
Admin workflow
The request becomes a job your staff can see and act on.
Operational system
Follow-up
Confirmations and reminders go out without anyone remembering.
Where every project starts
I don’t start with the homepage.
The homepage is the last thing I can design well, because it depends on everything behind it. So I start with the questions that decide whether it works.
- 01What should the customer be able to do?
- 02What happens after they submit?
- 03Who handles it?
- 04What needs to happen automatically?
- 05What does the owner need to see?
- 06What breaks when the business grows?
Then I design the experience around the answers.
The whole picture
The parts, and how they connect.
These are the parts I think about on every project. Not every business needs all of them — but each one changes what the others have to do.
Where customers find you, trust you and start something.
Connects to
How I build
Built like a product, not decorated like a template.
One rule runs through all of it: build it so it tells the truth, including when something is broken.
- 01Understand the workflow firstBefore anything is designed, I want to know how your day actually goes — when you're busiest and where the same job gets written down twice.
- 02Remove unnecessary frictionEvery extra step is a customer who doesn't finish. I take steps out before I add features.
- 03Design for real mobile useYour customers are on a phone, usually in a hurry. That's the version I design first.
- 04Connect the toolsThe booking, the customer record and the invoice should be one record moving through stages, not three copies drifting apart.
- 05Build for changeNew services, new staff, a second location. The system should bend without a rebuild.
- 06Verify before launchI test the awkward cases — two people booking one slot, a payment that half-succeeds — before your customers find them.
Why it matters to me
Built by somebody who actually runs businesses.
Most of what I build starts with the same conversation. An owner describes their week, and somewhere in the middle they say something like “and then I write it in the book.” That sentence is usually the whole project.
I know that sentence from the inside. In the businesses I run, software has to earn its place on a busy day — so a system isn’t finished when it looks right. It’s finished when nothing falls between the cracks.
- Leads get lostEvery inquiry lands in one place
- Customers don't know what happens nextThey're told, in writing, right away
- Booking lives somewhere elseBooking is part of the same system
- Follow-up is done by handReminders and follow-ups send themselves
- Staff don't have the right informationEach person sees what their job needs
- The owner can't see the weekA dashboard built from the real records
How the work built up
From running businesses to building their systems.
Not a résumé with dates — the layers it built up in. Every step links to the real projects behind it.
01
Running my own businesses
Hauling, music and claims recovery. I built for businesses I run before I built for anyone else.
02
Building the tools they needed
Quotes, dispatch and crew pay — and the dashboard I use to run everything else.
03
Turning one system into a platform
The operations system became Operion, which now runs a second company on the same code.
04
Websites and booking for other businesses
The same thinking, for salons, barbershops and shops that were renting their booking from someone else.
05
Shop systems and client portals
Systems where the public site is the front door to the work behind it.
06
Automation and AI, where they earn it
Reading paperwork, drafting the routine parts, and capping what AI is allowed to cost.
What I actually build
The website is usually one layer.
The public site is often just the part customers see. Here's what can sit behind it — built only where the business needs it.
Website
Storefront
Products and menus people can actually buy from.
Booking
Appointments with real availability and deposits.
Client portal
A private view of a customer's job and balance.
Dashboard
How the week went, from the real records.
Operations
Jobs, schedules, staff and stock in one place.
Automation
The follow-ups nobody has to remember.
AI
Drafting and reading, with a person approving.
Working together
What it’s like to work with me.
You'll always know where things stand
No silent weeks. If something is slower than expected, you hear it from me, not at a deadline.
Plain language
If I use a technical term, I explain it in the same breath.
You see it early
A working link to click through as it comes together, not a surprise at the end.
Tested on the awkward cases
The double booking, the half-finished payment, the phone that loses signal mid-order.
Launch is planned, not hoped for
Going live is a planned event, and you and your staff will know how to run what you're launching.
It belongs to you
Your data, your accounts, your domain. If we ever stopped working together, you'd keep everything and it would keep running.
If that’s how you want your business built, start with the plan.
Answer a few questions about how your business runs and get a recommended build, an estimated range and a direction — before we ever talk.