Hermes Bot
34 lines
4.1 KiB
Markdown
34 lines
4.1 KiB
Markdown
## THE FATWA (HUKM)
|
||
|
||
**HUKM:** We will adopt value-based pricing as the default model for all new product tiers, with cost-plus as a baseline floor, and dynamic pricing only for high-demand seasonal features — and will not use freemium as a primary acquisition strategy.
|
||
|
||
**DALEEL:** User interviews across four segments revealed perceived injustice in uniform pricing (e.g., small teams paying the same as enterprises, though receiving less value). Willingness-to-pay data showed a 40% spread between segments. Shura with finance confirmed cost-plus alone leaves 30% revenue on the table, while freemium attracted 70% non-converting users — a waste of Hifz al-Mal. Classical qiyas on *'adl* in exchange (Qur'an 4:29, "mutual consent in trade") and *bay' murabahah* principles supports pricing that reflects actual benefit to buyer, not just seller's cost.
|
||
|
||
**MAQSAD:** Hifz al-Mal (Preservation of Wealth) — for both the company (sustainable revenue to continue serving) and the customer (fair price for value received, avoiding *ghabn* (deception) and *riba* (unjust increase)). Also Hifz al-'Aql (rational economic decision-making) by transparently communicating the value metric so users can make informed choices.
|
||
|
||
**SHURUT:**
|
||
- Must publish a clear, measurable value metric (e.g., number of active projects, users, or outcomes delivered) and an anchor price for each tier.
|
||
- Must offer a low-cost entry tier (no free tier) to preserve access for those with limited means (Sad al-Dhara'i against exploitation of the poor).
|
||
- Must A/B test any price change on a <10% user segment for at least two weeks before full rollout.
|
||
- Must define a "price fairness ratio": max 5x between lowest and highest tier to avoid *gha'ish* (excessive gouging) and preserve *maslaha* of community.
|
||
|
||
**MUNKATHIRAT:**
|
||
- If customer complaints about pricing exceed 15% in any tier within 30 days of release, rollback to previous pricing and redo discovery.
|
||
- If conversion rate from trial (paid trial, not free) drops below 5%, invalidate the tier structure and return to cost-plus until new value data is gathered.
|
||
- If any recognized Islamic finance body issues a fatwa against the pricing model (e.g., charging for value not yet delivered = *gharar*), suspend immediately and consult.
|
||
|
||
---
|
||
|
||
## THE PROTOCOL
|
||
|
||
**STEP 1: Value Discovery (This Sprint)** — Conduct 10 "value-level" interviews with existing customers using the JTBD framework. Ask: "What job did you hire our product for? How much does that job cost you if not done? What would you pay to eliminate that pain?" Map answers onto a 3-level scale: Low (basic need, <$10/month), Medium (core job, $10–$25/month), High (mission-critical, $25–$60/month). Do this in 5 working days.
|
||
|
||
**STEP 2: Build & A/B Test Pricing Matrix (Next Sprint)** — Using the value-level data, construct three tiers: Basic ($10), Pro ($25), Enterprise ($60). Ensure lowest tier covers cost-plus floor. Set up a 2-week A/B test on 5% of new signups (control: old cost-plus pricing; variant: value-based tiers). Measure conversion rate, ARPU, and churn. Use a simple landing page with clear value metric (e.g., "Pay per active project").
|
||
|
||
**STEP 3: Rollout & Monitor (Week 3–4)** — If A/B test meets success criteria (conversion > control by 10%, fairness ratio ≤5x, complaints <15%), roll out to 100%. Add a 30-day money-back guarantee to preserve trust (*trust = Hifz al-'Aql*). Monitor daily for Munkathirat triggers. If any trigger fires, execute rollback within 24 hours and return to cost-plus with a note in your retrospective.
|
||
|
||
---
|
||
|
||
## MUHASABA (RETROSPECTIVE)
|
||
|
||
When we set the price, whose *'adl* did we truly prioritize — the company's need for sustainable revenue, or the customer's need for affordability and fairness? Did we actually understand the value we deliver, or did we just guess based on competitor benchmarks? What would it mean to price with the same rigorous discovery we apply to feature decisions? Here's the piercing question: **Would you, the product team, pay this price for your own product? If not, why are you asking your customers to?** Let that sit. Then ask: *What one change would make the pricing feel just to both sides?* |