Hire a web developer
The developer you hire is the one who builds your site
At ArdinGate, there's no account manager relaying your requirements, no project coordinator translating your feedback, and no junior contractor who gets quietly handed the work after the sales call. You communicate directly with the person writing your code from the first scoping email through launch and every support request after. One developer, one point of accountability, fixed price agreed before a line of code gets written.
What your site needs to bring in new business
A small business site isn't a brochure with a phone number tacked to it. It's the first place most prospects go before they call — and it either builds enough credibility to earn a callback or loses the lead to a competitor whose site does. Here's what a well-built site covers, and why each piece matters to your bottom line.
A separate page for each service you offer
A single "Services" page that lists everything in bullet points can't rank on Google for any specific service someone searches for, and it gives a prospect no useful depth on the particular thing they need right now. A plumber who does drain cleaning, water heater installation, and sewer line repair needs three separate pages — each one written around what a prospect is thinking when their water heater dies at 6pm on a Friday. Each page addresses the problem, explains the process, answers the questions people always ask, and has a clear way to contact you. That structure is how organic search traffic finds you for specific services instead of dumping everyone on a homepage that tries to say everything and says nothing useful.
An About page that shows who they're actually hiring
People hire people, not company names. Before a prospect contacts a service provider, they want to know who they're going to be dealing with. A solid About or Team page that covers your background, how long you've been operating, what you specialize in, and what clients can expect from working with you does more trust-building work than any other page on the site. This is especially true for solo operators and small teams where the owner is the service — a blank or generic about page is a trust gap a competitor with a better site can exploit. Certifications, licenses, professional memberships, or peer review ratings belong on this page where a deciding prospect will see them, not buried in the footer they never reach.
A contact or intake form that captures what you need to respond
A generic "Name, Email, Message" box collects a submission but not the information you need to reply usefully. A well-designed intake form asks the questions you'd ask in the first follow-up email anyway: what service is needed, what location, what's the project scope, when is the target date. Prospects who fill out a form that asks the right questions arrive as qualified leads instead of raw inquiries that require three more emails before you know whether they're a fit. The form also needs spam protection, reliable email delivery, and a clear on-screen confirmation so the prospect knows their message went somewhere — three things template builders get wrong often enough that they're worth spelling out.
Trust signals that matter in your specific industry
Trust signals aren't decoration — they're what separates a prospect who calls from one who clicks back. The right signals depend on your field: bar membership and peer review ratings for attorneys, license numbers for contractors, board certifications for healthcare providers, association logos for financial professionals, Google review counts for local service businesses. These signals should appear on the pages where a prospect is actively deciding whether to contact you, not just on an About page they may never reach. Google can also surface some of these signals directly in search results before a prospect ever clicks through to your site — but only if the site's behind-the-scenes labeling (which tells Google what your business is and what it does) is set up correctly.
Privacy-compliant handling of customer information
If your site collects any personal information — even just a name and email through a contact form — it needs a privacy policy that accurately describes what data is collected, how it's stored, and whether it's shared with anyone else. California's privacy law applies to California residents regardless of where your business is located. HIPAA requirements apply if you're in healthcare and the form collects anything about a patient's condition. The form itself needs to transmit data securely and never expose customer information in the page source or to bots. These are baseline requirements, not optional compliance overhead.
Fast loading on a phone with a slow connection
More than half of all web traffic is mobile, and for local service businesses the proportion skews even higher — someone looking for an emergency plumber or a last-minute hair appointment is on their phone, not their laptop. A site that takes more than two seconds to load on a slow mobile connection loses a significant share of those visitors before they see anything. Website builders like Wix and Squarespace load a heavy JavaScript engine before any of your content appears, which means the page is blank on slow connections while the platform warms up. A hand-coded site ships only the HTML and CSS needed to display the page immediately — no platform overhead standing between the server and your visitor's screen.
The due-diligence checklist for hiring a web developer
Hiring a web developer is a different kind of purchase than hiring most service providers. You're handing someone technical control over your digital presence and, in many cases, your customer data. The worst outcomes in developer engagements — locked-out owners, disappeared contractors, sites that go dark when the relationship ends — almost always trace back to skipping one of these five checks before signing.
Open the portfolio links in a browser, not just in the screenshots
Screenshots of past work tell you nothing about how a site performs for real visitors. Open the portfolio links directly, run them through Google PageSpeed Insights (a free tool — just paste the URL), and check the mobile experience on your own phone. A slow site in the portfolio is a preview of what you're going to get — developers don't build faster sites for some clients and slower ones for others; their performance standards are consistent. Also check whether the sites in the portfolio look like the same template with swapped colors, or whether each one was built for its specific purpose. Identical layouts across clients is a sign that the "custom build" in the pitch isn't as custom as the price tag suggests. Dead portfolio links are a separate red flag about how the developer handles long-term client relationships.
Verify the business registration
A developer who presents as a business entity should be verifiable as one. Florida LLC registrations are searchable on the Florida Division of Corporations website in under thirty seconds. Most states have an equivalent public database. A quick search for "[state] LLC lookup" will find it. An "LLC" that doesn't appear in the state registry is either a sole proprietor operating without proper registration or one that lapsed. Neither is a confidence-builder when you're handing over a deposit and your domain credentials. ArdinGate LLC appears in the Florida state database. A developer who can't point you to a registration record for their stated entity type deserves a direct question before anything gets signed.
Read the contract before you sign anything
The contract is where developer engagements go wrong most often, and the language that matters most is about ownership and hosting dependencies. A contract that grants you a license to use your own site instead of outright ownership means the developer retains a legal claim on the code. A hosting clause that ties the site to the developer's account rather than yours means the site could go dark if the relationship ends badly. Scope language that says "reasonable revisions" instead of a defined count means you're at the developer's discretion on what counts as in scope. These are the standard failure modes in contracts written without the client's interests in mind. A legitimate developer will walk you through every clause, answer questions without pushback, and not treat contract review as an obstacle.
Ask who actually builds the site
At agencies and some freelancer arrangements, the person you talk to in the sales process is not the person who builds your site. This matters more in web development than in most service categories because the difference between a senior developer and a junior subcontractor is enormous in ways that directly affect your outcome: code quality, security practices, SEO, mobile performance, and the ability to answer questions about technical decisions after launch. Ask directly: who writes the code? If the answer is "our team" or "we have a process for that," follow up until you have a name and a portfolio link. With a solo operator, this question has a one-word answer: the person you're talking to. With agencies, the answer is often intentionally vague.
Ask what you receive at the end and what happens if you leave
Portability is the test that separates a good engagement from one that traps you. After the project is complete, you should be able to hand the site to a different developer without any cooperation from the original one. You receive: the full source code in a format any developer can read, database credentials and a clean export if there's a database, domain registrar access in your own account, and hosting that isn't tied to a proprietary platform the next developer doesn't support. Ask this before you sign: if I need to move this site to a different developer in two years, what exactly do I receive and what do I need from you? A developer who hesitates, adds conditions, or mentions a migration fee is signaling a lock-in model. A developer who answers immediately and completely is giving you the right answer.
Where the inquiry funnel breaks and how the site fixes it
The path from "someone searches for your service" to "they submit an inquiry" is short — search, land, read, assess, contact. The brevity is deceptive. Each step has a specific failure mode, and most small business sites fail at more than one. Here's where drop-off occurs and what a well-built site does differently at each stage.
Search traffic lands on the homepage instead of the relevant service page
A prospect who searched for a specific service and lands on your homepage has to do extra work to confirm you even offer what they need. Organic traffic for specific service queries should land on a service-specific page that immediately confirms relevance. A roofing company whose "roof leak repair" page is the actual landing page for that search converts at a meaningfully higher rate than one whose homepage tries to cover all services at once. Individual service pages improve search rankings and are the mechanism by which search traffic converts into actual inquiries.
Nothing above the fold gives the prospect a reason to keep reading
The first thing a prospect sees when they land determines whether they scroll. If the top of the page is a full-bleed stock photo with a tagline and two buttons, most visitors who arrived with a specific question bounce before they find anything that answers it. A credibility signal placed in the hero section (years in business, a Google rating, a license number, a recognizable client logo) tells the prospect immediately that this is a legitimate business worth reading further. The absence of any signal is itself a signal, and it's the wrong one.
The contact form submits silently and the prospect never knows if it worked
A form that submits with no confirmation message, no thank-you redirect, and no email receipt leaves the prospect wondering whether their message went anywhere. A non-trivial share of "I never heard back" complaints turn out to be form submissions that either failed silently or went to the business's spam folder. An immediate on-page confirmation and an automatic email receipt to the prospect solve both the uncertainty and lost-inquiry problems. They're standard features, and any form without them is leaving inquiries on the table.
The mobile experience actively blocks conversions
For local service businesses, mobile is the primary channel, not one channel among many. A phone number that isn't a tappable link, a contact form that requires horizontal scrolling on a phone screen, or a navigation menu that covers the page content on mobile is actively blocking conversions from the channel that sends the most traffic. These are the default failure mode of templates built primarily for desktop. A mobile-first build treats the phone experience as the primary one and the desktop version as the expanded layout, not the other way around.
Google can't tell what your business is, so search results look generic
Behind-the-scenes labeling that tells Google your business name, address, phone, hours, and service area in a format it can read reliably affects how your business appears in search results before a prospect ever clicks through to your site. Google Business Panel cards, local pack listings, and star rating display in search results all depend on this labeling being present and correctly set up. Most template builders either skip this entirely or implement it through a plugin that gets it wrong half the time. Hand-coded labeling is set up once, correctly, and stays correct.
No page exists for the service the prospect needs right now
A business with ten services and one Services page is invisible in search for nine of them. Google can't send traffic to a page that doesn't exist. The fix is straightforward: one page per distinct service, each with its own URL, headline, and copy written around what a prospect searching for that service is trying to find out. This is the single highest-return structural change for most small business sites because it multiplies the number of search queries the site can rank for without requiring any ongoing content work beyond the initial build.
Why a website builder isn't the same as hiring a developer
Wix, Squarespace, and WordPress with a page builder can produce something that looks like a website. What they can't produce is a site optimized for your specific business, your specific conversion goals, and your specific industry's trust requirements. The difference isn't cosmetic, and it compounds over time.
| Factor | Website builder / template | Custom hand-coded build |
|---|---|---|
| Page load speed on a phone with a slow connection | 2.5–5 seconds (the builder's JavaScript loads before your content) | Under 1.5 seconds (HTML/CSS renders immediately, no platform overhead) |
| Monthly platform fee | $16–$49+/month, forever, on top of hosting | None — you own the code, host it anywhere |
| Individual pages per service | Possible, but the template structure constrains what each page can do | Each page built for its specific purpose and conversion goal |
| Behind-the-scenes labeling that tells Google what your business is | Requires a plugin; frequently incomplete or broken | Included in every build, correct by default |
| Contact form reliability | Platform mail function; frequent spam folder and delivery issues | SMTP relay, spam protection, rate limiting — tested before launch |
| Looks identical to your competitors' sites | Yes — same template, same stock layout, same generic feel | Built around your brand, your content, your differentiation |
| Code ownership | The platform owns the runtime; you're leasing access to your own site | You own the code outright from day one |
| Total ongoing cost to keep it running | Platform fee + hosting + plugin subscriptions (adds up fast) | Hosting only ($30–$75/month with managed plan) |
The problem templates can't solve
When two service businesses in the same category are running the same Squarespace template, design stops being a differentiator entirely. The decision comes down to price or who responds first. A custom site built around what actually makes your business different gives a visitor something specific to react to before they ever contact you. That's hard to put in a table, but it shows up in inquiry rate — and it compounds over the years the site is live.
Pricing
A single-page custom site starts at $1,200. Multi-page builds — a homepage, individual service pages, an About page, and a contact page with a custom intake form — run $2,800–$5,000 depending on page count and feature scope. Behind-the-scenes labeling that tells Google what your business is, Google Search Console setup, mobile optimization, and spam-protected contact forms are included in every build regardless of tier. Nothing on that list is an upsell.
Managed hosting and maintenance is $30–$75/month, month-to-month, no annual contract. That covers nightly backups, SSL certificate management, uptime monitoring, and content edit hours for copy updates, new pages, image swaps, and service additions after launch. The same person who built the site handles every post-launch request — no support ticket queue.
Every project is fixed-price, agreed in writing before any work starts. No hourly billing surprises, no scope creep on the invoice. If the scope changes, the addition gets quoted and approved before work on it begins.
Common questions about hiring a web developer
Managed hosting and maintenance is $30–$75/month, month-to-month, with no annual contract. That covers nightly backups, SSL, uptime monitoring, and content edit hours after launch. Every project is fixed-price, agreed in writing before any work starts — the number you approve is the number on the invoice. Full pricing breakdown →
The full process runs two to six weeks on average depending on site scope and how quickly your content arrives. Content is the most common timeline variable — the project brief sent at the start is specifically designed to surface that dependency early so there are no surprises at the finish line.
You receive the full source code and credentials to every service involved in the project. If you decide to move to a different developer or hosting provider at any point in the future, you have everything you need to do it without anyone's cooperation. No hostage situations, no recurring platform dependency, no fine print. More on website ownership →
ArdinGate starts with a fixed price before any work begins, communicates directly over email, uses a written contract with clear ownership terms, and keeps one developer accountable from scoping through launch and every post-launch request. No middleman, no meter running, no subcontractor you didn't know was involved. Full comparison: ArdinGate vs. agency →
Ongoing SEO — keyword research, content strategy, monthly ranking reports, link building — is a separate engagement. Most small business sites benefit more from getting the technical foundation right first than from paying for ongoing SEO campaigns on a site with structural problems. Start with the foundation.
Online booking can be integrated using a third-party scheduling tool (Calendly, Acuity, Booksy, Jane) embedded directly in the page, or built as a custom PHP booking form if the appointment data needs to live in your own database. Payment collection and calendar sync depend on the specific tool and are scoped individually based on how your workflow runs.
The most consistent source of delays is content: copy and photos that aren't ready when the build starts push the launch date regardless of how fast the development moves. The project brief sent at the start of every engagement is designed to surface that dependency early — what content is needed, what format it needs to be in, and when it needs to arrive — so there are no surprises near the finish line. Full timeline breakdown →
A good developer engagement should leave you in a stronger position if you ever choose to leave — not a weaker one. That's by design here, not an accident.
Photography: if you have professional photos, use them. Image quality is the first thing visitors judge, and it affects how many of them contact you more than almost any other element of the site. If you don't have professional photos, high-quality licensed stock photography can be sourced and included. Sites launched with stock photography consistently underperform sites with actual photos of the business, the team, and the work. If budget allows, commissioning a half-day photography shoot before the project starts is worth more than most individual site features.
Revisions within the agreed scope are included. Scope additions are quoted and approved as separate line items before any work on them starts — there are no surprise charges. Payment is by bank transfer, check, or major credit card. A signed agreement and received deposit is what starts the clock on the build. What to look for in a developer contract →
The only practical difference with a remote client is that site photography (if any) generally comes from the client directly rather than being shot locally. Everything else — scoping, proposal, staging review, launch, and post-launch support — works exactly the same way. About working with a remote developer →
For one-off changes outside a maintenance plan, hourly work is available. Changes are scoped and quoted before any work starts — there are no surprise charges. Month-to-month with no annual contract; cancel any time if you'd rather handle hosting independently.
You can read the full guide to choosing a web developer and what belongs in a developer contract before you decide. If after reading through everything the answer is yes, the contact form is a short message away. If not, the guides are useful regardless.
Related reading: Guide to choosing a web developer · Questions to ask before hiring · What to look for in a developer contract · DIY vs. hiring a developer · Freelancer vs. agency vs. studio · How much does a website cost? · Website ownership: what to retain · ArdinGate vs. agency
Tell me what you need. I'll tell you what it costs.
A short description of your business and the site you're looking for is enough to get a realistic scope and a fixed quote back within 24–48 hours. No sales call required to get a number.
Get a quote