Small-business websites
A site that clearly explains what your business does and makes it easy for customers to find information and get in touch.
Responsive layout · semantic HTML · contact flow
Services · for small businesses
I'm a software engineer in the Houston area. I build and fix websites and web tools for small businesses, remotely or locally.
A lot of good businesses have websites that don't show it. They're out of date, hard to use on a phone, or missing the one thing a customer came for. That's the kind of problem I'd like to help fix.

Pick the one that sounds like yours. Each one links to the kind of work that usually fixes it.
"My website looks outdated."
A redesign can improve how the site looks and how easily customers find what they need.
"It's terrible on a phone."
Sometimes that takes a few targeted fixes. Sometimes the site needs rebuilding for phones.
"People visit but don't know what to do next."
Make the next step easier to find: calling, booking, ordering or visiting.
"Customers keep calling us for information that should be online."
Make commonly requested information easier to find online.
"We're doing something manually that could probably be a web tool."
Spreadsheets passed around, the same form filled in by hand, a process only one person knows: some of these are worth a small custom tool.
"Our site technically works, but using it is frustrating."
Broken forms, confusing steps and buttons that don't do what they say can often be fixed without starting over.
"We don't have a website yet."
Start with what customers need to know and how to reach you.
A site that clearly explains what your business does and makes it easy for customers to find information and get in touch.
Responsive layout · semantic HTML · contact flow
Improve an outdated or confusing site: navigation, how it works on a phone, and putting the information people call about where they'll find it.
Navigation · information hierarchy · mobile behavior
Custom browser-based tools with user accounts, saved information, dashboards or workflows, forms and application logic, when the scope fits my experience.
React · Node/Express · Supabase
The parts of a website or app people see and use: interfaces, reusable components, responsive layouts, forms and interactive features.
React · JavaScript · CSS
Connect your site or app to the outside services and data it needs.
REST APIs and similar web integrations
Make your site easier for more people to use: page structure, keyboard use, focus, contrast, forms, and phones and touch screens.
Practical fixes, not a formal compliance audit or certification
The on-page basics search engines look for, built in properly.
Titles and descriptions · headings · alt text · sitemap · social previews · performance basics
Implementation, not SEO strategy. And no ranking promises; nobody can honestly make those.
Find what's broken, fix problems on phones, and smooth out the steps that confuse people.
JavaScript · React · API · browser issues
Two so far: one I built on my own, and one I built with a team.
QuestKeeper: a web app my D&D group uses during our games, with accounts, saved characters and a live table the game master runs.
Case study →Nugget externship (team project): four weeks on a team of six, building features for a real company's app alongside other engineers, designers and QA. My part was community groups and a step-by-step review form.
Project note →What's going wrong, and for whom.
Sometimes that's less than you expected.
In writing, before the build starts.
You'll see progress along the way, not just at the end.
We review the site on phones and with the content your customers will see.
You'll know how to log in, what to update and who owns what.
Tell me what's going on and I'll tell you how I'd approach it, including if I'm not the right fit.
Start a conversation →