Judgment is the product, not the configuration.
Solaz takes a position, on purpose. This is the model that gets a team working without building anything from scratch.
The core idea
The Archetype you pick has already settled how the Project is structured, so you are not left configuring one forever. You choose a shape instead of building a blank board.
Pick an Archetype
Backlog1
Payment stories
Design1
Card flow
Build1
Payment form
Review1
Error testing
Done1
Order summary
Lead1
Intro call with Acme
Qualified1
Qualify the retail lead
Proposal1
Proposal for Norte Foods
Negotiation1
Renewal pricing
Won1
Pilot signed
Requested1
Request the pallet quote
With vendor1
Pallet delivery
At risk1
Late customs paperwork
Delivered1
Warehouse count check
Accepted1
Quarterly report
From conversation to tracked work
Decisions stop evaporating into chat. Talk becomes Decisions and Tasks with an owner and a trail.
- 01
Capture
Meeting Decisions
Not just minutes: log the explicit Decision, its rationale, and who was there when it was agreed.
- 02
Assign
Tasks with a shape
Every Decision creates Tasks with an owner, a deadline, and a link back to where it came from.
- 03
Execute
Living Docs
Tasks land in living Docs that carry the whole chain, from Meeting to deliverable.
One graph across every area
Projects, Docs, Meetings, and Decisions share a single data layer. A software sprint and a sales team run on the same Task backbone; only the Archetype changes.
Software sprint
Same Task backbone
Sales team
For the tools your team already uses
The Agents you already use connect to the Org Graph over MCP and can read and write to it from day one.
Start with a shape, not a blank board.
Solaz builds the rest, and reshapes it when your team changes.