What being a solo consultant buys you:

Consultants are paid for what they think. Someone with a budget has a problem. They’ve already spent money trying to fix it, and they’ve probably asked AI too. Now they want an outside view from someone who’s been through it before. You look, tell them what you’d do, and help them decide.

Your technical skills come with you. You might build a prototype or show their team how you’d do it. But nobody assigns you what to build. And the project doesn’t depend on you to ship.

Consultants can tell clients the truth. You don’t report to anyone at your client, so you can say what you see, even when it’s not what they hoped to hear. That honesty is a big part of what clients are paying for.

Consultants own their results. Each client project is a standalone piece of work with your name on it: what you found, what you recommended, and why. If it helps, the client knows it was you. If it misses, that’s yours too.

Consultants can eventually work fewer hours than an employee. On a salary, getting twice as fast just gets you twice the work. On an hourly contract, it cuts your pay in half. AI is making everyone faster, so that gap grows every year. Consultants charge for their impact, not the time it takes. So clients pay the same whether it takes you three weeks or one. As you get better, you can also charge more. Then the same income takes fewer hours.

Consultants build a reputation that carries over to the next technology. A reputation built on knowing the newest technology resets every few years, and AI is making that happen faster. A reputation for sound judgment carries over to whatever comes next, and it grows with every client you help.

Consultants don’t have to chase clients forever. Early on, you reach out to find work. Over time, the people you’ve helped tell others. Someone you’ve never met comes to you with a problem you’ve already solved, because they heard how it went.

Your guide

I’m Jayme Edwards, host of the “Developer Reborn” and “Healthy Developer” YouTube channels. Over 30 years in tech, I’ve worked with more than 25 companies, from finance to healthcare to energy.

One day while working for a consulting agency, I was reading a book during lunch. The problems it described were right in front of me at my client. Without being asked, I built a six slide pitch to diagnose what was wrong. The client said yes. When I presented what I found, eight people were in the room. They stopped asking me what I could build, and started asking me what they should do.

I ran that play for years, but the agency billed my hours and my pay didn’t move. I could have been selling that work myself all along. Instead I kept giving the job more of my time. It was the only thing I knew to offer. Mostly it got me overtime. By the time I left, my marriage was in trouble and my kids were teenagers I barely knew. Knowing what I needed to do was never the expensive part. Not moving on it was.

So I went solo as a consultant. And since then I’ve also coached over 150 developers.

What solo consulting asks of you:

Becoming a consultant starts with conversations. Not forming an LLC, and not picking out a perfect specialty or niche before you start.

You talk to people who already know your work, about a problem you see in their world. And you do it more than once.

Some of the people you’ll reach out to are former managers and colleagues who’ve only known you as an employee.

Here’s the message most people send first:

“Hey, hope you’re doing well! I’m starting to do some consulting on the side. If you ever need help with cloud migrations, let me know.”

It’s friendly, and it goes nowhere. The usual reply is “Will do, good luck!” It asks for work and lists a skill, so it reads like someone looking for a job.

An employee asks whether there’s anything available, lists what they can do, and waits to be handed a problem. A consultant arrives already holding one.

Sending the message is just clicking a button. The hard part is sounding like a consultant when you write it. You’ve spent your whole career showing up as an employee, so you won’t notice it in your own writing.

Landing your first client usually takes months, not a week. How long depends on who you know and how urgently they need help.

Most people’s first paid consulting work is a few hours a week alongside their job. Then the consulting side grows until it can replace the job.

If you’re not willing to have these conversations, consulting isn’t the right path for you.

But if you want everything you know to pay off, and keep paying off, this is how it starts.

The workshop is where you do it for the first time, with me in the room.

How it works

The Solo Technical Consultant Workshop takes place over five evenings. It’s live on Zoom with Jayme and a small group of tech professionals like you.

Enroll in the workshop

Use the checkout page to pay and reserve your seat. You’ll receive an email confirming your enrollment and inviting you to a Discord channel for your cohort.

Join your cohort’s Discord channel

Use the link in your confirmation email to join the channel before we start. It’s where you’ll post what you send and anything that comes back. It stays open until a week after Friday’s session.

Show up for five evenings

You’ll receive an email every morning of the workshop. It includes a link to join that evening’s Zoom meeting.

At every session:

  • I teach for about 20 minutes, to prepare you for the session’s main activity.
  • I coach people live, in front of the group.
  • You complete the activity with my guidance and support.
  • A video replay is sent out the next morning.

Attend the breakout session

If you want help staying on course once the workshop ends, I’ll show you what I offer right after Friday’s session.

Your first week as a consultant

This is the fourth cohort of the Solo Technical Consultant Workshop, live with me.

You’ll leave having picked a problem you’ve worked on that you think other companies are struggling with too. You won’t leave with a client, but you’ll have sent at least one message about it to someone who already knows your work.

That’s the hardest part: sounding like a consultant to people who’ve only known you as an employee. The 50 tech professionals who’ve been through this workshop weren’t short on information. They’d just never offered their advice instead of asking for a job.

This is the first week of a road that takes months, and it’s the only part with a date on it. I run this workshop almost every month. If you can’t spare the evenings for this cohort, sign up for the next one. But doing more research isn’t a good reason to wait.

The Solo Technical Consultant Workshop is currently only available to US residents. Outside the United States and want access in your country? Join the regional waitlist. Your interest helps shape where I expand next.