Method
How I build your online presence.
It starts with research, not a template. By the time you see anything, I have studied your market, your competitors, and how a customer in your trade decides who to call.
Most web projects start with a questionnaire and a wireframe, and hand the hard thinking back to the owner. This one starts with me doing the work: learning the business and the market well enough to build something real, then showing it to you and letting you tear it apart.
Think of me as an engineer who connects things
You already know there are tools that would solve your problems. You have probably seen ads for half of them. What you do not have is the time to find the right ones, learn them, and make them work together.
That is the job. Your calendar talks to your intake, which talks to your invoicing, which talks to your reminders. The website stops being a brochure parked at the edge of the business and becomes the front door of the same system your team already works in. One person is responsible for all of it, which is the part that is hard to buy anywhere else.
01 / RESEARCH
I learn the business and the market before I build anything
I do not take every business that comes along. I choose the ones I think I can genuinely move, and then I study them. What you actually sell and which parts of it are worth the most to you. What your current site claims, what it leaves out, and which of its pages have earned search traffic worth protecting. Your reviews, in detail, because customers explain in reviews what made them choose you far more honestly than any brand exercise will.
Then the competition. Who ranks for the work you want, what they say, what they charge where it is public, where their sites are thin, and what a customer comparing three of you would actually see. I look at what the answer engines currently say when someone asks for a business like yours in your town, because increasingly that is the first thing a customer sees and most owners have never checked it.
Out of that comes a view of the market and a specific argument for why someone should hire you instead of the other three. That argument is what the site gets built around.
02 / CONTENT
I write it, sourced and checked
Then I write the thing: the services, the process, the pages that answer the questions your customers ask, the local pages that give a town-by-town search something real to land on. Every factual claim is either sourced or explicitly flagged for you to confirm. Nothing gets invented to fill a page, and no claim goes up that you would be uncomfortable defending.
I write to be understood by two audiences at once. A person skimming on a phone with a problem to solve, and a machine trying to work out whether you are the right business to name in an answer. Those two want more of the same things than people expect: clear structure, direct answers up front, real specifics, and no padding.
03 / THE BUILD
A site engineered for function, not just a nice-looking one
The site is built as software, on the same stack a serious application would use. Fast on a phone on a bad connection, accessible, structured so that search engines and AI assistants can read it correctly, and wired so an inquiry does something the moment it arrives instead of sitting in an inbox.
Design is not decoration here. Most small-business sites look like a template because they are one, and a customer reads that instantly. A site that looks considered is doing work for you before anyone has read a word of it.
04 / YOU SEE IT WORKING
I send you the real thing, and a way to attack it
What arrives in your inbox is a working site, not a mockup and not a slide deck. Alongside it I send an adversarial review prompt you can paste into ChatGPT or Claude, aimed at finding everything wrong with my work: unsupported claims, migration risk, ownership problems, missing proof.
I do this because asking you to trust a stranger with your online presence is a lot, and because the work should survive a hostile read. If it does not, I would rather find out from you than have you find out later.
How to run the review
- Open the demo, the dossier, and your current website side by side.
- Ask your preferred AI to act as a skeptical owner, not as my copy editor.
- Tell it to test claims, old URLs, disclaimers, ownership, security, and the conversion path.
- Ask it to separate verified facts, reasonable inferences, and missing evidence.
- Send me the objections. I will fix what is wrong and disclose what is not yet proven.
Keep the prompt adversarial. If it steers toward a sale, the review loses the trust that made it worth running.
It is the most honest version of a portfolio I can offer while the portfolio is still short. Rather than showing you my best past work and asking you to assume yours would go the same way, I show you the actual work and hand you the tools to find its faults.
05 / WE TALK, AND THE SITE CHANGES
The part research cannot do on its own
Research gets me a long way. It cannot tell me the things only you know, and this conversation is where the site stops being good and starts being yours.
What actually makes you different from the other three, in your words rather than the industry boilerplate everyone uses. Which customers you want more of and which you would rather never hear from again. The jobs with the best margins and the ones you take because you feel obliged. The questions you answer on the phone ten times a week. What your competitors get away with claiming that you would not. What is coming: a service you want to grow into, a part of the trade you are moving toward, a season that makes or breaks the year.
Then I rebuild the site around those answers. Not a round of small edits. If the conversation reveals that the money is in the work I put on page four, page four becomes the homepage. This is also where a rebrand can happen, if what you want to be hired for and what your business is currently called have drifted apart.
What I am listening for
I say an hour, but leave yourself a little more. Some businesses are straightforward and some have layers, and I would rather understand yours than finish on time.
The questions are not the ones you expect. Not what software do you use, but what happens when you are under a sink and the phone rings. Not how many people work here, but who is supposed to answer when everyone is busy.
What I am hunting for is the pain you have stopped noticing, because you built habits around it years ago. The calls that go to voicemail. The follow-up that never happened. The quote nobody chased. The invoice sitting unpaid because there was no time.
And the work your people quietly will not do. Have you ever asked your salespeople to reach back out to old clients? How did that go. Have you asked someone to follow up on every quote that did not close, request a review after every job, chase every late payment? These jobs sink to the bottom of the list. They are tedious and repetitive and they get skipped the moment things get busy. They are also, almost always, where the money is going.
We do not have to start big
If something costs you fifteen minutes a week, it may not be worth automating. I would rather start where the leverage is: the things actively stopping you from making money, or eating the hours your team should spend on billable work. That is why the offer is a base plus a menu rather than a package. You are not buying a tier that happens to contain the one thing you needed.
Garbage in, garbage out
This is the part clients underestimate. None of it is magic, and it can only ever be as good as the information behind it. I need to understand how you operate: what you say when someone asks for a quote, how an emergency differs from a routine request, where your service area really ends, what happens after a quote goes out or a job finishes or an invoice goes unpaid, what makes a lead worth your time, and what your scheduling rules genuinely are rather than what they are on paper.
If none of that is written down, that is normal. Most small businesses do not have written procedures. You just know how it works. I bring templates and we adjust them to match you, and the useful side effect is that you end up with the operational documentation you never found time to write.
You correct facts once, on a single document, rather than hunting through twenty pages. I turn those corrections into the site.
06 / MIGRATION
Nothing you already earned gets dropped
If you have an existing site, it is an asset even when it looks dated, because search engines have spent years learning its addresses. A rebuild that ignores that quietly throws the equity away, and the owner usually finds out months later when the calls thin out.
So every indexable URL on the old site gets inventoried and given a documented destination: preserved at its exact address, redirected to the page that replaced it, or deliberately retired. The map is a real document you can read and check, not a promise that we handled it.
07 / LAUNCH
The key turn
I point the domain, hand over the logins, verify every old address still resolves somewhere useful, and get the business registered where it needs to be: Google Business Profile, Bing, the directories that matter for your trade, and the government vendor portals where those apply.
Payment handling gets wired up in the same pass where that applies, so invoices, card and ACH acceptance, autopay for recurring work, and the reminders that chase what has not been paid all run through the same system as everything else.
08 / THE WATCH
Then someone stays responsible for it
This is the part that makes the rest worth anything. A site nobody maintains starts decaying the week it launches. I monitor it, fix it, keep it current as the answer engines change how they read, and send you a monthly report of what I did and what it produced.
Not impressions. The number of inquiries, where they came from, what happened to them, and what changed since last month. If you cannot tell what you are getting for the money, I have not done my job.