Skip to content
Menu
Discuss your project

How to choose a web developer before paying a deposit

DevNomadPublished Updated

Before paying a deposit, ask the developer to show a similar working feature and explain how you will test yours. This makes the scope and the result you are buying clearer. A portfolio on its own will not answer those questions.

Test the work before you commit: Working demo → Written quote → Access and source code

Ask for a demonstration of the task you need

For a website that takes payments, follow a purchase from product selection to order confirmation. Ask what happens after a declined payment and who receives the notification. For a bot, try a question outside its menu and the route to human support.

A demonstration does not need to expose client data. A test environment or recording may be enough. Restricted access to a client project is reasonable, provided there is another way to demonstrate the relevant work.

Turn the quote into testable results

“CRM integration” leaves important questions open. Which fields reach the record? Who owns the lead? What happens after a repeated submission? Put the answers in the proposal.

For example, one inquiry creates one CRM record with the name, phone number and service. If the CRM is unavailable, the inquiry is saved and sent later. This is an illustrative acceptance requirement, not a claim about a completed project.

Ask the developer to identify copywriting, data migration, analytics setup and third-party costs separately. You can then compare proposals for the same work.

Make each line of a quote testable
Proposal wordingWhat to ask
Payment integrationHow is payment verified and the purchase delivered?
Client portalWhat can customers see, and how are permissions checked?
Website handoverWhich accounts, source files and instructions will you receive?
Post-launch supportWhat are the response times, working hours and paid changes?

Agree on milestones and account ownership

Each stage should produce something you can inspect: a design, a test site or a working flow. Agree when you will see it and how to give feedback.

Find out who registers the domain and service accounts, when source code is handed over and how the site can be restored from a backup. Use a separate account with suitable permissions instead of sending a shared password in chat.

Record the agreed revisions and how additional requests are priced. Discuss a change in scope or deadline before the extra work begins.

If the project is already delayed

Ask for the current version, completed features and the specific obstacles to finishing. Separate missing materials you need to provide from unfinished work by the developer. Agree on a small next milestone with a clear test.

Before changing developers, collect account access, source code and a backup. A missing handover can take longer to resolve than an individual defect.

You can send DevNomad an existing quote and describe the customer action that matters most. This is enough to identify what still needs clarification.