Templates belong to a product and auto-fill that product’s name, pricing, and affiliate terms. Write once, personalize automatically, and never mix products again.
Free forever for 1 product · 14-day full access · No credit card
IMAGE #5: Product-scoped template composer
Template editor with {{product_name}}, {{price}}, {{affiliate_rate}} variables shown auto-filling from the selected product's record.
Short answer
Product-native templates belong to one product and auto-fill its details. Open the template picker inside a product's pipeline and you only see that product's templates, with name, pricing, affiliate commission, and media-kit URL populated from its record — so the wrong pitch can't go to the wrong partner.
In every other tool the template library is a single flat list. A $29 UI kit pitch sits right next to a $299/year SaaS pitch — and under deadline pressure, the wrong one ships.
Your Figma UI Kit pitch, your Notion Template pitch, and your SaaS pitch all live in the same library, separated by nothing but a hopeful naming convention.
Send the $299/year framing to a partner interested in your $29 kit and you’ve undercut the conversation before it started — and on a small team, that mistake is one dropdown away.
Product name, price, affiliate commission, media-kit URL — pasted in by hand on every send, which means a typo or a stale number eventually slips through.
Open the template picker inside your WP Caching Plugin pipeline and you only see that product’s templates. The wrong pitch isn’t buried — it isn’t even in the list.
Product name, price, affiliate commission, media-kit URL, and your custom fields fill in on send. Your $29 Figma UI Kit pitch reads nothing like your $299/year SaaS pitch — and never gets mixed up.
Build “Blogger – WP Caching Plugin” or “YouTuber – Figma UI Kit” once and reuse it forever. Your best-performing template is reusable, not rediscovered each time.
Write once, personalize automatically, never mix products. The wrong-pitch-to-the-wrong-partner problem becomes structurally impossible — not a discipline you have to maintain.
Open a product’s pipeline and its scoped templates are right there in the picker.
Explore →A dedicated inbound alias per product keeps replies — and their templates — in one place.
Explore →Per-product sequences send your scoped templates on schedule, automatically.
Explore →How product-native templates keep every pitch on-SKU.
Each template belongs to a specific product. When you open the picker inside that product’s pipeline, you only see its templates — so your Figma UI Kit templates and your WP Caching Plugin templates never share a list.
Product name, price, affiliate commission, media-kit URL, and any custom fields you define all auto-populate on send. You write the template once and the per-product details fill themselves in.
Yes. Build entries like “Blogger – WP Caching Plugin” or “YouTuber – Figma UI Kit” once and reuse them forever, so the right framing for the right audience is always one click away.
Yes — by design. Because a product’s picker only shows that product’s templates, the wrong-pitch-to-the-wrong-partner mistake isn’t something you have to remember to avoid; it’s structurally out of reach.
Start free with one product, one seat, 50 contacts a month — no time limit, no credit card. Bring your whole portfolio in whenever you’re ready.