# Everything Bundle vs one $99 kit: when the $149 pack pays for itself

> When buyers should take the $149 Everything Bundle instead of one $99 kit: two-plus kits, landings plus a kit, and the separate-buy math.
> By Dave · 2026-09-18
> Source: https://otf-kit.dev/blog/everything-bundle-vs-single-kit

You already know you need a paid kit. The free SDK covers components. Checkout is open. The real hesitation is narrower: buy one $99 lane, or pay $149 once for the Everything Bundle.

Buy the Everything Bundle when you need two or more product lanes in the next ninety days, or when a kit plus several client landings is already on the roadmap. Buy a single $99 kit when one vertical is the only thing you will ship this quarter and you can name the lane without hedging. That is the whole decision. Everything below is the math and the failure modes that make it stick.

This post is not “free SDK versus any paid kit.” That sibling lives at [Free SDK vs paid kit: when buying actually pays for itself at checkout](/blog/free-sdk-vs-paid-kit-when-to-buy). Here you have already decided paid is on the table. The question is SKU shape on [pricing](https://otf-kit.dev/pricing): one kit versus the $149 pack that includes all listed kits plus all fifteen landing templates.

## The sticker math on pricing

Numbers below match the live [pricing](https://otf-kit.dev/pricing) page (verified 2026-09-18). Do not invent other tiers.

- Free SDK: $0 forever
- Landing template: $9 each
- Individual full-stack kit: $99 each
- Everything Bundle: $149 one-time (listed against a $630 separate-buy total; save $481)

The bundle line item is: all five kits named on pricing, plus all fifteen landing templates. The clear, shippable value for most buyers is three lanes plus landings:

- [Fitness Kit](https://otf-kit.dev/templates/fitness-kit) — web + mobile
- [SaaS Dashboard Kit](https://otf-kit.dev/templates/saas-dashboard) — web
- [Booking Kit (Cadence)](https://otf-kit.dev/templates/booking-kit) — web + mobile

Arcade and Marketplace appear on the pricing bundle list. Treat them as included line items, not as the reason you buy. Price the pack against Fitness, SaaS, Booking, and landings. Do not invent module paths or screen counts — open the product pages and live demos for inventory.

Live proof before checkout: [saas.otf-kit.dev](https://saas.otf-kit.dev) and [fitness-preview.otf-kit.dev](https://fitness-preview.otf-kit.dev). Every paid kit ships AI configs so Cursor, Claude, and similar tools read the same conventions you do.

![Two kits exceed the Everything Bundle price](https://cdn.otf-kit.dev/blog/everything-bundle-vs-single-kit/inbody1-20260918a.png)

*Byte and Nova: two $99 kits already cost more than the $149 pack.*

## Decision matrix: one kit versus the bundle

Use this table as a hard gate, not as mood.

| Situation | Prefer |
| --- | --- |
| You can name one vertical and will not ship a second product this quarter | One $99 kit |
| You need Fitness **and** a marketing site set for the same launch | Bundle (kit + landings already inside $149) |
| You need two kits (for example Fitness + Booking, or SaaS + Booking) | Bundle ($198 for two kits alone already exceeds $149) |
| You need three clear lanes (Fitness + SaaS + Booking) | Bundle ($297 for three kits alone) |
| Agency / studio with rotating client landings plus at least one kit | Bundle (15 landings at $9 = $135 before any kit) |
| You are still on the free SDK and unsure paid is needed at all | Do not buy yet — read the free-vs-paid sibling first |

The matrix collapses to one rule: **one kit when the lane is known and singular; bundle when you need two or more kits, or landings plus a kit, inside the same purchase window.**

## When one $99 kit is the honest buy

A single kit is the right SKU when three things are true at once.

First, the product object is one vertical. You are shipping a fitness product, or an operator dashboard, or a booking product — not “fitness now and a second SaaS for the same company in six weeks.” If the second product is already funded and scheduled, you are not in the one-kit case.

Second, landings are not a parallel workstream. One marketing page you will hand-build, or a page you already own, does not justify the pack. Fifteen landings matter when client work or multi-offer launches will burn $9 pages repeatedly.

Third, your calendar payback still works at $99. Run the four-line day count from the free-vs-paid sibling against that one kit. If screens, schema, auth/billing, and agent docs for that lane already pay back a single kit, stop. Do not buy the bundle to feel covered.

Concrete one-kit paths:

- Fitness-only consumer app → [Fitness Kit](https://otf-kit.dev/templates/fitness-kit)
- Operator SaaS / issues-projects dashboard → [SaaS Dashboard Kit](https://otf-kit.dev/templates/saas-dashboard)
- Availability, confirmations, client booking → [Booking Kit](https://otf-kit.dev/templates/booking-kit)

If you later need a second kit, you can buy it then — unless the second lane was already funded inside ninety days.

## When the $149 pack pays for itself

The pack pays for itself the moment your separate-buy total would cross $149.

**Two kits.** $99 × 2 = $198. That is already $49 above the bundle before you add a single landing. If Fitness and Booking are both on the board — consumer app plus scheduling — the bundle is cheaper than buying the two lanes apart, and you still receive the landing set.

**Three kits.** $99 × 3 = $297. Fitness + SaaS + Booking is a common studio shape: consumer product, operator dashboard, and booking. At $297 à la carte you are nearly double the pack price, and landings are still unpaid.

**Landings plus one kit.** Fifteen landings alone are $135 on pricing. Add any one kit and the separate total is $234. The bundle is $149. If you know you will ship more than a handful of client or offer pages this year, landings alone push you toward the pack even before a second kit appears.

**Full separate list.** Pricing lists the bundle against $630 (five kits + fifteen landings). The $481 savings figure is that gap. Use it as an upper bound; price against the lanes you will actually open.

![Ninety-day plan favors the pack when two lanes are funded](https://cdn.otf-kit.dev/blog/everything-bundle-vs-single-kit/inbody2-20260918a.png)

*If a second lane is funded inside ninety days, price the pack now.*

## Worked examples (no invented inventory)

**Example A — one clear lane.** You are building a fitness product only. Mobile and web matter. You have no second product and no agency landing queue. Open the Fitness preview, confirm the spine matches your job, buy the Fitness kit at $99. The bundle would waste budget on lanes you will not open this quarter.

**Example B — two lanes already funded.** You need a consumer fitness app and a booking surface for trainers. Two kits at $198 already lose to $149. Take the bundle. Inspect [fitness-preview.otf-kit.dev](https://fitness-preview.otf-kit.dev) and the Booking product page before checkout; do not invent screen counts — use what those pages show.

**Example C — SaaS plus client landings.** Your own product is an operator dashboard. On the side you ship marketing sites for clients. One SaaS kit ($99) plus even a modest landing cadence (for example ten pages at $9 = $90) is $189 before a second kit exists. The bundle clears that bar and leaves room if Booking or Fitness appears later.

**Example D — still free-SDK only.** Components are enough; schema and auth are not on the critical path. Do not buy a kit or the bundle to get more UI. Stay on the free SDK and revisit when the product spine is the thing you were about to invent. That is the free-vs-paid post, not this one.

## How to decide in one sitting

Block one hour. Open [pricing](https://otf-kit.dev/pricing). Open the two or three kit pages you might need. Write three lines:

1. Kits I will open in the next ninety days (name them).
2. Landings I will ship in the next ninety days (count).
3. Separate-buy total = ($99 × kit count) + ($9 × landing count).

If line 1 is exactly one kit and line 2 is near zero, buy that kit. If line 3 is already ≥ $149, or line 1 is two or more kits, buy the Everything Bundle. If line 1 is zero, close checkout and stay on the free SDK until the spine question is real.

Do not buy the pack “just in case” when you cannot name a second lane. Do not buy kits one-by-one out of habit if the ninety-day plan already showed two lanes — that is how teams overpay relative to the $149 SKU on the same page.

For ownership math after you ship, see [Price your AI-built app honestly: the ownership math that keeps you shipping](/blog/app-ownership-cost-math). For picking any starter without a rewrite, see [Choose a starter kit once: the six checks that prevent a full rewrite later](/blog/choose-starter-kit-without-rewrite). Those answer different questions. This one only answers: one $99 kit, or the $149 Everything Bundle.

Checkout ends when you count kits and landings on a ninety-day calendar. One kit wins when the lane is singular. The pack wins when two lanes, or landings plus a kit, are already real work.

## Sources

- [OTF pricing](https://otf-kit.dev/pricing) — Free SDK $0, Landing $9, kits $99, Everything Bundle $149 (listed vs $630 / save $481); bundle contents (verified live 2026-09-18).
- [OTF Fitness Kit](https://otf-kit.dev/templates/fitness-kit) — web + mobile fitness lane; live preview at fitness-preview.otf-kit.dev (verified 2026-09-18).
- [OTF SaaS Dashboard Kit](https://otf-kit.dev/templates/saas-dashboard) — web operator dashboard lane; live preview at saas.otf-kit.dev (verified 2026-09-18).
- [OTF Booking Kit](https://otf-kit.dev/templates/booking-kit) — web + mobile booking / Cadence lane (verified 2026-09-18).
- [Stripe Checkout custom success page](https://docs.stripe.com/payments/checkout/custom-success-page) — primary docs for one-time Checkout confirmation patterns (context for kit billing spines; not a price source).