Skip to content

Orivon

Before you build it, it needs a shape.

Most products fail long before anyone writes code. They fail in the part nobody helps with: turning an idea into the shape of a real product, and the shape of a company around it. Orivon is what I'm building for that part.

An idea

A shaped product

The same idea, from a feeling to a form.

I went looking for help with this. There wasn't any.

When I had an idea of my own, I wanted to shape it properly before building anything. Who is it really for? What exactly does it solve? Why would anyone pay, and why would they stay? What makes it hard to copy? What does the first version have to prove?

The options were a consultant I'd pay by the hour, a general AI chat that agreed with everything I said, or one of the many thin wrappers around that same chat. None of them had real know-how for this one job. There's a lot of help for building a product. There's almost none for forming one.

  • A consultant

    Expensive, and on their schedule.

  • A general AI chat

    Agrees with you.

  • A wrapper around the same chat

    The same answers, on a different screen.

Where people go for help today.

An idea

A shaped product

Built

Launched

Growing

The gap

A sketch of where help exists, not a measurement.

What “shaped” means.

A shaped product is more than a pitch. It's the problem drawn precisely, the people who have it, how the product creates value for them, what form it takes, how it behaves, how it earns, what story it tells, and what makes it hard to copy.

And, because I'm an engineer, it ends with the part most people skip: a specification of how it could actually be built.

Most people arrive with one of these as a feeling, and another as a guess. Orivon's job is to fill in the rest, and to tell you plainly when a piece doesn't hold.

Leaves with

  1. The problemUsually a feeling
  2. The people
  3. How it creates value
  4. Its formUsually a guess
  5. How it behaves
  6. How it earns
  7. Its story
  8. How it gets built
  9. The test against reality
Nine layers of a product. Most ideas arrive with one or two.

Not one chat. A room of specialists.

The mistake is asking one general model to do all of this in one long conversation. It drifts, it flatters, and it forgets what it agreed to an hour ago.

Orivon is built from dedicated agents, each made for one part of the job, with its own instructions, its own loop, and its own way of checking its work. Some can be models trained for the task. Others are custom agents built on large models. One draws out what you actually mean. One argues with you. One works through the economics. One writes the specification. They hand their work to each other in order, and each builds on what the one before it settled.

The goal isn't to polish your idea. It's to press on it until what's left can carry a company.

What it was handed
Its work
Checked against its own rules
Handed on
Each one has its own loop, and its own check.

Your idea

  1. The listener
  2. The framer
  3. The skeptic
  4. The architect
  5. The economist
  6. The storyteller
  7. The spec writer
  8. The tester
The kinds of specialists involved, simplified.

What you walk away with.

Not a chat history. A dossier, built around one core that everything ties back to, so the brief, the scope, the economics, the story, and the build specification can't quietly disagree with each other.

It's for anyone with an idea that could become a product, digital or physical. You shouldn't have to learn to talk like a product manager first. The structure should come to you.

And when the idea is a piece of software, its shape is exactly what Caddy needs to build it.

BriefScopeEconomicsStoryPitchBuild specification

Scattered notes drift apart.

BriefScopeEconomicsStoryPitchBuild specificationThe core

Everything ties back to one core.

The same six documents, loose and tied.
  1. 1The problem
  2. 2The people
  3. 3How it creates value
  4. 4Its form
  5. 5How it behaves
  6. 6How it earns
  7. 7Its story
  8. 8How it gets built
  9. 9The test against reality

Dossier: your product

An illustration of what the dossier holds.

An idea deserves its shape before it gets its code.

Building has never been easier. Knowing what's worth building, and in what shape, is still the hard part.

Next: Caddy, which builds what Orivon shapes

You are in the studio: Orivon

Next in the studio: Caddy

Give it an idea. It asks until the idea is whole, then builds it in sessions that never have to guess.

Previous: Tedge
Back to the studioBring me yours