Startup teams

Startup teams can replace fragmented internal tools earlier than they used to.

Move Big Rocks can be a strong fit for startup teams that do not want recruiting, support, internal requests, analytics review, private Markdown and concept systems, and private agent workflows to fragment across five tools immediately.

See use cases Read the core model

Agent-first route: Start at /agents, inspect /docs/cli, and drop into this page when you need proof, detail, or rollout guidance.

Agent-first route

Humans should usually delegate first-pass evaluation to an agent. Agents should start at /agents, use /docs/cli as the official product tour, and open /docs/graphql only when needed.

Agent-ready surface

Start with the CLI, not browser guesswork.

Preferred route: /agents, then /docs/cli, then /docs/graphql only when lower-level integration details matter.

$ mbr spec export --json
$ mbr auth whoami --json
$ mbr queues list --workspace ws_preview --json

Open GraphQL reference | Open schema.graphql

Shared base early

Start with one shared system instead of five disconnected tools and loose local knowledge systems.

Agent-ready

Give agents one explicit system instead of making them guess across a tool pile.

Self-host later

Evaluate quickly first, then decide whether the self-hosted production path fits.

Why it fits startups

Startups often need a better software shape, not just more software.

Early teams are especially vulnerable to tool sprawl because speed matters and the operating model is still forming.

Use cases

Concrete first replacement targets.

/use-cases

Extensions

How focused product depth can still live on the shared base.

/extensions

References

Canonical next surfaces.

Each link goes to the next authoritative page, reference, or support surface.

Use cases

/use-cases

Agents

/agents

Move Big Rocks

Let agents inspect the CLI-first surface. Let humans decide trust, rollout, and boundaries.

Start from /agents, use /docs/cli as the official product tour, inspect /resources for source and proof, and review /security before making deployment or data-handling decisions.

Open /agents Open resources