MamNajem Poland Launch Validation Pack¶
Validation thesis¶
The attached research converges on the same first paid wedge: self-managing Polish landlords with 2–10 units, with the densest early opportunity in major cities and the strongest initial economics in the 2–5 unit range. The same research also argues that one-unit owners are useful top-of-funnel but are less dependable as the paid core, which is why the validation pack below is built to learn from the right landlords rather than maximize response volume. fileciteturn0file1 fileciteturn0file4
The most credible launch promise is not “property management software.” It is a mobile-first lease operations product for real leases: payment follow-up, handovers, documents, tenant communication, and final settlement. At the same time, your attached reports flag two important constraints for validation. The first is that maintenance/issues are likely to be a real expectation gap unless you prove a minimum useful workflow. The second is that you should not over-promise digital signing: under eIDAS, electronic signatures cannot be denied legal effect solely because they are electronic, but only a qualified electronic signature has the equivalent legal effect of a handwritten signature, and the Polish government explicitly states that the trusted signature is not equivalent to a handwritten signature for private matters such as contracts or annexes with private persons or companies. That means your pilot should be honest about which lease and notice flows are in-product versus hybrid. fileciteturn0file6 fileciteturn0file8 fileciteturn0file9 fileciteturn0file0 citeturn9view4turn10view0
The operating rule for this validation is simple: reward evidence, not enthusiasm. “Sounds useful” is weak. “Show me the last handover protocol, rent reminder, bank transfer proof, deposit settlement, or repair thread” is stronger. “I will move one live lease into the product this month” is stronger still. “I will sign a pilot agreement or leave a refundable deposit at a tested price” is strongest.
| Validation stage | Recommended sample | What you are really testing | Minimum proof you want |
|---|---|---|---|
| Discovery interviews with landlords | 18–24 | Whether the target ICP actually experiences recurring operational pain across the workflows you named | Live walkthrough of recent artifacts: lease doc, handover photos, payment tracker, tenant chat, deposit calculation, repair thread |
| Discovery interviews with tenants | 8–12 | Whether tenant-side collaboration is a real adoption lever or just a nice-to-have | Screenshots of payment proof, move-in docs, issue reporting, deposit discussion |
| Behavioural survey | 75–150 qualified landlords | Frequency, recency, and relative importance of the target workflows | Recent activity counts, current tools, current spend, willingness to join a live pilot |
| Fake-door pricing and landing-page tests | 2–3 landing pages, 200+ qualified visits each if possible | Message-market fit and price acceptance | Real CTA conversion to “book portfolio review,” “apply for founding pilot,” or “move one real lease” |
| Founding pilot | 8–12 landlords, roughly 20–40 live units | Whether landlords will run real operations inside the product, not just explore it | One real lease imported, tenant invited, at least three target workflows completed in-product |
Recruitment and screening¶
The screening logic should follow the product and market reality in your attached reports: recruit private self-managing landlords, not agencies, not PRS, not short-term hosts, and not people who have already outsourced the work you want to validate. The goal is to speak to landlords who still run the rental business themselves through a messy stack of spreadsheets, chats, folders, bank apps, and ad hoc processes. That is exactly the segment your GTM, pricing, and market research identify as the sharpest first buyer. fileciteturn0file4 fileciteturn0file3 fileciteturn0file9
| Dimension | Must-have | Prioritize | Exclude |
|---|---|---|---|
| Portfolio size | 2–10 long-term residential units in Poland | Balanced mix of 2–3, 4–5, and 6–10 units | 1-unit accidental landlords as the majority of sample; 11+ unless you want edge cases |
| Management style | Personally handles tenant communication and at least three of: lease docs, handovers, payment tracking, reminders, deposit settlement, repairs | No outsourced manager; maybe accountant for taxes only | Agencies, delegated managers, co-living operators with staff, PRS |
| Rental type | Long-term residential leases | Mostly whole-flat rentals; a smaller quota for room-by-room if relevant | Short-term/Airbnb-only, holiday rentals, commercial-only |
| Geography | Poland | Priority cities: Warsaw, Kraków, Wrocław, Trójmiasto, Poznań | None needed, but do not over-index on small towns in wave one |
| Workflow recency | At least one active tenancy right now | At least one move-in, move-out, renewal, or deposit settlement in the last 12 months; at least one late payment or maintenance issue in the last 6 months | “I have tenants but nothing really happened recently” |
| Tools today | Uses at least two manual tools | Spreadsheet + bank app + chat/email/folders is ideal | Heavy happy users of mature landlord software unless you deliberately want 20% switcher interviews |
| Decision authority | Can decide whether to try software and move a real lease | Sole owner or clear decision-maker in a family-held portfolio | People who need third-party approval to pilot |
| Evidence willingness | Ready to show real documents or screenshots in interview | Comfortable screen-sharing files, payment reminders, chats, handover photos | Refuses to show any artifacts |
| Pilot readiness | Open to moving one live lease or workflow into a pilot within 30 days | Has an upcoming move-in/out, renewal, or active reminder/issue to run | “Happy to chat, not willing to pilot anything real” |
Use a simple scoring rule when recruiting. Give 2 points each for: 2–10 units, self-managing, active leases today, recent move-in/out, recent late payment, recent maintenance issue, uses manual tools, can show artifacts, can decide alone, willing to pilot a real lease. Prioritize anyone scoring 14+ out of 20.
Use quotas, not just a minimum count. A good starting mix is 6–8 owners with 2–3 units, 6–8 with 4–5 units, and 6–8 with 6–10 units. Ensure at least 6 of them have completed a deposit settlement in the last year, at least 6 have dealt with a late payment in the last six months, and at least 6 have handled a repair or issue in the last six months. That way every critical workflow gets tested with real recency, not vague recall.
Pay for participation if you can. Otherwise, you will over-sample hobby landlords, unusually chatty users, and people who like proptech more than they need it. A practical structure is a cash honorarium for interviews, then a stronger migration/help incentive for pilot users rather than a larger cash amount.
Landlord interview script¶
This interview should be behaviour-first and artifact-first. Send a prep note in advance asking the landlord to have ready: the last lease they started or renewed, the last handover they handled, the last rent reminder or payment-tracking file they used, the last deposit settlement they completed, and the last issue/repair they coordinated. If they cannot show any of those, that is already signal.
| Interview block | Exact prompt | Proof to request | What counts as strong signal |
|---|---|---|---|
| Portfolio context | “Tell me what you personally manage today: number of units, cities, lease types, and what you still do yourself.” | None yet; just verify fit | They clearly own the workflows and can answer without hesitation |
| Last 30–90 days reconstruction | “Open your calendar, messages, or notes and walk me through the last 30–90 days of rental admin work you personally did.” | Calendar, WhatsApp, email, notes, spreadsheet | They can reconstruct recent work from real artifacts, not memory alone |
| Lease operations | “Show me the last lease or annex you prepared. Start from the moment you decided to rent to this tenant. Where did the text come from? What did you copy? What did you check? What took time?” | Lease file, template folder, email chain, contract notes | Manual copying, uncertainty around lease type, multiple tools, worry about formalities |
| Real lease migration test | “If we asked you to move one live lease into MamNajem in the next two weeks, which lease would it be and why that one?” | Lease list or active-tenancy view they already use | They can name a specific lease immediately |
| Handover | “Please show me the last move-in or move-out. How did you document condition, meter readings, keys, and photos? How did the tenant confirm it?” | Protocol, photo album, PDF, note, chat acknowledgment | Scattered photos, no standard template, awkward signatures, no easy retrieval later |
| Deposit settlement | “Show me the last time you returned or deducted from a deposit. How did you decide the amount? Where did you store the evidence? How did you explain it to the tenant?” | Calculation sheet, message thread, invoice, photo proof | Delay, disagreement, unclear evidence bundle, lots of manual cross-checking |
| Rent reminders and payment tracking | “Open the exact place where you know who has paid and who has not. Show me the last late payment and the reminder you sent.” | Bank app, spreadsheet, reminder message, screenshot | Manual reconciliation, reminder sent ad hoc, no clean status, fear of forgetting |
| Tenant communication | “Where do tenant conversations happen today? Show me one normal operational thread and one difficult thread.” | WhatsApp, SMS, email, Messenger | Communication split across channels; documents and decisions lost in chat |
| Maintenance or issues | “Walk me through the last repair or issue from first report to resolution. Who reported it? How did you decide responsibility? How did you schedule access? How did you prove it was done?” | Messages, photos, invoice, building-admin chat, call notes | No structured intake, unclear responsibility, poor timeline, trouble linking cost to tenant or deposit |
| Current spend and workaround cost | “What do you already pay for software, accountants, managers, screening, or admin help? If not money, how much time do you personally lose each month?” | Invoices if handy, remembered monthly costs | They already spend money or high-value founder time solving fragments of the problem |
| Price test | “Imagine the last lease you just showed me had been run in one place: lease record, handover, rent reminders, tenant chat, issue timeline, and final settlement. For your current portfolio, would you start next month at [tested price]?” | None | Clear yes/no tied to current portfolio, not abstract ‘maybe’ |
| Commitment test | “Would you join a 90-day pilot and move one real lease or one real move-in/move-out into the product? What would block that?” | Willingness to schedule onboarding then and there | The strongest signal is a concrete lease, concrete date, and concrete blocker list |
Two rules matter during the interview.
First, always ask for the last actual example. Not “how do you usually do handovers?” but “show me the last one.” Not “would reminders help?” but “show me the last late payment.” Not “is maintenance annoying?” but “open the last issue.”
Second, do not pitch features until the end. If you show the product too early, the landlord starts reacting to your framing instead of their own operating reality.
Tenant interview script¶
Tenants are not the economic buyer, but they are a critical adoption gate for handovers, payment proof, communication, issue reporting, and fair deposit closeout. The tenant interview should verify whether the landlord can reliably get tenants to complete the actions MamNajem needs, and whether the product solves enough friction from the tenant side to avoid becoming “just another app the landlord asked me to install.” Your attached product and maintenance research both imply that tenant-side value is strongest when it is tied to concrete tasks, not generic messaging. fileciteturn0file6 fileciteturn0file9
| Interview block | Exact prompt | Proof to request | What counts as strong signal |
|---|---|---|---|
| Rental context | “Tell me about your current or most recent rental in Poland. Was it long-term? How long did you stay? Did you deal directly with the owner?” | None | Direct landlord relationship, recent experience |
| Move-in and documents | “Show me the last move-in materials you received: contract, handover, house rules, meter readings, inventory, any annexes.” | Email, PDF, photos, chat | Documents scattered across email/chat/folders; no clear single source |
| Payment proof | “How do you know what to pay, when to pay, and that the landlord recognized your payment?” | Bank transfer, reminder, receipt, screenshot | Tenants saving screenshots manually; uncertainty whether owner saw payment |
| Communication | “Show me one normal thread with your landlord and one thread where something was confusing or stressful.” | Chat or email | Lost decisions, poor searchability, attachments mixed into chat history |
| Issues and repairs | “Have you reported any issue or repair? Walk me through the last one from first message to closure.” | Thread, photos, invoice or update messages | No dedicated place to report, no status, no proof of what was agreed |
| Move-out and deposit | “If you have moved out before, show me how deposit return or deductions were explained to you.” | Message thread, settlement note, photos | Little documentation, weak comparison to move-in, distrust around deductions |
| App adoption test | “If your landlord asked you to use one app for lease docs, handover, payments, issue reporting, and final settlement, which parts would you actually use and which would you ignore?” | None | Concrete willingness tied to tasks, not generic positivity |
| Pilot task | “Would you be willing to try one real workflow in a pilot, such as a handover confirmation, payment-proof upload, issue report, or deposit statement acknowledgment?” | None | Ready to do a real task, especially if landlord is already in pilot |
The ideal tenant sample is a mix of: tenants referred by pilot landlords, tenants who recently moved in or out, and tenants who recently had an issue or deposit discussion. Do not rely only on tenants handpicked by highly organized landlords; add a few independent tenants from major-city rental communities so you can hear where the default landlord workflow is actually breaking.
Survey and pricing tests¶
Use the survey after the first landlord interviews, not before. The goal is not discovery by spreadsheet. The goal is to size and rank the patterns you already saw in the interviews. Use the survey to measure frequency, recency, current tools, current spend, and pilot willingness. Use pricing tests to measure real purchase intent for the actual portfolio, not abstract “willingness to pay.” Your attached pricing and GTM research both support testing a small fixed subscription and explicitly advise against beginning with percentage-of-rent pricing. fileciteturn0file3 fileciteturn0file4
| Question | Recommended answer format | Why this matters |
|---|---|---|
| How many long-term residential units do you personally manage in Poland today? | 1 / 2–3 / 4–5 / 6–10 / 11+ | Primary segmentation |
| In which city or cities are most of those units? | Multiple choice + other | City density and launch focus |
| Which of these do you personally handle today? lease documents, handovers, rent reminders, payment tracking, tenant communication, repairs/issues, deposit settlement | Multi-select | Confirms self-managing behaviour |
| How many active leases do you have right now? | Numeric band | Verifies operational load |
| In the last 12 months, how many move-ins did you personally handle? | 0 / 1 / 2 / 3–5 / 6+ | Measures handover frequency |
| In the last 12 months, how many move-outs and deposit settlements did you personally handle? | 0 / 1 / 2 / 3–5 / 6+ | Measures closeout frequency |
| In the last 3 months, how many tenants paid late? | 0 / 1 / 2 / 3+ | Measures payment-friction frequency |
| Which tools did you use the last time you handled a late payment? | Spreadsheet / bank app / email / WhatsApp / paper / landlord software / other | Reveals current stack |
| How do you currently document move-in and move-out condition? | Paper protocol / Word/PDF / photos only / video only / no standard process / software | Measures handover maturity |
| In the last 6 months, how many repairs or issues did you personally coordinate? | 0 / 1 / 2 / 3–5 / 6+ | Measures maintenance relevance |
| What happened the last time you settled a deposit? | Short open text | Surfaces real dispute patterns |
| What do you currently pay each month or year for rental admin tools or services? | Numeric + “none” | Gives price anchor from existing behaviour |
| Which one workflow would you move first into a new product? | Lease setup / handover / reminders & tracking / communication / issues / final settlement | Helps decide wedge if product must narrow |
| Would you join a 90-day founding pilot if it meant moving one real lease or one real move-in/out into the product? | Yes / maybe / no | Filters for strong signal |
| If yes, what is the next real event you could run in a pilot? | Move-in / move-out / renewal / late payment / issue / other + timing | Tells you whether the pilot can produce live behaviour |
For pricing, do not rely on one soft survey question. Run a stack of tests.
| Test | Exact wording | What to learn | Strong signal |
|---|---|---|---|
| Current-spend anchor | “What do you already pay today for tools, accountants, managers, reminders, screening, or admin help related to your rentals?” | Whether you are replacing cost or adding new spend | They already spend money or value time highly |
| Portfolio-specific price test | “For your current portfolio of [X] units, if MamNajem handled the last workflow you showed me, would you start next month at [19.99 / 49.99 / 99.99 PLN depending on portfolio band]?” | Immediate purchase intent | A clear “yes, for my current units” |
| Alternative-to-status-quo test | “For the next three months, would you rather keep your current system exactly as it is, or pay [tested price] to run one live lease in one place?” | Whether pain is actually strong enough to beat inertia | They choose the paid option without hedging |
| Annual-prepay test | “If setup and migration were included, would you choose monthly or annual billing for your current portfolio?” | Whether migration help unlocks commitment | They accept annual at launch |
| Refundable reservation test | “To reserve a founding slot, would you leave a fully refundable deposit today?” | Revealed preference, not stated preference | Card or transfer commitment |
| Post-pilot price-lock choice | “If the pilot works, which plan would you continue on for your actual portfolio?” | Whether price maps to real portfolio shape | They choose a concrete plan, not “depends” |
Use the PO-approved pilot ladder and validate willingness to pay by portfolio band. The cleanest validation is:
- up to 3 units at 19.99 PLN
- up to 10 units at 49.99 PLN
- up to 25 units at 99.99 PLN fileciteturn0file3 fileciteturn0file4
That keeps the test focused on the real ICP. Do not test percent-of-rent pricing at this stage. It will confuse the category and muddy whether users want landlord operations software or a risk/financial product. fileciteturn0file3
Landing page copy variants¶
The attached GTM research recommends leading with mobile-first operational control, not “property management,” enterprise automation, or payment infrastructure. The strongest headline direction in the research is effectively “run every rented flat from your phone,” and the broader market research supports positioning around lease operations rather than a manager suite. fileciteturn0file4 fileciteturn0file9
All copy below is written for a Polish-facing landing page. Every CTA should ask for a real next step, not a passive waitlist.
| Variant | Hero | Subhead | CTA | What this tests |
|---|---|---|---|---|
| Operational control | Prowadź cały wynajem z telefonu. | Czynsz, umowy, protokoły, dokumenty i rozmowy z najemcą w jednym miejscu. Dla właścicieli, którzy samodzielnie zarządzają 2–10 mieszkaniami. | Dołącz do programu Founding Landlord | Broadest, clearest category fit |
| Anti-chaos | Koniec z Excelem, przelewami i wiadomościami w pięciu miejscach. | MamNajem porządkuje najem: przypomnienia o płatnościach, przekazanie mieszkania, dokumenty, zgłoszenia i rozliczenie kaucji. | Pokaż mi, jak przenieść 1 aktywną umowę | Pain around fragmentation and manual admin |
| Evidence and fairness | Każde przekazanie mieszkania, płatność i rozliczenie kaucji udokumentowane. | Zdjęcia, protokoły, historia wiadomości i finalne rozliczenie bez szukania plików i screenów po fakcie. | Zobacz przebieg 1 realnego najmu | High-trust wedge for handovers and settlements |
| Local workflow | Zaprojektowane pod polski najem długoterminowy. | Najem zwykły i okazjonalny, harmonogram płatności, protokoły, dokumenty i współpraca z najemcą w jednym procesie. | Umów 15-minutowy przegląd portfela | Whether local relevance and compliance framing increase trust |
Use proof blocks under each hero, not long feature lists. The three strongest proof blocks to test are:
| Proof block title | Short copy |
|---|---|
| Płatności i przypomnienia | Wiesz, kto zapłacił, kto się spóźnia i jakie działania już zostały podjęte. |
| Przekazanie mieszkania | Zdjęcia, liczniki, klucze i podpisany protokół bez chaosu po przeprowadzce. |
| Rozliczenie bez sporów | Historia dokumentów, wiadomości i potrąceń z kaucji w jednym miejscu. |
Avoid the following in launch copy until you have the product and legal execution to support it: “dla zarządców nieruchomości,” “pełna legalizacja e-podpisu,” “automatyczna eksmisja,” “wszystko dla property managera,” or anything that implies that every formal Polish lease/notice flow is already native and fully digital. Your product-spec and e-signature research are clear that this would create avoidable trust debt. fileciteturn0file8 fileciteturn0file0 citeturn9view4turn10view0
Founder outreach and pilot offer¶
Your attached GTM work recommends a Founding Landlord Program with migration help and a price lock, not a broad discount. That is exactly the right structure for a behaviour-first validation, because it trades operational help for real adoption and case-study signal. fileciteturn0file4
Use short founder messages that sound like research, not sales. The point is to recruit landlords who have recent operational reality, not people who enjoy idea conversations.
| Scenario | Polish outreach message |
|---|---|
| Cold DM to landlord | Cześć [Imię], rozmawiam teraz z właścicielami, którzy samodzielnie zarządzają 2–10 mieszkaniami w Polsce. Nie sprzedaję usługi — próbuję zrozumieć, jak dziś ogarniacie umowy, przekazania mieszkań, przypomnienia o czynszu i rozliczenie kaucji. Jeśli to Twój case, czy znajdziesz 30 minut w tym tygodniu? W zamian dam krótkie podsumowanie wniosków i pierwszeństwo do programu pilotażowego. |
| Warm referral ask | Cześć [Imię], [osoba polecająca] podpowiedziała mi, że samodzielnie prowadzisz kilka mieszkań na wynajem. Robię serię rozmów z właścicielami 2–10 lokali o tym, co naprawdę dzieje się przy umowach, czynszu, przekazaniach i kaucji. Czy mogę podpytać Cię przez 30 minut i poprosić o pokazanie ostatniego realnego procesu? |
| Follow-up after no reply | Hej, podbijam wiadomość. Szukam tylko kilku właścicieli 2–10 mieszkań, którzy pokażą mi, jak wyglądał ostatni realny najem: umowa, protokół, płatność albo rozliczenie kaucji. Jeśli to nie jest dobry moment, daj proszę znać — jeśli tak, wyślę 3 konkretne terminy. |
| Community organizer message | Cześć, buduję narzędzie dla właścicieli, którzy samodzielnie zarządzają najmem długoterminowym. Chciałbym zrobić krótką, praktyczną sesję dla Waszej społeczności: jak uporządkować czynsz, dokumenty, protokoły i rozliczenie kaucji bez Excela i chaosu. Bez sprzedażowego webinaru — raczej warsztat oparty o realne przypadki. Czy jest sens porozmawiać o wspólnym terminie? |
| Pilot invitation after strong interview | Dzięki za rozmowę. Na podstawie tego, co pokazałeś, bardzo pasujesz do pierwszej grupy Founding Landlord Program. Propozycja jest prosta: 90 dni pilota, pomoc w migracji i stała cena founderska po starcie, jeśli wprowadzisz u nas co najmniej 1 realną umowę i przejdziesz przez 3 realne workflowy. Jeśli chcesz, wyślę 1-stronicowe zasady i od razu zarezerwujemy onboarding. |
The pilot itself should be explicit, narrow, and honest about legal boundaries.
| Pilot element | Recommendation |
|---|---|
| Name | Founding Landlord Program |
| Who it is for | Self-managing landlords with 2–10 long-term residential units in Poland |
| Strongest-fit candidates | Owners with an upcoming move-in, move-out, renewal, late payment, or active issue in the next 30–60 days |
| Duration | 90 days |
| What they get | White-glove onboarding, migration help, direct founder support, fast bug handling, and a locked-in founding price if they activate |
| What you get | One real lease or one real transition imported, at least one tenant invited, and permission to learn from actual workflows and artifacts |
| Minimum activation rule | Import one live lease within 14 days and complete at least three real workflows in-product |
| Best workflows to require | Lease record, payment schedule/reminder, handover, deposit or final settlement, communication thread, issue reporting |
| Pricing test inside pilot | Lock accepted pilots to 19.99 / 49.99 / 99.99 PLN based on portfolio band |
| Right founder incentive | Migration help, priority support, and price lock — not a large permanent discount |
| What stays hybrid if needed | Any lease or notice flow that still needs wet ink, QES, or notarial/off-platform handling |
Be especially explicit about the hybrid legal boundary in the pilot. If a landlord uses an occasional lease pack, a >1-year fixed-term lease where they want written-form confidence, or a landlord notice that legally requires written form, the pilot can still manage the record, archive, tasking, and evidence trail, but execution may need to stay hybrid until the proper signature/notarial path is in place. That is better than pretending the app already closes every legal loop. fileciteturn0file8 fileciteturn0file0 citeturn9view4turn10view0
Success criteria and red flags¶
Your attached GTM work gives useful later-stage commercial targets: 30–50 paying ICP landlords, 150+ active units, 40%+ activation, 70%+ 90-day retention, and at least two repeatable channels. For validation, you need earlier thresholds that tell you whether it is worth pushing toward those launch metrics at all. fileciteturn0file4
| Area | Continue if you see this | Narrow if you see this | Stop if you see this |
|---|---|---|---|
| Interview signal | 70%+ of qualified landlords can show at least three recent target workflows with real artifacts | Pain is real but concentrated in only one workflow | Most target landlords cannot show the workflows or do not handle them personally |
| Real-lease willingness | 40%+ of qualified landlords agree to pilot one real lease or real transition event | They will only test a narrow wedge such as handover or reminders | Almost nobody will move anything real, even with white-glove migration |
| Tenant-side adoption | 50%+ of invited pilot tenants complete at least one real task | Tenants will only use document or handover flows, not broader collaboration | Tenants ignore the product and landlords are unwilling to require any usage |
| Workflow usage in pilot | 60%+ of pilot landlords complete three or more target workflows in-product | Usage clusters around one narrow wedge | Most pilots stall after setup or founder hand-holding |
| Price validation | 30%+ of qualified pilot landlords accept or pre-commit to the tested post-pilot price for their real portfolio | They want the product, but only at a lower or narrower price tied to fewer workflows | The price floor required for viability is consistently rejected by the ICP |
| Founder dependence | After onboarding, users can operate core workflows with light support | Founder is needed for one critical step only | Product value exists only when founder manually substitutes for the product |
| Launch readiness | You are trending toward the GTM thresholds from the attached report | One channel or one wedge works, but not the full launch story | No repeatable acquisition path and no real operational stickiness |
The red flags that matter most for this product are not generic SaaS warnings; they are specific to the thesis and the current product shape.
| Red flag | What it means | What to do |
|---|---|---|
| The strongest recurring pain is pre-lease lead screening and application flow, not lease operations | Your current wedge is too far downstream | Narrow toward pre-lease funnel first, or stop calling the current launch thesis validated fileciteturn0file7 |
| The strongest recurring pain is maintenance/issues, and landlords treat that as a must-have before adopting anything else | A dedicated issue timeline may be a prerequisite for paid adoption | Narrow to a minimum useful maintenance workflow before broad launch fileciteturn0file6 fileciteturn0file9 |
| Landlords like the idea but refuse to put a real lease or real handover/settlement into the product | You have curiosity, not trust | Do not declare validation; improve onboarding, evidence handling, or legal clarity first |
| The only people eager to pay are 1-unit accidental landlords | The revenue wedge in the attached financial research is not proving out | Re-test the business case, because the paid core may be too small or too price-sensitive fileciteturn0file1 |
| Most serious landlords immediately ask for agency/team/manager workflows | The target user is different from the product’s current owner-tenant reality | Narrow to self-managing landlords or build a manager model before broadening the promise fileciteturn0file9 |
| Prospects block on legally complete digital signing for every lease and notice flow today | Legal trust is gating adoption | Narrow the promise to post-signing operations, or add QES/hybrid execution before continuing fileciteturn0file8 fileciteturn0file0 citeturn9view4turn10view0 |
| Price acceptance is only strong when the product is effectively free | The category fit may be real, but the business model is not | Stop broad launch work until the value or wedge changes |
| Activation happens, but nobody comes back after the first setup | You have onboarding novelty, not operational habit | Do not scale acquisition; fix stickiness first |
The simplest go/no-go rule is this: do not greenlight the first Polish launch just because landlords say the idea sounds useful. Greenlight it only if the target ICP will do three hard things: show you the current mess, move one real lease or real workflow into the product, and accept a realistic fixed monthly price for their actual portfolio. If those three things happen together, you have the beginnings of a validated launch wedge. If they do not, narrow the promise before you scale.