Working with web developers

Why this matters

Working with developers can feel intimidating if you do not know what to expect. Clear communication, realistic expectations, and good planning make projects run smoothly.

This guide helps you understand the process, ask the right questions, and work together effectively.

What developers do

Technical implementation

Developers turn designs and requirements into working websites.

• Write code that makes websites function.
• Build features and functionality.
• Ensure sites work across different devices and browsers.
• Optimise for performance and accessibility [2]Source 2 [1]Source 1 .

Problem solving

Developers solve technical problems and find practical solutions.

• Work through technical challenges.
• Balance requirements with constraints.
• Make trade-offs when necessary.

How to brief a project

Start with goals

Explain what you want to achieve, not just what you want built.

• What problem are you solving?
• What does success look like?
• Who is the site for?
• What actions should visitors take?

Provide context

Share information that helps developers understand your needs.

• Your business or organisation and what you do.
• Your target audience.
• Your current website and what works or does not work.
• Examples of sites you like or dislike, and why.

Be specific about requirements

Clearly define what you need.

• Must-have features and nice-to-have features.
• Content types and how they will be managed.
• Integration requirements, such as forms, payment, or third-party services.
• Accessibility and performance requirements [1]Source 1 [2]Source 2 .

Set realistic timelines

Allow time for proper development and testing.

• Good work takes time.
• Rushing leads to problems later.
• Discuss timelines early and be realistic.

Questions to ask developers

About their process

• How do you approach projects?
• What is your development process?
• How do you handle testing and quality assurance?
• How do you ensure accessibility [3]Source 3 ?

About technical choices

• Why did you choose this platform or technology?
• How will this affect performance [2]Source 2 ?
• How easy will it be to maintain and update?
• What are the long-term implications of these choices?

About deliverables

• What will I receive when the project is complete?
• Will I own the code and content?
• How will I update content after launch?
• What documentation will you provide?

About support and maintenance

• What support is included after launch?
• How do you handle updates and maintenance?
• What happens if something breaks?
• How do you handle ongoing improvements?

What to expect during development

Communication

Expect regular updates and clear communication.

• Regular progress updates.
• Questions when requirements are unclear.
• Discussion of trade-offs and alternatives.
• Early warnings about potential problems.

Testing and review

Expect opportunities to review and test.

• Access to test versions during development.
• Time to review and provide feedback.
• Testing on different devices and browsers.
• Accessibility and performance testing [3]Source 3 [2]Source 2 .

Iteration

Expect some back-and-forth to get things right.

• Refinements based on feedback.
• Adjustments as requirements become clearer.
• Balancing ideal solutions with practical constraints.

Managing changes

Scope changes

Changes to requirements affect timelines and costs.

• Discuss changes early and understand the impact.
• Be clear about what is in scope and what is not.
• Understand that changes may require additional time or cost.

Feedback

Provide clear, constructive feedback.

• Be specific about what works and what does not.
• Explain why something does not work for you.
• Focus on goals and outcomes, not just implementation details.

Red flags to watch for

• Developers who promise everything without asking questions.
• Unrealistically low prices or timelines.
• Vague answers about process or deliverables.
• No mention of accessibility or performance [1]Source 1 [2]Source 2 .
• Reluctance to discuss technical choices.
• No process for testing or quality assurance.

What makes projects successful

• Clear goals and requirements from the start.
• Good communication throughout the project.
• Realistic timelines and budgets.
• Trust and respect between client and developer.
• Focus on outcomes, not just features.
• Willingness to iterate and refine.

After launch

Handover

Expect a proper handover when the project is complete.

• Documentation of how to update content.
• Information about hosting and maintenance.
• Training on using the CMS or editing tools.
• Access to code and assets if agreed.

Ongoing support

Discuss ongoing support and maintenance.

• What support is included and for how long.
• How to request changes or fixes.
• What maintenance is needed and who handles it.

Building a good relationship

Good working relationships lead to better outcomes.

• Be clear and honest about your needs and constraints.
• Respect developers' expertise and time.
• Provide feedback constructively.
• Trust the process and allow time for proper work.

Next step

If you are planning to work with a developer, start by clarifying your goals and requirements. Write a brief that explains what you want to achieve and why. Ask questions about process, technical choices, and deliverables. Discuss timelines and budgets realistically. Then work together with clear communication and mutual respect. Good collaboration leads to better websites. If you are looking for a developer, get in touch to discuss your project, or use the quote calculator to get an estimate. For help choosing between a designer and developer, see choosing a web designer vs developer. For realistic timeline expectations, see website project timelines.