Provider
A provider is the entity that serves resources to users: the company, the founders, the employees building and operating the product. They supply the tools, features, content, and services the user works with to get what they came for, and they earn revenue from supplying them.
Definition
The provider is the entity supplying affordances in the user-provider transition, capturing margin on the route-efficacy improvement users get by integrating those affordances into their pursuits.
What the provider supplies
The provider is the affordance-supplying side of the user-provider transition. The user supplies the pursuit — energy, intent, the sought state — and the provider supplies action-possibilities that make the user's route more efficacious than it would be without them. Pursuits live on the user side and can't be generated from the provider side; affordances live on the provider side and aren't action-possibilities until the user integrates them into a pursuit they're already on.
Also referred to as "the team" or "the company" in operational discussion. The provider's complete affordance output is its offering — the app, the workflow, materials, support, integrations the provider builds. The offering sits inside a broader affordance landscape that also includes third-party integrations, the user's own tools and knowledge, and substitutes the user falls back on when the offering doesn't serve. Most of the landscape is outside the provider's control.
How the provider captures value
Providers earn margin-on-efficacy — margin priced against the delta between the user's baseline route efficacy without the offering and their route efficacy when integrating the offering's affordances. Margin attaches to the efficacy delta. If the user could already reach the sought state without the offering, no delta exists for the provider to capture margin on.
In self-serve SaaS, the capture form is typically subscription, which structurally requires continuous route-efficacy delivery. The provider keeps capturing margin only as long as it keeps producing efficacy improvement over the life of the subscription.
The provider is plural
A provider isn't a single decision-maker. Different teams within the same provider focus on different commercial outcomes — activation team on conversion, retention team on renewal, finance team on CAC payback. Each commercial outcome is a milestone in the provider's pursuit of sustainable margin; the teams partition the long arc of the user-provider relationship into windows they can intervene on.
The provider also operates with structural advantages the user doesn't have: full attention to the design problem, full context across users, time to absorb complexity. The user is one person, attention-divided, working with partial information. This asymmetry of attention places responsibility for path-clarity on the provider — the side with full attention and full information across users is the side with the capacity to carry it.
Example
For a SaaS invoicing tool, the provider is the company that builds the product. The product team supplies affordances (templates, the invoice editor, the send flow, payment-collection integrations) that improve the route efficacy of a freelancer trying to get paid. Without the offering, the freelancer drafts an invoice in a Word doc, attaches it to email, and waits for a check; with the offering, they send an invoice in three minutes and get paid by ACH the next week. The provider captures margin on that efficacy delta through monthly subscription pricing. Internally, different teams within the same provider work different commercial outcomes — the activation team on first paid conversion, the retention team on renewal, the finance team on CAC payback — each acting through a different commercial-outcome lens within the same user-provider relationship.