It's social proof that you're an expert. You'll often get work just by being at these places in the role of a speaker, if you're looking for it. There are many people who have clients they either don't like the work from the client, or want to get help with a thing -- so they can handoff clients/work to you.
We are talking about consulting right? You want to pitch technical topics to non-technical (owners presumably)?
Find a way to meet them and literally tell them that "you wrote the book on that (said subject that will... Fill in the blank)". Then hand them a copy of the book .
Folks like to work with experts (or people who are passionate enough to write a book).
I mean how should non-technical prospects find you? They don't go to such tech talks/conferences, don't read tech books. Such clients usually go to software agencies but not to individuals.
So can I write a book on any technical topic or programming languages only?
Like I am / wish to be involved in some projects but they are sparsely related , maybe I can apply the pareto principle to see what is a good balance of my interests and what pays / there is demand for.
My main nut which I like to crack is breaking nat's. It drives me crazy when I can play a minecraft server on nats.
But I also don't want to reveal such things because they work because I spent hours tinkering and if I tell to the world , it would take the nat owners just minutes fixing it. But still , I don't know , I was thinking of creating an article because book seems pretty heavy.
How long does the book have to be , can it be a 50 75 pages long ? or does it have to be insanely bulky like 1000 pages ?
Sorry if I sound a bit immature because I totally am. I always used to think of blogs as a way to increase my reputation but now I am thinking why not both ? the topics I am good at , can really be both blog / article and a mini book.
Should it be digital or should it be by a publisher ?
Maybe start off with a blog to see if you can get traction/attention.
I created a course about technical book authoring and interviewed a dozen authors. Some made a lot of money from writing. Others less so. Those that treated it like a business seemed to make more money (from the book and related activities).
I think my problem is my knowledge isn't very domain specialized.
I know many tips and tricks that you might thank me for telling you about software but they are sparsely connected to each other. They are connected by my journey of software engineering and the interests I gathered along the way.
So blog might be the way to go. I am going to create my first blog now.
Write a book.
Speak (at conferences) about what you want to consult on.
Augment above on social.