Appearance
12-month strategic direction (August 2026 → August 2027)
Part of Strategy: competitor analysis & market positioning. Evidence-class legend there.
The prioritisation rule
🔎 Business impact ÷ effort, for a team of two: one developer and one digital-content/marketing person. Two consequences that shape every row below:
- The developer is the binding constraint on everything except the channel. So a recommendation that needs weeks of engineering must beat one that needs days by a wide margin, not a small one.
- The marketing person's capacity is the only way this business acquires distribution, and 🔎 it is currently the least-used asset in the plan. 🧮 Nothing anywhere in the portal describes a channel, a reseller programme or an association motion. Half the team has no documented workstream.
⚠ A third constraint, stated because it changes what can be committed: 🔎 bus factor is 1. One person holds the schema, the gates, the release system and the money path. Any plan that has the developer fully committed for twelve consecutive months has no slack for illness, and the launch is 27 days away.
The one-paragraph strategy
🔎 Win the festival season small and measured; convert that into a reseller channel and a public discovery surface during Q4; use both to sell a year-round recurring plan and MLM upline seats through H1 2027. The four things that gate all of it — measurement, transport, catalogue population, and a priced recurring plan — are collectively under three weeks of engineering, and none of them is on the current roadmap's critical path. Everything else waits.
MUST HAVE — by 31 October 2026
Ordered. 🔎 Each blocks revenue or blocks the ability to know whether revenue happened.
| # | Item | Owner | Effort | Why it is must-have |
|---|---|---|---|---|
| M1 | Fix the SMTP credential and merge the SPF include | dev | hours | 📘 Email OTP has returned 535 since ~1 Aug. Sign-in, order confirmation and every transactional message are down. 🔎 The highest-value hour available anywhere |
| M2 | One measurable number per merchant — repoint the beacon, minimal event table, one dashboard line | dev | 1-2 d | 🧮 The beacon posts to an archived function and records nothing (QRS-734). Without it there is no renewal argument, no nudge, and 📘 QRS-489's pre-committed commission rule cannot be applied |
| M3 | Merchant order alert on a working channel | dev | 2-3 d | 📘 "A booking nobody hears about during a four-week season is worse than no booking at all." 🧮 merchant_payment_alert_reads already exists for this |
| M4 | Catalogue population: bulk paste + multi-photo draft creation | dev | 1-2 d | 🧮 6 items and 0 photographs platform-wide. 📘 ~50 hours of entry per vendor. The card is the product and it is empty |
| M5 | Done-for-you setup, sold — ₹5,000-15,000, 12 vendors first | marketing | 0 eng | 🔎 Populates catalogues, produces reference cards, and 📘 generates the willingness-to-pay evidence Q21 could not |
| M6 | Ask V1, V4, V5 and V8 — will they pay · did Razorpay onboarding complete · will a reseller carry it · where do customers find them | marketing | ~1 wk | 🔎 Four unknowns that close before the season for zero engineering. See revenue-model §7 |
| M7 | Launch blockers on the money path — atomic stock decrement, the Razorpay return leg, subscribe the missing webhook events | dev / owner | 2-3 d | 📘 A one-of-a-kind idol can currently be sold N times, and 📘 an unsubscribed Razorpay event is lost forever and never redeliverable |
| M8 | The legal and governance floor — privacy, terms, named grievance officer, takedown runbook, advance-forfeiture disclosure at the point of payment | owner | days | 📘 A release acceptance criterion before the first public signup, and 📘 the non-refundable advance is a contract term under the E-Commerce Rules once published |
| M9 | A priced recurring plan with a collection path | dev | 4-6 d | 🧮 pro.price_minor is NULL. ⚠ Hard-dated: not collecting by 31 Oct and twelve months of compounding are gone (revenue-model condition 1) |
| M10 | Concentrate the launch cohort geographically | marketing | 0 eng | 🔎 Virality L1: one saturated market is a reference, twelve scattered vendors are twelve anecdotes |
🔎 M1 through M4 total roughly one week of engineering and unblock everything downstream. M5, M6, M8 and M10 need no engineering at all. M9 is the only multi-day item, and it is the one with a hard date.
HIGH-VALUE NEXT — November 2026 → March 2027
| # | Item | Owner | Effort | Payoff |
|---|---|---|---|---|
| H1 | The reseller and association channel — 10 active resellers by 30 Nov, 30-40% of first-year revenue, referral attribution via 📘 QRS-532's share token | marketing (+ ~3 d dev) | Sustained | 🔎 The single highest-leverage item in the plan and revenue-model's condition 2. The only route past ~50 merchants |
| H2 | Public SEO directory — area and category pages, server-rendered, indexable | dev | 4-6 d | 📘 The only discovery claim that is true on day one. ⚠ Reverses the current build order — change C2 |
| H3 | Google review funnel + rating on the card | dev | 3-5 d | 🔎 The largest absent capability, addressed by complementing the competitor we cannot beat rather than fighting them |
| H4 | WhatsApp share-and-notify rail — share sheet, pre-composed status images, click-to-chat fallback | dev | 2-4 d | 🌐 78% merchant penetration. ⚠ Reverses the documented "No WhatsApp CTA" constraint — change C1 |
| H5 | Season archive and one-tap re-open | dev | 2-3 d | 📘 Retention costs ₹5-73/vendor/yr and deleting costs more. 🔎 Removes the 50-hour objection permanently at renewal |
| H6 | Direct-seller vertical — sessions, leads, media library, team chat | dev | Weeks (26.0.2) | 📘 Year-round, recurring, and the strongest proactive-value answer of any vertical evaluated. Unlocks H7 |
| H7 | MLM upline seats (member_owned) | dev + owner | Medium | 🔎 Revenue-model's largest realistic line (₹20-45 L). ⚠ Compliance floor first |
| H8 | Two more seasonal verticals scoped — Navratri/Durga, Diwali, weddings | owner | Discovery | 🔎 Ganapati fires once inside the window. Without a second season R1 is capped |
| H9 | Instrument support minutes per merchant | both | Low | ❓ 🔎 The most important unknown in the business — it decides whether sub-₹5,000/yr merchants are viable at all (QRS-748) |
DIFFERENTIATION BETS — pick at most two
🔎 These are the items that could change the platform's competitive position rather than close a gap. Picking all four is how a two-person team ships none of them.
| Bet | Upside | Cost & risk | 🔎 Recommendation |
|---|---|---|---|
| B1 · Proactive assistance, made real — one grounded insight per merchant per week, from stored rows only, never fabricated | 🔎 The differentiator nothing else in this market has. 📘 The Indian SMB tool market is passive record-keeping | Needs M2 + M3 first, then per-vertical derivations. Medium and ongoing. Risk: 📘 noise, which spends the mechanism permanently | ✅ Take it. It is the product's stated first principle and 🧮 it currently has zero substrate. Cheapest possible version: one insight, one screen, one vertical |
| B2 · AI catalogue ingestion — photo → draft name, height, material, style, price | Turns 50 hours into 5, attacks the measured #1 blocker, and 🔎 nothing in the Indian SMB catalogue market does it | 5-8 d, plus per-image inference cost. Risk: wrong drafts erode trust — the merchant must confirm every field | ✅ Take it, after M4's manual bulk import proves the workflow |
| B3 · ONDC seller app | 🌐 3 lakh sellers, 100+ buyer apps. The only answer to "where does demand come from" that does not require building an audience | Weeks. 🌐 Adoption is metro-concentrated while our merchants are not; contradicts "own your customer" | 🟡 One day of written feasibility, then decide (QRS-747). Do not build in this horizon, and do not leave it undecided |
| B4 · Create-and-share consumer artifacts | 📘 Supply-free — the only consumer-acquisition loop that works before inventory exists | 📘 A second product: high-risk third-party PII, its own URL namespace, intermediary-host obligations | 🟡 Reserve the URL namespace and the share-token model now (📘 QRS-531 names both as the only expensive retrofits). Build after the merchant side has revenue |
LATER / FUTURE — beyond August 2027, or behind a customer
| Item | Gate that should release it |
|---|---|
| In-app marketplace depth — facets, vendor feed, recommendations | 🧮 10 of 11 consumer screens are built; finish and stop. Depth waits until 📘 QRS-498's facet decision is taken and there is measurable consumer demand |
| Campaigns engine (📘 ADR-0025) | 🧮 organizations has 0 rows. Sequence behind a paying enterprise customer |
| Car-dealership enterprise + org-admin portal | 🔎 Needs an ADR-0011 amendment, a design pass, and a sales motion two people do not have. After H7 proves seats work |
| Consumer subscriptions and scheduled life (📘 QRS-529) | 📘 A calendar is meaningless before bookings exist, and 🧮 schedules does not exist |
| Khata / Balance | 🔎 Build for retention, price on something else (product-gaps G9) |
| Multi-template picker · palette gallery | A merchant who asks for it |
| First-party reviews (order-gated) | After H3's Google funnel, and after moderation tooling exists |
| Native push | 📘 Needed for the store ship anyway. Decide it deliberately rather than by deferral |
| Intercity bus vertical | 📘 Already correctly rejected: "you do not need to build a booking platform to put your brand on a bus, you need to pay for the bus" |
AVOID / DEPRIORITISE — and the reason, so "no" stays cheap
| Do not do | Reason |
|---|---|
| Targeted / profiled advertising | 📘 Reverses ADR-0010 D7's counts-only decision, brings DPDP profiling duties, needs a consumer base that will not exist. Change C7 |
| Third-party ads on cards | 📘 ADR-0004's brand question has been open since July and compliance_profile does not exist. Answer it "no" for this horizon and stop carrying it as an option |
| Inheriting the archived revenue projections | 📘 ₹4.75 Cr of ad revenue from 950,000 free users, ₹3-3.5 Cr of white-label, ₹1-1.7 Cr of API. 🔎 All assume organisations that do not exist. Disown them explicitly |
| White-label · reseller SaaS · developer/API programme | 🔎 Each implies a partner manager, a developer-relations function, or a sales team |
| Bulk B2B QR services | 🔎 Enterprise account-based selling. Wrong motion entirely for two people |
| Any in-app purchase CTA on native | 📘 ADR-0002 / Apple 3.1.3(d). A store-review risk, not a preference |
| A workflow engine or "fully configurable" platform | 📘 Refused on three independent grounds in industry scope. Keep refusing |
| Restaurants, cafés, dine-in operations | 📘 F2 fails, and dine-in ops is a POS |
| Billing / GST / accounting | 🌐 Vyapar spends ₹102 Cr of salary to hold that market |
| Chasing dealership enterprise before MLM | 🔎 Change C4. The upline can decide this afternoon; the dealer needs six months |
| A second card product abstraction (event cards, vCards) before one exists | 📘 The standing rule already forbids a shared contract across card products that do not exist |
| Spreading the launch cohort across cities | 🔎 Destroys the market-adjacency loop, which is the strongest free channel available |
The calendar
Two decision points to pre-commit now
🔎 A plan without pre-committed revision rules is a plan that gets quietly abandoned — 📘 which this repo measures at ~0 completion for deferred reconciliation.
| When | Rule |
|---|---|
| 25 September 2026 (season close) | Read the measured numbers: paying vendors, online GMV share, support minutes per merchant, catalogue completion. If online share is under ~10%, commission stops being a revenue line (📘 QRS-489's own rule). Replace every 🔎 on revenue-model with a 🧮 within two weeks |
| 30 November 2026 | If fewer than 10 resellers are actively selling, restate the target to the exit run-rate form (revenue-model §6) and set the base case at ₹45-50 lakh. Do not carry an unreachable number into 2027 |
The one thing to take from this page
🔎 The engineering is ahead of the commercial motion, and the plan keeps adding engineering.
🧮 A live money loop, a verified four-layer platform model, 27 of 36 screens built, 56 tables, 24 gates — against 5 cards, 6 catalogue items, 0 photographs, 1 paying customer, nothing measured, and no message able to reach anyone.
The next three weeks should contain almost no new features. They should contain: a fixed email credential, one number per merchant, an order alert, a way to get 1,500 photographs in, twelve populated cards in one market, and five conversations with people who might sell this for us.