Resume Prompt
Continue Sergey's plan per docs/tomorrow-2026-04-29.md (Wednesday 2026-04-29). Six tasks: (1) competitor research on 4 new (Matterport / Spaceform / VRX Studio / Kuula) + Stripe vs Paddle comparison filtered by 4 currency support (USD+EUR+AED+AUD — local providers PayTabs/Telr effectively eliminated by yesterday's decision); (2) build docs/landing-v1.html using brandbook v1.1 with placeholder pricing, 3 tiers, Gold CTAs, multi-column footer; (3) expand brandbook with 3 priority sections — Property UI Patterns (hotspots / floor selector / 360 toggle / walkthrough), Imagery Guidelines, Forms; (4) read launch-plan-v3.2 fully and analyse — especially Phase 1.6 needs new sub-phase 1.6.7 for Australian compliance (GST + APP) after yesterday's geography decision; (5) send Ilya v3.2 highlighting priority swap 1.3↔1.9 + Phase 1.9 reframe (5-8 → 3-4 weeks) + 30 [BL] markers + 5 new sub-phases + 2 suggestion callouts; (6) close 7 remaining strategic open questions — hard-delete scope, AuditLog retention, refund policy, tariffication unit (NEEDED for landing — projects/renders/seats?), block vs read-only post-trial, permissions granular vs roles, required SSO providers. Plan corrections from CONV-11 are fully applied — plans/launch-plan-v3-corrections.md can be marked ratified. 5 strategic decisions accepted yesterday: pricing placeholder, currencies USD+EUR+AED+AUD, trial без карты, geography EU+UAE+AU+global, payment provider deferred.
Summary
Applied the full plan corrections batch (8 groups) to docs/launch-plan-v3-full.html and docs/launch-plan-v3-visual.html. Major changes: Phase 1.9 reframed from "build-from-scratch" to "extension of existing Super Admin Panel" (3-4 weeks vs 5-8), priority swap 1.3 ↔ 1.9 (MCP demoted Critical→High, Operator Dashboard promoted High→Critical), 5 new sub-phases (1.8.7 / 3.3.4 / 3.3.5 / 3.5.5 / 4.5.5) plus 4.5.6 backlog watch, [BL]/[OPL] markers across ~30 sub-phases (using Ilya's backlog cross-reference), and 2 suggestion callouts in Phase 1.2.1 (Organisation entity gap + DB security). Also created refined operator-panel-v1.html (multi-page mockup with project settings + Settings/Payment Provider) replacing single-page preview, did full Russian-language pass on Phase 1.9, added Buttons section implementation-idea callout to brandbook (last gap closed), and conducted holistic brandbook review against volume.vision identifying 3 priority gaps (Property UI Patterns / Imagery Guidelines / Forms). User accepted 5 strategic decisions: pricing placeholder, currencies USD+EUR+AED+AUD, trial без карты, geography EU+UAE+AU+global, payment provider deferred to tomorrow.
Changes
docs/launch-plan-v3-full.html— Markers legend updated (+[BL]/[OPL]); Phase 1.9 reframe + scope corrections (1.9.1 deps now → Phase 1.2.1, 1.9.2/1.9.6/1.9.7 simplified, 1.9.8 deferred to Стадия 2); priority swap 1.3↔1.9 with new callouts; 6 new sub-phases (1.8.7 + 3.3.4 + 3.3.5 + 3.5.5 + 4.5.5 + 4.5.6); 2 suggestion callouts in 1.2.1; ~30 [BL]/[OPL] markers across phases and sub-phases; Phase 1.9 added to priority order table; phase counts updated 22→25; v3.2 changelog entry added; full Russian-language pass on Phase 1.9; CSS fix for<strong>on navy phase background; "Этап" → "Итерация" terminology fixdocs/launch-plan-v3-visual.html—#staff-mockupsection rewritten to embedoperator-panel-v1.htmlinstead ofstaff-panel-preview.html; new "What's new in v1" block; comparison table extended to "Итерация 1 vs Итерация 2 / Стадия 2 / Стадия 4" (5→7 rows); footer link + dates updated 2026-04-24 → 2026-04-28docs/operator-panel-v1.html— created earlier in session (NEW FILE, multi-page mockup); Projects tab in drawer extended with full project settings (feature flag toggles for 13 flags, Information section, Assets section); Settings page with Payment Provider placeholderdocs/brandbook/v1.html— Buttons section gets implementation-idea callout (last token-section gap closed; brandbook now has 11 callouts, fully covered)plans/launch-plan-v3-corrections.md— NEW. Full 8-group correction plan, status: draft (now ready to ratify since all groups applied)docs/tomorrow-2026-04-29.md— NEW. Tomorrow's plan: 7 tasks (competitor research × 4 + Stripe vs Paddle compare, landing page mockup, brandbook expansion 3 sections, plan analysis, Ilya follow-up, open questions, carry-over). Includes 5 strategic decisions accepted today + their implications
Decisions
Phase 1.9 reframed as extension, not from scratch. Tech team (Ilya) confirmed via screenshots that Super Admin Panel exists and works in production with project list, feature flag toggles, asset uploads, action log. Phase 1.9 = subscription/payment/audit log/multi-tenant client list on top of what exists. Estimate cut from 5-8 weeks → 3-4 weeks. Rejected: "build new staff panel from zero" approach.
Priority swap 1.3 ↔ 1.9. Old (CONV-9): MCP was Critical because "Без MCP не запускаться" — Sergey. New (CONV-11): MCP demoted to High because launch is possible without it (studios can use admin UI). Operator Dashboard promoted to Critical because there's no tool to manage studios from day-1 of pilot. Recorded as v3.2 changelog entry. v3.1 entry kept as historical record.
"Итерация" terminology added. Plan hierarchy now explicit: Стадия (4) → Фаза (25) → Итерация (sub-iterations within a phase, e.g. Phase 1.9 has Iteration 1 and Iteration 2). Rejected: "Этап" (introduced briefly, then replaced because user said it doesn't exist as a tier).
4 currencies (USD + EUR + AED + AUD) accepted. Sergey's strategic decision. Implications: PayTabs/Telr (MENA-focused) effectively eliminated; Stripe vs Paddle become the realistic choice for tomorrow's comparison. Operator panel Settings → Payment Provider cards already mention this in plan.
Geography year 1: EU + UAE + Australia + global. Implication: Phase 1.6 (Legal & Compliance) scope expands significantly. Need new sub-phase 1.6.7 for Australian compliance (GST + Privacy Act / APP). Multi-jurisdiction strategy (single entity vs subsidiaries) becomes a strategic question for tomorrow.
Trial без карты. Sergey chose frictionless onboarding over higher paid conversion. Implication: Phase 1.5.5 needs anti-abuse measures (rate limits, email validation, device fingerprint), and stronger email nurture sequence to compensate for lower trial-to-paid conversion (~30-40% vs 60-70% with card).
Brandbook holistic review identified 3 critical gaps. After comparing with volume.vision (existing main product), gaps confirmed: (1) Property-specific UI Patterns (our unique moat — hotspots, floor selectors, walkthrough controls), (2) Imagery & Photography Guidelines (sales-app = render gallery), (3) Forms (admin = 80% forms). Rejected: copying VV's pure black-and-white minimalism — we deliberately chose warmer Navy+Gold for differentiation between the two products.
Suggestion callouts deferential, not directives. Two callouts in Phase 1.2.1 (Organisation entity gap + DB security checklist) framed as "no action needed from product side, ignore if already covered." Same pattern as brandbook v1.1's 11 implementation-idea callouts. User explicitly said: "we are not tech team and we should respect their work and knowledge."
Next Steps
- Continue competitor research — 4 new competitors (Matterport, Spaceform, VRX Studio, Kuula) per
docs/tomorrow-2026-04-29.md. Roma's Dropbox list closed (6 watched). - Compare Stripe vs Paddle on 4-currency support (USD/EUR/AED/AUD) — local providers (PayTabs/Telr) likely eliminated. This is THE filter for tomorrow.
- Build landing page mockup
docs/landing-v1.htmlusing brandbook v1.1 — placeholder pricing, hero with full-bleed render, 3 pricing tiers, comparison table, Gold CTAs, multi-column footer. - Expand brandbook with 3 priority sections in
docs/brandbook/v1.html: Property UI Patterns (hotspot pin / floor selector / 360 toggle / walkthrough controls / overlay), Imagery Guidelines (aspect ratios / compression / lighting / device mockups), Forms (inputs / selects / checkboxes / validation). - Send Ilya updated
docs/launch-plan-v3-full.html(v3.2) — highlight: priority swap 1.3↔1.9, Phase 1.9 reframe (3-4 weeks), [BL] cross-reference (~30 markers), 5 new sub-phases. - Read launch-plan-v3.2 in full and analyse: cross-reference consistency, dependency cycles, missing items, Stage 4 contents, Phase 1.6 scope expansion (now needs 1.6.7 Australian compliance after geography decision).
- Close 7 remaining strategic open questions: hard-delete scope, AuditLog retention, refund policy, tariffication unit (projects/renders/seats — needed for landing!), block vs read-only post-trial, permissions granular vs roles, required SSO providers.
Open Questions
- Stripe vs Paddle final choice (waiting on tomorrow's comparison)
- Hard-delete scope: Phase 1 or Phase 2?
- AuditLog retention: 12 months active + archive forever, or different?
- Refund policy: 14 days / pro-rata / never / case-by-case?
- Tariffication unit: by projects / renders / seats? (needed for landing page tomorrow)
- Block vs read-only post-trial?
- Permissions: granular per-action vs Admin/Editor/Viewer roles?
- Required SSO providers at launch (Google / Microsoft / Apple)?
- 2FA mandatory at launch or Iteration 2 of Phase 1.9?
- IP allowlist mandatory or optional?
- Single payment entity vs subsidiaries (multi-jurisdiction strategy)?
- Phase 1.6.7 — needs to be added as new sub-phase for Australian compliance (GST + APP)
- Phase 1.5.5 anti-abuse measures specifics (rate limits, email validation, device fingerprint)
- MCP top-10 endpoints for Iteration 1?
- Should
plans/launch-plan-v3-corrections.mdbe markedratifiednow that all 8 groups are applied?
Context for next session
- Sergey has Dropbox folder for competitor research — closed (6 watched: Caramel Creative, BuildMedia, BINYAN, Display Sweet, iCreate, Sensoreal). Tomorrow's list is from Claude (Matterport, Spaceform, VRX Studio, Kuula) — not Roma's.
- Plan has v3.2 in changelog with full detail of today's revisions. v3.1 entry kept as historical record (Sergey's "Без MCP не запускаться" quote stays in v3.1 — superseded but not rewritten).
- Brandbook is now 100% complete on token-section coverage (11/11 implementation-idea callouts). Next iteration is expansion, not finalisation: add Property UI Patterns / Imagery / Forms sections per
docs/tomorrow-2026-04-29.md. operator-panel-v1.htmlis the canonical operator dashboard mockup (replacesstaff-panel-preview.html). Visual appendix points to v1; old preview file remains in repo but isn't referenced.- Phase 1.9 sub-phases all use Russian "Итерация" terminology now (not "Этап", not "Phase 1 of 1.9"). Hierarchy: Стадия → Фаза → Итерация.
- Plan v3.2 was NOT yet sent to Ilya. v3.1 was sent end of CONV-10 and Phase 1.9 was added after. v3.2 has further changes (priority swap, reframe, [BL] markers, 5 new sub-phases). Tomorrow Sergey needs to send updated version.
- 5 strategic decisions made today (pricing placeholder, 4 currencies, trial без карты, 3+ regions, payment provider deferred) have implications already noted in
docs/tomorrow-2026-04-29.md— most importantly Phase 1.6 scope expansion (need 1.6.7 for Australia). - CSS bug fix:
<strong>was navy on navy phase background — now.phase .phase-desc strong { color:#fff; }rule added. Also added.phase .phase-desc codeand.phase .phase-desc astyles for visibility. plans/launch-plan-v3-corrections.mdis instatus: draft. Should be ratified since all 8 groups executed today — leaving as draft pending user decision.docs/tomorrow-2026-04-28.md(yesterday's tomorrow file) remains in repo as historical record. New filedocs/tomorrow-2026-04-29.mdis canonical for next session.