Variants are the new way to bundle service options
We retired Build Recipes. The same job — keeping consistent install doctrine across similar work without copy-pasting your service three times — is now handled directly on each service through Variants.
How it works
On any service detail page, hit Create variant. A small modal opens that pulls from your pricing multipliers (tile size, tile material, pattern — the ones you tuned in the pricing interview):
- Pick the modifier(s) that describe this variant — Pattern: Herringbone, Tile size: Large format, etc. Each dropdown shows the multiplier next to the label, like Herringbone (1.35×).
- Quick-pick chips cover common qualifiers — Small / Medium / Large / Curbless / With niche / Premium. Click a chip or type your own.
- The Preview block shows the variant's name and the calculated base price (parent price × compound multiplier) before you commit.
- Hit Create variant. Materials and tasks deep-copy from the parent with fresh IDs so future edits stay independent.
Each variant carries a small badge row at the top of its detail page and on the Services list — pattern badges are terracotta, size badges are brass, material badges are sage. Scan-friendly so you know at a glance which row is the herringbone variant, which is the natural-stone variant, etc.
Why we made the change
Build Recipes added a layer of indirection most contractors never needed. Variants live on the service that needs them, multipliers come from your existing pricing interview answers, and the badge UI keeps the catalog readable as it grows. One fewer concept, same outcome.
If you'd already set up Build Recipes, nothing about your services breaks — they just stop showing the Recipes page. Use Variants going forward.
Where to start
- Building your service catalog — full walkthrough of Variants, the Create Variant modal, and modifier badges
- Service materials and favorite-for-roles — the favorite-for-role layer that covers the other thing Recipes used to do