CLONE VOICE TEAM

17 workstreams, one context each.

Clone Voice builds someone's voice from a few seconds of audio and speaks 80+ languages with it. Precisely because that is easy now, whose voice gets cloned — and with whose permission — is a workstream of its own.

17

workstreams this needs

4

kinds of user we build for

8

steps every workstream follows

WHO IT IS FOR

Who Clone Voice is built for

The people making something with it, the people taking it to market, the people wiring it in — and the one nobody should forget: whoever the voice belongs to.

Producers

The people making e-learning and audiobooks with it.

Workstreams serving them12

  • Clone quality
  • Multilingual speech
  • Editing and export
  • iOS development
  • Android development
  • Microsoft add-in
  • SEO and content
  • Sales
  • Help content
  • CS / QA
  • Feature requests
  • Billing

Marketers

The people who need the same message in more languages.

Workstreams serving them6

  • Multilingual speech
  • Microsoft add-in
  • SEO and content
  • PR / SNS
  • Sales
  • Feature requests

Voice owners

Whoever the voice came from. Consent starts here.

Workstreams serving them3

  • Clone quality
  • Consent and rights
  • Security

Developers

The people building it into a service of their own.

Workstreams serving them2

  • MCP / API
  • Help content

THE ROSTER

The workstreams behind Clone Voice

One workstream, one objective. What follows is not a snapshot of who is busy today — it is the set of workstreams this product needs.

Making the voice

4

Build the voice, make it speak another language, and keep it something we are allowed to use.

Clone quality

Get from seconds of audio to a voice you cannot tell from the original.

Producers Owners

Multilingual speech

Sound like a native of each of the 80+ languages, not like a translation.

Producers Marketing

Editing and export

Fix a phrase, a pause or the pace without going back into a recording booth.

Producers

Consent and rights

Whose voice, used by whom, for what. No clone without permission.

Owners

Running where it is needed

3

A voice is wanted where the writing and the recording happen, so it has to reach those places.

iOS development

Record and generate on the spot, on iPhone and iPad.

Producers

Android development

Deliver the same on Android, so a chance to record is never lost.

Producers

Microsoft add-in

Send what someone is writing in Office straight into a voice, without leaving the document.

Producers Marketing

Connecting it up

1

What the screens can do should be reachable from outside tools and AI agents too.

MCP / API

Let outside tools and AI agents work with Clone Voice's features and data.

Developers

Getting found, and sold

3

Building it is not enough. These carry someone from never having heard of it to using it.

SEO and content

Be findable, and say what it does before anyone has to ask.

Producers Marketing

PR / SNS

Keep saying, outside, what this is actually for.

Marketing

Sales

Find the right prospects, make the case, and keep the thread alive. An agent researches and drafts; a person has the conversation.

Producers Marketing

Standing behind it

2

Nobody gets stuck after they start, and what they tell us turns into a fix.

Help content

Let people solve it themselves instead of waiting for support.

Producers Developers

CS / QA

Answer what comes in, and turn it into a fault that cannot happen twice.

Producers

Deciding what comes next

1

The workstream that runs before anything is built: what was asked for, read against how it is used.

Feature requests

Gather what users ask for and what usage shows is missing, and decide what gets built next.

Producers Marketing

Holding it up

3

It stays up, it stays protected, and the billing adds up.

Server watch / log analytics

Find errors and slowness first, so nobody meets them mid-task.

Security

Check on every change that what must be protected still is.

Owners

Billing

Bill what was used, correctly and on time.

Producers

THE LOOP

How one workstream moves

Every workstream turns the same way. A person sets the objective, an agent does the work, and the decision to ship comes back to a person.

See the eight steps

See how a change gets released

  1. 01
    Set the objective

    A producer, a marketer or the owner of the voice — who it gets better for, and how. People decide that.

  2. 02
    Open the session

    One session per workstream, started with the code conventions, the past decisions and the current numbers already in hand. A workstream that turns into a long piece of work gets a branch of its own.

  3. 03
    Build it, review it

    Changes go out small, through review and an automated test suite, onto a staging environment — and a person makes the call to put them live.

  4. 04
    Check the number

    Did it make anyone flinch? We check that with the numbers and with our ears.

ONE AT A TIME

That is how this much stays covered

The workstreams do not all run at once — one moves at a time. Neither voice quality nor consent slips because one conversation only ever holds one workstream.

Instructions do not mix

Improving multilingual speech never pushes consent work down the list. The side in a hurry does not get to shove the side that protects.

What is shared, and what is not

Code conventions and the quality bar are the same across the whole project. What stays separate is the mission and the context around it.

Context survives

Decisions accumulate inside each workstream, so picking it up again does not start from zero.

Long ones get their own branch

When a workstream turns into a long piece of work, it moves to a branch of its own. The work is kept apart the same way the context is.

Ship small

Many small changes rather than one large one — each inside a range we can roll back.

STILL OURS

What people decide

More agents does not move the responsibility. That stays with people.

  • Whose voice we clone

    A voice belongs to the person it came from. However much else is automated, consent stays a human check.

  • What we will not do

    We can do more than before. That is exactly why the decisions worth our time are the ones to decline.

  • What we promise clients

    Dates, estimates, quality. A company promises those, and a company is people.

  • What goes to production

    Review and merge. A person presses the last button.

LET'S TALK

Your product can move the same way.

The way we run Clone Voice is the way we run the work clients bring us. Tell us what you need moved first.

Talk to us