All product families

Audio companions

Build a character whose appearance, touch and voice belong together.

Start with the experience

A plush reference is the beginning of a development conversation. Decide whether the experience uses fixed recordings, a local recording function or connected conversation before choosing the electronics. These are separate product architectures with different content, power and support requirements.

Discuss this format

Plan the product together

Use the first review to connect the physical format, the content and the operating sequence.

Give the character a physical identity

Bring front, side and back views, the expression, the approximate size and the parts that must remain recognizable. Review fabric pile, embroidery, seams and the position of any attachment on a physical sample. A round keychain character and a larger companion need different handling and internal layouts.

Place the interaction where it makes sense

Describe how a child starts and ends an interaction. A press point needs to be easy to locate without exposing uncomfortable hardware. Speaker placement, the enclosure around the electronics and the fabric all affect the sound. Review the assembled plush instead of approving an uncovered sound module.

Separate the voice from the connection

For recorded audio, approve the exact files and trigger map. For connected behavior, define account setup, connectivity, service ownership, recurring costs and what happens when the service cannot answer. A character name containing AI does not establish which architecture is included in a quotation.

Keep care and packaging part of the brief

Ask how the chosen construction supports access to the power system and any removable assembly. Agree care instructions for that configuration. Check the packed product for presentation, compression and the information needed to start using it.

Prepare a useful sample brief

Provide a reference for each decision and agree how the sample will be reviewed.

AreaBring to the briefReview on the sample
CharacterViews, fabric references, expression and dimensionsSilhouette, seams, embroidery and feel
InteractionTrigger location, scripts and expected responseStart, repeat, stop and unavailable response
AssemblySpeaker, power and access requirementsHandling, sound through fabric and component fit

Explore product references

Open a reference to read its use context, development questions and quotation preparation notes.

Questions before you begin

Resolve the scope before treating a reference as a production specification.

Can we use our own recordings?

Include scripts, approved recordings, languages and content rights in the brief. File compatibility, track mapping and the loading process are reviewed against the selected configuration.

What can be customized?

List appearance, content, controls and packaging changes separately. The team can then distinguish changes supported by the starting platform from work that needs further design or engineering.

How are MOQ and timing confirmed?

Share an order estimate, variant list, target market and shipment date. MOQ, tooling, sample scope and lead time depend on the actual specification and are confirmed in the project quotation.

What should we approve before production?

Agree the sample identifier, materials, control behavior, content manifest, artwork and packaging record. Keep open points separate from approved items and confirm which revisions need another sample.

Read the development guide