Hiring a web developer is one of the most consequential decisions a small business owner can make. The right choice sets you up with a website or application that drives revenue for years. The wrong one drains your budget and leaves you with something you'll need to rebuild in twelve months.
The problem is that most business owners don't know what to look for. You're not evaluating code quality or architecture decisions every day. So here's a practical framework for making this decision well.
Your four options
Before you start evaluating individuals, you need to decide which type of engagement makes sense for your situation.
Agency
Agencies offer a team: designers, developers, project managers, QA testers. You get structured processes and broader skill coverage. The tradeoff is cost. Agencies carry significant overhead — office space, salaries, benefits, management layers — and all of that gets baked into your project rate. Expect to pay two to five times what you'd pay an independent developer for comparable work. Agencies tend to work best for larger projects with six-figure budgets where you genuinely need a team of specialists working in parallel.
Freelancer
Freelancers are independent developers you find on platforms like Upwork or Fiverr, or through referrals. Rates vary wildly, from $20 per hour to $200 per hour. The challenge is consistency. Many freelancers juggle multiple clients, and you may find your project stalling when they take on other work. Communication can also be hit or miss. That said, skilled freelancers can deliver excellent results at a fraction of agency pricing.
Independent consultant
An independent consultant sits between a freelancer and an agency. They typically have deeper experience, work with fewer clients at a time, and bring strategic thinking alongside technical skills. They'll help you figure out what to build, not just how to build it. You get a single point of contact who owns the outcome, not just the deliverables. Rates are higher than most freelancers but well below agency pricing.
Full-time employee
Hiring a developer in-house makes sense when you have ongoing, continuous development needs — not a one-time project. A full-time developer costs $70,000 to $150,000 or more per year in salary alone, plus benefits, equipment, and management overhead. For most small businesses, this only pencils out if you need 30 or more hours per week of development work on an ongoing basis.
What to look for
Regardless of which route you choose, certain qualities matter across the board.
Communication skills. A developer who writes clean code but can't explain decisions in plain language will create friction at every turn. During your initial conversations, pay attention to whether they translate technical concepts into business terms or hide behind jargon.
Relevant experience. "I've built 200 websites" means less than "I've built e-commerce sites for retail businesses your size." Look for someone who understands your industry or your specific type of project. They'll make better decisions because they've already learned the lessons.
A clear process. Ask how they manage projects. Good developers have a defined workflow: discovery, planning, development, review, launch, and support. If they can't describe their process, they probably don't have one.
Ownership mentality. The best developers care about whether your project succeeds, not just whether the code works. They'll push back on bad ideas, suggest better approaches, and think about long-term maintainability.
Red flags to watch for
Over the years, I've seen the same warning signs repeatedly. Any one of these should give you serious pause.
No portfolio or references. Every competent developer has work they can show you and past clients who will vouch for them. If they can't produce either, walk away.
Unrealistically low prices. If someone quotes you $500 for a project that everyone else quotes at $5,000, something is wrong. They're either going to cut corners, disappear halfway through, or deliver something that technically "works" but falls apart under real-world use.
Resistance to contracts. A professional developer welcomes a clear contract. It protects both parties. Anyone who pushes back on defining scope, timelines, payment terms, and intellectual property ownership is someone you don't want to work with.
Promising everything. Be wary of developers who say yes to every request without discussing tradeoffs. Good developers tell you what's possible, what's practical, and what's going to blow your budget. "Yes, and here's what that will cost" is a much healthier response than "sure, no problem."
No post-launch plan. A website or application needs maintenance, updates, and support after it goes live. If a developer's plan ends at launch day, you're going to have problems.
Questions to ask before you hire
These questions will reveal more than any portfolio review.
- "Can you walk me through a recent project from start to finish?" Listen for structure and clarity.
- "What happens if the project scope changes midway through?" Their answer tells you how they handle the unexpected.
- "How do you handle bugs or issues after launch?" You want to hear about warranties, support agreements, or maintenance plans.
- "Who owns the code and design assets when we're done?" The answer should be you. Always.
- "Can I talk to two or three past clients?" Willingness to provide references is a strong positive signal.
How to evaluate a portfolio
Don't just look at screenshots. Actually use the sites and applications in someone's portfolio. Here's what to pay attention to.
Speed. Does the site load quickly? Slow performance means sloppy development or poor hosting choices.
Mobile experience. Pull up their portfolio pieces on your phone. If the sites aren't responsive and easy to use on mobile, that's a fundamental gap in their skills.
Functionality. Click around. Do forms work? Do pages load without errors? Are there broken links? These details reveal how much care goes into the finished product.
Design consistency. Good developers maintain consistent typography, spacing, and visual hierarchy throughout a site. Inconsistency suggests rushed work.
Age of work. A portfolio full of projects from five years ago raises questions. Web standards evolve quickly, and you want someone who's actively building with current technologies.
Why the cheapest option usually costs more
This is the most important lesson I can share. I've had dozens of conversations with business owners who went with the cheapest developer they could find, only to come back a year later needing a complete rebuild.
The cheapest developer often delivers code that's difficult to maintain, impossible to extend, and riddled with security vulnerabilities. They skip the planning phase, ignore performance optimization, and build on shaky foundations. The site works on launch day and starts crumbling shortly after.
When you factor in the cost of the initial build plus the cost of fixing it plus the cost of eventually rebuilding it, the "cheap" option frequently ends up being the most expensive path. A mid-range developer who does it right the first time almost always saves you money over a two to three year horizon.
Think of it like construction. You can hire the cheapest contractor to build an addition on your house. But when the foundation cracks and the roof leaks, you'll spend more on repairs than you saved on the original build.
Making your decision
Match the engagement type to your situation. Choose an agency if you have a large budget and complex needs. Choose a freelancer if you have a well-defined, smaller project and you're comfortable managing the relationship. Choose an independent consultant if you want strategic guidance alongside technical execution. Hire full-time if you have continuous, ongoing development needs.
Then evaluate candidates based on communication, relevant experience, process, and portfolio quality. Watch for red flags. Ask hard questions. And resist the urge to optimize purely on price.
The right developer is an investment that pays for itself many times over. The wrong one is an expense you'll regret.
If you're evaluating your options and want a straightforward conversation about what your project actually needs, get in touch. I'm happy to help you think it through, even if we're not the right fit.