For small businesses

I build websites for small businesses. The kind that take orders and bring you leads.

I build websites for small businesses, and the working parts behind them: a store that takes orders, a form that puts a new lead in front of you, an assistant on the site, and help drafting quotes and invoices. I’m one person. I write the code, and I run the hardware the assistants use. When something needs changing, you’re talking to the person who’ll change it. Client work is done by Robinson Labs LLC under a written agreement.

What I build

What gets built, and what happens after.

Sites · stores · assistants
Storefronts · equipment dealer

A store that takes the order

A national storefront for Piedmont Industrial Sales, an air-compressor dealer. It has more than 800 product pages, a cart that checks out on the owner’s own PayPal, and the business’s pricing and checkout rules built in. Prices update every hour. Behind a sign-in, the owner handles leads, orders, quotes and invoices from one page. A rule change the owner signed off on went live the same day.

piedmontind.com
Site rebuild · mortgage brokerage

A site that sends applicants to the right officer

A new site for The Equity Exchange, a mortgage brokerage, replacing its WordPress site: team, loan and service-area pages, plus landing pages for the loan officers. Each loan officer’s Apply button now opens that officer’s own application page. Kickoff to the new site on its own domain took 13 days.

theequityexchangellc.com
Assistants · back office

Drafts you approve before anything goes out

If your evenings go to quotes, invoices and the email you keep meaning to send your customers, I can set up an assistant that drafts them from the catalog and customer records you already have. It writes the first draft. You read it, fix what’s off, and tap approve on your phone. Nothing goes to a customer until you do, and the records stay yours. Piedmont Industrial Sales has one.

Assistants · on your site

An assistant on your website

It answers the questions your customers ask most, and when someone’s ready to buy or wants a call, it hands you their name and how to reach them. On the storefront above, one helps customers size a compressor. Its links are checked against the catalog, and the price a customer pays always comes from the catalog at checkout. It runs on hardware I operate, so the owner isn’t paying an AI company for every question. I won’t pretend there’s no cloud: the site is hosted there, and when my hardware can’t answer, a paid backup service does. If you get a handful of questions a week, a clear FAQ page does the job for a lot less.

piedmontind.com
Advice · before you build

Is it worth building at all?

Before you pay anybody to build something, start with where your week actually goes. I’ll sit down with you, look at the tools you already pay for, and tell you which jobs an off-the-shelf app handles fine and which ones might be worth building. Sometimes the honest answer is a setting you haven’t turned on yet. That’s a good answer too.

After launch

What happens after launch

I keep it running after launch: new pages, price and catalog changes, fixes. Your domain is registered in your name and you pay for it yourself. Your payment account is in your name too. Each business gets its own code and its own logins. If you move on, or I’m ever not around to do the work, you get the code, a copy of your data and every login and key, moved into your name, so another developer can pick it up.

Not a ServiceNow practice, and deliberately so. The day job is the day job. This is small-business work, and it’s what pays for the lab.

Start here

Tell me what the business does and what’s eating your week. I’ll tell you plainly what I’d build, and whether you need me at all.