Type

Type is a multiplayer AI workspace where teams work alongside agents together, not one at a time in separate chat windows. Little Plains built the brand from the ground up: verbal strategy, visual identity, motion direction, and an agent-readable atomic system delivered as the launch kit.

Every team right now has someone using AI well and someone who can't access what they're doing. The best work lives in one person's chat history. Type's founding team, drawn from companies that scaled some of the most-used collaborative products in the world, saw the same pattern at scale: AI was transforming individual output while team output stayed stuck behind the same old coordination ceiling.

The brief was direct. Type needed to enter the market at the moment AI collaboration was becoming real, with a brand that didn't feel like another AI tool. The audience wasn't developers. It was the ops lead, the support manager, the marketing person watching someone else get more done and wondering when it would be their turn.

The central positioning question was: where does Type live relative to everything else? Agents are everywhere. Every tool has one now. The real problem isn't having agents; it's that they all live in separate rooms. Type isn't where you build them. It's where they work. That's the distinction the whole strategy hangs on, and it took getting there by elimination. We spent time ruling out every positioning frame that put Type in competition with the agents themselves before arriving at the one that put it above them.

The persona work helped sharpen it. We kept coming back to one figure: the person watching a colleague pull something real out of AI while they sit locked out of it. Not a decision-maker. Not a builder. The observer who wants in. That's who Type is for first.

The mark started from a conceptual brief: something that suggests multiple forces converging. The marble was the right answer because it's familiar and strange at once. Kids know marbles. They're physical, tactile, a little chaotic. That's not usually how B2B SaaS brands think about their iconography, which is exactly why it worked. The wordmark pairs a lowercase serif "type" with it. The tension between the playful 3D mark and the grounded, classical letterforms is what gives the lockup its character.

The marble system became the visual language of the whole brand. Each sphere is generated, not illustrated — the node-based generative workflow in Flora produced a family of unique outputs from the same base logic, delivered as a reusable technique rather than a set of static files. The marbles float, stack, and group. They live in the background of the gradient fields and in the product as agent avatars. The motion system specifies easing curves and transition speeds that give the spheres their particular physical weight: elements enter fast and decelerate smoothly, then settle without overshoot.

The motion direction came with named principles: calm movement, never overshoots. The names aren't decorative; they're job descriptions. Every agent loading, every thread appearing, every hover state maps to one of four curves. The spec was delivered as a JSON file and as an interactive HTML component the team could feel rather than just read. That's how the whole kit was structured: every piece designed to be ingested by an agent as instructions, not just consulted as documentation.

The final package shipped in two folders. The /human folder contains the brand strategy deck, guidelines PDF, and Figma files. The /agent folder contains everything encoded as instructions: positioning, voice, and audience in Markdown and YAML; colors, typography, and components in CSS and HTML; motion in JSON; marble assets as SVG and PNG. Type's team pulled the kit into their editor, ran a single prompt, and watched a near-complete landing page come together the same day. Correct fonts, working hover states, production copy, motion that matched the spec.

That's what the work is now. The thinking creates the system, and the system extends the thinking.

Type launched in May 2026 with the brand already live in the product, because the founding team had been building from the atomic kit directly in their codebase the whole time. There was no handoff gap, no drift, no version of the brand that existed only in a PDF. The system shipped as working code, and the team kept extending it from there.

See the full experience at type.com.