Web design and web development get used interchangeably, and the difference matters when you are paying for one of them. Design decides how a site looks and whether it persuades. Development decides whether it can do the thing your business needs it to do.
Most local businesses only need design. A site with pages, a form and good structure will do the job. If that is you, say so and I will build that instead, because paying for development you do not need is the most common way businesses waste money online.
Development is what you need when the site has to hold a large catalogue, connect to something else you already run, or handle a process rather than just describe one. High Reach carries 129 indexed pages covering dozens of machines with their own specifications. That is not a design problem.
Built so the next person can maintain it, which is not always how custom work is left.
Product and equipment ranges structured so each item has its own page, its own specifications and its own chance to rank.
Calculators, filters, quote builders, booking flows. Anything the business does that a static page cannot describe.
Connecting the site to the systems you already run, so you are not copying data between two places by hand.
Routing, conditional logic and notifications, rather than a form that lands in an inbox nobody checks.
A catalogue site with hundreds of pages behaves differently from a five page brochure. Caching and queries configured accordingly.
Written up so another developer can pick it up. Custom work that only one person understands is a liability, not an asset.
High Reach Inc. sells and rents equipment that buyers search for by model number, not by category. The site was rebuilt around that.
Each model line has its own page, and those pages hold position 2 for "orion forklift" and page one for the Versa-Lift searches. Read the full case study.
Design decides how the site looks and whether it persuades. Development decides what it can do. Most local businesses need design and a good structure, not custom development, and I will tell you if that is the case.
Probably not, if your site is describing services. Probably yes, if it needs to hold a large catalogue, connect to another system, or run a process. Send me the URL and I will give you an honest answer.
WordPress for almost everything, because you keep ownership and are not locked into a platform. Where something genuinely needs a different approach, I will say so rather than force it.
You can, I can, or another developer can. Custom work gets documented so it is not dependent on me being available, which is the usual problem with bespoke builds.
Longer than a straight build. Two to three weeks covers design and pages. Custom functionality is quoted separately with its own timeline after we scope it.
Send me your URL and I will send back a plain-English audit of what is working, what is not, and what it would take to fix. No charge, no pitch deck.