Chat on WhatsAppFastest way to reach us
FREE 30 MINUTE INTRO CALLFIXED SCOPE PROPOSALS IN USD OR ZAR3 HOUR AVERAGE REPLY TIMERATED 5.0 ON GOOGLE FREE 30 MINUTE INTRO CALLFIXED SCOPE PROPOSALS IN USD OR ZAR3 HOUR AVERAGE REPLY TIMERATED 5.0 ON GOOGLE
WEB DEVELOPMENT

How to Choose a Web Development Company: 15 Questions Worth Asking

Hiring a web development company is not just a design decision. You are choosing who will help shape one of your most visible sales channels, and possibly the systems your customers and staff will use every day.

A polished portfolio and a friendly sales call are useful starting points, but they cannot tell you whether a company understands your commercial goals, can manage the project well or will support the website after it launches. This guide gives South African business owners a practical evaluation framework: what to look for, how to compare quotes, which questions to ask and how to recognise warning signs early.

First, be clear about what you are buying

A company offering inexpensive template websites may be a good fit for a straightforward launch. A specialist e-commerce developer is better suited to complex checkout and inventory requirements. A custom software team becomes relevant when you need customer accounts, workflow automation, APIs or tailored business logic. None is automatically better; they solve different problems.

Define whether you need a new website, a redesign, an online store, an ongoing development partner or a custom platform. Then write down the main outcome: more enquiries, fewer manual tasks, online sales, better customer self-service or improved credibility. If you cannot explain the desired outcome, it becomes difficult to judge whether a proposal solves the right problem.

The 15 questions to ask before hiring a developer

1. What similar projects have you completed?

Ask for live websites or case studies relevant to your business model, not simply the industry. A service website that generates enquiries requires different thinking from a high-volume catalogue. Ask what the problem was, what the team delivered and what can be independently observed. Respect confidentiality: agencies may not be able to disclose private commercial metrics.

2. Who will actually do the work?

Meet or learn about the people responsible for discovery, design, development, content, testing and project management. Find out whether work is subcontracted, what time zones are involved and who remains accountable. Subcontracting is not inherently bad; unclear accountability is.

3. How will you understand our business before designing?

A strong provider asks about customers, current processes, competitors, priority services and success metrics. Be cautious when the first conversation consists entirely of themes, animations and a price before anyone has asked what the website must achieve.

4. Why do you recommend this platform?

Ask for the reasoning behind WordPress, Shopify, Webflow, WooCommerce or a custom stack. The explanation should cover capabilities, editor usability, future changes, integrations, hosting and total cost of ownership. 'It is the only platform we use' is not a business case.

5. What exactly is included in the quotation?

A useful proposal identifies unique page templates, expected content, forms, integrations, responsive breakpoints, accessibility expectations, technical SEO, analytics configuration, training, testing, deployment and revisions. Separate confirmed requirements from assumptions and optional extras.

6. What is not included?

This can be more revealing than the list of inclusions. Ask specifically about copywriting, photography, product uploads, brand identity, stock imagery, premium themes, licences, email hosting, payment fees, integrations, translations and third-party subscriptions.

7. What is the design and feedback process?

Will you receive a site map, wireframes and mobile designs before development? How many review rounds are included? How are disagreements resolved? Ask who gives feedback and how consolidated comments should be submitted to avoid contradictory instructions.

8. How do you handle changes to the brief?

Almost every project discovers a new requirement. A professional change process records the proposed change, business reason, extra cost, timeline effect and explicit approval. You should not be surprised by invoices, nor expect unlimited additions to a fixed price.

9. How will you protect site performance and accessibility?

Ask about responsive testing, image optimisation, caching, form labels, colour contrast, keyboard access and real-device checks. Developers should be able to explain important measures such as Core Web Vitals in plain language, without pretending that every page can achieve perfect scores under all conditions.

10. What security practices are included?

Discuss HTTPS, administrator access, multifactor authentication where available, updates, backups, restore testing, least-privilege permissions, secure form handling and incident response. For portals and stores, also ask about personal data, retention and third-party services. In South Africa, POPIA considerations may be relevant to how customer information is handled.

11. How will we measure success?

A company focused on outcomes should ask what counts as a valuable conversion. Examples include quote submissions, qualified phone leads, completed purchases, applications or successful customer self-service. Agree on analytics ownership, event tracking and how results will be reviewed.

12. Who owns the website, accounts and content?

Your contract should specify ownership or licences for custom code, design assets, stock media, domain names, customer data and accounts. Check your right to export content and move the site. Ideally the business controls its core accounts and grants the agency access, not the reverse.

13. What happens after launch?

A handover should include credentials, backup and update instructions, key integration details and training. Ask about warranty or defect-fix periods, support response targets, maintenance retainer options and what counts as new development.

14. What will you need from us, and when?

Websites stall when product descriptions, photographs, approvals or technical credentials arrive late. A credible timeline lists client responsibilities and dependencies rather than promising a launch date while assuming all materials will magically appear.

15. Can you explain the risks and trade-offs honestly?

Ask: 'What is the weakest part of this plan?' Useful answers might concern legacy data, third-party APIs, rushed content, unusual product options or a short deadline. Be cautious of providers who claim there are no risks or promise guaranteed top Google rankings.

Compare proposals using a simple scorecard

Price should matter, but it should not erase the rest of the evaluation. You can score each shortlisted company from 1 to 5 against the following criteria:

Criterion Suggested weight What to assess
Understanding of business outcomes 20% Quality of discovery and recommended approach
Relevant portfolio and proof 15% Comparable live work and credible examples
Deliverables and scope clarity 20% What is included, excluded and measurable
Technical quality and security 15% Performance, testing, data and maintenance plan
Communication and project management 15% Responsiveness, milestones and ownership
Total cost and long-term value 15% Build plus realistic operating costs

Multiply each 1–5 rating by its weight, then discuss any category scoring poorly. The weights are an illustrative framework, not a universal formula. A company with the lowest initial price can be more expensive if it leaves out content, maintenance or essential integrations.

What a professional proposal should contain

At minimum, expect the business objective, scope of work, page and functionality list, platform recommendation, design deliverables, dependencies, responsibilities, milestone dates, testing and acceptance approach, price and payment terms, third-party costs, change process, ownership and support arrangements.

For larger projects, ask for an architecture overview, integration assumptions, data migration plan, roles and permissions, a security approach and a phased launch strategy. If a detailed functional specification is not available yet, a separately scoped discovery engagement can be a sensible first purchase.

Local agency or remote development company?

Both can work well. A Cape Town team may offer useful context for local service areas, regional customer behaviour and South African payment, delivery and operating realities. A remote specialist may be the better choice for a niche technical requirement. What matters is clear communication, an overlap in working hours, responsibility for decisions and a process you can understand.

Ask where meetings happen, how progress is shown, how urgent issues are reported and whether support coverage matches your business hours. Never assume 'local' automatically means more available, or 'international' automatically means better technical quality.

Warning signs worth taking seriously

  • Guaranteed rankings or instant results: Search visibility and revenue depend on factors no agency controls completely.

  • No clear contract or deliverables: A vague one-page price creates ambiguity when changes arise.

  • No access to your own accounts: Domain, hosting and analytics access should be addressed explicitly.

  • A portfolio with no live examples: Mock-ups are useful but are not evidence of performance in production.

  • Pressure to pay everything upfront: Payment arrangements should be proportionate, documented and tied to agreed terms.

  • A solution chosen before your needs are understood: The platform should follow the problem.

  • Security and maintenance dismissed as irrelevant: Every production site needs an operating plan.

  • Unrealistic turnaround promises: Fast delivery is possible for narrow, prepared scopes, not for every project.

One red flag does not prove a company is unsuitable, but it is a reason to ask deeper questions before committing.

Before you sign: a short practical checklist

Confirm that the proposal names the exact business and deliverables; the payment milestones are clear; essential licences and subscriptions are identified; ownership and administrator access are documented; the launch and acceptance criteria are agreed; the process for revisions and new features is written down; and your team knows who will supply and approve the content.

Ask the provider to walk you through one typical user journey from arrival to conversion. If that journey is unclear during the proposal stage, it is unlikely to become clearer by itself during development.

Frequently asked questions

Should I hire a freelancer or an agency?

A skilled freelancer can be excellent for a defined site or a specialist task. An agency may provide wider coverage across design, development, SEO, security and support. Choose based on project complexity, continuity needs, accountability and verified work, not the label.

Should I choose the cheapest quote?

Choose the least expensive proposal that meets your actual requirements and acceptable risk level. A low quote is attractive when scope is genuinely simple; it is risky when key deliverables or operating costs are missing.

How many quotes should I get?

Two or three well-briefed, comparable proposals are often more useful than ten generic estimates. Send the same requirements to each provider and allow questions before they quote.

Is a custom website always better than a template?

No. A good template with strong content and thoughtful configuration may be ideal for a straightforward business. Custom development is justified when it creates meaningful value through unique workflows, integrations, design requirements or control.

What if I already have a website?

Start with an audit of conversion barriers, content, performance, security and current technology. Improvements or a partial rebuild may deliver better value than replacing everything.

How can I judge an agency if I am not technical?

Focus on whether it explains options in language you understand, shows comparable work, documents responsibilities, invites questions and can demonstrate a working site rather than only discuss code.

Choose a partner who can explain the 'why'

The best development partner is not necessarily the one with the longest technology list. It is the team that can translate your goals into a realistic scope, show its reasoning and remain accountable from planning through handover.

At ZA TechLabs, our approach brings web development, software, SEO and business technology into one conversation. We start with the problem and recommend the build that fits it. See how we approach web development or book an introductory discussion.

Further reading: What goes into a custom business website? · Plan a business website project with confidence

KEEP READING

More
insights.

All insights ↗︎
START WITH A HELLO

Let’s buildsomethingworth making.

Thirty minutes, your ideas and someone who knows their stuff. A free first chat to see what makes sense.

  • Talk to the people doing the work
  • Clear pricing in ZAR or USD
  • Replies in about 3 hours
  • A clear plan before we start
  • One team for build, growth and cloud
  • A clear handover when we’re done
  1. 01FREE 30 MINUTE INTRO CALLPick a time, bring your questions and meet the team. We’ll be honest about whether we’re the right fit.
  2. 02GETTING INTO THE DETAILSWe get into your goals and current setup. You leave with useful advice, whether or not we work together.
  3. 03FIXED SCOPE PROPOSALA clear plan, timeline and price in ZAR or USD. You know what’s included before you say yes.

Book a free intro call