A single source of truth for every offer, price and description, written once in your voice and synced to your storefront.
Category
Business Operations
Return
~1 hr / week
Stack
Notion · Storefront sync
The Problem
Offers scatter as they grow. The price on the website disagrees with the booking page, the description in the proposal is two versions old, and updating one service means hunting it down in four places. Buyers notice inconsistency, and inconsistency reads as carelessness at exactly the wrong moment.
The Solution
One catalog database that owns every offer. Name, price, description, intake questions and metadata live in a single row per service, written once in your voice, and the storefront, the proposals and the marketing all read from the same source.
How It Works
- Every service becomes a structured row: pricing, description, audience, intake questions and search metadata.
- Descriptions get written to a house standard, in your voice, with a rewriting workflow for any row that reads generic.
- The catalog syncs to your commerce platform, so the storefront and the source of truth agree by construction.
- Proposals and marketing pull descriptions from the catalog instead of reinventing them per document.
- A price or description changes in one row, and it changes correctly on every surface.
Built With
- A services database in Notion with a full field set per offer
- A description-rewriting workflow enforcing the house voice
- Sync to the commerce platform for storefront truth
It supplies the Proposal Builder with its building blocks and gives the Client Journey its named stages of purchase.
What You Get
- Every offer defined once, correct everywhere
- Descriptions in your voice at a consistent standard across the catalog
- Price changes that take one edit instead of a scavenger hunt
The Numbers
One to two days to structure the catalog and connect the storefront. It returns about an hour a week of synchronizing and rewriting, and the buyer-facing consistency does quiet work on trust the whole time.