How to Hire a Web Developer (and What Good Work Actually Looks Like in 2026)

Hire a web developer by defining the job in plain language first, then asking who owns the code and domain. You should. Get a fixed scope, a written quote, and full access to the repo and hosting before any work starts.
Part of the complete web development guide.
On this page
- Start With What You Actually Need
- Questions That Separate Real Developers From Talkers
- What Good Front End Code Looks Like in 2026
- Performance Budgets, Not Vague Promises
- Pricing, Honestly
- Contracts and Ownership, the Boring Stuff That Saves You
- After Launch
- FAQ
- How much should a small business website cost in 2026?
- Do I really need to own the code and hosting accounts?
- How do I tell if a developer is any good before hiring them?
Most people hiring a developer for the first time get burned by the same three things: vague scope, no ownership of the code, and a site that’s slow six months later. I’ve been building sites for businesses around Long Island and beyond for a long time, and the difference between a good hire and a bad one rarely comes down to price. It comes down to whether the person can explain their decisions and whether you actually own what you paid for.
Start With What You Actually Need
Before you talk to anyone, write down the job in plain language. “I need a five page site that loads fast, works on phones, and lets me edit text without calling you.” That sentence rules out half the bad options immediately. If a developer can’t restate your goal back to you in their own words, they’re not listening yet.
Three categories cover almost everything:
- Marketing site. Static or lightly dynamic. Your goal is speed, clean markup, and easy content edits. This is where most small businesses live.
- Web app. Logins, dashboards, payments, data. This is a software project, not a brochure, and it should be priced and scoped like one.
- Rescue job. Someone else’s half finished mess. Expect to pay for a code review before anyone quotes you a number.
Questions That Separate Real Developers From Talkers
Ask these. The answers matter more than the portfolio.
- “Who owns the code and the domain?” The correct answer is you. Not “we’ll host it for you.” You should have access to the GitHub repo, the domain registrar, the hosting account, and the DNS. If any of those are locked to the developer, you’re renting your own business.
- “What happens when I want to leave?” A good developer has a handoff process. A bad one gets defensive.
- “How do you handle content edits?” For a marketing site, the answer should involve a CMS you can actually use, or a plain text workflow you understand. Not “email me and I’ll change it.”
- “Can I see the Lighthouse scores on a recent project?” Real developers have this data. You want Performance and Accessibility both in the 90s on mobile.
- “What’s your process for a change request?” If the answer is “we’ll figure it out,” your invoice will too.
What Good Front End Code Looks Like in 2026
You don’t need to read code to spot quality, but knowing two or three signals helps. Here’s a small example. This is the kind of thing that separates a site that scores well from one that doesn’t.
<picture>
<source srcset="/hero-800.avif 800w, /hero-1600.avif 1600w"
sizes="(max-width: 700px) 100vw, 50vw"
type="image/avif">
<img src="https://i0.wp.com/www.kennykey.com/hero-1600.jpg"
alt="Storefront on Main Street"
width="1600" height="900"
loading="eager" fetchpriority="high" decoding="async">
</picture>
Points to notice: AVIF with a JPEG fallback, explicit width and height so the layout doesn’t jump, and fetchpriority="high" on the hero image because that’s the largest thing on screen. If a developer hands you a site where the hero image has no dimensions and loads as a 4MB PNG, they’re not paying attention to performance.
Here’s a second signal. Modern CSS handles layout and responsiveness without JavaScript, which means less to break and less to download:
.card-grid {
display: grid;
grid-template-columns: repeat(auto-fit, minmax(280px, 1fr));
gap: 1.5rem;
}
@media (prefers-reduced-motion: reduce) {
* { animation: none; transition: none; }
}
That second block respects users who get motion sick. It costs nothing and it’s the kind of thing that shows up in an accessibility audit. Small details like this are why I still do a lot of custom web development by hand rather than dropping everything into a page builder. Builders are fine for some jobs, but you inherit their performance ceiling, and you can’t fix what you can’t see.
Performance Budgets, Not Vague Promises
“Fast” is not a spec. A performance budget is. Ask for one in writing. A reasonable target for a 2026 marketing site on a mid range phone over 4G:
- Largest Contentful Paint under 2.0 seconds
- Interaction to Next Paint under 200 milliseconds
- Cumulative Layout Shift under 0.1
- Total JavaScript under 150KB compressed for a mostly static site
Those numbers come from Core Web Vitals, which Google still uses as a ranking signal. If a developer doesn’t know what INP stands for, that’s your answer. You can check any live site yourself at PageSpeed Insights. Do it before you sign, not after.
Pricing, Honestly
Nobody can give you a real number without scope, so be suspicious of anyone who does in the first email. Rough ranges for a small business, knowing that a custom design costs more than a tuned template:
- Simple marketing site, few pages: low four figures.
- Custom design plus a CMS and integrations: mid to high four figures.
- Web app with logins and payments: five figures and up, billed in phases.
Watch for these traps: hourly billing with no cap, “unlimited revisions” that quietly means “until I get annoyed,” and retainers that cover nothing specific. Fixed price per phase, with a written scope, protects both sides.
Contracts and Ownership, the Boring Stuff That Saves You
Get these in writing before work starts:
- Deliverables, page by page or feature by feature.
- Timeline with dates, and what happens if either side slips.
- Payment schedule tied to milestones, not calendar dates.
- IP assignment. Work for hire, code and design transfer to you on final payment.
- Access list: domain, hosting, repo, analytics, email. All in your name.
- Post launch support window, and what it covers.
If a contract is missing the IP clause, that’s the one to push back on. Everything else is negotiable.
After Launch
A site is not a painting, it’s a machine that needs occasional maintenance. Budget for it. Dependencies get security patches, browsers change behavior, and your content goes stale. A small monthly retainer for updates and monitoring is normal and worth it. What you don’t want is a developer who disappears for a year and then charges you emergency rates to fix something they should have patched.
One last thing. You’re allowed to ask for a second opinion, even mid project. If something feels off, get a code review from someone else. Any developer confident in their work will say yes to that without flinching.
FAQ
How much should a small business website cost in 2026?
For a straightforward marketing site with a few pages, expect low four figures. Custom design, a CMS you can edit, and integrations push it into the mid to high four figures. Anything with user accounts or payments is a software project and priced accordingly.
Do I really need to own the code and hosting accounts?
Yes. If you can’t log into your own domain registrar, hosting, and code repository, you don’t control your business’s web presence. Ask for access at the start of the project, not at the end.
How do I tell if a developer is any good before hiring them?
Ask them to explain a recent technical decision, show Lighthouse scores from a real project, and describe their handoff process. Vague answers on ownership or performance are the biggest red flags.


