Skip to content

MamNajem Pre-Release Strategy And Scope Audit

Date: 2026-05-30

Updated: 2026-06-12 to refresh admin-support, pricing, and privacy/retention status against the current local workspace.

This document is a read-only audit of the local MamNajem workspace. It was produced from the actual repositories, local documentation, architecture notes, tests, configuration, and all files in docs/deep-research.

Repositories inspected:

  • backend
  • mobile-frontend
  • web-admin
  • architecture
  • docs

No files were modified during the original audit. This document was created afterward at the user's request.

1. Project Scope Summary

Area Implemented Partial / Missing / Unclear Evidence
Backend capabilities Broad Spring WebFlux API: auth/user init, legal acceptance, properties, leases, tenants, invitations, assets, handovers, payment schedules, rent requests, receipts, Stripe, subscriptions, chat, notifications, audit logs, data export/delete, problem reports. Missing Poland-specific legal workflow engine: lease type gates, ordinary/occasional/institutional rules, notices, delivery proof, QES/notary paths, tenant screening, pre-lease funnel. backend/openapi.json, backend controllers, backend services
Mobile app Full Expo app for auth, onboarding, landlord/tenant roles, properties, leases, tenants, invitations, payments, Stripe Connect, subscriptions, handover, documents, messaging, notifications, support, data export/delete. Landing/app positioning is broad and still mentions landlords, property managers, and tenants equally. Legal/pilot activation flows are not narrowed to the research-backed ICP. mobile routes, mobile flow docs, LandingPage.tsx (mobile-frontend/components/landing/LandingPage.tsx)
Web/admin Separate React admin console with Cognito admin sign-in, access allowlist, operational browsing, problem report triage, and Stripe webhook/processed-webhook recovery surfaces. Launch readiness still needs integration-environment verification, support runbook signoff, and a short admin smoke checklist. web-admin App.tsx, web-admin api.ts, backend/openapi.json
Payments/subscriptions Strong Stripe subscription, Stripe Connect rent checkout, durable webhook inbox, disputes/refunds, native Apple/Google store verification. Overbuilt for first Polish MVP. Research says off-ledger rent tracking first, web billing first, no rent take-rate. Current plan prices do not match final research direction. RentPaymentService.java, StripeConnectServiceImpl.java, SubscriptionService.java, 2026-05-05-basic-subscription-tier.sql (backend/src/main/resources/db/changelog/2026-05-05-basic-subscription-tier.sql)
Notifications/messaging In-app notifications, Expo push, push tokens, REST chat, read state, action requests, attachments. Email is a stored channel/preference but no real transactional email sender was found. No SMS path. Chat is REST, not realtime, which is acceptable for MVP. NotificationService.java, ExpoPushSender.java (backend/src/main/java/pl/mamnajem/service/ExpoPushSender.java), ChatsController.java
Documents/assets/handover S3-backed uploads, asset attachment/reorder/delete, lease/property documents, handover protocols/items, tenant confirm/decline. No immutable legal artifact engine: rendered PDF hash, signature method, delivery proof, versioned service address, QES/notary status. StorageController.java, AssetService.java, HandoverProtocolService.java
Tenant/landlord flows Tenant invite, tenant lease access, tenant payment visibility, tenant handover/settlement confirmation, messaging. Landlord property/lease/payment/admin flows are substantial. Research says owner-first activation should be primary. Current product can require too much tenant adoption before landlord value is obvious. InvitationsController.java, LeaseTenantsController.java, mobile routes
Maintenance / issue reporting Generic in-app problem reporting exists for authenticated owners and tenants with topic, description, optional screenshot, plaintext backend submission, and admin triage statuses. EP9-T1 limits launch copy to simple in-app issue reports; EP9-T2 accepts plaintext support-report handling; EP9-T3 verifies owner and tenant submission; EP9-T4 verifies admin triage. ProblemReportService.java, useSubmitReportProblem.ts, AdminProblemReportController.java, support-problem-report.real.spec.ts, simple issue reporting promise, plaintext problem report contract, problem report submission smoke, admin problem report triage smoke
Admin/support tooling Backend and web-admin now expose allowlist management, problem report triage, processed-webhook browsing, and Stripe webhook browsing/replay paths. Runbooks exist. Problem-report admin triage is accepted through EP9-T4; remaining support parity work is outside the simple problem-report gate. AdminProblemReportController.java, StripeWebhookOpsController.java, admin webhook runbook, web-admin App.tsx, admin problem report triage smoke
Architecture/infra Mature AWS/Terraform/CI docs: integration Lightsail, production ECS/RDS/ALB, Cognito, S3, Amplify, Stripe, Google/Firebase, alerting/runbooks. Production RDS recovery policy, RDS alarm lookup, admin Cognito hardening, integration domain consistency, and release worktree hygiene are now approved for the paid pilot. architecture README, aws-production main.tf, runtime.tf, production database recovery policy, RDS alarm verification, Admin Cognito hardening, Integration domain consistency, Release worktree checklist
Docs/code gaps Docs correctly identify launch blockers: legal core, maintenance, email/SMS, retention, off-ledger payments, and admin support verification. IBAN handling, retention policy, and production readiness are now explicitly decided for the paid pilot. Remaining gaps are legacy/plaintext row migration before paid production, Polish counsel review, and the non-infra launch gates still marked open or partial in the charter. privacy-policy-v1.md, BankAccountService.java, BankAccountEntity.java, DATA_RETENTION.md, retention policy alignment, pre-release charter

2. Deep Research Coverage Map

Topic Question answered Main conclusion Confidence More before release?
Market opportunity Is Poland viable? Viable as focused profitable SaaS, not broad venture-scale proptech by default. Medium Field validation yes. More desk research no.
ICP Who buys first? Self-managing Polish landlords with 2-10 units, sharpest at 2-5 units in major cities. High Validate with real pilots.
Competitors Where is the gap? Gap is Poland-first mobile lease operations, evidence, handover, rent visibility, not generic property management. Medium-High No major pre-release desk research.
Positioning What should the product be known for? "Run every rented flat from your phone": lease ops, compliance clarity, handovers, rent visibility, settlement. High Landing smoke test needed.
Product gaps What blocks paid MVP? Legal workflow, email/SMS, retention/evidence lifecycle, off-ledger rent posture, admin parity, pricing, and GTM validation. High Confirm in pilot.
Pricing/subscriptions What should be charged? Landlord-paid portfolio SaaS; no rent take-rate; web billing first. Final direction is 30-day trial plus read-only Archive, then 19.99 / 49.99 / 99.99 PLN gross monthly. Medium Price test required.
Financial viability Can unit economics work? Yes if CAC stays founder/community/search-led and paid mix skews to multi-unit landlords. Medium CAC/WTP/retention validation required.
GTM How to launch? City-first, founder-led, communities/educators/search/SEO, founding landlord program. Medium-High Channel tests required.
Validation What proof is needed? Evidence over enthusiasm: real artifacts, real lease migration, paid intent. High Must execute before public launch.
Legal/compliance What needs lawyer review? Lease types, deposits, notices, signatures, delivery, GDPR, screening, payments. High as checklist Mandatory.
E-signature How to sign legally? Four lanes: in-app evidence, external e-sign, QES/wet ink, hybrid notary for occasional lease. Medium-High Counsel/provider validation required.
Payments/rent collection Should rent be embedded? Keep Stripe, but do not make Connect checkout default MVP; use IBAN, proof, reminders, mark-paid. Medium-High Legal/payment review if Connect remains exposed.
Maintenance workflow Is maintenance needed? Simple in-app reports are the launch scope. Lease-linked repair workflow is post-launch backlog unless pilot evidence expands the promise; no vendor suite. Medium Pilot decides priority.
Pre-lease funnel Is lead funnel core? Internal tracking/manual posting can wait; do not build listing syndication first. High Can validate later unless pilots demand it.
Founder memo What is the decision? Narrow, not no-go and not broad platform. High Execute validation/legal gates.
Launch plan What must happen before launch? Owner-only activation, landing tests, legal artifact spine, off-ledger payments, web billing, pilot cohorts. Medium-High Use as release gate.
Legal checklist What must counsel review? Ordinary/occasional/institutional lease assumptions, deposits, notices, delivery, e-sign, GDPR, screening, payments. High Mandatory.
Irrelevant file Healthcare system comparison. Not relevant to MamNajem release. High Exclude from launch strategy.

Research sources:

3. Final Product Direction

MamNajem should become a Poland-first mobile lease operations system for self-managing landlords, not a broad landlord/tenant/property-manager platform.

First ICP: private self-managing landlords with 2-5 active long-term units in Warsaw, Krakow, Wroclaw, Trojmiasto, and Poznan. Secondary ICP is 6-10 unit self-managers. Property managers, agencies, PRS, short-term rentals, tenant-first tools, and full accounting workflows should wait.

Lead pain: "I need one reliable workflow for leases, rent follow-up, documents, handovers, deposit settlement, reminders, and evidence, without spreadsheets, WhatsApp chaos, and legal uncertainty."

Avoid positioning it as:

Avoid Reason
Full property management suite Current product lacks team/delegation/vendor/manager-grade workflows.
Legal automation or law firm replacement Polish lease/signature/notice rules are too form-sensitive.
Rent fintech/payment processor Research says Polish rent MVP should be off-ledger first.
Tenant app Tenant is a workflow participant, not the buyer.
Listing marketplace Pre-lease syndication is not the validated wedge.

First paid MVP promise: "For a self-managing Polish landlord with 2-10 flats, MamNajem keeps every active lease organized: property and lease setup, tenant invite, document vault, rent schedule, payment proof, handover protocol, messages, reminders, and final settlement evidence."

Does implementation match? Partly. The operational core is unusually broad and close: property, lease, tenant, rent schedule, handover, documents, messaging, notifications, subscriptions all exist. Simple in-app issue reporting also exists, so lease-linked maintenance should stay post-launch unless pilot evidence expands beyond support-style issue submission. The product is still not release-aligned because legal workflows, email/SMS, retention/privacy consistency, admin support verification, pricing, and GTM validation are not ready.

Contradiction resolution:

Contradiction Resolution
Perma-free 1-unit tier vs bootstrap revenue urgency Drop perma-free as an acquisition mechanism. Use a 30-day no-card trial as the public acquisition surface. After trial: paid or read-only Archive (data access only, no new entities). Founding Landlord Program (first ~50 cohort, conditional) is the only "free." Reasoning: 1-unit landlords rarely upgrade by buying a 2nd flat, LTV is below CAC at low prices, and support cost > funnel value. The research's "free 1 unit forever" pitch is imported B2C freemium folk wisdom, not a Polish-landlord-behavior finding.
Pilot pricing Public test starts with 19.99 / 49.99 / 99.99 PLN gross. Current DB plans 9.99 / 89.99 / 249.99 PLN must be replaced.
Tier caps unspecified Hard caps on active entities (archived excluded): Solo 3 properties / 10 tenants; Portfolio 10 / 35; Plus 25 / 100. Soft-warn at 80%, hard-block new cap+1 creates immediately, and apply 14-day grace only when migration or downgrade leaves an owner already over cap. Never restrict already-created entities.
26+ unit inbound No self-serve above 25. "Contact us" wall. Optional Plus+ design-partner at 199 PLN/month for 26–50 single-operator portfolios (max 2 customers in year 1, no SLA, explicit design-partner agreement). Refer 51+ to Bidrento / casavi and capture on agency waiting list. Never custom-build for a single >25-unit customer.
Maintenance blocker vs optional Post-launch and validation-gated. The paid-pilot promise is simple in-app reports only. Reopen lease-linked maintenance only if pilot/interview evidence says it is the wedge. No vendor suite.
Pre-lease as MVP vs later Do not build portal syndication. At most add manual lead tracking after pilot evidence.
Stripe Connect built vs off-ledger strategy Keep Stripe for billing and optional future checkout, but default MVP rent flow is IBAN/proof/reminders/mark-paid. Take-rate is currently hardcoded setApplicationFeeAmount(0L) at StripeConnectServiceImpl.java:219 — keep it zero.
Mobile app-store billing built vs web-first research Disable or hide native store purchase as default launch channel. Use Stripe web billing first. Verify EXPO_PUBLIC_NATIVE_STORE_BILLING_ENABLED in store builds — misconfig sends digital subscriptions to web checkout, an App Store 3.1.1 rejection risk.
Payment-reminder templates exist vs no scheduler emits them Only @Scheduled methods in the backend are metrics snapshots and Stripe webhook retry/reconcile. PAYMENT_DUE / PAYMENT_OVERDUE / LEASE_ENDING templates exist but no cron fires them. Reminder scheduler is a P0 release blocker (Epic 6).

4. Full Pre-Release Scope

Must Have Before Release

Item Status / evidence Why / business impact Risk if skipped Priority / deps
Narrow ICP and hide broad positioning Partial. Landing says landlords, managers, tenants: common.json, LandingPage.tsx (mobile-frontend/components/landing/LandingPage.tsx). Converts the right buyer and prevents low-fit signup/support load. Broad launch attracts 1-unit hobbyists, tenants, and managers the app cannot fully serve. P0. Depends on landing/onboarding copy.
Owner-only activation funnel Partial. Core flows exist; research event taxonomy not fully matched. First value must happen before tenant adoption. Activation stalls if tenant invite is required too early. P0. Depends on analytics events.
Legal workflow gate for lease type/execution Missing. No API paths for legal artifact engine; research requires it: polish-residential-lease-product-spec.md. Core trust driver in Poland. Legal overstatement, invalid assumptions, failed paid conversion. P0. Depends on lawyer review.
Handover and final settlement hardening Partial. Handover exists; final settlement exists; legal artifact/evidence layer missing. One of the strongest evidence workflows. Product feels like data entry, not legally useful proof. P0. Depends on artifact/PDF/versioning decisions.
Deposit ledger and refund deadline Partial. Deposit can exist as charge/payment request; no full ledger/refund calculation/deadline engine. Deposit settlement is a high-conflict workflow. Landlords still use spreadsheets for the painful part. P0. Depends on legal deposit rules.
Off-ledger rent tracking default Partial. Payment requests/receipts exist; Stripe Connect checkout also prominent. Fits Polish rent behavior and avoids PSP complexity. Users reject fees/checkout; support burden from disputes/KYC. P0. Depends on UX copy and payment settings.
Fix privacy/retention promises Pilot-aligned. EP8-T1/EP8-T2 record the IBAN/export decision and transfer-instruction implementation; EP8-T3 records matching retention periods, no automated cleanup before pilot, deletion blocks, and evidence exceptions. Legacy/plaintext row cleanup remains before paid production. Legal trust and GDPR credibility. Compliance and trust risk before paid launch. P0. Policy/code alignment closed for pilot; legal review still required.
Transactional email basics Missing. In-app/push exist; no email sender found. Invites, reminders, billing, and legal docs need reliable delivery beyond push. Tenants miss invites/reminders; support burden rises. P0. Depends on SES/app email path.
Simple issue reporting / maintenance workflow Promise-aligned. EP9-T1 and EP9-T5 confirm the paid-pilot promise is simple in-app issue reporting, not lease-linked repair management. Research says maintenance may be an adoption expectation gap. Pilot users may reject product as incomplete if interviews prove maintenance is the wedge. Post-launch backlog. Build lease-linked maintenance only if pilot evidence expands the promise.
Admin/support parity Partial. Backend and web-admin expose allowlist, problem report, processed-webhook, and Stripe webhook recovery surfaces. Integration smoke verification, runbook alignment, and support acceptance are still required. Paid launch needs support recovery tools that work outside a developer shell. Manual DB/API ops during first failures. P0. Depends on admin smoke verification.
Pricing model: trial + caps + plans + paywall + Archive Partial/overbuilt. Current DB plans 9.99 / 89.99 / 249.99 PLN; perma-free 1-unit assumed; native IAP overbuilt; no trial/Archive states. Aligns revenue with the narrow ICP, filters tire-kickers, prevents free-brand drag, handles >25-unit inbound without scope creep. Wrong price signal, app-store complexity, confused plans, perma-free dabblers eat support, whales rewrite the roadmap. P0. Depends on pricing decision and §6.
Production ops hardening Pilot-aligned. RDS recovery policy, RDS alarm lookup, admin Cognito hardening, .pl integration domain consistency, and release worktree hygiene are approved for paid pilot. Paid production needs recoverability and clean config. Data loss, auth confusion, deploy risk. P0. EP8 infra gate closed; keep production rollout manual.
Landing, pricing, pilot CTA Partial/missing. Landing exists; pricing/founder program/SEO assets mostly missing. Needed to validate demand and sell pilots. Launching blind. P0. Depends on ICP copy.
Field validation cohort Missing execution. Research gives plan. Demand proof before broad launch. Building past evidence. P0. Depends on pilot offer and onboarding SOP.

Should Have Before Release

Item Status / evidence Why / business impact Risk if skipped Priority / deps
Founder migration/onboarding SOP Missing in product; launch plan requires it. Reduces switching friction for 2-10 unit landlords. Lower activation. P1.
Help center/support macros Partial support pages exist. Lowers founder support load. Repeated manual answers. P1.
SEO pages for Polish terms Missing. Captures high-intent search. Slower acquisition. P1.
Case study/demo assets Partial demo mode exists; no launch case studies. Builds trust. Lower conversion. P1.
RDS-specific alarms and backup policy uplift Pilot-aligned. Backup/recovery policy is approved in EP8-T4; RDS alarm lookup and actual alarm names are accepted in EP8-T5. Improves operational safety. Thresholds may need tuning after production baseline data. P1.
Evidence export pack Partial via data export/assets. Strengthens legal/evidence promise. Users still assemble court/settlement files manually. P1.

Could Wait Until After Release

Item Status Reason
Embedded BLIK/P24/PayU/Tpay rent collection Missing / Stripe Connect exists Only after rent collection proves retention value.
Autenti/KIR full integration Missing Track execution method and upload proof first; integrate when legal flow is reviewed.
Pre-lease funnel/listing pipeline Missing Not the strongest first wedge unless validation says otherwise.
Tenant screening Missing High legal/GDPR/partner complexity.
KSeF/accounting/tax reporting Missing Useful later, not first paid promise.
Lease-linked maintenance suite Missing Post-launch only unless pilot evidence expands the simple issue-reporting promise.
Realtime chat Missing REST chat is acceptable.
Property-manager teams/roles Missing Later ICP.

Do Not Build Before Release

Item Why
MamNajem rent take-rate Research says fee stack is unattractive in Poland and confuses category.
One-click legal notices/eviction flows High legal risk without counsel-reviewed form, signature, and delivery proof.
Full marketplace/listing syndication Heavy integration with weak first-wedge fit.
App-store-first subscription strategy Margin/policy complexity before pricing is validated.
Direct debt/tenant screening product Compliance-heavy and not required for first promise.
Broad property-manager suite Current product lacks manager/team/accounting/vendor depth.

5. Product Release Checklist

Area Checklist item Required Status Evidence / notes
Landlord onboarding Capture role, city, unit count, self-managed vs agency Yes Missing/Partial Current onboarding exists, but ICP capture is not clear: onboarding route.
Landlord onboarding Owner-only activation: property, lease, document, rent schedule Yes Partial Backend/mobile flows exist; instrumentation needs release taxonomy.
Tenant onboarding Invite tenant and accept legal terms Yes Implemented InvitationsController.java, LegalController.java.
Tenant onboarding Minimal tenant tasks: handover, payment proof, document access Yes Partial Handover/payment/docs exist; payment-proof flow should be checked in pilot.
Property setup Property CRUD, costs, status, bank account Yes Implemented PropertiesController.java, OwnerPropertyCostService.java, BankAccountService.java.
Lease setup Basic lease, tenants, invitations, renewal Yes Implemented LeaseController.java, LeaseRenewalService.java.
Lease setup Lease type and legal eligibility gates Yes Missing Required by polish-residential-lease-product-spec.md.
Documents/legal artifacts Terms/privacy acceptance Yes Implemented terms, privacy.
Documents/legal artifacts Immutable PDF/hash/execution method/delivery proof Yes Missing Research requires artifact spine; no API surface found.
Handover protocol Move-in/move-out protocol with photos and tenant confirmation Yes Implemented/Partial Implemented; legal immutability/versioning still missing.
Deposit/final settlement Deposit ledger, deductions, refund deadline, settlement statement Yes Partial FinalSettlementService.java.
Rent tracking Rent schedule, requests, receipts, overdue/compliance Yes Implemented PaymentScheduleService.java, PaymentRequestService.java.
Rent tracking Off-ledger proof-first default Yes Partial Payments exist, but Stripe checkout is also built/prominent.
Notifications In-app and push Yes Implemented NotificationService.java, ExpoPushSender.java (backend/src/main/java/pl/mamnajem/service/ExpoPushSender.java).
Notifications Email reminders/invites Yes Missing Email channel exists but no sender found.
Notifications SMS reminders No Missing / postpone Add as paid bundle later.
Messaging Lease chat, unread/read, action requests Yes Implemented ChatsController.java.
Maintenance Lease/property-linked repair workflow No for paid pilot Post-launch backlog Generic app support reports are the launch scope.
Pre-lease funnel Lead/application tracking No Missing / postpone Research says not first unless validation demands it.
Billing Web Stripe subscription checkout/portal Yes Implemented SubscriptionsController.java.
Billing 30-day trial → paid or Archive (read-only) Yes Implemented Trial starts from explicit CTA; Archive is read-only for writes.
Billing Tier caps (Solo 3/10, Portfolio 10/35, Plus 25/100); archived excluded Yes Implemented Active properties and active tenants are counted separately.
Billing 80% soft-warn + immediate cap+1 block; 14-day grace only for migration/downgrade overages Yes Implemented Paywall responses expose stable subscription block codes.
Billing ">25 units" contact-us wall + Plus+ design-partner policy + agency waitlist Yes Missing Need policy doc (EP1-T8) + landing capture (EP1-T9).
Billing Hide/feature-flag native IAP for launch; web-Stripe default Yes Partial isNativeStoreBillingEnabled flag exists; verify prod config to avoid App Store 3.1.1 rejection.
Admin/support Problem report triage UI Yes Partial Backend exists; web-admin lacks UI.
Admin/support Stripe webhook replay UI/runbook Yes Partial Backend/runbook exists; web-admin lacks UI.
Analytics Activation funnel events Yes Partial Telemetry exists; research event schema not fully mapped.
Privacy Export/delete Yes Implemented DataExportService.java, AccountDeletionService.java.
Privacy Retention automation and IBAN encryption Yes Pilot-aligned IBAN and retention decisions are documented for the paid pilot; legacy/plaintext cleanup and counsel review remain before paid production.
Security JWT/RBAC/rate limits/security headers/audit logs Yes Implemented SecurityConfig.java, AuditService.java.
Legal review Polish counsel review of launch copy and workflows Yes Missing Required by legal docs.
Landing/GTM Polish ICP landing page, pricing page, founder offer Yes Partial/Missing Landing exists; pricing/founder offer absent.
Ops runbooks Deploy/alerts/incident/webhook runbooks Yes Partial/Implemented deployments.md, incident-triage.md.

6. Business Model And Pricing

Refined model (replaces perma-freemium with trial + Archive after 2026-05-30 review):

Element Recommendation
Acquisition surface 30-day no-card trial (full Portfolio features during the trial). NOT a perma-free tier — in this market most 1-unit landlords never upgrade by adding a 2nd flat, LTV is below CAC at low prices, and the support cost of perma-free users outweighs the funnel value.
After-trial fallback Archive (read-only). Old / cancelled users keep access to their lease and document data but cannot add new properties, leases, tenants, or send notifications. Keeps GDPR data-access promises without subsidizing dabblers, and avoids the "you locked my files" support nightmare.
Founding Landlord Program First ~50 cohort, closed once filled. 90 days free. Conditional: ≥2 live units activated within 30 days + testimonial / case-study consent. Founding price-lock for 12 months after pilot.
Paid tiers (public launch) Solo 19.99 PLN / Portfolio 49.99 PLN / Plus 99.99 PLN gross monthly.
Hard caps (active entities only; archived excluded) Solo: 3 properties / 10 tenants. Portfolio: 10 / 35. Plus: 25 / 100. Separate property and tenant caps so room-by-room rentals are not punished.
Paywall behavior Soft-warn at 80% of cap; hard-block new creates at cap+1 immediately; apply 14-day grace only when migration or downgrade leaves an owner already over cap. Never restrict access to or editing of already-created entities. Cap applies on creation, not on existence.
26+ unit inbound No self-serve above 25. "Contact us" wall replaces the upgrade button. Optional Plus+ design-partner at 199 PLN/month for 26–50 single-operator portfolios (max 2 customers in year 1, no SLA, explicit design-partner agreement, no custom features). 51+ units, or any team / accountant / agency need → "Not the right fit" path: refer to Bidrento (from ~187 PLN/month at 15+ units) or casavi, capture on agency waiting list. Never custom-build features for a single >25-unit customer.
Annual Roughly 10 months paid (≈20% discount). Annual not exposed until after pilot proves monthly conversion.
Add-ons Tenant verification 159 PLN single / 249 PLN property pack; SMS bundles (19 PLN/100, 79 PLN/500); extra storage; concierge migration 149–299 PLN; QES / external signing pass-through.
Do not monetize yet Rent take-rate, tenant fees, legal guarantees, embedded payout margin.
Rent payment take-rate No. Off-ledger tracking first. Take-rate is currently hardcoded setApplicationFeeAmount(0L) at StripeConnectServiceImpl.java:219 — keep it zero.
Billing channel Web / Stripe first. Native app-store billing should not drive the model. EXPO_PUBLIC_NATIVE_STORE_BILLING_ENABLED must be correct at store submission (App Store 3.1.1 rejection risk if a digital subscription is routed to web checkout).

Actual implementation:

Area Exists Gap / overbuild
Subscription engine Stripe checkout, portal, change plan, cancel, webhook handling, entitlement enforcement (SubscriptionEnforcementFilter). Good foundation.
Native store billing Apple StoreKit2 + Google Play verification and mobile purchase flow exist. Overbuilt for MVP and conflicts with web-first strategy; feature-flag off for launch.
Current DB plans Starter 9.99 PLN up to 3; Standard 89.99 PLN up to 10; Pro 249.99 PLN up to 50; BASIC free; GRANDFATHERED legacy. Does not match recommended pricing or cap structure. Must be replaced before launch.
Trial / Archive states None — current model assumes perma-free BASIC plus paid tiers. Trial timer, Archive state, post-trial downgrade behavior, and cap-enforced paywall trigger all missing.
Rent payments Stripe Connect checkout, disputes/refunds/webhooks. Heavy for first Polish rent MVP; should not be default.
Reminder scheduler None for payments / leases. Only @Scheduled jobs are metrics snapshots and Stripe webhook retry/reconcile. PAYMENT_DUE / PAYMENT_OVERDUE / LEASE_ENDING templates exist but no cron emits them. Must be wired before charging for "reminders."
Take-rate Hardcoded to 0 in Stripe Connect destination charges. Intentional, but worth a code comment so it isn't accidentally flipped on.
Missing Pricing page, founder/pilot offer, cap+1 paywall behavior, annual pricing test, public plan copy, agency waitlist intake, "Not the right fit" referral script. Must be fixed before credible paid launch.

Evidence:

7. Go-To-Market Release Scope

Asset Rank Current repo support Notes
Narrow positioning Required Partial Landing is broad; rewrite around self-managing Polish landlords.
Polish landing page Required Partial Landing exists but needs ICP/pain/founder CTA.
Pricing page Required Missing Needed for price test and paid conversion.
Founding Landlord Program Required Missing 90 days free, migration help, price lock, 2 live units.
Pilot intake form Required Missing Needed before public launch.
SEO pages Should have / required for launch motion Missing Start with occasional lease kit, handover/settlement, rent reminders, spreadsheet-vs-system.
Outreach list Required Not in repo 50 landlord/community/educator leads minimum.
Community/partner plan Should have Docs only Needed for low-CAC acquisition.
Referral plan Can wait / should have Missing Useful after first pilots.
Analytics Required Partial Telemetry exists; business activation taxonomy needs alignment.
Demo assets Should have Partial App/demo mode exists; no case studies.
Support materials Required Partial Support pages/runbooks exist; onboarding/help macros missing.
Agency waiting list capture Required Missing Single-field email capture on pricing page for >25-unit inbound; routes them away from self-serve and gathers demand signal for a future agency product. EP1-T9.
"Not the right fit" referral script Required Missing One-page script (kept in docs/operations/) for support and founder to handle >25-unit inbound: name-check Bidrento / casavi, decline politely, offer agency waitlist. Protects scope from the most flattering customers. EP1-T8.

Evidence:

8. Validation Required Before Release

Required validation before public release:

Test Minimum
Landlord interviews 18-24 self-managing landlords, with real artifacts shown.
Tenant interviews 8-12 tenants, focused on handover, payment proof, docs, issues, deposit.
Survey 75-150 qualified landlords after interviews, not before.
Landing smoke tests 2-3 Polish landing variants, ideally 200+ qualified visits each.
Pricing validation Pilot uses 19.99 / 49.99 / 99.99 PLN gross monthly; no percent-of-rent test.
Paid pilot/design partners 8-12 landlords, 20-40 live units, one real lease imported, three workflows completed.

Success metrics:

Metric Target
Owner-only activation 40%+ qualified signups create property + lease + document + rent schedule in 7 days.
Real-lease willingness 40%+ qualified landlords agree to move a real lease/workflow.
Tenant task completion 50%+ invited pilot tenants complete one real task.
Workflow depth 60%+ pilot landlords complete 3+ target workflows.
Price acceptance 30%+ accept or pre-commit to tested post-pilot price.
Strong public-launch signal 30-50 paying ICP landlords, 150+ active units, 2 repeatable channels.
Narrow signal 10-29 payers plus strong activation and one winning channel.

Red flags:

Red flag Meaning
Nobody moves real leases Idea is liked but not behaviorally valuable.
Tenants ignore required flows Owner value must be made more independent.
Only 1-unit landlords convert Paid market may be too small/price-sensitive.
Maintenance is the dominant pain Pause broad launch and validate the post-launch maintenance backlog before expanding the public promise.
Pre-lease is dominant pain Current wedge may be too far downstream.
Users only accept free Stop broad launch until value/pricing changes.
Topic Gate Product area affected Current status / evidence
Ordinary lease Must review before release if lease docs/templates are positioned as legal artifacts. Lease setup, documents, signing. Basic lease exists; written-form/QES logic missing.
Occasional lease Should not be included as supported until reviewed. Lease type, notary attachments, tax notification, vacate demand. Missing; research says hybrid notary flow required.
Institutional lease Should not be included in first release unless separately reviewed. Business landlord eligibility, deposit caps, vacate path. Missing; postpone.
Deposit rules Must review before release. Deposit ledger, deductions, refund deadline, settlement. Partial; settlement exists but legal ledger/deadline logic missing.
Handover protocol Must review before release. Move-in/out evidence, photos, confirmation wording. Implemented but legal artifact immutability missing.
Rent increase notices Should not be included until reviewed. Notices, delivery proof, QES/wet ink. Missing; do not add quick toggle.
Termination notices Should not be included until reviewed. Arrears/breach sequencing, statutory grounds. Missing; high-risk.
Arrears warnings Should not be included until reviewed. Payment compliance, warning/cure deadline. Payment overdue exists; legal warning engine missing.
E-signature/QES/notary Must review before any claim of legal signing. Documents, lease execution, notices. No e-sign implementation found; in-app confirmation only.
Delivery proof Must review if notices/artifacts launch. Address history, registered mail, e-delivery, proof storage. Missing.
GDPR/retention Must review before paid launch. Privacy, export/delete, retention, IBAN. Pilot policy/code alignment is recorded in retention policy alignment; Polish counsel review still required.
Tenant screening Should not be included until reviewed. Pre-lease, verification, partner data. Missing; postpone.
Payments/rent collection Must review if Stripe Connect rent checkout remains exposed. Rent payments, Connect onboarding, refunds/disputes. Implemented but research says demote to optional/future.

10. Overengineering And Missing Pieces

Overengineered before release:

Area Evidence Why it distracts
Stripe Connect rent checkout, disputes, refunds StripeConnectServiceImpl.java, RentPaymentService.java Heavy PSP/KYC/support surface before off-ledger rent value is validated.
Native store subscription stack service/store Web-first billing is recommended; native billing adds policy/margin complexity.
Broad audience positioning LandingPage.tsx (mobile-frontend/components/landing/LandingPage.tsx), common.json Attracts managers/tenants before product is optimized for them.
Production infrastructure depth without release gates architecture Infra is mature, but launch blockers are legal/GTM/activation.

Missing for release:

Missing Why it matters
Legal artifact engine Core Poland trust and differentiation.
Lease type eligibility and execution method Avoids dangerous legal overstatement.
Deposit ledger and deadlines High-conflict landlord/tenant workflow.
Transactional email Invites/reminders/legal flows need non-push delivery.
Lease-linked maintenance workflow Post-launch backlog unless interviews prove simple issue reporting is insufficient.
Admin support verification and runbook signoff Paid support needs triage/replay tools proven in integration.
Pricing/founder/pilot pages Needed to sell and validate.
Privacy/retention/encryption alignment Legal and trust gate.
Production config hardening Paid reliability gate.

Simplify now:

Simplification Action
Rent collection Default to IBAN + payment request + proof + mark-paid.
Billing Use web Stripe only for launch.
Onboarding One owner-first activation path.
Legal Track execution/proof first; do not automate legal notices until reviewed.
Landing One ICP, one promise, one pilot CTA.

11. Final Pre-Release Recommendation

Recommendation: Narrow, not broad go. Do not run a broad public paid release yet. Run a controlled paid/founding pilot after P0 legal, privacy, admin, pricing, email, and GTM gates are closed.

Recommended first ICP: self-managing Polish landlords with 2-5 long-term residential units in major cities, expanding to 6-10 units if activation and WTP hold.

Recommended first product promise: one mobile workflow for Polish long-term rental operations: lease setup, tenant invite, document vault, rent schedule/proof, handover protocol, messages, reminders, deposit/final settlement evidence.

Required pre-release MVP scope: owner-only activation, property/lease setup, documents, handover, rent schedule/payment proof, deposit/final settlement, basic messaging, in-app/push/email reminders, simple in-app issue reporting, web billing, admin support tools, activation analytics.

Required legal/compliance gates: Polish lawyer review of lease-type copy, handover wording, deposit logic, final settlement wording, e-sign/QES/notary claims, notice/delivery boundaries, GDPR retention, IBAN handling, and Stripe Connect rent-payment exposure.

Required GTM assets: Polish ICP landing page, pricing page, Founding Landlord Program, pilot intake form, outreach list, two smoke-test landing variants, activation dashboard, basic support/onboarding materials.

Recommended pricing: 30-day no-card trial → paid plans Solo 19.99 / Portfolio 49.99 / Plus 99.99 PLN gross monthly, hard-capped at 3 / 10 / 25 active properties (archived excluded). Post-trial fallback is read-only Archive, not a perma-free tier. Founding Landlord Program (first ~50, conditional) is the only "free." No rent take-rate. Web billing first. 26+ units: contact-us wall, no self-serve, referred to Bidrento / casavi or captured on agency waiting list.

Biggest release blocker: not code volume. The blocker is mismatch between a broad, technically advanced product and the narrow legally sensitive paid promise the research supports. The sharpest concrete blockers are legal workflow gaps, privacy/retention mismatch, and no validated paid pilot.

Most important next action: freeze scope to the narrow landlord MVP, fix the legal/privacy/admin/billing gates, and run the founding pilot with real landlords before any broad public release.