Tenor is the interface studio for AI-built software
Tiffany4 min read
We started Tenor with a simple conviction: AI could make interface design more immediate, visual, and conversational.
A person should be able to bring a reference, describe an idea, and watch it become a working component. They should not need to translate every design decision into CSS values or reconstruct the result in another tool before it could become software.
Our early design sprints proved there was something powerful in that interaction. People could move from an idea or screenshot to interactive React quickly. They could make something, respond to it, and continue shaping it through conversation.
That’s increasingly how software gets built with AI. The logic works, the data flows, the application exists. Then the builder looks at the interface and realizes that a working app is not the same as finished.
The next evolution of Tenor
Tenor is becoming more focused.
What we're not doing:
- Trying to become another full-stack app builder.
- Rebuilding Figma around a prompt box.
- Chasing the idea that one perfect prompt should produce a finished product.
Tenor is the interface studio for AI-built software.
It sits between the first working version your coding agent creates and the implementation you are ready to stand behind.
Bring Tenor a rough component, an existing piece of React, a screenshot, or a visual reference. Work with the result as live software. Describe the visible change you want. Compare directions. Refine the strongest version until the component feels like it belongs to the product around it.
Then continue with that working component in Codex, Claude Code, or the codebase where the rest of the product is being built.
What stays and what gets stronger
The things our early adopters responded to are still central to Tenor:
- starting from visual references and real product intent
- working with interactive components instead of static mockups
- directing changes through conversation
- seeing the result immediately on a live canvas
- carrying working React back into an existing build
What changes is the standard we are building toward.
The next component should not feel like another one-off. It should feel like it was always meant to be in the product you’re building.
Who Tenor is for now
Tenor is for people who can already get software working with AI and care enough to notice when the interface still does not feel right.
They already have something.
They have a working application whose interface stopped at the first plausible answer. A component that almost matches the reference. A client product that keeps drifting with every change. A coding agent that can implement anything but does not always know what belongs.
Tenor gives your work a focused place to become more intentional.
Start with what you know
You don’t need to move your entire application into Tenor or adopt a new end-to-end workflow. Bring one real component. Bring the reference for what you meant. Make one change you can judge.
See whether Tenor helps you close the distance between what your agent made and what you are ready to show.
To everyone who joined an early sprint, became a member, shared a component, or sat down with us on a call — thank you.
The enduring value of Tenor is about refining what you built to look as good as you imagine, which goes beyond simply making UI appear.
Tenor is the interface studio for AI-built software. If your product works but its interface still feels like a draft, Tenor is for you.