---
title: "Praxis by delivery situation"
route: "/solutions/by-stage"
description: "Choose a Praxis path from the product work that is breaking down: clarity before build, traceable change, or connected team delivery."
template: hub
intent: "Route a delivery owner to the situation they recognize."
parent: "/solutions"
primaryCta: { label: "See the connected method", href: "/platform" }
schemaType: CollectionPage
hero:
  eyebrow: "By situation"
  headline: "Start from where the product work is breaking down."
  sub: "These are recurring working conditions, not company-age tiers. Pick the moment that repeats in your delivery week."
  primaryCta: { label: "See the connected method", href: "/platform" }
sections:
  - { id: starting, kind: cards, heading: "When you are starting a product" }
  - { id: after-launch, kind: cards, heading: "When the product has recently launched" }
  - { id: team-delivery, kind: cards, heading: "When a team is delivering" }
  - { id: method-link, kind: cta, heading: "One connected method" }
---

## When you are starting a product

The founder needs a requirement that can be accepted before a fast agent turns a moving idea into code. [Start with product clarity](/solutions/by-stage/starting-a-product)

## When the product has recently launched

The team needs each change to show the decisions and contracts it changes before implementation begins. [Keep change traceable](/solutions/by-stage/after-launch)

## When a team is delivering

The delivery leader needs one work package to move between roles instead of reconnecting agents after every handoff. [Connect the delivery flow](/solutions/by-stage/team-delivery)

## One connected method

Each situation can begin with one role harness. Compatible artifacts and explicit approvals let the next role continue; a reviewer may return a package for revision. The roles do not have to run automatically or all be installed for one person.