Overcoming Rima's Objections¶
Rima already stocks and successfully sells generic "Science Kits" in the $50–$100 range. Any pitch for custom STEM kits has to answer, directly, why this is additive rather than a redundant, riskier version of something already working. Below are the objections she's likely to raise, in the order she's likely to raise them.
1. "I already sell science kits in this price range. Why do I need different ones?"¶
Her current kits are general-purpose science kits (chemistry sets, crystal-growing, volcano models) — consumable, single-use experiments. Custom STEM kits are reusable electronics platforms paired with an intelligent textbook: a kid builds, reprograms, and rebuilds the same hardware dozens of times. They sit next to her existing kits as a distinct category, not a competing SKU — the pitch should open with a side-by-side comparison on the shelf, not a replacement.
2. "Will this cannibalize sales of the science kits I already have working?"¶
Different buyer intent: a science-kit buyer wants a one-time weekend experiment; a STEM-kit buyer wants an ongoing hobby, a club supply, or a gift that keeps giving. Cross-merchandising (place them near, not in place of, each other) turns this into a bigger combined basket rather than a split one. Track both categories' sales for the first 90 days to confirm.
3. "What's my margin, really — after I account for support time?"¶
Unlike a shrink-wrapped science kit, an electronics kit can generate customer questions and troubleshooting. This is a real, ongoing labor cost. Answer it by pricing support into the plan up front: pair the kit with the intelligent textbook (which answers most "why isn't this working" questions without a staff member), and start with a small SKU count so the support burden is boundable before scaling.
Margin is the same formula she already uses for her $50–$100 science kits:
For example, a starter kit priced at $75 with a $45 landed cost — parts, packaging, and an amortized share of curriculum development — clears \( \frac{75 - 45}{75} \times 100 = 40\% \), before support time. Model support time as a per-unit labor cost added to the $45, the same way she'd account for any labor-intensive product, and re-run the same formula before setting the shelf price.
4. "What if a kit doesn't work, or a part is defective?"¶
Electronics have a different failure mode than a chemistry set — a bad sensor, a bad cable, a bricked microcontroller. Needs a clear return/exchange policy stated before launch, and a vendor relationship that will replace defective units without a fight. This should be settled with suppliers before the first kit hits the shelf, not after the first return.
5. "My customers are used to a $50–$100 price point. Will these kits fit that, or will I need a new price tier?"¶
A well-scoped starter kit (one sensor, one microcontroller, the companion lesson) can land in the same $50–$100 range she already prices to, minimizing sticker shock. Higher-end kits or bundles can be a later, optional upsell once the entry tier is proven — don't open with the expensive SKU.
6. "Will I need to hire or train staff who understand electronics?"¶
This is the real long-term cost, not the inventory. Mitigate it in the pilot: pick kits simple enough that the intelligent textbook — not the staff member — carries the explanation, and lean on the vendor/curriculum team for a short staff walkthrough before the kits go on the shelf. Staff expertise can grow over time; it doesn't need to exist on day one.
7. "What if the technology is out of date in two years?"¶
Reasonable, since electronics move faster than a crystal-growing kit ever will. Answer: choose kits built on standard buses (I2C, I2S) and widely supported parts rather than a single vendor's proprietary platform, so kits can be refreshed by swapping a component, not by re-buying an entire new product line.
8. "Do I have the shelf space and display fixtures for this?"¶
Science kits are boxes on a shelf; STEM kits benefit from a working demo (lights, motion, sound) to sell themselves. That needs a small footprint — one end-cap or a counter display, not a full aisle — for the pilot. This should be scoped as "how much space for one end-cap," not "how do I reorganize the store."
9. "Is there really customer demand for this, or is this a solution looking for a problem?"¶
The existing science-kit sales are proof people already come to her for hands-on learning products — the STEM kits are a bet that some of those same customers (and the teachers/homeschoolers she doesn't yet reach) want a more advanced, reusable version. The honest answer is: start small, watch actual sell-through against the existing science-kit baseline, and let data decide before any larger commitment.
10. "What if the kids find electronics harder than a science-kit experiment and get frustrated instead of engaged?"¶
A poorly scoped kit can absolutely produce this outcome. The intelligent textbook exists specifically to prevent it — a simulation before the physical build, and small, achievable steps rather than one big project. The pilot should test this directly: watch a few real kids/teachers use the kit in-store before it goes to the general shelf.
The Underlying Ask¶
None of these objections argue against trying custom STEM kits — they argue for starting small, next to what already works, and proving it with real sales data before expanding. That's the same "start with one end-cap" pilot recommended in Why Custom STEM Kits — this page is the answer key for the questions Rima will ask before agreeing to that pilot.