Skip to content

MamNajem Poland Launch Plan

Strategic focus

The right launch wedge is not “all-in-one property management.” It is a much narrower promise: lease operations + compliance + rent visibility for self-managing Polish landlords with 2–10 long-term units, with the sharpest early focus on 2–5 unit owners in Warsaw, Kraków, Wrocław, Trójmiasto, and Poznań. The attached research is unusually consistent on this point: that segment has real recurring pain, remains self-managed, is economically capable of paying a modest fixed subscription, and maps to MamNajem’s current owner–tenant workflow far better than agency or property-manager accounts. fileciteturn0file1 fileciteturn0file3 fileciteturn0file4

For launch, MamNajem should be positioned as the mobile operating system for the Polish landlord workflow, not as a protection product, not as a full-service manager substitute, and not as an enterprise PM system. The product should solve: property and lease setup, required documents, handovers, deposit and final settlement, rent schedule and reminders, and the legally sensitive steps around ordinary and occasional leases. Payments should start as off-ledger payment requests plus proof and reminders, not as embedded marketplace money movement. Listing syndication should stay manual at first; MamNajem should become the place where inquiries, applications, leases, handovers, and settlement converge. fileciteturn0file5 fileciteturn0file7 fileciteturn0file8 fileciteturn0file9

The practical implication is that the next 90 days should be mostly about re-scoping, hardening, instrumenting, and packaging what already exists in your product description, rather than building more surface area. The launch should deliberately de-emphasize areas the research says are expensive, risky, or premature: delegated manager/team workflows, deep listing integrations, embedded rent collection, heavy maintenance operations, KSeF/B2B invoicing, and international-signature vendor complexity. fileciteturn0file0 fileciteturn0file6 fileciteturn0file7 fileciteturn0file8 fileciteturn0file9

The smallest team that can execute this well has four functional roles, even if one person wears multiple hats:

Role Core ownership in this plan
Founder ICP decisions, customer interviews, pricing, partnerships, webinars, pilot sales, support escalation, final product cuts
Product engineer Mobile/backend flow hardening, legal workflow state, reminders, payments visibility, analytics events
Frontend or growth engineer Landing pages, web onboarding, pricing/paywall, analytics dashboards, SEO implementation
Ops and customer success Pilot migration, manual QA, help center, support playbooks, weekly cohort check-ins

In a very small team, the Founder will usually double as GTM + Customer Success, and the frontend/growth role can be part-time or contractor-based. The only outside specialist I would budget for in the first 90 days is a narrow legal review of templates, notices, and launch copy, not a broad legal workstream. fileciteturn0file0 fileciteturn0file9

Weekly execution plan

This weekly plan is sequenced around five evidence-backed priorities: target 2–10 unit self-managing landlords, lead with lease operations and compliance, use owner-only activation before asking for tenant adoption, keep payments off-ledger for MVP, and build acquisition around search/SEO, communities, educators, referrals, and remarketing, not broad paid awareness. fileciteturn0file1 fileciteturn0file3 fileciteturn0file4 fileciteturn0file8

Week Product work GTM work Validation work Key deliverables Primary owner Success metric Main risk
Week 1 Put the product into Poland launch mode. Hide or remove “property manager” from main navigation and onboarding. Add ICP capture to signup: role, city, number of units, self-managed vs agency. Define business-event taxonomy for activation and billing. Rewrite homepage brief around one ICP and one wedge. Create Polish-first hero copy, founding-program waitlist form, and a simple pilot intake form. Build outreach list of 50 landlords, community leads, and educators. Schedule the first landlord interviews. Finalize scorecard, screener, and interview guide. ICP brief, kill-list of deferred features, event schema, homepage copy brief, outreach list Founder 10 landlord interviews booked, event schema approved, homepage copy locked Staying too broad publicly and attracting low-fit signups
Week 2 Ship owner-only activation v1: property created → lease created → document uploaded → rent schedule set. Instrument every step. Add simple “launch cohort” tagging in admin. Launch two landing-page variants in Polish: lease operations vs compliance. Founder-led outbound to community contacts and educator shortlist. Run 6–8 landlord interviews and 4–5 tenant interviews. Start warm-traffic test to landing pages. Two live landing pages, first interview synthesis, activation funnel dashboard Founder + frontend/growth engineer One variant reaches early qualified conversion above the other; at least 100 qualified visits from warm traffic Message drift between pages and product reality
Week 3 Lock MVP scope. Add ordinary vs occasional lease gating, required field checks, notarial-attachment checklist, mandatory move-in protocol, and deposit timer fields. Do not build end-to-end e-sign yet; build status tracking for hybrid execution. Publish content asset one: occasional lease starter kit with pilot CTA. Polish on-page SEO, schema, and internal links. Finish the core interview sprint. Rank wedges. Confirm first 5 pilot candidates. MVP scope memo, legal workflow matrix, content asset one, 5 pilot commits Founder + product engineer 12 landlord interviews and 10 tenant interviews complete; one winning wedge is obvious Legal scope expands into a full document automation rewrite
Week 4 Harden off-ledger rent operations: landlord IBAN, payment request, payment reference, proof upload, mark-paid, overdue state, reminder events. Add an audit timeline for payment state changes. Launch two search-intent pages: one for “program do zarządzania najmem,” one for handover/settlement pain. Set up lead-routing and nurture email. Run fake-door pricing test and landing-page CTA test. Rent-visibility beta, price-test page, search-intent pages Product engineer + frontend/growth engineer 30%+ of target landlords answer definitely/probably yes at 29–49 PLN; at least 200 qualified visits cumulative Pressure to build BLIK checkout too early
Week 5 Build legal artifact engine v1: rendered PDF, version hash, signer/execution method field, attachment status, service-proof fields, deadline automation for deposit return and occasional-lease steps. Add core transactional emails for invites and reminders. Publish content asset two: PIT-28 rental tax explainer with calculator or worksheet download. Book first webinar with a landlord community. Observe live setup with the first 3 pilot landlords. Record every onboarding block. Legal artifact spine, transactional email basics, content asset two, webinar date Product engineer + Founder 3 landlords finish guided setup in under 72 hours Too much legal language creates UX friction
Week 6 Build concierge migration workflow instead of a full importer: admin-assisted property/lease import, document upload checklist, support macros, and checklist-based onboarding. Run webinar one. Publish content asset three: move-in/move-out protocol checklist. Add retargeting pixels. Launch pilot cohort A with 3–5 landlords and 10–20 units. Measure time-to-first-value. Migration SOP, webinar recording, pilot cohort A live Founder + ops/customer success 40%+ of qualified signups complete owner-only activation; 3 landlords activate at least 2 live units Support load eats product time
Week 7 Add only the minimum tenant surface needed for the wedge: tenant invite, document access, handover acknowledgment, payment proof, and issue-specific thread when required. Improve reminder reliability. Turn on narrow Google Search campaigns on 5–10 high-intent keywords. Publish comparison page: Excel/WhatsApp chaos vs one landlord workflow. Review the lead mix by channel and cut traffic sources that over-index on one-unit hobby landlords or renters. Tenant-minimum flow, search campaigns, comparison page, channel-quality dashboard Frontend/growth engineer + Founder 60%+ of new signups match ICP; search produces at least a few qualified calls without obvious waste Paid search burns budget on generic real-estate traffic
Week 8 Ship pricing wall and web checkout behind a feature flag. Trigger the paywall when a landlord activates the second live unit, with a short grace period. Use web billing only. Launch the Founding Landlord Program publicly. Run webinar two with an educator or community partner. Start a simple referral incentive. Start pilot cohort B and test conversion from trial to paid or firm paid commitment. Paywall, Stripe web checkout, founding offer, cohort B live Founder + frontend/growth engineer First 5 paying customers or signed paid commitments; 10 qualified demos from webinar Charging before enough value is demonstrated
Week 9 Build one conditional feature only if pilots demand it strongly: either lightweight pre-lease tracking or final-settlement polish. Default choice is settlement if signals are mixed. Publish first case study from a founding landlord. Publish content asset four: deposit settlement guide. Review weekly active use in cohort A. Run short “what would make you very disappointed to lose this?” pulse among activated landlords. Case study one, content asset four, one conditional feature shipped Founder 60%+ of earliest cohort remains weekly active Building a shiny side feature for a minority problem
Week 10 Finalize move-out and final-settlement workflow with acknowledgement wording, deduction categories, downloadable statement, and deposit-deadline reminders. Add owner dashboard cards for overdue rent, leases ending, and deposit due. Add one partner-led motion: referral page or bundle with verification, insurance, or educator workflow help. No deep integration yet. Decide whether to hold or raise public pricing based on observed conversion quality. Settlement v1, dashboard polish, partner referral page, pricing decision memo Product engineer + Founder 10 activated ICP landlords; second meaningful action rate above 25% Too many partnership conversations dilute execution
Week 11 Focus on bug fixes, speed, and reliability. Add simple help-center content inside onboarding. Improve reminder copy and support macros. Publish content asset five: late rent and written warning guide. Turn on remarketing with pilot proof and screenshots. Fill pilot cohort C only if support quality is holding. Start measuring trial-to-paid by channel. Help center, content asset five, remarketing creatives, cohort C Ops/customer success + Founder 15–25% of activated ICP landlords convert to paid; support load remains manageable Churn from onboarding gaps rather than missing features
Week 12 Launch-readiness hardening: permissions audit, analytics QA, billing QA, legal copy QA, retention rules, and backup/support procedures. Deliberately hide unfinished modules from the public product. Publish content asset six: spreadsheet vs landlord system comparison or a second case study. Prepare narrow public-launch email and webinar replay. Review channel economics, lead quality, pilot outcomes, and support cost per active landlord. Launch checklist, support playbook, content asset six, launch email draft Founder + product engineer Two channels show repeatable ICP acquisition; P1 launch blockers near zero Polishing non-essential infrastructure instead of launch blockers
Week 13 Release the narrow Poland ICP build. Keep the product visibly centered on owner workflows, legal records, handovers, rent visibility, and settlement. Freeze a post-launch backlog instead of adding new features. Run narrow launch: founder email, webinar replay, community posts, educator placements, search, remarketing, and case studies. No broad PR push. Execute the formal go / narrow / stop review with funnel, unit, revenue, and retention data. Public launch build, day-90 scorecard, go/narrow/stop memo, next-quarter backlog Founder Strong outcome: 30–50 paying ICP landlords, 150+ active units, 2 repeatable channels. Narrow outcome: 10–29 payers plus strong activation and one winning channel Mistaking polite interest for repeatable demand

The key deliverables by day 30 should be: one obvious wedge, one Polish-first landing-page winner, one locked MVP scope, a functioning owner-only activation flow, and 5 pilot commitments. By day 60, you should have live pilot cohorts, off-ledger payment visibility working, a founding offer, web billing behind a flag, and the first content cluster live. By day 90, you should have a narrow launch-ready product, 2 repeatable channel experiments, early case studies, and clean evidence for a go/narrow/stop decision. fileciteturn0file3 fileciteturn0file4 fileciteturn0file8 fileciteturn0file9

Pricing and subscription setup

The pricing model should be landlord-paid portfolio SaaS, not a take rate, not a tenant fee, and not a protection-like commission. The first public pilot should use 30-day trial / 19.99 PLN / 49.99 PLN / 99.99 PLN, because it keeps the first paid decision low-friction for a 2–10 unit landlord while still testing willingness to pay. At the same time, the financial research suggests the long-run business can likely sustain higher portfolio pricing, so the right move is to test low-friction public pricing first, then raise new-customer pricing only if conversion holds. Keep subscriptions on web checkout, not Apple or Google billing, because app-store fees materially reduce margin for a low-ticket SaaS. fileciteturn0file1 fileciteturn0file3

A practical first setup is:

Plan First-90-day public price Who it is for What is included now What is intentionally excluded now
Free 0 PLN Owners testing with 1 live unit Property, 1 lease, 1 tenant, document vault, handover, rent schedule, reminders, basic settlement Concierge setup, advanced compliance tracking, priority support
Solo 19.99 PLN / month Owners with up to 3 active units All core launch flows, occasional-lease checklist, legal deadline reminders, email reminders, basic support Deep partner services, advanced reporting, team roles
Portfolio 49.99 PLN / month Owners with up to 10 active units Everything in Solo plus migration help, cash-view export, priority onboarding, higher doc volume Agency permissions, embedded PSP checkout, accounting integrations

The paywall should trigger when the landlord activates the second live unit, not when they merely sign up. That is the cleanest moment at which the product moves from trial behavior to operational value. Give them a 14-day grace period after the second unit activates, then present one clear choice: keep the founding rate or stay on one unit. That makes monetization feel like a business decision, not a surprise. fileciteturn0file3

The best launch offer is still the Founding Landlord Program: 90 days free, migration help, founding price lock, and concierge onboarding, reserved for landlords with 2–10 units in the priority cities, and unlocked only if they activate at least two live units. This filters for serious users, produces testimonials and case studies, and reduces the switching friction that matters far more at this stage than a generic discount. fileciteturn0file3

The subscription rules should be strict:

Rule Recommendation
Billing rail Use existing Stripe web billing for subscriptions only
Rent collection Do not make Stripe Connect checkout the default Polish MVP
Tenant charging Do not charge tenants separately in the first 90 days
Per-unit pricing Test only on selected traffic; do not make it the default public story
Annual plan Offer only after week 10 if monthly activation and support economics are healthy
Refund posture Keep simple: 14-day cooling-off support, founder-handled exceptions

That structure follows the research: rent collection in Poland should begin with payment requests, IBAN, proof, reminders, and status, while subscriptions should be monetized on the landlord side. fileciteturn0file1 fileciteturn0file8

Landing page, messaging, content, and outreach

The landing page should be Polish first, even if founder materials and internal planning stay in English. The research is explicit that the public site should use the real local vocabulary people search for and understand: najem okazjonalny, protokół zdawczo-odbiorczy, kaucja, rozliczenie, czynsz. The strongest hero remains a mobile-control message, not generic proptech language and not “property manager” language. fileciteturn0file3 fileciteturn0file4

The first homepage version should use this message structure:

Element Recommended direction
Hero Prowadź każdy wynajmowany lokal z telefonu
Subhead Umowy, protokoły, czynsz, dokumenty i rozliczenie w jednym miejscu — dla właścicieli mieszkań w Polsce
Primary CTA Dołącz do programu pierwszych właścicieli
Secondary CTA Umów 20-minutową rozmowę
Proof block one Lease documents, handover, deposit and final settlement
Proof block two Rent schedule, reminders, proof, overdue visibility
Proof block three Ordinary vs occasional lease workflow, deadlines, document checklist

The site work should be staged, not dumped all at once:

Week Landing page and messaging task Goal
Week 1 Core homepage rewrite Clarify ICP and remove manager ambiguity
Week 2 Two wedge pages: lease ops vs compliance Find the stronger promise
Week 4 Search-intent pages Capture demand from JTBD queries
Week 6 Webinar replay page and founding-program proof Convert warm community traffic
Week 9 Case study page Improve trust and paid conversion
Week 12 Narrow launch page with testimonials and pricing Convert launch traffic efficiently

SEO and content should stay tightly attached to conversion. The first cluster should be only the topics the research repeatedly identified as both high-intent and highly relevant:

Publish order Content asset Why this comes early Conversion target
First Occasional lease starter kit High confusion, strong compliance pull, direct product fit Template lead magnet → pilot call
Second PIT-28 private rental tax guide Stable recurring search demand and owner pain Calculator / worksheet → sign-up
Third Move-in and move-out protocol checklist High operational relevance and strong product proof Checklist → trial
Fourth Deposit settlement guide Close to your settlement workflow and dispute anxiety Guide → trial
Fifth Late rent and written warning guide Strong monetizable pain; fits reminders + legal records Guide → demo
Sixth Spreadsheet / WhatsApp vs landlord system comparison Captures bottom-funnel software intent Comparison page → paid trial

Community and partnership work should also be tightly focused. The research supports landlord communities, educator brands, and ecosystem partnerships as high-trust, lower-CAC channels, but it does not support broad portal/API integration or cold social prospecting at this stage. The practical outreach sequence is:

Partner lane What to do in 90 days What success looks like
Landlord communities Secure 1–2 webinars and at least one local chapter talk 10+ qualified demos per event
Landlord educators One co-branded webinar and one newsletter or guide placement CAC below search CAC
Referral / ecosystem One partner referral page for verification, insurance, or landlord education First 3–5 partner-sourced signups
Remarketing Use only once search, content, and webinars create warm audiences Improved reactivation and lower blended CAC

What you should not do here is just as important: do not lead with “property manager software,” do not attempt a broad “all of Poland” channel mix, do not spend on cold Meta to find landlords from scratch, and do not sink the quarter into portal syndication APIs. The product should learn from intent and trust, not from artificially inflated top-of-funnel traffic. fileciteturn0file1 fileciteturn0file3 fileciteturn0file4 fileciteturn0file7

Analytics, activation, and first pilot cohort

Your north-star metric for the first 90 days should be activated units under management, not signups, installs, or website traffic. The research is very clear that the meaningful signal is a landlord who sets up real units, uploads real documents, sets a real rent schedule, and keeps using the workflow. The activation sequence should therefore remain owner-first, so value is visible before tenant participation becomes necessary. fileciteturn0file3 fileciteturn0file4

Use one operational dashboard with these definitions:

Metric Definition Day-90 target
Qualified signup share % of signups that are self-managing landlords with 2–10 units 60%+
Owner-only activation Property created + lease added + document uploaded + rent schedule set within 7 days 40%+ of qualified signups
Second meaningful action Tenant invited, handover started, or second live unit activated 25%+ of qualified signups
Activated units under management Units tied to active workflow, not placeholders 150+ is strong go signal
Paid conversion Activated ICP accounts converting to paid within 30 days of threshold 15–25%
Retention Activated ICP landlords still active after 30 / 60 / 90 days 80% / 75% / 70%+
Channel repeatability At least 2 channels produce qualified signups with acceptable CAC/payback 2 channels
Support load Founder or ops time required per activated landlord in month one Drive toward under 2 hours

Event tracking should be minimal and business-focused. Instrument these events first: qualified_signup, icp_units_selected, property_created, lease_created, document_uploaded, rent_schedule_created, payment_request_sent, payment_proof_uploaded, handover_started, handover_completed, tenant_invited, second_live_unit_activated, subscription_started, subscription_canceled, and pilot_case_study_approved. Anything beyond this can wait. fileciteturn0file3 fileciteturn0file8 fileciteturn0file9

The first pilot cohort should be deliberately small and operationally heavy-touch:

Pilot element Recommendation
Size Start with 3–5 landlords in cohort A, then expand to 12–15 total by week 11 only if support quality holds
Portfolio size Prioritize landlords with 2–5 units; allow some 6–10 unit accounts for pricing and migration learning
Cities Warsaw, Kraków, Wrocław, Trójmiasto, Poznań first
Selection criteria Must be self-managing, must have handled move-in/move-out/renewal/late-payment in the last year, must be willing to activate 2 live units, must accept a weekly check-in
Offer 90 days free, migration help, founding price lock, shared feedback loop
Expected exchange One testimonial, one quote, or one case study if activation succeeds

Pilot operations should follow a tight cadence: one onboarding session, one check-in after 7 days, one workflow review after 21 days, one pricing conversation after the second live unit, and one retention conversation before the free period ends. This is not just support; it is your primary learning engine for the first quarter. fileciteturn0file3 fileciteturn0file4

Decision gates, risks, and what not to do yet

You should make explicit go/narrow/stop decisions at day 14, day 30, day 60, and day 90. That keeps the quarter from turning into endless product motion without economic proof. The strongest thresholds already exist in the attached validation and GTM research, so the launch plan should adopt them rather than inventing softer standards. fileciteturn0file3 fileciteturn0file4

Gate Go Narrow Stop or park
Day 14 One wedge is clearly winning, 5 pilot landlords commit, 30%+ price acceptance at 29–49 PLN, landing page gets strong warm conversion Message is promising but still split between lease ops and compliance No wedge reaches clear unprompted demand, weak conversion, weak pilot pull
Day 30 40%+ owner-only activation and obvious setup value for pilots 20–39% activation but interviews strongly support one wedge Under 20% activation and no single fix keeps coming up
Day 60 8+ activated ICP landlords, early paid intent, one webinar/community channel works Pilots are active but monetization is weak or support burden is too high Pilots do not stay active and tenant or owner adoption continues to stall
Day 90 30–50 paying ICP landlords, 150+ active units, 2 repeatable channels, strong early retention 10–29 paying landlords or 50–149 active units with one clear channel and strong activation Fewer than 10 payers, weak activation, no repeatable acquisition, or value depends on building a different product

The main risks are structural, not cosmetic. The first is scope drift: MamNajem already has enough surface area to drown itself if launch work turns into new feature production. The second is legal overstatement: Polish lease, notice, signature, and occasional-lease rules require careful language and artifact handling, so the product must avoid promising that a simple in-app action automatically creates written-form or notarially sufficient outcomes. The third is payments overreach: embedded rent collection can create avoidable PSP, KYC, and platform-liability complexity long before it proves monetization value. The fourth is support load: landlord software in Poland is close to legal and operational pain, which means even good users will ask for help. The fifth is tenant-friction risk: if the owner gets value only after a tenant adopts the app, activation will slow dramatically. fileciteturn0file0 fileciteturn0file1 fileciteturn0file8 fileciteturn0file9

The right “not yet” list is therefore strict:

What not to do yet Why it should wait
Deep property-manager or team workflows The best first buyer is the self-managing owner; team/delegation complexity can become a second product
Portal syndication APIs Manual posting plus internal lead/application tracking is enough for MVP
Embedded rent collection and marketplace payouts Off-ledger payment requests prove value with less legal and operational risk
Full maintenance/vendor portal Maintenance should remain a falsification test or lightweight ticket until demand is obvious
KSeF, B2B invoicing, deep accounting integrations Useful later, not necessary to validate the first ICP
BIG/KRD screening built in-house Better as partner handoff after core workflow proves out
Docusign/Adobe-style signature platform expansion If signing becomes a blocker, Autenti is the only Poland-first integration worth testing first
Cold paid social prospecting Search, communities, educators, referrals, and remarketing have better early economics
Apple and Google in-app billing for subscriptions Margin compression is too meaningful at launch pricing

The strategic discipline for this quarter is simple: every week must either sharpen proof of demand or reduce friction in the core landlord workflow. If a task does neither, it should not make the 90-day plan. fileciteturn0file0 fileciteturn0file1 fileciteturn0file6 fileciteturn0file7 fileciteturn0file8 fileciteturn0file9