Future StackThe businesses that get the most out of a first consultation call almost always come in with a small amount of preparation, and it doesn't need to be extensive — a handful of clear answers goes a long way toward making that first conversation genuinely productive rather than a broad, exploratory chat that has to happen again later anyway.
The first useful thing to have ready is a rough sense of the problem you're actually trying to solve, stated as plainly as possible. Not "we need a website," but the specific gap — "customers keep calling to ask questions we could answer online" or "we're managing bookings by hand and it's error-prone." This single detail shapes almost everything about how a project should be scoped.
Second, gather a few examples of things you like, even if they're not in your industry. A specific website or app whose layout, tone or functionality resonates with you gives a development partner something concrete to work from, rather than trying to interpret an abstract description of "modern and clean," which means something different to nearly everyone.
Third, have a rough sense of timeline and any hard deadlines, even if the budget itself isn't fully settled yet. A launch tied to a specific event or season changes how a project gets planned and prioritised, and it's far more useful to know upfront than to discover partway through the build.
None of this needs to be polished or complete — a first consultation is exactly the place to work through the gaps together. Coming in with even rough answers to these three questions tends to turn a vague first call into a genuinely useful conversation that moves a project forward immediately.
If you only have time to prepare one of these three things, make it the first — a clear, specific statement of the actual problem. Everything else in a first consultation tends to flow naturally once that's genuinely clear, even if the examples and timeline are still rough.