Compare book-making approaches by your needs, available time, source material, and review responsibilities.
You already explain your best ideas to clients, colleagues, and audiences. Join Mike Giannulis, founder of Dictate, for practical 10- to 15-minute episodes on turning that spoken expertise into a published book through conversations with an AI interviewer. Each episode gives experts, coaches, and business owners one clear step to capture their ideas, shape their message, and move their book forward.
Episodes of this show are narrated by an AI-generated voice.
Every approach to book-making makes a different promise. But the promise isn't what matters. What matters is the work it asks of you, and whether your voice survives the process.
Welcome to Talk Your Book Into Existence with Mike Giannulis, founder of Dictate. Learn how to turn the ideas you already share out loud into a published book, one conversation at a time. Today, you will leave with one practical step you can use on your own book.
A quick note before we begin: this episode is narrated by an AI-generated voice.
What Each Path Actually Asks You to Do.
Before you pick a process for getting your book done, ask what the process needs from you and what it delivers. Features and price matter, but they do not tell you how your working week will look. Compare the actual tasks: preparing material, explaining ideas, reviewing pages, answering questions, and making decisions.
In my book I compare several approaches: writing yourself, hiring a ghostwriter, using an AI tool, and combining coaching with AI assistance. These are useful categories, not an exhaustive list. You can combine them, and providers within the same category may work very differently. The aim is to find a process that suits your reader, material, resources, and preferred way of working.
Writing yourself gives you direct control over the draft. You can start with notes, an outline, or a rough explanation of a question your reader asks. You still need to revise and check the result. Enjoying the subject does not automatically make drafting easy, but neither does a slow start mean you cannot write a book.
Plan for more than first-draft writing. You may need to reconnect chapters, replace an opening that no longer fits, check examples, and remove repeated explanations. The time required varies with scope, research, experience, and the help available. Instead of treating a general estimate as your deadline, try one short section and measure the work involved. Include revision in that experiment. A fast first draft followed by substantial corrections is useful information about your process.
If you enjoy writing and can protect regular time for it, this may suit you. If the project has repeatedly stalled, identify which task stalls first. Difficulty choosing an order calls for different help from difficulty finding examples. A method can work well in principle and still be a poor fit for your current schedule.
A ghostwriter may begin with interviews, recordings, documents, or a combination. You provide the ideas and review the resulting prose. Ask how much preparation the interviews require, who checks factual claims, and how you will see progress. Hiring writing help can change your workload, but it does not remove your responsibility for what appears under your name.
Reviewing someone else's version of your thinking takes attention. If a sentence sounds wrong, identify why. Is the vocabulary unfamiliar, the claim too strong, or the example missing an important detail? Specific feedback gives a writer something to change. Agree on how comments will be handled before a large amount of prose accumulates. You want a process that makes disagreement productive, with a clear next draft and a record of decisions.
Ask for a schedule based on your project, including interviews, draft delivery, your review windows, and revisions. Check what happens when either party misses a date. A promised completion date is less useful if the review time it assumes will not fit your calendar.
AI tools also vary according to the material and instructions you provide. A broad topic prompt gives the system little of your own experience. A transcript, carefully chosen example, or existing explanation supplies more context. Neither input guarantees an accurate result. Compare the draft with the source, identify additions, and check whether qualifications survived. Ask what the tool does when information is missing: does it ask a question, mark a gap, or produce plausible wording that you might mistake for something you said?
A coach working alongside AI may help with scope, accountability, and review. Ask what that support includes. A meeting schedule and encouraging feedback are different from detailed editorial work. If the service includes an AI interviewer, ask to see how an answer becomes a paragraph. Notice what was kept, what was rearranged, and what was added. Judge the actual workflow rather than assuming a label guarantees depth or fidelity.
Alongside price and timeline, ask where the material comes from and how changes are checked. For a book based on your expertise, you want a dependable route from your explanations to reviewed prose. The next step is to test that route on a small piece of your own material.
If you want to work through this process in more detail, my book, Talk Your Book Into Existence, is at startdictate.com/talk-your-book. The link is also in the episode notes.
Test How the Process Preserves Your Voice.
Next, look at voice. In my book, I treat preserving the author's voice as a priority throughout the process. Here that means more than inserting a favorite phrase. It includes how you explain a problem, the distinctions you make, and the strength of the claims you are willing to defend.
A reader needs a clear explanation and reasons to trust it. A recognizable voice can help make that explanation feel connected to a particular author, but it does not replace accuracy or useful content. When you review a sample, look at both. Does it sound like something you would say, and does it express what you actually mean? A fluent paragraph can fail either test.
So how do you evaluate any process on this dimension before you commit to it?
Start with a concrete example. Think about how you explain your work to a new client or colleague. You may lead with a story, a question, or a distinction. You may use short sentences for instructions and longer ones when you discuss exceptions. Choose an explanation you already have permission to share, remove private details, and use it as a reference. You do not need to turn every spoken habit into a rule; the aim is to recognize the patterns that make the explanation yours.
Ask a prospective collaborator how they preserve those patterns when turning a conversation into prose. Notes, transcripts, and recordings offer different levels of detail. A draft will involve choices about order and wording. Ask which changes will be shown to you and how your corrections will guide later chapters. A vague answer is a reason to ask for a demonstration, not proof that the process will fail.
For an AI-assisted process, inspect the same steps. Supplying your own speech or writing gives the tool material to work from. It can still alter emphasis or introduce language you would not use. Labels such as extraction or generation do not establish the quality of the result. Compare the source and the draft. Find one paragraph that preserves your meaning and another that needs work, then explain the difference.
Try reading a short sample aloud, followed by a short piece of your own writing on a similar subject. Notice vocabulary, sentence rhythm, and how strongly each version states its conclusions. An email and a book chapter serve different purposes, so they need not sound identical. Use the comparison to identify specific changes, then ask for a revised sample. The revision tells you whether your feedback leads to a better fit.
Ask who checks the claims, how many review rounds are included, and how unresolved questions are tracked. If a draft changes might to will, it has strengthened a claim even if the sentence sounds smoother. If it turns a hypothetical example into a story about a real client, that is a substantive error. Explain these distinctions during the sample review so they become part of the working process.
A sample based on your material can provide useful evidence alongside references, relevant experience, and a clear description of the work. Ask about its scope and any cost before commissioning it. A provider may have legitimate limits on unpaid samples. You are trying to reduce uncertainty about a major project, not to demand a complete chapter for free.
The Three Questions to Ask Before You Choose.
So now you have the framework. Four paths, each with a different distribution of work, a different voice risk, and a different kind of review responsibility that lands on you. The question is: how do you actually make the decision?
I want to give you three specific questions to take into any conversation with any provider. Not generic due diligence questions. The ones that surface the structural issues we just talked about.
Question one: where does the content come from? You want a clear, specific answer to this. Does the process start with you talking? And if it does, how does your speaking get turned into prose? Who does that translation, a human or a system, and what's the mechanism for preserving the words and patterns you actually use? If the answer involves generating content about your topic rather than capturing content from you, that's important information. It doesn't make the provider dishonest. It tells you what the process is designed to do and what it isn't.
Question two: what is my actual review responsibility? Every path requires something from you at the review stage, but they require different things. Writing it yourself means you're the editor of your own prose, which requires a skill set you may or may not have. With a ghostwriter, you're evaluating a translation of your thinking and flagging where the voice diverges. With an AI-extraction process, you're reading content that came from your own conversations and checking it for accuracy and completeness. With any AI-assisted draft, check both the source-based material and any additions. Your review includes accuracy, emphasis, completeness, and voice.
Get specific about what review looks like. How many rounds are included? What happens if you read the draft and something is factually wrong? What happens if a section doesn't capture your actual position on a topic? If the answers are vague, the review responsibility may be larger than the process description suggests.
Question three: can I see a sample drawn from a real conversation with me? This gives you a practical comparison. A portfolio of other people's books is evidence that a provider can produce books. It's not evidence that they can produce your book, in your voice, from your knowledge. One useful piece of evidence is a page or a few paragraphs written from an actual session with you.
If a provider says the sample comes after you sign, that's worth noting. It's not automatically a red flag. Some workflows don't produce a sample until onboarding. But if a sample isn't available at any point before you commit, ask directly: what would it take to get one? Use the answer to decide whether the available evidence is sufficient for you.
Here's how these three questions work together. The first one tells you what the process is actually designed to do. The second one tells you how much of the outcome depends on your own effort at the review stage. The third one gives you empirical evidence rather than a promise.
None of these questions are adversarial. They're practical. You're making a significant investment of time, and in many cases, money. You deserve a clear picture of the work, the risk, and the outcome before you commit.
The right process for you isn't necessarily the fastest one, or the cheapest one, or the one with the most impressive-sounding technology. It's the one where the content comes from you, where your voice is protected by design rather than by luck, and where the review responsibility is sized for what you can realistically sustain alongside everything else you're managing.
Before choosing a book-making process, write down what you need help with and how much time you can give to the work. Ask how your material becomes a draft, what you must review, and how corrections are handled. Where practical, compare a short sample based on your own explanation with the source. Look for accuracy, familiar phrasing, and a useful response to feedback. Consider that evidence alongside scope, cost, schedule, and relevant experience. Your next step is one specific question or a small test, not a commitment to an entire book project.
Take the next small step on your book today. For more guidance, find Talk Your Book Into Existence at startdictate.com/talk-your-book.
Visit startdictate dot com slash talk your book.
Next time on Talk Your Book Into Existence: What an AI Interviewer Can and Cannot Do. Learn how a structured conversation can turn your explanations into draft material, and why the author still needs to review the result. Follow the show so the next episode is ready when you are.
Thanks for listening to Talk Your Book Into Existence. Follow the show for your next practical step, and share this episode with someone who has a book in them. Your next conversation could be the start of a chapter.