After launch
Most of what goes wrong with a site happens months after it launches, when whoever built it has moved on. This is the part I am actually selling.
Not resold, not a support ticket into a company neither of us can reach. I administer the machine your site lives on.
Backed up on a schedule and watched, so I usually know something is wrong before you do.
Platform, plugins, certificates, patches. The maintenance nobody notices until it has been skipped for a year.
New prices, a staff photo, a page that needs rewording. Included, not quoted each time.
Sites break at inconvenient hours. When yours does, you text one person and that person answers.
Moving an existing site onto my hosting costs nothing, and visitors will not notice it happened.
What I build
The right one is usually obvious after thirty minutes on the phone. Most businesses need the first one.
The one most people are here for. Marketing sites, service businesses, practices, organizations. Built from scratch so there is nothing in it you did not ask for, which is also why they load fast.
Four to eight weeks, typically, from the plan to launch.
When you want to write your own posts and swap your own photos without calling me. I build the theme, you get the admin, and I stay responsible for keeping it patched.
Also the right answer when you already have a WordPress site and it needs rescuing.
When a website is not enough: member portals, booking and scheduling, document libraries, dashboards, payments, client logins. Screens that respond instantly instead of reloading the page.
I lead a payment platform by day, so integrations, card readers and encryption are familiar ground.
Installs to a phone's home screen with an icon, opens without a browser bar, keeps working on a bad connection. No app store, no review process, no fifteen percent of anything.
Cheaper and faster than a store app, and there is nobody to ask for permission. The tradeoff is reach: people cannot find it by searching a store.
Real apps for iPhone and Android, built with React Native so both come from one codebase instead of paying twice. Submitted to the App Store and Google Play under your accounts. Worth it when you need the camera, push notifications, offline storage or a listing people can search for.
Both stores charge a developer fee and Apple's review adds time. I will tell you on the call whether you need this or the option above.
Software that runs on a machine in your office, talks to hardware, and works when the internet does not. Kiosks, point of sale, back-office tools.
Seven years of this in payment and kiosk software.
In everything
Designed for the phone first, because that is where most of your visitors already are.
Tested with one, not just checked against a list. It is how people with low vision use your site, and in the US it is also a legal exposure.
Speed is the one thing every visitor notices and nobody compliments. Google counts it too.
English and Spanish, written by the same person who built the site, not run through a translator.
Design and imagery
Most developers treat images as files to upload. I was a designer first, so they get treated as part of the design.
Every photo on your site gets corrected, cropped and retouched before it goes up. Colors matched, distractions removed, the crop chosen for the space it sits in.
Sized for the screen that will show it and compressed until it is small without looking it. Images are what make most sites slow.
Logos, brand materials, social graphics, print. If the site needs something that does not exist yet, I can make it rather than send you out to find someone.
Getting found
No guaranteed rankings, no monthly report full of numbers that do not move. These are the things that are in my control, and I do all of them.
Pages structured so a search engine can tell a heading from a caption. Same work that makes a screen reader make sense.
A ranking factor and the reason people leave. Measured, not assumed.
Written per page, in the language the page is in. This is the text people read before deciding to click.
Submitted, not just generated, so new pages get found instead of waiting to be stumbled on.
The markup behind hours, addresses, reviews and events showing up directly in search results.
Set up properly, then explained once so the numbers mean something to you.
What your customers actually type, which is rarely what your industry calls itself.
Which pages should exist, what each one is for, and which ones you are better off deleting.
Straight answers
Every studio has work it does well and work it takes because it was offered. Here is which is which.
Not my usual work. I can build one, and for a client I already know I will, but if your whole business is a catalog with inventory and shipping rules you may be better served by someone who does only that. I will say so on the call.
You know your business better than I ever will, so the best sites happen when the copy comes from you. If writing is not your thing, we do it together on a call and I draft from what you said. Either way it should sound like you, not like a template.
The site is yours. If you ever want to take it elsewhere there is a one-time handover fee, written into the contract before you sign, and I will hand over working files rather than make it difficult.
That is what the first call is for. Thirty minutes, English or Spanish, no pitch.