Use cases Early-stage product design
Turn a product concept into a model before the design locks in
For designers and engineers shaping a physical product while the concept is still moving: a kitchen appliance, a wearable, a handheld instrument. Cairn turns what you know, and what you're only assuming, into a model of parts, requirements and interfaces you can check as the concept changes.


The problem
Early on, most of what anyone believes about a product is assumption: who holds it, where it's used, how long the battery has to last. Those assumptions harden into requirements without anyone deciding they should.
The concept also changes every few weeks. A new enclosure or a different battery ripples into heat, mass, cost and the interfaces between parts, and the reasons for the last choice are gone by the time the next one is made.
A workflow in Cairn
Separate what you know from what you assume
In the interview, every answer becomes a fact marked You said or Assumed. Not sure whether a handheld meter has to survive a drop onto concrete? Say so, and Cairn records an assumption, which stays out of the model unless you keep it.
The interview →Choose the first architecture part by part
The Architect proposes the first parts and the interfaces between them, say a sensor head, a main board and a battery. Tick the parts that match the concept and leave the rest waiting in Change Review.
System decomposition →Write requirements from the model
Ask for requirements on a part and they are written from what the model says about it: its parts, its interfaces and the requirements above it. Each arrives with a rationale and acceptance criteria, checked for wording.
Requirements →Keep the concepts you dropped
When the concept moves from a replaceable battery to a sealed one, keep the replaceable battery as an alternative set aside, with why it lost. If that reason stops holding, the record shows which decision to revisit.
Design decisions →Find the gaps as it changes
Completeness shows what each part is still missing: a description, an interface, a requirement, a way to verify it. Each gap leads to the lens that closes it.
Completeness checks →Go back to last month's concept
History keeps every change with what it touched and why. Undo one, or restore the whole model to the point before a concept you've dropped; the restore is itself a change, so nothing is lost.
Change Review and History →
What Cairn doesn't do yet
- Cairn doesn't hold geometry or connect to CAD. It models what the product is made of and must do, not its shape.
- There is no shared workspace yet: a project lives in one person's browser and can back up to their account. Others get a copy by export and import.
- Cairn doesn't read or write SysML or ReqIF.
- Cairn is pre-launch and in early access.
Questions
- When is a concept ready for Cairn?
- When it has parts that have to work together. A few sentences about what it does and who uses it are enough to start the interview.
- Does Cairn replace CAD?
- No. Cairn holds the system model: parts, requirements, interfaces, behavior, verification and the decisions behind them. Shape and geometry stay in CAD.
- Can the AI change the model directly?
- No. Every AI proposal opens in Change Review, and nothing applies until you apply it. Any change can be undone from History.
See it on your own system.
Describe what you are building and Cairn interviews you, then builds the first model with you.