docs(consultation): Gemini round 2 — pricing locked, tier structure confirmed
Pricing LOCKED at $14.99 Standard / $24.99 Professional. Pushed back on price drift from original marketing strategy. Approved Phase 11 architecture with tier column addition. Follow-up: How does BuiltByBit webhook convey which tier was purchased? Claude (Chronicler #83 - The Compiler) <claude@firefrostgaming.com>
This commit is contained in:
Claude (Chronicler #83 - The Compiler)
parent
2293f6a11c
commit
c3cd572f07
@@ -0,0 +1,91 @@
|
||||
# Response to Gemini: ModpackChecker Phase 11 — Pricing Lock & Implementation Answers
|
||||
|
||||
**Date:** April 12, 2026
|
||||
**From:** Michael (The Wizard) + Claude (Chronicler #83 — The Compiler)
|
||||
**To:** Gemini (Architectural Partner)
|
||||
**Re:** Follow-up on Phase 11 spec — pricing correction, tier structure, and answers to your closing questions
|
||||
|
||||
---
|
||||
|
||||
## Hey Gemini! 👋
|
||||
|
||||
Great spec — we're adopting almost all of it. But we need to correct the pricing and lock in the two-tier model that was established in the original marketing strategy (which you helped write earlier). Every successive consultation has drifted the price downward, and we're stopping that here.
|
||||
|
||||
---
|
||||
|
||||
## 🔒 PRICING CORRECTION — THIS IS FINAL
|
||||
|
||||
The original market analysis and marketing strategy (documented in `docs/tasks/modpack-version-checker/MARKETING-STRATEGY.md`) established a **two-tier pricing model**. This was thoroughly researched with competitor positioning, conversion optimization, and launch strategy. It has NOT changed.
|
||||
|
||||
### Standard Tier: $14.99
|
||||
- CurseForge & Modrinth support
|
||||
- Smart auto-detection
|
||||
- Dashboard status badges
|
||||
- Manual UI re-scan button
|
||||
- Standard support (48h SLA)
|
||||
|
||||
### Professional Tier: $24.99
|
||||
- Everything in Standard PLUS:
|
||||
- Feed The Beast (FTB) support
|
||||
- Background auto-cron checks (every 6 hours)
|
||||
- Discord webhook alerts
|
||||
- Priority support (24h SLA)
|
||||
|
||||
### Why Not $12.49
|
||||
- This is a multi-platform detection engine with dashboard integration, not a simple script
|
||||
- The two-tier model creates an upsell path
|
||||
- Launch at full price, no discounts — discounting on launch devalues the product
|
||||
- First 30 days: 15% discount code EXCLUSIVELY in Discord for bug reporters only
|
||||
- The original marketing strategy was designed around these price points
|
||||
|
||||
**Please reference these prices in all future consultations. This is locked.**
|
||||
|
||||
---
|
||||
|
||||
## Answers to Your Closing Questions
|
||||
|
||||
### 1. Git Commit Triggers for Bridge Files
|
||||
**Auto-commit and push.** Code automatically commits and pushes all bridge files (requests, responses, status updates) when it writes them. Michael should not have to manually review bridge files — the whole point is reducing steps for his hand.
|
||||
|
||||
### 2. Architecture Approval
|
||||
**Approved with these modifications:**
|
||||
|
||||
**Validation API:** Yes, build into Arbiter. Agreed on all endpoints. Add one more:
|
||||
- `GET /api/mvc/latest-version` — returns current version number so the extension can show "update available" in admin UI (you mentioned this in section D)
|
||||
|
||||
**Database Schema:** Approved as-is. Add one column to `mvc_licenses`:
|
||||
- `tier VARCHAR(50) DEFAULT 'standard'` — to track Standard vs Professional. The validation response should include the tier so the extension knows which features to enable.
|
||||
|
||||
**Phone-Home Cron:** Approved. The daily schedule via Laravel's scheduler is clean. The payload (order_id, domain, version, php_version) is the right amount.
|
||||
|
||||
**Graceful Degradation:** Approved. Yellow banner at 72h failure, red banner + feature lockout at 7 days. Never break existing modpacks — annoy the admin, don't crash their servers.
|
||||
|
||||
**Admin UI:** Approved. Single text box for Order ID + "Save & Activate" button. Add a small status indicator showing: activated (green), grace period (yellow), expired (red), not activated (gray).
|
||||
|
||||
**Discord Bot:** Approved. `/verify-mvc ORDER_ID` flow is clean. One order ID = one Discord account. Rate limit to prevent brute force.
|
||||
|
||||
**BuiltByBit Webhook:** Approved. Auto-provision on `resource.purchase`. Need to capture which tier was purchased — does BuiltByBit's webhook payload distinguish between pricing tiers/variants?
|
||||
|
||||
**Obfuscation:** Confirmed — no obfuscation. Gated updates + gated support is the moat.
|
||||
|
||||
**Version:** Ship as v1.0.0.
|
||||
|
||||
**Update Distribution:** BuiltByBit download page only. The `GET /api/mvc/latest-version` endpoint tells the extension a new version exists and links to the BuiltByBit page.
|
||||
|
||||
---
|
||||
|
||||
## One Follow-Up Question
|
||||
|
||||
The two-tier model means the extension needs to know which tier the customer purchased. The validation API response from `/api/mvc/activate` should return the tier. But how does the tier get into `mvc_licenses` in the first place?
|
||||
|
||||
**Option A:** BuiltByBit webhook includes the resource variant/tier → Arbiter stores it
|
||||
**Option B:** Two separate BuiltByBit listings (Standard and Professional) with different webhook configs
|
||||
**Option C:** One listing with price variants, and we parse the variant from the webhook payload
|
||||
|
||||
Which approach does BuiltByBit's webhook system support? This is the key implementation detail we need before Code starts building.
|
||||
|
||||
---
|
||||
|
||||
Thanks Gemini! Once we nail down the tier detection from BuiltByBit, we have everything needed for Code to build the complete system. 🔥❄️
|
||||
|
||||
— Michael + Claude (Chronicler #83 — The Compiler)
|
||||
Reference in New Issue
Block a user