What should I have ready before I call someone?

A first call goes far better when you arrive organised, and organised does not mean technical. It means having a handful of plain facts and honest answers ready, so the conversation is about your actual situation rather than twenty minutes of them trying to work out what you have. Here is the short list worth preparing.

Step by step

1. Write a plain description of what it is and what you wantIn a few honest sentences, say what the app is, who uses it, and what you want to happen next. "It is a booking system for my studio, clients use it, and I need it secure enough to take payments" is plenty. You are not writing a specification; you are giving a partner the shape of the thing quickly so the call can go deeper. This single paragraph, prepared beforehand, saves the first ten minutes of every conversation and helps you sound clear about your own goal.
2. Note the tool you built with and where things liveWrite down which builder or platform you used, and anything you know about where the pieces sit: is there a code repository, where is the data, what services does it connect to. If you do not know some of these, note that too, because the gaps are as useful as the facts. A partner hears "built in Bolt, data is somewhere in Supabase, not sure about the keys" and immediately understands your situation. You are handing them a map, even an incomplete one, rather than making them draw it blind.
3. Prepare safe access so they can actually see itArrange a way for them to look at the app during or soon after the call, without handing over your crown jewels. A screen-share of you clicking through it works well early on. If they need to see the code, read-only access to the repository is safer than full control. Never gather up live passwords and secret keys to email over; a good partner will not ask for them that way. Having safe access ready turns an abstract chat into a real assessment much faster.
4. List what is broken and what worries youJot down the concrete problems, the visible ones like a broken form, and the nagging ones like "I do not know if my customers' data is safe". Include the questions you cannot answer about your own system. This list is genuinely valuable, because it points a partner straight at what matters to you and often reveals the real job behind the obvious one. Bringing your worries, not just your bug list, lets a good partner address the thing you are actually anxious about rather than only the symptom you noticed.
5. Decide your rough budget and timelineHave a rough range in mind for what you can spend and by when you need it, even if loosely held. You do not have to lead with a number, but knowing it lets you steer the conversation toward realistic options rather than daydreams. If a partner asks and you share a range, a good one uses it to shape a sensible plan, not to bill up to it. Arriving with a sense of your own limits keeps the call grounded and helps both sides know quickly whether you are a fit.