MamNajem product gap audit for a Poland-first paid MVP¶
Executive verdict¶
MamNajem is closer to a strong landlord-operations engine than to a launch-ready Poland-first paid MVP. The attached research consistently says the winning first product is a mobile-first operating system for self-managing landlords with roughly 2–10 units, not an agency platform and not an enterprise property-management suite. The commercial logic is also narrow and disciplined: Poland can support a small profitable SaaS, but the most attractive paid segment is the self-managing 2–10-unit landlord, not the one-unit dabbler and not the professional manager segment. fileciteturn0file1 fileciteturn0file4 fileciteturn0file10
That means the current product is strategically right in some important places and strategically wrong in others. It is right in the parts that matter most to the recommended wedge: lease lifecycle, tenant collaboration, handovers, evidence capture, payment follow-up, and final settlement. It is wrong, or at least still too thin, in the places that make a Polish paid launch credible: legally correct lease execution and notices, maintenance/repair workflow, non-app communications, a focused pre-lease funnel, and a simpler Poland-first payments stance. fileciteturn0file5 fileciteturn0file6 fileciteturn0file7 fileciteturn0file9 fileciteturn0file10
The strict conclusion is this: do not keep broadening the platform. Narrow it. Ship a product for Polish self-managing landlords that helps them convert a lead, execute the right lease, collect rent predictably, manage handover and repairs, communicate clearly, and close the tenancy with defensible evidence. Everything else should either wait or be actively de-scoped. fileciteturn0file4 fileciteturn0file5 fileciteturn0file8 fileciteturn0file9 fileciteturn0file10
Current product against the recommended MVP¶
Where the current product is already strong. The current build already covers the part of the workflow that the reports treat as the most promising initial wedge: owner onboarding, property and lease records, tenant invites, payment schedules and proof, messaging, handovers, and final settlement. That is not trivial. In fact, the reports repeatedly argue that MamNajem should win on mobile-first lease operations, especially the flow from lease activation through payment follow-up, handover evidence, and move-out settlement. In other words, you have built a lot of the right middle of the product. fileciteturn0file4 fileciteturn0file5 fileciteturn0file10
Where the current product is directionally right but commercially misframed. Your payment schedules, payment requests, receipts, proof upload, bank account storage, and mark-paid flows are conceptually close to the recommended Poland-first model. The dedicated payments report, however, argues that the MVP should be off-ledger and bank-transfer-first, with landlord IBANs, due dates, reminders, proof of payment, and confirmation logs as the default behavior. The broader market-research memo is slightly more permissive and allows one localized hosted payment path, but the dedicated Poland payments report is more precise and should carry more weight. The implication is that the current rent-collection capability is usable, but its Stripe Connect-heavy emphasis is ahead of what the market actually needs first. fileciteturn0file8 fileciteturn0file10
Where the current product falls short of the recommended MVP. The most important shortfalls are the same ones that recur across the attached reports: a real tenant maintenance workflow, a minimal but real pre-lease funnel, operational email and SMS, and a legally defensible Polish lease/document system. The research is blunt on all four. It says the missing launch pieces are maintenance, pre-lease lead/application tracking, signature/template workflow, and email/SMS reality rather than app-only communication. Separately, the lease-spec and e-signature reports show that a Polish launch needs lease-type gating, written-form and QES logic where required, occasional-lease notary pack handling, deposit and notice workflows, and proof of service. Those are not optional polish. They are launch credibility. fileciteturn0file6 fileciteturn0file7 fileciteturn0file9 fileciteturn0file10
Where the product is overbuilt relative to the recommended MVP. The current platform already contains deep subscription, payment, and operational infrastructure: Stripe Connect onboarding, disputes, refunds, webhook durability, native purchase handling, admin Stripe tooling, release pipelines, and enterprise-grade infrastructure. The attached reports repeatedly say not to let those systems define the first paid release. The monetization report explicitly recommends web billing, no rent take-rate, and restrained add-ons. The market-research report says to avoid more billing complexity before proving recurring usage. The payments strategy says not to launch full embedded rent collection as the Polish default. In short: the product is more mature operationally than it is commercially focused. fileciteturn0file3 fileciteturn0file8 fileciteturn0file10
Where positioning is ahead of product truth. The product description still uses “property manager” language, but the attached reports are clear that the first ICP should be self-managing private landlords, not managers or agencies. The validation plan specifically treats property managers as only a falsification sample, not the initial buyer. The GTM plan says to hide “property manager” from the main hero until the delegated-team model is real. The market-research report reaches the same conclusion from the competitive landscape. So the current product is not just missing PM features; it is carrying PM positioning debt that should be removed before launch. fileciteturn0file4 fileciteturn0file5 fileciteturn0file10
Product gap audit¶
Current strengths. The strongest assets are the ones that overlap with the recommended wedge: mobile-first lease operations, tenant collaboration, handovers, final settlement, payment schedules, proof handling, and a reasonably serious operational backend. That gives MamNajem a better starting point than a typical “just another landlord CRM” because the reports explicitly say these operational flows are the most differentiating part of the product in Poland if framed for self-managing landlords. fileciteturn0file4 fileciteturn0file5 fileciteturn0file10
Missing must-have features before launch. Five gaps are serious enough to treat as pre-launch requirements: a real maintenance ticket flow; a Polish lease/legal engine for ordinary and occasional leases; email and SMS reminder infrastructure; retention, legal-hold, and evidence-lifecycle tooling; and a minimal pre-lease funnel with leads, applications, viewings, reservation, and outsourced screening handoff. If those are not present, MamNajem will feel broad but still not safely sellable in the exact market it wants to target. fileciteturn0file6 fileciteturn0file7 fileciteturn0file9 fileciteturn0file10
Useful but should wait. Profitability reporting, cashflow summaries, accountant exports, bank reconciliation, KSeF-related depth, delegated co-owner or accountant access, and a deeper screening integration are all useful, but the reports consistently place them after the first paid landlord-ops MVP. They help the product mature, but they are not the tightest proof of value for a 2–10-unit self-managing owner. fileciteturn0file3 fileciteturn0file7 fileciteturn0file10
Features that seem overengineered for the first paid release. The current depth in Stripe Connect rent checkout, refunds, disputes, native IAP, subscription state machinery, webhook durability, and enterprise-grade infrastructure is beyond what the reports say the first paid release should emphasize. So is any ongoing work that expands the demo/offline domain layer or deepens “property manager suite” assumptions before the owner-landlord wedge is proven. These are not necessarily bad investments forever; they are just not what will make a Poland-first landlord SaaS succeed first. fileciteturn0file3 fileciteturn0file8 fileciteturn0file10
Compliance or legal-product gaps. This is the largest launch-risk category. The attached legal work makes clear that a Poland launch needs: lease-type eligibility gating; ordinary plus occasional lease support; routing between in-app documentary confirmation, external e-sign, and QES/wet-ink flows; notary-pack tracking for occasional lease; deposit cap and return logic; lawful rent-increase and arrears-warning workflows; proof of service and delivery evidence; and retention rules that balance GDPR with claim periods. As currently described, MamNajem has lease CRUD and document storage, but not the full legal execution and notice system that the launch spec recommends. fileciteturn0file0 fileciteturn0file6 fileciteturn0file9
Monetization gaps. The commercial model should be much simpler and much more Poland-specific than the current “BASIC / STARTER / STANDARD / PRO-style” stack suggests. The attached monetization work recommends a landlord subscription sold through web billing, with a permanent free entry tier and price steps like Free / Solo / Portfolio / Plus, gross-PLN presentation, no rent take-rate at MVP, and add-ons only where there is clear third-party cost such as screening, SMS, or onboarding. That matters because the financial-viability report says subscription-only can work on this segment without inventing enterprise pricing or payments margin. fileciteturn0file1 fileciteturn0file3
Tenant-side UX gaps. The tenant surface is still missing some of the highest-value trust builders. The reports point to a tenant experience centered on clear documents, rent reminders and proof, transparent deposit settlement, issue reporting with photos, and low-friction communication. The biggest current misses are guest-safe pre-lease handling, a proper maintenance workflow, non-app reminder channels, and a clearly designed hybrid path for documents that cannot be completed by simple in-app acceptance. The tenant app should stay narrow and useful; right now it risks being operationally rich in some places and thin in the moments that matter most to trust. fileciteturn0file5 fileciteturn0file6 fileciteturn0file7 fileciteturn0file9
Landlord-side UX gaps. The landlord experience needs a more obvious happy path. The GTM and validation work both argue for a concrete flow that starts with lead or lease setup and continues through rent schedule, handover, reminders, maintenance, and settlement. Today the product sounds broad, but not yet ruthlessly sequenced around the exact job-to-be-done of the 2–10-unit owner. What is missing is not more modules. It is a stronger landlord command flow: eligibility decision, template choice, invite tenant, set payment instructions, resolve issues, close tenancy. fileciteturn0file4 fileciteturn0file5 fileciteturn0file6 fileciteturn0file7
Payment and rent-collection gaps. The product has a lot of payment technology, but not yet the right Poland-first payment doctrine. The attached reports say the first paid MVP should be dominated by payment requests, landlord IBAN, due dates, reminders, proof upload, landlord confirmation, and audit logs, not by embedded marketplace-style money movement. If you later add online checkout, it should be localized and narrow, likely via a Polish PSP pilot, not by making Stripe Connect rent checkout the core value proposition. Also missing from the current description are bank import or reconciliation flows, which the reports explicitly classify as useful soon after launch, not before. fileciteturn0file3 fileciteturn0file8 fileciteturn0file10
Notification, email, and SMS gaps. Push and in-app notifications are not enough. The attached research is explicit that operational landlord software in Poland still depends on email and often SMS, especially for rent reminders, document prompts, visit scheduling, and lapsed-user re-engagement. For legal notices, generic push is not merely insufficient; it is the wrong evidence standard. So the gap is not “add another channel someday.” The gap is “build a real channel strategy with templates, preferences, resend logic, delivery states, and legal-service separation.” fileciteturn0file0 fileciteturn0file3 fileciteturn0file10
Admin, support, and tooling gaps. Operational tooling exists, but it is not yet shaped around the exact support burden of a compliance-adjacent landlord SaaS. The research says the product needs admin support tooling that can safely operate payments, documents, evidence, and disputes. Against that benchmark, your own note that the admin web and backend look out of sync is a real warning sign, not a cosmetic bug. Add to that the missing automated retention cleanup and the need for document-service proof, maintenance evidence, and customer support inspection tools, and the picture is clear: internal operations are promising, but not yet tight enough for a paid legal/ops product. fileciteturn0file6 fileciteturn0file9 fileciteturn0file10
Prioritized roadmap¶
Launch blocker. Narrow the launch to self-managing landlords with 2–10 units and remove property-manager language; ship a Polish legal core for ordinary plus occasional lease, including eligibility gating, template generation, execution routing, deposit rules, notice flows, and proof of service; add the minimum maintenance workflow; add operational email and SMS plus delivery-state handling; implement retention, legal-hold, and evidence-lifecycle jobs; make Poland rent collection off-ledger by default; and fix the admin/support parity issues that would make customer operations brittle on day one. fileciteturn0file4 fileciteturn0file5 fileciteturn0file6 fileciteturn0file8 fileciteturn0file9 fileciteturn0file10
Must ship in the first paid MVP. Keep and polish the strong existing core: property, lease, tenant, document records; tenant invites and lease threads; payment schedules, reminders, proof upload, and manual confirmation; handover protocols; final settlement; and audit history. Add the minimum pre-lease layer the reports want: lead capture, application tracking, viewing scheduling, reservation, and outsourced screening handoff. Commercially, launch with web-billed landlord subscriptions, a free entry tier, and a simple Poland-first tier structure, rather than a payments-margin story or app-store-led monetization. fileciteturn0file3 fileciteturn0file7 fileciteturn0file8 fileciteturn0file10
Should ship within 90 days. Add bank import or reconciliation, basic landlord cashflow and profitability summaries, accountant/export basics, delegated access for a spouse or accountant, deeper email/SMS automation, and a tightly scoped localized payment pilot only if landlords actually want it after using the off-ledger flow. This is also the right window for a deeper but still outsourced screening integration and for migration/onboarding packages that help serious landlords move from spreadsheets. fileciteturn0file3 fileciteturn0file7 fileciteturn0file8 fileciteturn0file10
Later. Add institutional lease if and only if you intentionally expand toward business landlords; richer export, KSeF-adjacent, or accounting behavior if you move upmarket; contractor-facing workflows; broader co-owner or team permissions; deeper analytics; and a larger localized payments layer. These are reasonable second-stage expansions, but they should follow proof that the self-managing landlord wedge is retained and monetizing. fileciteturn0file1 fileciteturn0file3 fileciteturn0file8 fileciteturn0file9
Do not build yet. Do not build an agency or enterprise manager suite; do not make listing syndication a centerpiece of the MVP; do not build in-house insurance, rent-guarantee, or deposit-replacement products; do not add a visible rent take-rate; do not make native IAP the main billing path; do not expand webhook, dispute, or refund sophistication as a customer-facing priority; and do not spend more time deepening offline/demo-domain duplication. For this market, those are all distractions from the product that can actually become profitable first. fileciteturn0file3 fileciteturn0file7 fileciteturn0file8 fileciteturn0file10
The strictest single-sentence summary is this: MamNajem should launch as the mobile operating system for Polish self-managing landlords, not as a generalized rent-payments platform and not as a future enterprise manager suite. If you cut to that shape, the current product becomes commercially coherent; if you do not, it will remain impressive but strategically diluted. fileciteturn0file4 fileciteturn0file5 fileciteturn0file10