Start with one customer and one hiring situation
A customer journey map is a simple outline of what someone does, thinks, and needs while deciding whether to hire a service provider. It can help you spot questions your website does not answer, delays in your inquiry process, or points where a potential customer may hesitate. It is not a script that every customer follows.
Begin with a specific situation rather than a broad audience. For example, imagine a small business owner who needs a designer to update an outdated website before launching a new service. That journey may differ from one involving a large team seeking ongoing design support. Write down the customer, the problem they are trying to solve, the likely urgency, and the decision you want to understand: hiring a provider for a defined project.
Lay out the steps from problem to project start
Draw a line with five stages: recognizing the need, exploring options, contacting providers, choosing a provider, and getting started. These are working labels, not rules. Some customers move back and forth, pause to secure approval, or return months later. The point is to make the decision process visible enough to discuss and improve.
At each stage, record what the customer might do and what they need to know. The business owner might first ask colleagues why the current website is not working. Next, they may look at examples of similar projects and decide whether to hire a freelancer or an agency. When contacting providers, they may ask about availability, process, and a rough scope. Before choosing, they may compare proposals, check whether expectations are clear, and discuss the cost with a partner. After agreeing, they need to know what information to provide and what happens first.
Add the places where each interaction happens: a referral conversation, a search result, a portfolio page, an email exchange, a call, or a proposal. Also note who else influences the choice. A person who sends the first inquiry may not be the person who approves the work.
Separate what you know from what you assume
Your first map will contain guesses. Mark them as such. You may believe customers worry most about price, while their real concern is whether a provider can meet a deadline or explain the work clearly. Keeping assumptions visible prevents a polished diagram from being mistaken for evidence.
To check the map, review questions from past inquiries, notes from sales calls, and common points of confusion during onboarding. If appropriate, ask recent customers how they found you, what alternatives they considered, what nearly stopped them, and what made the next step feel safe. Ask open questions rather than prompting for praise. Avoid including private details in a shared map; summarize patterns instead.
Look for differences as well as similarities. A referral may arrive ready to discuss scope, while someone unfamiliar with your work may need examples and a clear explanation of your process first. If those routes differ substantially, make two small maps rather than forcing them into one.
Find the moments where clearer information helps
For each stage, ask: What decision is the customer making here? What information would help them make it? What could create unnecessary effort or uncertainty? In the website example, the customer may want to see the kinds of projects the designer takes on before booking a call. A short description of suitable projects and a few explained examples may help them decide whether to inquire.
Match improvements to the specific friction you find. If people repeatedly ask what an initial call covers, explain it near your contact form. If proposals generate the same questions, clarify deliverables, responsibilities, and the steps for requesting changes. If customers agree to work together but stall before kickoff, send a concise checklist of the materials needed to begin. The aim is not to remove every pause; some decisions deserve careful consideration.
Keep the map small and revisit it
A useful first version can fit on one page. Make a row for each stage and add columns for customer actions, questions, contact points, possible obstacles, and ideas to test. Choose one or two changes you can make without redesigning your entire business. For example, revise a service page to answer a recurring question and make your inquiry response explain the next step.
After using the changes for a while, compare new inquiries and conversations with your earlier notes. Are customers arriving with a clearer idea of the service? Are the same questions still appearing? Your map may need to change as your services, customers, or hiring process change. Treat it as a practical guide for learning, not a prediction that guarantees a sale.
