A Home Page That Says What You Do
The most common failure on a small business site is a homepage that never plainly states the service and the area it covers. Yours will, above the fold.
Some organizations do not fit a package, and pretending otherwise produces a bad website. An association with members, a business with six locations, a directory that has to stay fast as it grows, a registration process that has to reach the right person: these are real pieces of work, and they need to be scoped before they can be priced.
That is what this is. The same standard as every other build, sized and shaped to what your organization actually does.
If your website has a job the packages do not cover, this is the right route. Associations and membership organizations, businesses running several locations, and anyone who needs a directory, a member area, a registration system, or a site that talks to software you already run.
The most common failure on a small business site is a homepage that never plainly states the service and the area it covers. Yours will, above the fold.
One page per thing you sell, each able to rank and convert on its own, rather than a single page listing everything you offer.
For a small business the About page is often the second most visited. It is where someone decides whether to trust you, so it gets written properly.
A form that reaches you, a number that taps to call on mobile, your real hours and a map. Tested before launch rather than after someone complains.
Your reviews and examples of your work, placed where people are actually deciding rather than buried on a page of their own.
Schema markup, location signals and page structure built in while the site is being made, instead of retrofitted months later.
Four stages, and you hear from me as each one is done. On a custom project the first stage matters most: scope is agreed in writing before a number is quoted, so the budget is based on the real job rather than a guess.
You deal directly with the person building your site. No account manager relaying messages, no ticket queue, no handover to somebody who has never spoken to you.
Your site is built on WordPress and set up on my hosting platform, with the domain, the files and the backups all in one place that I manage. That is what makes the rest of it work: one number to call when something needs changing, one person who already knows how the site is put together, and no chasing three vendors to fix one problem.
Every custom build is built on WordPress and designed mobile-first, because that is where most of your visitors will be.
Priced on the scope we agree together, not on a page count. You get a fixed number before any work starts, and it does not move unless the scope does.
Quoted alongside the build and billed monthly. Hosting, updates, backups, security monitoring and your content changes, the same care that comes with every site I build.
It is quoted per project, because a fair number depends on what the site actually has to do. A member directory, a registration system or an integration with your existing database are each real pieces of work, and a package price would mean either overcharging you or cutting corners.
The process is the same every time: we agree the scope in writing, you get a fixed number, and it does not move unless the scope does.
Longer than a brochure or growth site, and the honest answer depends on scope. A larger content site is usually six to ten weeks. Anything with member areas, registrations or integrations runs longer, because that functionality has to be built and tested rather than styled.
You get a timeline with the quote, not after work starts.
Not by size, by shape. It is for any organization whose site has a job the packages do not cover: an association with members, a business with several locations, a directory, a registration process, or a system the website needs to talk to.
If a growth site would do the job, I will tell you that instead. It costs you less and it is the honest answer.
Yes, exactly as with every other plan. It is standards based WordPress, documented, on infrastructure you can leave. There is no proprietary platform, no buyout figure and nothing that stops another developer picking it up.
That matters more at this size, not less. The bigger the build, the worse it is to discover you are renting it.
