Scheduling a consultation with a web developer can feel a bit like taking your car to the mechanic. You know something is wrong (or could be better), but you’re worried you won’t speak the language, or worse—that you’ll be sold something you don’t need.
The truth? A tech consultation isn’t an interrogation; it’s a discovery session. It is the bridge between your business goals and the technical tools needed to achieve them.
If you have a consultation booked, here is everything you need to know to feel prepared, confident, and ready to move forward.
How do I prepare?
The most important way to prepare is to define your problem, not the solution.
Many clients spend hours trying to learn technical jargon before a meeting because they think they need to tell the developer how to build the site (e.g., “I need a React app with a NoSQL database”).
Instead, focus on the what and the why.
- What is frustrating you right now?
- Why do you think a new website or software will fix it?
- Who are you trying to serve?
Relax. You are the expert on your business; the developer is the expert on the tech. You don’t need to know how the engine works to tell the mechanic that the car is making a weird noise.
What should I bring?
You don’t need a 50-page business plan, but gathering a few specific items will make the meeting much more productive:
- The “Wish List”: A brain-dump of features you dream of having (e.g., “I want customers to book appointments online”).
- The “Hate List”: A list of things on your current site that drive you crazy.
- Visual Examples: Links to 2-3 websites you love (even if they are in a different industry) and a brief note on why you like them.
- Login Access (Optional): If you already have a website, having your hosting or WordPress login handy saves time if the developer needs to peek “under the hood” to assess the current state of things.
What does the web developer need to know?
To give you an accurate quote and timeline, the developer needs three main things from you:
- Your Budget: It’s not a trap. Telling a developer your budget helps them design a solution that fits. There is a big difference between a $500 solution and a $50,000 solution. Being honest upfront saves everyone time.
- Your Timeline: Do you need this launched for a specific event next month, or is this a long-term project for next year?
- Your Business Goals: Are you trying to get more emails? Sell products? Just look professional? The code the developer writes depends entirely on the goal you are trying to hit.
What should I expect to get out of it?
You shouldn’t expect a finished website at the end of the meeting. Instead, the goal is alignment.
By the end of the call, you should feel that the developer understands your business. You should expect them to explain—in plain English—how they plan to solve your problem. You might get a rough ballpark estimate on cost, or they might tell you they need a day or two to write up a formal proposal. Both are normal.
What should I know when I leave?
Never leave a consultation with a question mark over your head. Before you hang up or shake hands, make sure you know:
- ** The Next Step:** Who is doing what? Are you sending them a logo? Are they sending you a proposal?
- The Timeline: When will you hear from them next?
- The Feasibility: Did the developer say your idea is possible within your budget? If not, do you understand the alternatives they suggested?
What if I forget something?
It happens to everyone. You’ll hang up the phone, and five minutes later you’ll remember, “Oh no, I forgot to mention we need a newsletter sign-up form!”
Don’t panic. Web development is an iterative process. A good developer expects the scope to evolve slightly as you discuss things. Just send a follow-up email with your additional thoughts. It’s much better to mention it late than to wait until the website is finished!