Alpha: Ships on npm at 7.0.0-alpha.07.0.0-alpha.0

Products and Services as pages

How a Product becomes a landing, a pricing page and a listing, and how a Service becomes an intake form, a sent page and terms, each one a record.

View as JSON
startupbuilder.dev defines
A Product is what a Customer gets from a Startup, with a promise the Customer can rely on.
Product startupbuilder.dev
startupbuilder.dev defines
An Offer is a Product, under a Brand, at a price, on terms, made by a Startup.
Offer startupbuilder.dev

startupbuilder.dev defines the Product, the Service and their Offers. mdxui draws the pages a customer reads about them. A Business that sells a Product and one that sells a Service need different pages, and each page is one record.

A Product: say it, price it, list it

Vanroster sells crew scheduling as software. Its Product reaches a customer through three pages.

PageTemplateWhat it carriesRecord
Landingapi-productThe promise, the proof, the features and the plans, in the order a buyer readspages/vanroster/home.json
Pricingapi-productPlans as OfferTiles, a plan table and the pricing questionspages/vanroster/pricing.json
Product pagedirectory-productOne feature as a listing: its head, facts, calls and endpointspages/vanroster/product/dispatch.json
From Vanroster › pricingcallboardOpen the frame

The pricing page's plans are Offers: a name, a price, terms and an action. Each is an OfferTile in pricing, and the same plans line up feature by feature in plan-table.

A Service: take the inquiry, set the terms

Ledgerhouse sells bookkeeping, done by two partners. A Service starts with a conversation, so its pages ask before they sell.

PageTemplateWhat it carriesRecord
ServicesarticleWhat the firm does, as a list of engagementspages/ledgerhouse/services.json
IntakecontactAn eight-field form and the steps that follow itpages/ledgerhouse/intake.json
SentarticleWhat happens next, after the formpages/ledgerhouse/intake/sent.json
TermsarticleThe engagement terms, as a documentpages/ledgerhouse/terms.json
From Ledgerhouse › intakevaultlineOpen the frame

The intake is a cta-form of up to eight bounded fields. Contact flow and 404 shows where its post goes.

One record per page, one Theme per Business

Every page above is its own record, and every record of one Business names one Theme. A plan changed on the pricing page is changed there only; the Product record is the Spec that gives every page one source for those facts.

Next steps

On this page