How speech-to-text works
How spoken words become text a machine can read, in real time and with the names spelled right.
Read the explainer →A plain-language tour of the ideas behind a voice you can talk to, with a link to the source paper behind each one, so you can go as deep as you like.
Each thread groups the explainers by the question it answers. Start with whichever one you are curious about.
Turning speech into text, and text back into a natural voice.
7 explainers → Retrieval & knowledgePulling the right facts across many sources, and mapping how they connect.
6 explainers → ConversationThe timing and turn-taking that make a spoken exchange feel natural.
6 explainers → Latency & systemsThe engineering that lets a voice reply without the wait.
6 explainers → Security & infrastructureHow sensitive work stays walled off while it runs.
10 explainers → Data & recordsSpotting duplicates, filling gaps, and turning messy records into one clean truth.
12 explainers → Pipelines & syncStoring, processing, and two-way syncing data across email, calendar, CRM, and tasks.
10 explainers → Models & trainingThe architectures and training ideas behind modern language and speech models.
10 explainers →Find an idea by topic, or search for a question, technique, or tool. Each explainer includes diagrams and a reading list of the original research.
67 explainers
How spoken words become text a machine can read, in real time and with the names spelled right.
Read the explainer →How a model pulls the right facts from a CRM, an inbox, and other sources before it answers.
Read the explainer →How a voice agent knows when you have finished speaking, and when it is the agent's turn to talk.
Read the explainer →What it takes for a voice to answer back fast enough to feel like a real conversation.
Read the explainer →How confidential computing keeps sensitive work isolated while it runs.
Read the explainer →How people, accounts, and conversations connect into a map a machine can follow.
Read the explainer →How written words become a voice that sounds natural enough to listen to.
Read the explainer →How a device listens for one short phrase, all the time, on almost no power, and almost never gets it wrong.
Read the explainer →How a system tells voices apart and labels who said which line.
Read the explainer →How background noise and echo get stripped away so the words come through clean.
Read the explainer →How tone, pace, and stress in a voice carry meaning beyond the words.
Read the explainer →How spoken words in one language become another, in near real time.
Read the explainer →How a model decides to act, call a tool, and use what comes back.
Read the explainer →How a model is held to a strict shape, so its output drops cleanly into fields.
Read the explainer →How answers get tied back to real sources, so a model says less that is not so.
Read the explainer →How a model holds a long history in view and keeps what matters.
Read the explainer →How meaning becomes numbers, so the right passage is found by similarity, not keywords.
Read the explainer →The tricks that make a large model answer quickly, from speculative decoding to smarter serving.
Read the explainer →How personal details get found and masked, and how models learn without exposing them.
Read the explainer →How a system spots that two records are the same account or contact, and merges them into one.
Read the explainer →How fields from different CRMs and tools get lined up so the data means the same thing everywhere.
Read the explainer →How blanks in a record get filled in well enough to act on, without making things up.
Read the explainer →How errors, typos, and contradictions in a dataset get found and fixed at scale.
Read the explainer →How free text and talk become the named fields a CRM expects.
Read the explainer →How near-duplicate names and records get matched quickly across millions of rows.
Read the explainer →How a system decides which value is right when sources disagree.
Read the explainer →How rules and noisy signals stand in for hand-labeled data to train a model.
Read the explainer →How messy names, addresses, and companies get put into one consistent form.
Read the explainer →How a system asks a person only about the cases where their judgment matters most.
Read the explainer →How a model ranks which leads are worth the rep's time, once the data is clean.
Read the explainer →How two parties match records without either one revealing the underlying personal data.
Read the explainer →How all the raw signals get stored cheaply in one place, ready to query later.
Read the explainer →How a change in one system flows to the others within seconds, by watching its log.
Read the explainer →How data gets handled the moment it arrives, not in a nightly batch.
Read the explainer →How two systems update each other and settle on one answer when both change at once.
Read the explainer →How work gets split across many machines to crunch data that will not fit on one.
Read the explainer →How an append-only log of events becomes the single source the rest is built from.
Read the explainer →How a record gets written once and only once, even when a sync retries.
Read the explainer →How copies on different machines end up agreeing, and when they are guaranteed to.
Read the explainer →How a system pulls only what changed since last time, instead of everything.
Read the explainer →How different tools get mapped to one shared shape so they work as a single picture.
Read the explainer →The architecture behind modern language and speech models, and why attention changed everything.
Read the explainer →How words and sounds get chopped into the units a model actually reads.
Read the explainer →How models learn from raw, unlabeled data before anyone labels a thing.
Read the explainer →How a model picks up a new task from a few examples in the prompt, with no retraining.
Read the explainer →How asking a model to show its working makes it reason more reliably.
Read the explainer →How a general model gets specialized to a domain without retraining the whole thing.
Read the explainer →How human preferences shape a model's tone, helpfulness, and judgment.
Read the explainer →How a big model teaches a small, fast one to behave almost the same.
Read the explainer →How a model routes each input to just the parts it needs, for scale without the cost.
Read the explainer →How a model keeps learning new things without losing what it already knew.
Read the explainer →How one system serves many customers while keeping each one's data walled off from the rest.
Read the explainer →How a system decides who can see and do what, and why less access is safer.
Read the explainer →How data is scrambled on the wire and on disk, and how the keys are kept.
Read the explainer →How you prove who you are once and move between systems safely.
Read the explainer →How a system keeps an honest, unchangeable record of who did what, and when.
Read the explainer →Why modern security trusts nothing by default and verifies every request.
Read the explainer →How data gets kept in the region a customer requires, and why it matters.
Read the explainer →What the big compliance frameworks actually ask for, in plain terms.
Read the explainer →How a system reads the mood and aim of a call as it happens, from both the words and the voice.
Read the explainer →How a system works out what a speaker actually wants: a question, an objection, a yes.
Read the explainer →How a system remembers what has been agreed and what is still open across a multi-turn talk.
Read the explainer →How a system knows who "they" and what "it" refer to, turns later.
Read the explainer →How fresh data reaches the app the instant it changes, instead of waiting for a refresh.
Read the explainer →How services talk to each other fast, with compact binary messages over efficient channels.
Read the explainer →How keeping a copy close cuts the wait, and the hard part: knowing when it has gone stale.
Read the explainer →How traffic gets spread across machines, and how the fleet grows and shrinks with demand.
Read the explainer →Try a broader search, choose another topic, or clear your filters.
The ideas are one thing. Put Prism on a real call and watch the note write itself.
No app required, just your phone number.