# Motions

URL: /business/motions · Id: `page:business/motions`

> A Motion names who buys an Offer and who acts with it, and it reshapes the template and the demand Plays that fit.

A [Motion](/business/nouns/motion) names who buys an [Offer](/business/nouns/offer) and who acts with it, written as a chain such as b2b or b2a2c. It is a property of the Offer, and it reshapes the template around it.

## Reading the chain
The first `b` is the [Startup](/business/nouns/startup), and each later letter is a party the Offer passes through. The letters are:

- `b`: a business.
- `c`: a person buying for themselves.
- `d`: a developer.
- `h`: a person who hands the Offer on.
- `a`: an [Agent](/business/nouns/agent).

So b2a2c reads: a Startup sells to an Agent, which buys for a person. In b2h2a, a person buys and their Agent uses what they bought.

## What a Motion changes
- Who the [Customer](/business/nouns/customer) is: the business, the person, the developer, or the principal an Agent acts for.
- Who [Actions](/business/nouns/action) are by and for: in b2a2b, Actions are by the buying Agent and for its business.
- When a [Mandate](/business/nouns/mandate) or an [Approval](/business/nouns/approval) applies: an Agent pays within its Mandate, and a purchase over its [Limit](/business/nouns/limit) waits for its principal.
- Which [Interfaces](/business/nouns/interface) lead: b2d leads with the API, SDK, and CLI, b2a with the MCP server, and b2c with the [Site](/business/nouns/site) and [App](/business/nouns/app).

One [Product](/business/nouns/product) can sell through several Motions. A meeting-notes Product sells b2c through its App, and b2h2a through its MCP server to the assistants people already use.

## Motion selects demand Plays
Each Motion fits the demand [Plays](/business/nouns/play) that reach its buyer where that buyer looks:

- b2c: [Paid social](/workflows/plays/paid-social) on Instagram, TikTok, and Facebook.
- b2b: [LinkedIn outbound](/workflows/plays/linkedin-outbound), [Cold email](/workflows/plays/cold-email), and [Paid search](/workflows/plays/paid-search) on Google Search.
- b2d: [Developer relations](/workflows/plays/developer-relations) and [Open source](/workflows/plays/open-source), with packages on npm and code on GitHub.
- b2a: [Answer engine optimization](/workflows/plays/aeo), [Agent registries](/workflows/plays/agent-registries) such as the MCP Registry, and [Agent-to-agent selling](/workflows/plays/agent-to-agent).

Every Motion page lists the full set, generated from each Play's fit.

## The catalog
| Motion | Buyer | Leads with |
| --- | --- | --- |
| [b2b](/business/motions/b2b) | A business, through the person who signs for it. | `api`, `sdk`, `webhooks` |
| [b2c](/business/motions/b2c) | A person, paying for themselves. | None. |
| [b2d](/business/motions/b2d) | A developer, often on a card before their company signs. | `api`, `sdk`, `cli` |
| [b2a](/business/motions/b2a) | An Agent, acting under its own Mandate. | `mcp`, `api` |
| [b2h2a](/business/motions/b2h2a) | A person, buying for the Agent that works for them. | `mcp` |
| [b2a2b](/business/motions/b2a2b) | A business, through an Agent holding its Mandate. | `mcp`, `api` |
| [b2a2c](/business/motions/b2a2c) | A person, through an Agent holding their Mandate. | `mcp`, `api` |
| [b2a2d](/business/motions/b2a2d) | A developer, through the coding Agent that builds for them. | `mcp`, `api`, `sdk` |