I build websites and custom tools for small businesses, then host and look after them. Most projects start with one of the three below. Not sure which one fits? Describe the problem and I'll tell you.
I build sites from scratch rather than on a page builder, so they're fast on a phone and nothing on them is rented. Every site comes with a simple editor set up around what you actually change: your hours, your menu, your event calendar. Changing your hours shouldn't need a support ticket.
5–12 pages, with your real photos and your own wording. Written to sound like you, not like a template.
Event schedules, menus, catalogs, newsletters. Set up so the person who knows the content can post it in a couple of minutes.
Members-only areas, booking and ordering flows, and customer logins, kept small and built around how you already run things.
Under the hood: Next.js or Astro, Payload CMS, Postgres. Proven tools I can maintain for years.
This is my day job. I'm a lead engineer at a payments company, where I design and build across the whole platform: the databases and services behind it, the internal admin tools, the integrations with partners' systems, and the apps businesses use to take payments. For a small business, the same skills turn a spreadsheet-and-phone-call process into one form, one dashboard, and one click.
One place to see and manage your customers, orders, or jobs, built around your data and your process instead of an off-the-shelf app you have to bend around.
When two tools should be talking and someone is copying data between them instead. I connect them and add monitoring, so I'm the one who finds out when something breaks.
Writing first drafts of replies, sorting incoming requests, pulling details out of documents. Only where it saves hours, and always with a person checking the result.
If Zapier or an off-the-shelf app already does the job well, I'll tell you to use it. I build the things that are too specific to your business for those.
Launch day is when you start relying on the software. I host what I build, keep it patched and backed up, and watch it so I usually hear about a problem before you do. When a card processor's security scan flags your site, or a domain is about to expire, I deal with it and explain what happened in plain English.
Your site or tool runs on servers I manage, with nightly off-site backups and security updates applied as they come out.
Uptime alerts, SSL certificates, and the compliance paperwork that comes with taking card payments. I handle the scans and the disputes.
A new page, a fixed typo, a button that should go somewhere else. Email me and it's done, with no ticket system.
Need ads or local SEO as well? I don't run ad accounts myself, but I bring in a marketing partner I trust when a project calls for it.
Most clients start with a project and stay on hosting and care afterward.
One page covering what I'll build, what it costs, and when it'll be done. You sign it and I start. Most websites and tools work this way.
Hosting, backups, updates, monitoring, and small changes, billed once a year so there are no surprise invoices.
Your current site, or a process you suspect could be automated. You get a short report in plain English that you can act on with me or with anyone else.
Stuck with a site someone else built? That one I'll take a look at. Sometimes it's a quick fix, and sometimes a rebuild costs less than patching it. Either way I'll tell you which before you spend anything.