Skip to content

Product Templates

Ten Product Templates, each defined by kind, supply, worker, Interfaces, buyer, earning model, and assurance.

A Product Template is a reusable definition of one kind of Product: what it sells, who supplies the work, who buys, and how it earns. Ten templates cover every Product a Startup sells.

Seven dimensions

DimensionValuesWhat it decides
Kinddata, software, agent, serviceWhich Builder builds it
Supplydigital, humanWhether demand is the only constraint
Workeragents, humans, agents-and-humansWho does each unit of work
Interfacesapi, sdk, cli, mcp, webhooksHow Customers and their Agents reach it
Who buyshuman, agent, human-or-agentWhich Motions fit
Earning modelsubscription, usage, commerce, marketplace, directoryHow money arrives
AssuranceOne sentenceWhat the Customer relies on

SoftwareBuilder builds every data, software, and agent Product. ServiceBuilder builds service Products and joins any template with human supply. SalesBuilder sells them all.

Each Product Template page opens with its business. It names the earning model and typical Prices, the Demand Budget first revenue needs, the one Metric per state, and its seed and compounding Plays.

Supply sets the work

Digital supply has no ceiling. Software and Agents serve the thousandth Customer the way they served the first, so a digital-supply Startup needs only demand.

Supply from people is finite: they are recruited, credentialed, scheduled, and paid. A human-supply template adds the Supplier onboarding, Credentialing, Dispatch, and Earnings Systems. It also adds an App where Suppliers take work.

Built from

Product Templates compose. Each one names the templates it is built from and inherits their Systems, Processes, and Roles.

How Product Templates composeHeadless SaaS is built from Dataset API; SaaS is built from Headless SaaS; Directory is built from Dataset API; Marketplace is built from Directory; Licensed-human marketplace is built from Marketplace; Agent as a Service is built from Headless SaaS; Services-as-Software is built from Agent as a Service; E2E managed service is built from Services-as-Software; Dropship store is built from Headless SaaS.Dataset API → Headless SaaSHeadless SaaS → SaaSDataset API → DirectoryDirectory → MarketplaceMarketplace → Licensed-human marketplaceHeadless SaaS → Agent as a ServiceAgent as a Service → Services-as-SoftwareServices-as-Software → E2E managed serviceHeadless SaaS → Dropship storeDataset APIHeadless SaaSSaaSDirectoryMarketplaceLicensed-human marketplaceAgent as a ServiceServices-as-SoftwareE2E managed serviceDropship store
Each arrow runs from a template to one built from it, which inherits its Systems, Processes and Roles.
Read as text

A Startup sells as many Products as it likes, each from its own template. A tax-research Startup sells its rulings as a Dataset API. Over the same records, it sells a filing review as Services-as-Software.

Goods ship from upstream

A Startup holds no stock. Physical goods sell only through the Dropship store: the Startup lists and sells them. An upstream holds the stock and ships each Order, and tracking passes through to the Customer.

The catalog

Product TemplateKindSupplyBuyerEarning model
Dataset APIdatadigitalhuman-or-agentusage
Headless SaaSsoftwaredigitalhuman-or-agentusage
SaaSsoftwaredigitalhumansubscription
Directorydatadigitalhuman-or-agentdirectory
Marketplacesoftwarehumanhuman-or-agentmarketplace
Licensed-human marketplaceservicehumanhuman-or-agentmarketplace
Agent as a Serviceagentdigitalhuman-or-agentusage
Services-as-Softwareservicedigitalhuman-or-agentusage
E2E managed serviceservicehumanhumansubscription
Dropship storesoftwaredigitalhuman-or-agentcommerce