← JobCoach
Earn independently

Your first client starts with a problem

A small, specific service gives a potential buyer something concrete to consider.

Professionals reviewing application materials together
AI-generated photographic scene; fictional people.

Your three-step practice plan

  1. Gather your facts

    Who has the problem and how do they describe it?

  2. Make a useful draft

    What limited deliverable can you responsibly offer?

  3. Check and use it

    What scope, price, revision limit, and completion criteria will you agree?

Pick one audience

Choose people whose work you understand and who can realistically buy your service. “Businesses” is broad. “Independent shops that need a clearer customer welcome sequence” creates a much more useful conversation.

Define a manageable deliverable

Explain what is included, how long it takes, what the buyer needs to provide, and how many revisions you will make. Promise a deliverable you control. Avoid guaranteeing revenue or other outcomes that depend on factors outside your work.

Talk before you build everything

Have five thoughtful conversations about how buyers handle the problem today. Listen for urgency, cost, and existing alternatives. Offer a small paid pilot where there is a fit. A portfolio sample can help people understand your approach.

Learn from the pilot

Track delivery time, expenses, revisions, and customer feedback. Compare the work with your agreed scope. Ask permission before using the project publicly. Use what you learn to adjust the service and price before expanding.

← Back to the journal

Turn a skill into a small pilot

Fictional example: a coordinator notices that a small service business loses track of incoming requests. Instead of offering to “transform operations,” the coordinator proposes one shared request tracker and a short handoff guide.

THE PILOT

Set up one tracker using the client's existing tool, test it with sample requests, and walk through the handoff with one team member.

THE BOUNDARY

One workflow, one agreed revision, and a written completion checklist. No promise of increased sales or a full software implementation.

Agree on what finished means

Before starting, put the deliverable, required access, timeline, price, revision limit, and responsibilities in writing. State what the client must provide and how you will handle confidential material. Use a payment arrangement both parties understand.

Define a check the client can perform: can the team enter a request, assign an owner, and see the agreed status? That is more reviewable than an undefined promise to improve productivity.

Learn from the first delivery

Record the time you actually spent, what created delays, which parts the client used, and what questions remained. Ask for feedback about the work, not a testimonial containing a result you have not measured.

If the client wants ongoing support, write a separate scope. If the pilot reveals that the problem requires a different specialist, explain that clearly. A first service should fit the skills, availability, and responsibilities you can genuinely take on.

Use the free offer builder to explore illustrative pricing and capacity, then replace assumptions with your own costs and experience. An estimated revenue scenario is not a forecast of clients or income.

YOUR PRACTICE SHEET

Turn the advice into something useful.

Use these questions with your own experience. Keep your answers in your notes or the editable worksheet.

  1. Who has the problem and how do they describe it?
  2. What limited deliverable can you responsibly offer?
  3. What scope, price, revision limit, and completion criteria will you agree?

Want another perspective? Bring one application, interview, or search problem to the $350 working session.