Bring the mess.

Chapter 01The why

A product builder’s partner, not another IDE.

You own the product: who it’s for, what ships, what waits. Saul is the desk that stays with you for the whole loop, shaping the project, gathering what you need to decide, working with your AI agents, and shipping versions without losing the thread.

And you don’t juggle several desks. All your projects sit in one Saul. Switch in a click, see who’s working, who needs you, what’s quiet. No second app, no second window of Saul for each product.

Chapter 02The map

Between the IDE and the generators.

One side optimizes the file tree. The other optimizes the first prompt. Saul sits in the messy middle, where real products live after the first demo, through priorities, research, agents, and ship.

Chapter 03The full circle

Saul does the product loop with you.

From a half-finished idea to shipped versions: research, prioritization, agents, code, release. You steer. Saul holds the workspace so the story never falls apart between tools.

1. 01

   Start from intent

   Say what you’re building and for whom. Saul helps shape the idea and prepares the technical base in the background. No empty folder ritual, no stack form.

2. 02

   Research when it matters

   Desk research, user insight, and evidence gaps, only when a real decision needs them. Optional depth, never a mandatory ceremony.

3. 03

   Prioritize together

   Tickets and prioritization frameworks with you and your agents. Trade-offs stay visible. You pick the lens. You keep the call.

4. 04

   Plug in your agents

   Claude Code, Codex, Grok Build, and more later. Same product story, one continuity, whichever model does the work.

5. 05

   Build. You correct.

   Agents implement. You steer taste, direction, and product judgment without living in the file tree unless you want to.

6. 06

   Ship versions

   Release the product and the versions that follow from one calm place. When it’s real, one deliberate ship. Not a silent deploy.

Then the loop continues: learn what shipped, choose the next good move, and ship again. Same desk, same product truth.

Chapter 04Everyday

You rarely have one project at a time.

One product is mid-build with an agent still running. Another is quiet but not finished. A third needs a decision only you can make. That is normal for a product builder, and it is why Saul keeps every project on one desk.

You do not open a second Saul, or jump to another tool just to remember what else is open. You stay here, switch when you need to, correct what matters, and leave the rest visible until you come back.

Chapter 05The desk

One desk. All your projects.

Swipe the Work card for context, files, or ship. Talk with your agent in the middle. On the right, every product you work on, always in view. Depth is optional: open the code when you want, stay with the product when you don’t.