Real-Time Text for Deaf Freelancers

A solo-work setup for reading client calls and turning them into clear scopes.

Voiskey Voiskey Team
Real-Time CaptionsAccessible CommunicationReal-Time Text Deaf

Prepare for Client Calls

Real-Time Text for Deaf Freelancers begins with a simple question: which client conversations need text, and which do not. Discovery calls, scope reviews, and handoff meetings benefit most, because they carry decisions that are easy to mishear. Status updates can often stay in writing. List the recurring conversations in your calendar and mark the ones where a missed line would cost time or money. Then decide how you will join each one: a video call with the text beside it, or an in-person meeting with a device at the table. A short list turns a vague worry into a plan. Send the explanation with the meeting invitation so the client knows before the call.

Prepare a client-facing explanation you can reuse. Write two sentences that say you read spoken conversation as text and that a short pause before you answer is normal. Add one line about how the client can ask for a repeat. Keep the explanation friendly and brief. Send it with the meeting invitation so the client is not surprised when the call starts. A prepared explanation removes the awkward moment of introducing an accommodation in the first minute, and it lets the conversation begin with the work itself. Send the explanation with the meeting invitation so the client knows before the call. Pack the call kit the night before and test the shortcut once.

Set up a call kit that works from any desk. A laptop, a headset, a stand, and a cable cover most situations. Add a second device as a backup in case the first one needs an update at the wrong moment. Test the shortcut before the call, not during it. Keep a quiet space and a plain background, because a cluttered room makes reading harder even when the text is clean. A kit that is packed and tested before the call gives you the calm to focus on the client rather than on the equipment. Send the explanation with the meeting invitation so the client knows before the call.

Decide how you will handle a call that runs long. Long calls produce long text, and long text is tiring to read. Plan a break at the halfway point and a summary at the end. Ask the client to send the agenda in advance so you can prepare questions. If the call is likely to exceed an hour, propose splitting it into two sessions. A plan for the duration protects both your attention and the quality of the notes you take away. Send the explanation with the meeting invitation so the client knows before the call. Pack the call kit the night before and test the shortcut once.

Run a Discovery Call in Text

A discovery call has one goal: understand the client's problem well enough to propose a scope. Ask the client to describe the situation in their own words, then wait. Read the full answer before asking the next question. Keep the questions short and open: what happens now, what has been tried, and what a good outcome looks like. Write each answer in a note beside the question. A discovery call that follows a fixed question list produces a usable record and prevents the conversation from drifting into a general chat. Write each answer beside its question so the notes read as a single document.

Explain the reading rhythm at the start of the call. Say that you will take a moment to read each answer, and that the pause is normal. Ask the client to finish a thought before starting the next one. If the client speaks quickly, ask them to slow down rather than asking them to repeat a whole paragraph later. Offer a signal for a missed line. A client who understands the rhythm usually adjusts within a few minutes, and the call settles into a steady pace that suits both sides. Write each answer beside its question so the notes read as a single document.

Capture decisions as they happen. When the client agrees to a constraint, a date, or a budget range, write it in the note and read it back. Ask a direct question to confirm: is that the number we should plan around? If the client hesitates, mark the item as open rather than filling the gap with an assumption. A discovery call often contains one or two decisions that shape the whole project. Reading them back while the call is live is the simplest way to keep them accurate. Write each answer beside its question so the notes read as a single document. Mark any item the client hesitates on as open rather than assumed.

Close the call with a short recap and a clear next step. Summarize the problem, the constraints, and what you will send next. Ask the client to correct anything that is wrong. Then say when the proposal will arrive and what it will contain. Write the recap into an email draft before you leave the call. A client who hears a clear next step is less likely to wonder what happens now, and you leave with a record that matches what was actually agreed. Write each answer beside its question so the notes read as a single document. Mark any item the client hesitates on as open rather than assumed.

Turn the Conversation into a Scope

A scope turns a conversation into a set of promises, so it deserves careful wording. Draft it the same day, while the call is fresh. Use the discovery notes as the source and write each item as a deliverable with a boundary. Say what is included and what is not. If the client asked for something you did not discuss in detail, mark it as an assumption to confirm. A scope that lists boundaries prevents the slow expansion that turns a small project into an unprofitable one. State every dependency and the date the client must provide the material. Ask for confirmation item by item instead of a general approval.

Separate the work from the price and the schedule. Describe the deliverables first, then the timeline, then the payment terms. Keep each section short and concrete. If a deliverable depends on the client providing material, say so and give a date by which it is needed. A dependency stated in the scope is easier to raise later than a dependency remembered in a call. Clear sections also make the proposal easier to read on a small screen and easier to approve without a second meeting. State every dependency and the date the client must provide the material. Ask for confirmation item by item instead of a general approval.

Write the revision terms in plain language. Say how many rounds are included, what counts as a round, and what happens when a request falls outside the scope. Keep the language neutral and specific. A client who understands the revision limit is less likely to ask for endless small changes. If the project is complex, add one line about how new requests will be handled: a written change request with a new date and a new price. Clear terms protect the relationship as much as they protect your time. State every dependency and the date the client must provide the material. Ask for confirmation item by item instead of a general approval.

Send the scope with a short cover note that points to the key sections. Ask the client to confirm the deliverables, the timeline, and the revision terms in a reply. Do not ask for a general approval; ask for confirmation of specific items. If the client edits the document, keep both versions and note what changed. A scope confirmed item by item is far easier to work from than one approved with a single word, and it gives both sides a reference when the project gets busy. State every dependency and the date the client must provide the material. Ask for confirmation item by item instead of a general approval.

Capture Quotes with Voiskey

Client calls produce phrases worth keeping: the problem in the client's own words, the outcome they want, and the constraint they care about. Capture those phrases right after the call with Voiskey. Open a note, press the shortcut, and speak the exact sentences you remember. Voiskey removes filler words, stutters, false starts, and self-corrections, so the note reads cleanly. Mark each phrase as a quote or a paraphrase. Exact client language is valuable in a proposal because it shows you listened and it names the problem the way the client sees it. Mark each captured phrase as a quote or a paraphrase. List the assumptions beside the quote and read them in the cover note.

Use Voiskey to draft the proposal in the field where you already type. Speak the sections in order: the problem, the approach, the deliverables, the timeline, and the terms. Voiskey adapts punctuation, formatting, tone, and word choice to what you are trying to do, so a spoken draft reads as a professional document rather than a transcript. Edit the result on screen, then read it aloud once to catch a sentence that sounds stiff. A proposal drafted from spoken notes is faster to produce and closer to the way you actually talk to clients. Mark each captured phrase as a quote or a paraphrase.

Voiskey learns names, jargon, acronyms, and spelling preferences, which matters when a client uses industry terms. Say each client name and technical term once, correct it at the insertion point, and reuse the correct spelling. Keep a short glossary for each client: their product names, their team titles, and the abbreviations they use. Correct spelling signals that you pay attention, and it prevents a proposal from looking careless on the first page. A glossary also speeds up the next proposal for the same client. Mark each captured phrase as a quote or a paraphrase. List the assumptions beside the quote and read them in the cover note.

Record the agreed quote and the assumptions behind it. A quote without assumptions is an invitation to dispute. Write the assumptions in the note: the number of meetings, the turnaround time, the material the client will provide. Read them back to the client in the cover note. If an assumption changes, update the quote rather than absorbing the difference silently. A spoken record of the assumptions makes the quote easier to defend and easier to revise when the project shifts. Mark each captured phrase as a quote or a paraphrase. List the assumptions beside the quote and read them in the cover note.

Download Voiskey and Set Your Terms

Download Voiskey and make it part of your client workflow. Voiskey is a voice typing app for macOS and Windows that works at the system level: press a shortcut, speak, and text appears at the insertion point in any app or text field. Use it to capture discovery notes, draft the scope, and write the cover note in the tools you already use. Practice the shortcut before a live call so it is automatic when a client asks a difficult question. A familiar workflow lets you spend your attention on the work rather than on the mechanics. Save the meeting explanation and revision terms as reusable paragraphs.

Set your terms once and reuse them. Keep a small library of paragraphs: the meeting explanation, the revision terms, the payment schedule, and the assumption list. Speak each one into a template and save it. When a new client arrives, adapt the template instead of starting from a blank page. Review the library every few months and remove anything that no longer matches how you work. A reusable library turns a repeated negotiation into a short, predictable step. Save the meeting explanation and revision terms as reusable paragraphs. Send a written change note when a request falls outside the scope. Keep the change note short so the request and the new terms are easy to approve.

Protect your time with a simple rule for new requests. If a request is outside the agreed scope, reply with a short note that describes the change, the new date, and the new price. Do not absorb the work silently. Keep the note polite and factual, and attach the updated scope. A clear rule makes the conversation easier for both sides and prevents the slow drift that turns a good client relationship into a stressful one. Save the meeting explanation and revision terms as reusable paragraphs. Send a written change note when a request falls outside the scope. Keep the change note short so the request and the new terms are easy to approve.

FAQ s

Voiskey is an AI voice typing app that works at the system level. When the client speaks, readable text appears at the insertion point on your screen. It removes filler words, stutters, and false starts and adapts punctuation, so discovery answers and constraints are easier to read while you take notes.

Yes. Speak the sections in order: the problem, the deliverables, the timeline, and the terms. Voiskey adapts tone and formatting to what you are trying to do and learns client terms you correct. Edit the polished draft on screen, then read it aloud once before sending the scope.

Voiskey learns names, jargon, acronyms, and spelling preferences. Say each client name and technical term once, correct it at the insertion point, and reuse the corrected spelling. A short glossary for each client keeps the proposal consistent and speeds up the next document you draft.

Speak the client's own phrases about the problem and the outcome, then speak the assumptions behind the quote. Voiskey polishes the note and learns the names involved. Mark each phrase as a quote or a paraphrase, and read the assumptions back in the cover note.

Say less. Get more
Say less. Get more
Say less. Get more
Say less. Get more
VoiskeyVoiskey

Your voice, amplified.

Download Voiskey for Mac and Windows and caption your next conversation in seconds.

Use it across macOS, Windows, iOS, and Android

Use it across