MamNajem Validation Plan for Polish Self-Managing Landlords and Tenants¶
MamNajem should not try to validate itself in Poland as a broad “all-in-one rental platform” first. Poland remains a strongly ownership-led housing market: the OECD reports that 84% of households in Poland were owner-occupiers in 2022, while 15% were renters in 2021, and it characterizes the private rental sector as relatively small and underdeveloped. At the same time, local offerings already compete around tenant screening, deposit-free protection, rent insurance, and outsourced property management rather than full-stack landlord operating systems. That combination usually favors a sharp initial wedge over a feature-complete launch. My recommended leading hypothesis is therefore: lease operations plus compliance for self-managing landlords with 2–5 units in major cities, with payments as the strongest secondary hypothesis and maintenance as a falsification test rather than the default bet. citeturn27view2turn8search4turn33view0turn32view0turn31view0
That recommendation is strengthened by three Poland-specific signals. First, the country is digitally ready for a mobile workflow: Statistics Poland reports 96.2% of households had internet access at home in 2025, 94.9% had broadband, and 88.9% of people aged 16–74 used the internet regularly; public-service usage is also mainstream, with 61.1% using e-government services and 81.8% among people aged 25–34. Separately, the Ministry of Digital Affairs said in January 2026 that the number of issued mObywatel digital IDs exceeded 11 million. Second, the legal workflow for rentals is not trivial: occasional lease in Poland requires specific documentation, tax-office notification, and special handling of deposits and notices. Third, self-managing landlords can already outsource management at fees far above typical SaaS pricing, so a software wedge only works if it removes a real recurring burden. citeturn17view0turn17view1turn18view2turn11search2turn3view2turn3view4turn3view1turn3view0turn32view0
Recommended validation thesis¶
The best two-week validation question is not “Do people like MamNajem?” It is:
Which single problem is painful enough that Polish self-managing landlords will pay for it now, tenants will actually use it when invited, and the current MamNajem scope can deliver it without building a second product?
For this market and this product description, the four wedges to test are:
| Wedge | Current prior | Why it is credible now |
|---|---|---|
| Lease operations | High | MamNajem already covers property setup, lease lifecycle, handovers, final settlement, messaging, and documents. Local competitors are stronger on risk protection and screening than on full lifecycle collaboration. |
| Compliance | High | Polish rentals have meaningful operational/legal steps around occasional lease, deposits, notices, and tax handling. |
| Payments | Medium | Poland is digitally mature and BLIK is huge, but landlords may still tolerate manual bank transfers if reminders and evidence are good enough. |
| Maintenance | Low to medium | Real pain exists, but your current product is thin here and the manager/service layer often solves it operationally rather than through software alone. |
The reason I would keep rental managers as only an optional sub-sample in this first sprint is straightforward: your current scope, as you described it, does not yet show a robust delegation, team, agency, or employee-permission model, while property managers in Poland typically cover tenant acquisition, lease signing, rent control, debt collection, repairs, utility reconciliation, deposit settlement, and legal coordination end to end. One provider explicitly describes rental management in Poland as a relatively new service that blends brokerage, ongoing management, rent control, repairs, deposit handling, and legal support. That makes managers useful as a falsification sample, but a risky initial buyer segment for the current product. citeturn31view0
If you can only test one positioning first, test this proposition:
“The mobile operating system for Polish self-managing landlords: lease documents, handovers, deposit settlement, reminders, tenant communication, and compliance in one place.”
That message matches your strongest current surface area and fits the local context better than a maintenance-first or manager-first story. It also avoids fighting local competitors head-on on deposit replacement or tenant verification alone. Rendin markets a 2.5% of monthly rent fee for digital agreements plus protection and handover; simpl.rent markets tenant verification from 159 PLN gross, rent-payment insurance, and occasional-lease support. Those categories are already legible in Poland, which is useful, but it also means MamNajem should not initially present itself as “yet another protection tool.” citeturn8search4turn8search11turn33view0
Poland market context and hypotheses¶
Poland’s rental market is important, but it is not a market where a broad software promise automatically wins. The OECD’s 2025 housing review says Poland’s rental market remains relatively small, with most households owning their dwellings and the rental sector appearing to shrink between 2011 and 2021. It also notes that real house prices and rents have increased sharply since 2013. Eurostat’s latest housing article adds that Poland had an overcrowding rate of 33.7% in 2024, among the highest in the EU, even while only 3.3% of people reported being unable to keep their home adequately warm. In practice, that suggests tenant pain is often tied to space, affordability, clarity of charges, and trust, not just to “smart home” or administrative convenience. citeturn27view2turn28view0
At the same time, Poland is digitally ready for a mobile-first workflow. Statistics Poland shows extremely high household connectivity and broad internet use, while government digital services are already normalized, especially for adults in prime renting age. That matters because it lowers adoption risk for document vaults, notifications, task reminders, push alerts, digital confirmations, and identity-adjacent workflows. It does not prove willingness to pay, but it does reduce one of the biggest excuses founders often hear: “our market is not ready to do this on mobile.” citeturn17view0turn17view1turn18view2turn11search2
Payments deserve testing, but not blind faith. BLIK reported 2.9 billion transactions worth PLN 441.5 billion in 2025, which confirms that digital payments are mainstream in Poland. But the crucial validation question is narrower: do small self-managing landlords want rent collection automation enough to change habit and pay for it, or do they merely want faster reminders, payment proof, and reconciled records? In other words, don’t validate “payments” as a technology feature. Validate chasing late rent, payment visibility, proof, and reconciliation pain. citeturn0search10turn0search18
Compliance may be more powerful than it looks. Polish law creates a real operational burden around rentals. For occasional lease, the law defines it as a residential lease by a natural person not conducting rental business, for a fixed term of up to 10 years, and requires attachments including a notarial declaration by the tenant and an indication of an alternative place to live in case of enforcement. The owner must notify the tax office within 14 days from the start of the lease. The security deposit for occasional lease cannot exceed six times monthly rent, and deposits are generally returned within one month after vacating, net of valid deductions. For ordinary rent increases under the tenant-protection act, the notice period is generally three months and must be in writing; for occasional lease, rent increases are only allowed on terms set in the contract. The Ministry of Finance’s 2024 lump-sum tax information also reports 85,041 notifications of occasional-lease contracts in 2024. All of that is exactly the kind of recurring, failure-prone workflow that a landlord ops product can simplify. citeturn3view2turn3view4turn3view1turn3view0turn22search5
Pricing context also matters. Full rental management in Poland is marketed at levels far above what a lightweight landlord SaaS can charge: one Polish property-management provider states that management fees generally range from 8% to 15% of monthly net rent, and gives an example of roughly 180–250 PLN gross per month for a 45 m² apartment in a large city. By comparison, existing “risk” products sit much lower on the ladder: Rendin’s fee is 2.5% of monthly rent with a 25 PLN minimum, and simpl.rent markets entry tenant verification at 159 PLN gross. These are not perfect benchmarks, but they provide a sensible pricing corridor: a self-managing landlord SaaS can plausibly test 19–79 PLN per month without looking absurdly expensive, provided it solves a recurring burden. citeturn32view0turn8search4turn33view0
Two-week fieldwork plan¶
The two-week sprint should combine problem interviews, a branching survey, four landing-page smoke tests, and a lightweight price experiment. The goal is not statistical certainty. The goal is to emerge with enough evidence to answer five questions:
- Which wedge creates the strongest pull?
- Who is the real buyer?
- Which minimum feature set earns a pilot?
- What price feels credible and survives contact with real prospects?
- Should you narrow, proceed, or stop?
Recruiting channels¶
Use channels that already aggregate Polish landlords and renters rather than trying to invent a panel from scratch. For landlords, the strongest practical channel is Mieszkanicznik, which describes itself as a nationwide association supporting rental-property owners and says its community includes 22,000+ members, supporters, and friends across 22 branches. For listings-based outreach, Otodom says it is the most popular real-estate platform in Poland according to Mediapanel Gemius, and OLX has a large active rental category that is easy to scrape manually for direct outreach and clearly includes current apartment rental listings. Since interview incentives in Poland can be paid easily through local digital channels, I would pay all incentives via BLIK. citeturn29view0turn24search11turn21search2turn21search11turn0search10
I would recruit as follows:
| Audience | Minimum completes | Stretch target | Best channels | Incentive |
|---|---|---|---|---|
| Self-managing landlords with 1–10 units | 12 interviews | 15 interviews | Mieszkanicznik branches/newsletters, direct outreach to Otodom/OLX landlords, founder referrals | 150 PLN |
| Tenants in long-term rentals | 10 interviews | 12 interviews | Referrals from interviewed landlords, city rental communities, warm network introductions | 80 PLN |
| Small rental managers | 3 interviews | 5 interviews | Manager associations, property-management firms, referrals | 200 PLN |
| Landlord survey completes | 80 | 120 | Same channels plus landing pages | none |
| Tenant survey completes | 120 | 180 | Same channels plus landing pages | none |
The landlord interview sample should be balanced on purpose, not left to chance. I would target roughly 4–5 owners with one unit, 5–6 with two to five units, and 3–4 with six to ten units. At least half should have had a move-in, move-out, lease renewal, deposit settlement, or late-payment episode in the last twelve months, because stale memory destroys interview quality. For tenants, oversample people who moved within the last twelve months or experienced a deposit, repair, or payment clarity issue, because they will remember details. Managers are optional and should be treated as a stress test rather than a core audience in week one.
Daily cadence¶
| Day cluster | What happens | Output |
|---|---|---|
| Early week one | Finalize screener, interview guides, survey, landing pages, ad copy, and scoring sheet. Recruit first wave. | Ready-to-run instruments |
| Mid week one | Run 5–6 landlord interviews and 4–5 tenant interviews. Launch survey and smoke tests. Nightly synthesis after every 3 interviews. | Early pain-pattern map |
| End of week one | Review transcripts and adjust probes. Kill obviously weak ad copy. Keep only the two strongest value props if needed. | Sharper hypothesis |
| Early week two | Run remaining landlord and tenant interviews. Add 3–5 manager interviews only if capacity allows. Launch price test on winning page(s). | Wedge comparison |
| Mid week two | Close survey, analyze pricing sensitivity, rank problems, identify pilot candidates. | Draft decision memo |
| End of week two | Make go / narrow / no-go call. Select MVP wedge, pilot cohort, and first price point. | Decision and next build brief |
Success targets for the sprint¶
The two-week sprint is successful if, by the final day, you have:
- at least 12 good landlord interviews and 10 good tenant interviews;
- at least 80 landlord surveys and 120 tenant surveys;
- at least 400 qualified landing-page visits across variants;
- at least 5 landlords willing to join a pilot within 30 days;
- one clearly winning wedge in both qualitative and quantitative evidence.
If you finish the period with “interesting conversations” but no clear leading wedge, the sprint has not succeeded, even if people were polite and liked the product idea.
Landlord interview script¶
The landlord interview should be behavior-first, not feature-first. The moderator should insist on the last real example, not general opinions. Start by saying:
“I’m not here to pitch software. I want to understand how you actually handled your last tenant, lease, payment issue, handover, or settlement. I’ll ask for specific recent examples.”
Use the following guide.
| Section | Core question | Good probes | What to score |
|---|---|---|---|
| Screening | “How many rental units do you personally self-manage today?” | Whole flats vs rooms, city, lease length, whether they use an agency at all | ICP fit |
| Recent episode | “Tell me about the last time you onboarded, renewed, or ended a lease.” | When was it, what triggered it, what documents changed hands | Freshness and recency |
| Workflow reconstruction | “Walk me through the process from candidate accepted to the first settled month.” | Listing, verification, lease drafting, handover, photos, deposit, reminders, receipts | Operational complexity |
| Tool stack | “Which tools did you use at each step?” | WhatsApp, phone, e-mail, paper, notes, Excel, Google Drive, accounting software, agency, lawyer | Fragmentation |
| Biggest friction | “Where did you lose time or feel uncertainty?” | Chasing signatures, unclear fees, handover evidence, reminders, deposit deductions, renewals | Pain severity |
| Compliance | “Do you use ordinary lease or occasional lease? Why?” | Notary step, tax-office notification, clauses, rent increases, deposit return timing, disputes | Compliance pain |
| Payment handling | “How do tenants pay you today, and what happens when payment is late or partial?” | Reminders, whether proof is shared, who tracks utilities and receipts, how long follow-up takes | Payment pain |
| Maintenance | “What happened the last time the tenant reported a repair or defect?” | Photos, responsibility, vendor coordination, evidence, response time, settlement disputes | Maintenance pain |
| Current spend | “What do you currently pay for to reduce work or risk?” | Agency fees, screening, legal templates, insurance, deposit alternatives, admin help | Existing budget |
| Alternatives | “Why haven’t you already solved this with another tool or service?” | Distrust, habit, complexity, poor fit, too expensive, tenant adoption risk | Switching barriers |
| Solution reaction | “If a mobile tool handled lease docs, handovers, reminders, messages, and settlement in one place, where would it help most and where would it fail?” | Ask them to rank lease ops, compliance, payments, maintenance | Wedge preference |
| Price and commitment | “Would you try this at 29 / 39 / 79 PLN per month depending on size? What would feel too cheap, fair, and too expensive?” | Ask for willingness to pilot, import one live lease, and invite one tenant | WTP and commitment |
Moderator notes for landlords¶
Do not ask “Would you use this?” until at least two thirds of the interview has been spent on actual behavior. If the interviewee says a problem is “annoying,” force them into specifics:
- “How often did that happen in the last year?”
- “How much time did you spend?”
- “Did it cost you money?”
- “What was the last message or document you had to chase?”
- “Would you pay to prevent that next month, or only in theory?”
The strongest positive signal is not enthusiastic language. It is a landlord who says some combination of:
- “I already pay for part of this.”
- “This happens every lease.”
- “I would move one active lease into a pilot.”
- “I would invite my current tenant.”
- “This would save me legal/admin stress.”
Tenant interview script¶
Tenants are not the primary economic buyer in this first sprint, but they are critical because landlord software fails when the tenant side feels confusing, intrusive, or low-value. Start by saying:
“I’m not evaluating you and I’m not working for your landlord. I want to understand how communication, payments, move-in, repairs, and deposits actually work in your rental.”
Use the following guide.
| Section | Core question | Good probes | What to score |
|---|---|---|---|
| Screening | “What kind of rental are you in now?” | Whole apartment vs room, direct owner vs agency, how long they have stayed | Fit |
| Recent move | “Tell me about your last move-in or move-out.” | Contract, handover protocol, photos, inventory list, deposit, what felt unclear | Lease-op experience |
| Communication | “How do you normally communicate with the owner or manager?” | WhatsApp, SMS, phone, email, apps, response times | Channel fit |
| Payment flow | “How do you pay rent and utilities, and how do you know everything is correct?” | Due dates, reminders, proof of payment, utility split, confusion around charges | Payment clarity |
| Repair flow | “Tell me about the last repair or problem in the apartment.” | How it was reported, photos, who paid, how fast it was resolved | Maintenance pain |
| Trust and evidence | “If there is a disagreement about the flat, what evidence do you have?” | Move-in photos, chat messages, protocol, bank transfers, invoices | Documentation pain |
| Legal clarity | “What parts of renting in Poland felt hardest to understand?” | Deposit return, notice periods, charges, occasional lease, responsibilities | Compliance anxiety |
| Landlord-invited app | “If your landlord invited you to an app for documents, payments, issue reporting, and move-in/out records, what would you actually use?” | What would be helpful vs redundant | Adoption signal |
| Privacy and friction | “What would make you reject such an app?” | Too much document sharing, unclear data use, extra fees, bad UX, duplicate data entry | Adoption risk |
| Willingness to pay | “Would you pay anything for convenience, or should the landlord always pay?” | One-off payment fee, optional premium, deposit alternative, insurance | Secondary monetization |
| Must-have ranking | “Pick the top two: payment reminders and receipts, issue reporting with photos, move-in/out protocol, document vault, deposit settlement transparency, clear utility charges.” | Force a choice | Value hierarchy |
Moderator notes for tenants¶
The tenant interview should answer three things:
- which problems tenants notice without prompting;
- whether the tenant will use a landlord-invited app if it makes their life easier;
- whether the tenant perceives the product as a tool for transparency or a tool for landlord control.
That third point matters. Tenants will accept more process if they get something tangible back, such as:
- one place for the contract and annexes;
- clear due dates and rent proof;
- transparent handover photos and inventory;
- repair tickets with timestamps;
- explicit deposit deductions and deadlines.
If the tenant interviews repeatedly produce reactions like “this sounds like surveillance” or “I’d still rather use WhatsApp,” that means the tenant-facing surface should stay minimal in the MVP.
Survey, landing-page smoke tests, and pricing¶
Survey questions¶
Run one branching survey in Polish. Keep it to 7–9 minutes. The survey should not be a giant feature checklist. It should force priority.
Use this common opening block for everyone:
| Question | Format |
|---|---|
| Which of these best describes you? | Landlord / Tenant / Rental manager |
| Which city or metro area are you in? | Multiple choice + Other |
| Have you rented out or lived in a long-term rental in the last 12 months? | Yes / No |
| Would you be willing to join a follow-up interview? | Yes / No |
| What is your age band? | Range |
| Which language do you prefer for rental communication? | Polish / English / Both |
For landlords, use these questions:
| Question | Format |
|---|---|
| How many units do you personally self-manage? | 1 / 2–3 / 4–5 / 6–10 / 10+ |
| In the last 12 months, how many move-ins, move-outs, or renewals did you handle? | 0 / 1 / 2 / 3+ |
| Which three tasks take the most effort? | Choose up to 3 from lease docs, handover, reminders, payments, repairs, deposit settlement, utilities, tax/compliance, tenant communication |
| Which one caused the biggest recent problem? | Single choice |
| How often have you had late or partial payments in the last 12 months? | Never / 1–2 times / 3–5 times / 6+ times |
| Which lease type do you use most often? | Ordinary / Occasional / Mix / Not sure |
| What tools do you currently use? | Multi-select |
| Roughly how much time per month do you spend on rental admin? | 0–1 h / 2–4 h / 5–9 h / 10+ h |
| What have you paid for in the last 12 months? | Screening / legal docs / agency / insurance / software / none |
| Which value proposition is strongest? | Lease operations / Compliance / Payments / Maintenance |
| At what monthly price would this feel too cheap to trust, fair, and too expensive? | Van Westendorp-style three fields |
| Would you join a pilot in the next 30 days if the product solved your top problem? | Yes immediately / Maybe / No |
For tenants, use these questions:
| Question | Format |
|---|---|
| What do you rent today? | Room / Studio / Apartment / House |
| Who is your contract with? | Direct owner / Agency / Manager / Not sure |
| Which recent issue was most frustrating? | Unclear charges / Deposit / Repairs / Documents / Late response / None |
| How do you communicate most of the time? | WhatsApp / SMS / Phone / Email / App |
| How do you pay rent most of the time? | Bank transfer / Card / Cash / Other |
| Which two things would make renting feel easier? | Pick 2 from repairs with photos, clear charges, payment reminders, document vault, handover protocol, deposit transparency |
| Would you use an app if your landlord invited you and it improved transparency? | Definitely / Probably / Maybe / No |
| What would make you reject it? | Open text |
| Would you pay anything yourself for convenience? | No / One-time only / Small monthly fee / Fee per payment |
| If yes, what feels acceptable? | 0–5 PLN / 6–10 PLN / 11–20 PLN / 20+ PLN |
Landing-page smoke test variants¶
All pages should be in Polish first, even though the research summary is in English. The pages should use plain local terms such as najem okazjonalny, protokół zdawczo-odbiorczy, kaucja, rozliczenie, and czynsz, because those are the real words people use in this market and in related products. Polish legal and tax rules make those terms meaningful, not cosmetic. citeturn3view2turn3view4turn3view1turn22search0
Use four variants with the same structure: headline, short explainer, three proof bullets, pricing teaser, qualification form, and CTA. The CTA should be “Join the pilot” or “Book an early-access call”, not plain “Learn more.”
| Variant | Headline | Promise | Best audience signal to watch |
|---|---|---|---|
| Lease operations | Run every lease in one place | Lease docs, move-in/out protocols, final settlement, messages, reminders, tenant collaboration | Do landlords see this as their day-to-day operating pain? |
| Compliance | Stay compliant with Polish rental rules | Occasional lease workflow, document checklist, deposit timing, rent-change records, audit trail | Do legal/admin fears drive urgency? |
| Payments | Make rent collection visible and on time | Due dates, reminders, proof, receipts, rent status, late-payment follow-up | Is the real pain collection or only reminders/evidence? |
| Maintenance | Handle repairs without WhatsApp chaos | Issue tickets, photos, status updates, responsibility tracking, repair history | Do both landlords and tenants rank this above docs/payments? |
Each page should ask only five qualifying fields:
- Are you a landlord, tenant, or manager?
- If landlord, how many units do you self-manage?
- City
- Did you handle a move-in, move-out, repair issue, or late payment in the last year?
- Would you be open to a paid pilot if this solved the problem?
The metric that matters is qualified conversion, not raw email capture. A student browsing housing content is noise; a landlord with 3 units who had a deposit dispute last quarter is a signal.
Traffic plan¶
Use a mix of:
- Warm/direct traffic from founder outreach, Mieszkanicznik, and referrals.
- Search traffic for high-intent phrases like occasional lease, handover protocol, deposit settlement, late rent, and landlord app.
- Paid social targeted by role proxies and city.
I would not overcomplicate attribution in this sprint. The one thing to hold constant is that each visitor should see only one primary wedge. Do not blend lease ops and maintenance on the same page in week one.
Pricing test¶
Use a two-stage pricing validation around the decided pilot ladder.
First, in the survey, run a Gabor-Granger style price question for landlords. Randomize one of these monthly price points for the primary wedge:
- 19.99 PLN
- 49.99 PLN
- 99.99 PLN
Ask: “If this product solved your top rental-admin problem, would you buy it at [price] per month?” Response options: definitely yes / probably yes / probably not / definitely not.
Second, on the winning landing-page variant from week one, validate the public pilot anchor with visible prices:
- From 19.99 PLN/month
- Portfolio at 49.99 PLN/month
- Plus at 99.99 PLN/month
The reason to start there is practical. Agency management is priced far above that, while Polish risk tools already sell into the market at much smaller but real amounts, such as Rendin’s 2.5% of rent model and simpl.rent’s 159 PLN one-off verification. A 19.99–49.99 PLN core monthly anchor is therefore high enough to test seriousness but low enough not to look detached from local alternatives, while 99.99 PLN tests the upper portfolio/support tier. citeturn32view0turn8search4turn33view0
My default interpretation would be:
- if 49.99 PLN converts within 80% of 19.99 PLN on qualified leads, keep Portfolio as the main money plan;
- if price resistance spikes above 49.99 PLN but demand is real, keep 99.99 PLN as a narrower Plus/support tier rather than lowering Portfolio;
- do not rely on tenant subscription revenue in this first decision round unless tenant interviews show strong willingness to pay for an optional convenience or insurance layer.
Scoring rubric, go-no-go criteria, and wedge evidence¶
Respondent scoring rubric¶
Score every landlord interview immediately after the call. Use a simple weighted score rather than vibes.
| Dimension | Scale | Weight |
|---|---|---|
| Pain frequency | 0–4 | 20% |
| Pain severity or money/time loss | 0–4 | 20% |
| Workflow fragmentation | 0–4 | 15% |
| Evidence of existing workaround or spend | 0–4 | 15% |
| Urgency / triggering event in last 12 months | 0–4 | 10% |
| Willingness to pay | 0–4 | 10% |
| Commitment to pilot | 0–4 | 10% |
Interpretation:
- 3.2+ average on a theme is strong.
- 2.5–3.1 is interesting but not yet decisive.
- Below 2.5 is weak.
- A “great conversation” without current pain, current spend, or willingness to pilot is still a low score.
For tenants, use a lighter version of the same model, but replace willingness to pay with adoption willingness and trust.
Go, narrow, or no-go criteria¶
MamNajem should get a go on a wedge if all of the following are true:
| Criterion | Threshold |
|---|---|
| Completed landlord interviews | At least 12 target interviews |
| Dominant pain | One wedge is mentioned unprompted by 60%+ of landlords |
| Tenant validation | Where relevant, 40%+ of tenants rank the same wedge in their top two pains |
| Landing-page signal | Winning variant gets 8%+ qualified conversion from mixed traffic, or 15%+ from warm traffic |
| Price acceptance | At least 30% of target landlords answer definitely/probably yes at 19.99–49.99 PLN/month |
| Pilot demand | At least 5 landlords commit to a live pilot within 30 days |
| Product fit | The wedge can be delivered without building a new manager/team product |
You should narrow rather than fully go if demand is clear but the product promise is too broad. Example: users love lease ops and compliance, but do not care yet about chat threads, subscription plans, or payment rails. In that case, narrow hard.
You should issue a no-go for the current wedge if any of the following happens:
| Red flag | Meaning |
|---|---|
| No wedge reaches 40% unprompted mentions | The market sees the product as a bundle, not a solution |
| Highest landing-page conversion stays below 4% after meaningful traffic | Messaging is weak or pain is insufficient |
| Fewer than 20% of target landlords accept even low pricing | Nice-to-have, not must-have |
| Tenants consistently reject landlord-invited workflow | Adoption friction too high |
| Managers want permissions, reporting, and team flows you do not have | Wrong first buyer segment |
Evidence that proves the right focus¶
This is the part that should directly drive product strategy.
| Focus | Evidence that proves it should lead | Evidence that disproves it |
|---|---|---|
| Lease operations | Landlords repeatedly describe chaos around contracts, handovers, annexes, renewals, deposit settlement, and document chasing; the lease-ops landing page wins by at least 1.5x over the next best; landlords agree to import a live lease into a pilot | Users say docs are easy enough already, or they only care when a rare dispute happens |
| Maintenance | Both landlords and tenants spontaneously rank repairs/issues in their top two pains; tenants describe repeated uncertainty about responsibility and response times; the maintenance page converts near or above lease ops; landlords want photo evidence and status tracking now | Repairs are infrequent, solved via phone/WhatsApp, or not painful enough to pay for |
| Payments | Landlords mention chasing late rent, unclear proof, partial payments, utilities reconciliation, and month-end admin without prompting; payment page converts strongly; landlords say they would adopt even without a full lease workflow | Most landlords say bank transfer plus manual reminders is “good enough”; demand is for reminders and receipts, not collection rails |
| Compliance | Landlords bring up occasional lease, notices, deposit rules, tax-office steps, or fear of mistakes early in the interview; compliance page performs best on intent-rich search traffic; willingness to pay remains solid even when framed as “avoid admin/legal errors” rather than “automation” | Compliance is seen as a once-a-year or lawyer-only task, not a recurring workflow |
My current pre-research prior is that lease operations and compliance will likely merge into one winning wedge. That is because Polish law creates real recurring admin steps, your product already covers much of the lease lifecycle, and current Polish competitors more visibly emphasize protection, verification, and insurance than an integrated landlord operations workflow. Payments could still win if late-rent chasing is far more painful than the current product brief suggests. Maintenance should only become the lead wedge if interviews strongly contradict the product’s present shape. citeturn3view2turn3view4turn3view1turn22search5turn8search4turn33view0turn31view0
Expected decisions at the end of two weeks¶
If the sprint is run well, you should be able to make these practical decisions immediately:
| Decision | What you should know by day fourteen |
|---|---|
| Primary buyer | Most likely self-managing landlord, not tenant, not manager |
| Primary wedge | Lease ops, maintenance, payments, or compliance |
| MVP scope | The 3–5 flows needed for the pilot |
| Tenant role | Required participant in workflow vs passive recipient |
| Initial price | Whether 19.99 PLN Solo, 49.99 PLN Portfolio, and 99.99 PLN Plus are credible |
| Segment cut | Whether to postpone managers, advanced payments, or maintenance |
| Positioning | “Operate every lease” vs “stay compliant” vs “collect rent” vs “manage repairs” |
If the evidence is mixed, the correct outcome is not “build everything and see.” The correct outcome is narrower positioning and a smaller MVP. For the product you described, that would most likely mean launching with lease documents, handovers, deposit settlement, reminders, tenant communication, and compliance records, while treating deep payments, manager tooling, and maintenance workflow as follow-on bets.