Skip to content

MamNajem Founder Decision Memo

Bottom line

MamNajem should not become a broad landlord-tenant-property-manager platform at launch. It should become the mobile operating system for Polish self-managing landlords: an owner-led rental operations product that handles the high-friction parts of long-term residential renting in Poland, from lead conversion and lease setup through handover, payment follow-up, maintenance-lite, and final settlement. Tenants are part of the workflow, but they are not the buyer. Property managers are a later expansion only after delegated roles, team permissions, and manager-grade workflows actually exist. fileciteturn0file11 fileciteturn0file5 fileciteturn0file4

The correct strategic call is Narrow. Not no-go. Not “keep building the broad current vision.” The research consistently supports commercialization of a much tighter product: Poland-first, city-first, landlord-paid, subscription-led, and centered on lease operations plus compliance clarity, not on embedded payments, accounting breadth, or property-manager complexity. The market can support a disciplined, profitable SaaS, but the evidence does not support a Poland-only venture-scale “super app” thesis. fileciteturn0file1 fileciteturn0file11 fileciteturn0file6

Your biggest strategic advantage is that the current product already contains unusually deep post-lease and in-tenancy workflow pieces: leases, handovers, settlement, messaging, reminders, payment requests, and document handling. Your biggest strategic mistake would be to keep investing primarily in invisible platform sophistication while the launch-critical customer-facing gaps remain pre-lease conversion, legally correct document/signature flows, maintenance-lite, and non-app reminders. fileciteturn0file5 fileciteturn0file11 fileciteturn0file7 fileciteturn0file8

Direct founder answers

What should MamNajem become? MamNajem should become the mobile operating system for Polish self-managing landlords, specifically for long-term residential rentals. The product category is not “property management software” in the broad enterprise sense. It is a mobile-first landlord operations product that makes documents, handovers, payment follow-up, tenant communication, maintenance-lite, and final settlement work together in one coherent system. fileciteturn0file4 fileciteturn0file5 fileciteturn0file11

Who is the exact first ICP? The exact first ICP is: a natural-person, self-managing landlord with 2–5 long-term residential units in Warsaw, Kraków, Wrocław, Trójmiasto, or Poznań, who currently runs rent, handovers, documents, reminders, and tenant communication through some combination of spreadsheets, bank transfers, chat apps, and file folders, and who does not yet have staff or a professional manager. One-unit landlords should remain a free-funnel segment; agencies, PRS, and delegated managers should be deferred. fileciteturn0file4 fileciteturn0file1 fileciteturn0file5

What problem should you lead with? Lead with operational chaos plus legal/compliance risk, not with payments, tenant screening, or “all-in-one property management.” The sharp problem statement is: “I can self-manage a few flats, but Excel + bank transfers + chat + scattered documents creates too much risk and admin around leases, handovers, reminders, deposit settlement, and tenant communication.” The best market-facing articulation is still the mobile-control angle: run every rented flat from your phone. fileciteturn0file5 fileciteturn0file4 fileciteturn0file6

What should you build first, next, and later? Build first the narrow Poland launch core: ordinary lease plus occasional lease workflows; lease-type gating; template/PDF/evidence layer; Autenti-based signing with QES escalation where required; deposit ledger; handover and final settlement; payment requests with reminders and proof; pre-lease lead/application/reservation flow without syndication; and a lean maintenance ticket flow tied to the lease. Build next PIT-28 cash-view reporting, simple invoices/exports, basic ID verification, and calendar sync. Build later embedded rent collection with a Polish PSP, partner screening, full KSeF/B2B tooling, utilities, insurance, analytics, and eventually team/property-manager workflows. fileciteturn0file6 fileciteturn0file10 fileciteturn0file8 fileciteturn0file7 fileciteturn0file9

What should you remove, postpone, or stop overengineering? Remove “property manager” from launch positioning. Postpone full embedded rent collection, percentage-of-rent monetization, listing syndication integrations, full accounting/KSeF breadth, in-house screening, insurance, and team workflows. Stop treating payment durability, native IAP complexity, or platform plumbing as the center of the product narrative. Those are not what the first buyer is buying. fileciteturn0file11 fileciteturn0file9 fileciteturn0file8 fileciteturn0file3

What should the subscription and pricing model be? Use a landlord-paid subscription priced by active portfolio size, not a payments take-rate. My recommendation is: Free only through the time-boxed pilot/trial path; Solo at 19.99 PLN gross/month for up to 3 active properties; Portfolio at 49.99 PLN gross/month for up to 10; Plus at 99.99 PLN gross/month for up to 25. Offer annual pricing only after the pilot proves demand. Keep third-party-cost items as add-ons: tenant screening, SMS, and higher-friction signature paths such as QES. Bill primarily through web/Stripe, not app stores, and do not take a cut of rent payments at MVP. fileciteturn0file3 fileciteturn0file4 fileciteturn0file1 fileciteturn0file9

What is the best go-to-market plan? Go city-first and ICP-first. The launch formula is: founder-led onboarding of self-managing landlords with 2–5 units in the top five cities, with messaging around mobile operational control and compliance clarity. Acquisition should start with Google Search and SEO, then landlord communities, landlord educators, partner distribution, and remarketing. The launch offer should be a Founding Landlord Program: 90 days free, white-glove migration from Excel/docs, and locked-in founding pricing after activation of at least two live units. fileciteturn0file4 fileciteturn0file1

What are the strongest parts of the current strategy? The strongest part is that the product already has a serious operational core for the owner-tenant lifecycle: lease handling, handovers, settlement, messaging, payment requests, and document/evidence flows. That gives you something many early landlord tools do not have: the foundations of a real operating system, not just a reminders app or a payments shell. fileciteturn0file5 fileciteturn0file1

What are the weakest parts of the current strategy? The weakest part is scope confusion. The current strategy tries to stretch across landlords, tenants, and future property managers while still missing some of the launch-critical basics that the actual first buyer expects: pre-lease conversion ops, maintenance-lite, legally correct signature and notice handling, and email/SMS reality. The second weakness is that the product appears technically more mature than it is commercially narrowed. fileciteturn0file11 fileciteturn0file7 fileciteturn0file8 fileciteturn0file0

What are the biggest business risks? The biggest business risks are: targeting too broad a market; attracting too many free one-unit landlords and too few paying 2–10 unit owners; spending into CAC before you own organic and partner intent channels; and pretending Poland alone is a venture-scale market when the research supports a solid SaaS business, not an obvious breakout platform. Legal/reputational overpromise is also a business risk if the product markets “fully legal e-signature,” eviction outcomes, or all-digital occasional lease flows too aggressively. fileciteturn0file1 fileciteturn0file4 fileciteturn0file10

What are the biggest product risks? The biggest product risks are: getting Polish legal-form and signature logic wrong; trying to automate notice or termination flows too aggressively; keeping maintenance and pre-lease too thin; relying too heavily on in-app/push instead of email/SMS; and turning embedded payments into a compliance and support burden before proving that landlords even need it. The property-manager role-gap is also a product risk if the roadmap keeps promising agency workflows without actual delegation, permissions, and team structures. fileciteturn0file0 fileciteturn0file10 fileciteturn0file7 fileciteturn0file9 fileciteturn0file11

What are the first 90-day execution priorities? The first 90 days should be used to lock the ICP, cut positioning, define the Poland launch core, ship the legal/document/signature layer, add pre-lease lite and maintenance lite, enable real reminder channels, and onboard live design partners in the target cities. The goal is not another broad build cycle. The goal is to get real landlords running real units through one complete lease cycle. fileciteturn0file6 fileciteturn0file4 fileciteturn0file5

What is the final go / narrow / no-go recommendation? Narrow. Move forward, but only on the narrowed thesis. Go-to-market the landlord operating system for self-managing owners in Poland. Do not go to market with the current broad landlord-tenant-property-manager platform story. If you refuse to narrow, the answer becomes much closer to no-go on the current strategy. fileciteturn0file1 fileciteturn0file11 fileciteturn0file5

Product strategy and roadmap

The strategy should be built around a single organizing rule: close one full rental lifecycle before expanding the platform again. In practical terms, that means MamNajem must win from inquiry to signed lease to move-out and settlement, but it must do that in a way that stays honest to Polish rental law and realistic landlord behavior. That is why the right synthesis is pre-lease lite, lease/compliance core, in-tenancy operations, and move-out evidence—not a marketplace, not a quasi-bank, and not a manager ERP. fileciteturn0file6 fileciteturn0file8 fileciteturn0file10

A central strategic decision is to launch with ordinary lease plus occasional lease, and not with institutional lease or manager-first segmentation. Ordinary and occasional lease cover the private-landlord launch market. Institutional lease, PRS flows, and manager operations all add a different legal and commercial shape that will dilute the first launch. fileciteturn0file10

The second central decision is document policy. MamNajem should own the template library and evidence layer inside the product, render immutable PDFs before execution, and then route documents by legal lane: in-app documentary confirmation for handovers and settlement records; external SES/AES for lower-formality documents; QES or wet ink when written form matters; and hybrid offline tracking for occasional-lease artifacts that still require notarial or certified elements. Autenti is the best primary provider for a Poland-first launch, with KIR as the QES fallback. fileciteturn0file0 fileciteturn0file10

The third decision is how to resolve the pre-lease and maintenance contradictions across the reports. The right answer is yes to both, but only in lightweight form. Pre-lease should mean internal lead/application/reservation tracking with excellent manual posting support, not brittle channel syndication. Maintenance should mean a lease-linked issue workflow with urgency, responsibility, access, scheduling, and closure-to-settlement logic, not a contractor marketplace or a property-manager work-order suite. fileciteturn0file8 fileciteturn0file7

Horizon What ships What stays out
First build Ordinary + occasional lease gating; template/PDF/evidence layer; Autenti integration and QES escalation; deposit ledger; move-in/move-out handover; final settlement; payment requests, receipts, and reminder engine; email/SMS reminders; lead/application/reservation pipeline; maintenance-lite Listing syndication APIs; institutional lease; embedded payments; team roles; full accounting/KSeF; in-house screening
Next build PIT-28 cash-view report; simple invoices/exports; basic ID verification; calendar sync; optional external screening handoff; better archives/search Marketplace payout model; insurance; utilities; deep analytics
Later build Optional Polish PSP for embedded collection; partner screening; manager/team roles; KSeF/B2B depth; insurance; utilities; portfolio analytics; cross-country layer Anything that re-broadens the launch before the core retention numbers work

This roadmap is the cleanest resolution of the research set. It preserves the strongest current product assets, fills the visible launch gaps, and prevents the company from spending the next cycle on integrations that do not materially change landlord adoption. fileciteturn0file6 fileciteturn0file8 fileciteturn0file7 fileciteturn0file9 fileciteturn0file11

Pricing and monetization

MamNajem should monetize as a subscription-led landlord operations SaaS, not as a rent-fintech take-rate business. That recommendation is unusually consistent across the research: portfolio-size subscriptions dominate landlord software, while percentage-of-rent pricing is more common in guarantees, deposit replacement, and underwriting-heavy products. Poland’s market anchors also support a low-to-mid tens-of-zloty monthly SaaS bill, especially for multi-unit owners who are already comparing software against outsourced management. fileciteturn0file3 fileciteturn0file1

I would resolve the pricing contradiction this way: trial / 19.99 / 49.99 / 99.99. That structure is optimized for the pilot: low-friction for first paid conversion, still visibly below management fees, and clear enough to test whether 2–10 unit owners will pay. That is an inference from the pricing, GTM, and financial reports taken together, updated for the pilot pricing decision. fileciteturn0file3 fileciteturn0file4 fileciteturn0file1

Plan Price Cap What the buyer gets
Free 0 PLN 1 active property, 1 active lease Full proof-of-value for one live rental lifecycle, but limited scale and channel usage
Solo 19.99 PLN gross / month Up to 3 active properties The first real paid plan for the actual ICP: documents, handovers, reminders, payment follow-up, tenant collaboration, maintenance-lite
Portfolio 49.99 PLN gross / month Up to 10 active properties Main money plan for serious self-managing landlords
Plus 99.99 PLN gross / month Up to 25 active properties Export-heavy and support-heavy plan, future home for advanced workflows before true team plans exist

Annual pricing should be roughly 10 months paid, presented in gross PLN on the site. Archived properties, archived leases, and historical documents should not count toward plan caps; only storage should. Otherwise you penalize good recordkeeping, which is the opposite of the product promise. fileciteturn0file3

Use web/Stripe as the primary billing channel. Do not architect the commercial model around app-store billing. On low-price landlord SaaS plans, margin compression matters. Keep third-party-cost flows usage-priced or pass-through: tenant verification, SMS quotas, and QES/external signing where needed. For rent, keep no platform take-rate at MVP. If online checkout is later offered, price it at processor cost until there is real additional value. fileciteturn0file1 fileciteturn0file3 fileciteturn0file9

Go-to-market and execution

The winning message is not “all-in-one rental platform,” “property management software,” or “payment automation.” It is mobile operational control for self-managing landlords. The best homepage framing is still: Run every rented flat from your phone. Under that, the job to be done is concrete: leases, handovers, payment follow-up, documents, tenant communication, and settlement in one place. That positioning differentiates MamNajem from protection-led products on one side and heavier back-office/accounting tools on the other. fileciteturn0file4 fileciteturn0file5

The acquisition stack should start exactly where the research converges: high-intent Google Search and SEO first, then landlord communities, landlord educators, partner distribution, and remarketing. That means content and paid intent around occasional lease, rent reminders, deposit return, handover protocols, rent increase rules, template workflows, and landlord admin pain. Later, after the internal lead pipeline exists, Meta Lead Ads can be worth testing; portal syndication should still wait. fileciteturn0file4 fileciteturn0file1 fileciteturn0file8

The commercial motion should be founder-led for the first cohort, not purely self-serve. The right launch asset is a Founding Landlord Program with 90 days free, white-glove migration from Excel/docs, and founder support through the first live activation. This is not just a discount tactic. It is the fastest route to case studies, objection handling, onboarding learning, and retention feedback from the exact segment you need. fileciteturn0file4

Period Execution priority Expected output
First month Rewrite positioning; remove property-manager messaging; set pricing; recruit 15–20 design partners in the top five cities through search, communities, and educators Clear ICP, clear offer, first interview and onboarding pipeline
Second month Ship Poland launch core: legal document/signature lanes, reminders, pre-lease lite, maintenance-lite, evidence outputs First live properties and leases running through the narrowed core
Third month Run founding cohort aggressively; migrate real landlord data; collect before/after stories; instrument metrics; prepare repeatable acquisition playbooks Real retention signal, first case studies, first repeatable GTM learning

The metrics that matter are not installs or vanity signups. They are qualified landlord signups, activated landlord accounts, active units under management, 90-day retention, and CAC payback by channel. I would define “activation” tightly: at least one live property, one real tenant invited, one active lease or signed document path, and one live operational workflow such as payment schedule, handover, or maintenance ticket. Beyond the first 90 days, the more durable proof point is the threshold suggested in the GTM work: 30–50 paying ICP landlords, 150+ active units, 40%+ activation from qualified signups, 70%+ 90-day retention, and at least two repeatable channels. fileciteturn0file4

Risks, strengths, and final call

The strongest part of the current strategy is the product’s operational depth where landlords actually feel pain. MamNajem already looks much closer to a real lease-lifecycle system than many early-stage landlord products. That matters because launch success in Poland will come from credible workflows, not from a shallow landing page thesis. Also, the product can plausibly become a profitable SaaS without needing enormous scale if it captures the right niche of multi-unit self-managing owners. fileciteturn0file5 fileciteturn0file1

The weakest part of the current strategy is that it is still trying to serve the company you want to become before finishing the company you can actually win as. The current direction spreads attention across landlords, tenants, subscription complexity, payments infrastructure, and future managers while delaying the customer-visible basics that would clarify category fit. That is classic scope drag. fileciteturn0file11 fileciteturn0file9

The biggest business risks are market-shape risks, not engineering risks. Poland’s private rental market is fragmented, price-sensitive, and full of single-unit landlords who will happily stay free. That creates a real trap: lots of signups, weak monetization. A second business risk is channel discipline. If you start buying broad awareness before the search/content/community engine works, CAC can outrun low-ticket SaaS economics. A third risk is strategic self-deception: treating Poland-first as a venture-scale story instead of a focused SaaS wedge. fileciteturn0file1 fileciteturn0file4

The biggest product risks are legal correctness and product sprawl. If the signature, notice, or occasional-lease logic is wrong, the brand damage will be disproportionate. If reminders stay too app-centric, operational value will look weaker than the product really is. If embedded rent collection becomes a first-order project, it can consume roadmap capacity without improving adoption enough to justify the complexity. And if you keep promising property-manager support without delegation, roles, and team permissions, you will misposition the product before it is ready. fileciteturn0file0 fileciteturn0file10 fileciteturn0file9 fileciteturn0file11

The decision checklist is simple:

  • Yes if the launch category is explicitly self-managing landlords in Poland, not landlords + tenants + property managers.
  • Yes if the first ICP is explicitly 2–5 unit private landlords in the top urban markets.
  • Yes if the first product story is lease operations plus compliance clarity, not payments or accounting.
  • Yes if the roadmap is narrowed to one complete rental lifecycle with pre-lease lite and maintenance-lite.
  • Yes if rent remains off-ledger at MVP, with no take-rate and no embedded collection dependency.
  • Yes if legal document lanes, Autenti-led signing, and evidence outputs are live before the main launch.
  • Yes if the first 90 days produce real activated landlords and live units, not mostly demos and free curiosity accounts.

My final recommendation is Narrow. Commercialize MamNajem now, but only after cutting it into the product the market research actually supports: a Poland-first mobile landlord operating system for self-managing landlords. That is a real company. The broader current ambition is not yet a real launch strategy. fileciteturn0file1 fileciteturn0file11 fileciteturn0file4