Skip to content

Pilot Pricing Test Log

Date: 2026-06-25

Status: Ready execution log for EP10-T7. This does not complete EP10-T7 until qualified pilot landlords answer the price test.

Related pilot ops: Founding pilot ops

Related scorecard: Pilot scorecard

Related landlord script: Landlord interview script

Related backlog: Pre-release delivery epics

Purpose

This log records the formal pilot pricing test for the first qualified landlords.

It tests whether self-managing Polish landlords with real portfolios will accept or pre-commit to a realistic fixed monthly subscription after the pilot. It does not test percent-of-rent pricing, rent-payment take-rate pricing, agency pricing, property-manager pricing, or annual-first pricing.

Tested Ladder

Use the portfolio ladder already approved in the pilot offer.

Plan Gross monthly price Active property cap Active tenant cap Ask this plan when
Solo 19.99 PLN 3 10 Landlord has 1-3 active rental properties.
Portfolio 49.99 PLN 10 35 Landlord has 4-10 active rental properties.
Plus 99.99 PLN 25 100 Landlord has 11-25 active rental properties or is a future-review account.

Do not discount the monthly ladder during the test. If the landlord asks about annual pricing, record the request as a signal, but do not make annual pricing the tested offer before pilot demand and retention are proven.

Test Script

Ask after the landlord has seen or used the workflow tied to their actual portfolio.

For your current portfolio, if MamNajem handled the workflow you ranked
highest, which post-pilot plan would you realistically continue on: Solo at
19.99 PLN/month for up to 3 active properties, Portfolio at 49.99 PLN/month for
up to 10, or Plus at 99.99 PLN/month for up to 25?

Then ask:

What makes that price acceptable or unacceptable for your actual portfolio?

If the answer is maybe, ask:

What would need to be true before this became a yes?

If the answer is no, ask:

What is the main blocker: value, missing workflow, trust, tenant adoption,
legal confidence, cash, habit, too many units, or something else?

Record the objection in the landlord's exact words with personal data removed.

Response Log

Use participant IDs only. Keep names, emails, phone numbers, property addresses, rent amounts, lease details, bank details, and tenant data outside this docs file.

Participant ID Qualified pilot Unit band Actual portfolio plan asked Tested price Response Accepted plan Objection code Exact objection with personal data removed Post-pilot next step
PILOT-001 no not_asked none Awaiting accepted pilot landlord. not_decided
PILOT-002 no not_asked none Awaiting accepted pilot landlord. not_decided
PILOT-003 no not_asked none Awaiting accepted pilot landlord. not_decided
PILOT-004 no not_asked none Optional capacity slot. not_decided
PILOT-005 no not_asked none Optional capacity slot. not_decided

Allowed response values:

  • accepted
  • maybe
  • rejected
  • not_asked

Allowed accepted-plan values:

  • solo
  • portfolio
  • plus
  • custom_review
  • none

Allowed objection codes:

  • value_gap
  • missing_workflow
  • trust
  • tenant_adoption
  • legal_confidence
  • cash
  • habit
  • too_many_units
  • other

Allowed post-pilot next steps:

  • start_paid
  • extend_pilot
  • downgrade
  • archive
  • churn
  • not_decided

Admin Capture

Pricing-test responses should be recorded on the accepted founding-pilot applicant row in web-admin after the landlord is asked the fixed monthly ladder.

The admin capture stores:

  • whether the applicant is a qualified pricing pilot
  • the plan asked: solo, portfolio, plus, custom_review, or none
  • the tested gross monthly price in grosz
  • the response: accepted, maybe, rejected, or not_asked
  • the accepted plan, when there is one
  • the objection code and personal-data-free objection note, when relevant
  • the post-pilot next step
  • the timestamp when pricing was recorded

This does not replace the response log below. Use the admin record as the operational source while the pilot is active, then copy anonymized participant IDs and aggregate results into this document, the scorecard, and the go / narrow / stop memo.

The Founding Pilot toolbar includes Copy pricing log, which copies an anonymized Markdown snapshot from the loaded pricing rows. The snapshot matches the response-log columns: participant ID, qualified-pilot flag, unit band, plan asked, tested price, response, accepted plan, objection code, objection note, and post-pilot next step. It intentionally excludes applicant names, emails, phone numbers, free-form intake messages, and review notes. Objection notes must already be scrubbed before they are saved in admin.

Before copying, the admin reloads every page matching the active founding-pilot filters at export size and includes Rows exported, so the response log is not capped to the visible admin page.

For Batch 1 rows, Copy pricing log also includes participants that have a saved batch status but no pricing response yet. Those rows copy as not_asked, none, and not_decided, so the response log can preserve pricing gaps from the Needs pricing queue instead of omitting them from the snapshot.

The web-admin Founding Pilot summary also shows global pricing-test counts:

  • qualified pricing pilots
  • pricing asked
  • pricing accepted
  • pricing maybe
  • pricing rejected
  • pricing not asked
  • rejected pricing responses with complete objections
  • rejected pricing responses missing an objection
  • pricing acceptance rate

For the actual Batch 1 cohort, the summary also shows pricing progress scoped to applicants with a saved pilot batch status:

  • batch pricing pilots
  • batch pricing asked
  • batch pricing accepted
  • batch pricing rejected
  • batch pricing missing
  • batch rejected with objection
  • batch rejected missing objection
  • batch pricing acceptance
  • batch post-pilot start paid
  • batch post-pilot extend pilot
  • batch post-pilot downgrade
  • batch post-pilot archive
  • batch post-pilot churn
  • batch post-pilot not decided
  • batch post-pilot missing

Use the batch-scoped metrics for the EP10-T7 completion calculation. Use the global pricing metrics only for broader demand diagnostics and lead-quality review. Use the batch post-pilot next-step metrics to separate actual start-paid intent from extend, downgrade, archive, churn, undecided, or missing follow-up before copying the pricing result into the scorecard and the go / narrow / stop memo.

Use the Founding Pilot action queue filter to resolve row-level pricing gaps:

  • Needs pricing: batched applicant has not been asked or recorded
  • Needs post-pilot: price response is recorded but post-pilot next step is missing
  • Needs refusal blocker: rejected/churned batched applicant is missing a blocker code or short outcome note

After filtering one of these queues, use Copy action queue to copy the anonymized queue worklist into follow-up notes. The snapshot preserves the participant ID, queue reason, batch status, pricing response, post-pilot next step, outcome, blocker code, and next action without applicant PII, free-form intake messages, review notes, or support case identifiers. The copy action reloads every page in the selected queue before copying and includes a Rows exported count, so pricing or post-pilot follow-up queues larger than one admin page stay visible in the copied worklist.

Calculation

Use only qualified pilot landlords who were asked the price for their actual portfolio.

Metric Formula Current value
Qualified landlords asked Count rows where qualified_pilot=yes and Response is not not_asked. 0
Accepted or pre-committed Count accepted responses plus explicit written pre-commitments. 0
Acceptance rate Accepted or pre-committed / qualified landlords asked. 0%
Rejected with exact reason Count rejected rows with an objection code and exact objection. 0

EP10-T7 passes only when at least 30% of qualified pilot landlords accept or pre-commit to a realistic fixed monthly plan, or the exact reasons they do not accept are documented.

Decision Rules

Result Decision
30%+ accept or pre-commit to the fixed monthly ladder Keep the ladder for the next pilot cohort.
Acceptance exists only for one plan or one workflow Narrow the offer around the workflow and plan that converted.
Most answers are maybe because activation is incomplete Continue the pilot but do not claim price validation yet.
Most rejections cite missing workflow or weak value Narrow product scope before spending on more acquisition.
Most rejections cite only free preference or no paid intent Stop or reposition before public launch.
Landlords ask for annual plans before monthly demand is clear Record the signal; do not make annual pricing the primary offer yet.

EP10-T7 Completion Rule

EP10-T7 can be marked complete only when:

  • qualified pilot landlords have been asked the fixed monthly price tied to their actual portfolio size
  • the tested offer is the 19.99 / 49.99 / 99.99 PLN gross monthly ladder or a documented equivalent
  • no percent-of-rent pricing has been tested
  • every rejection has an objection code and exact objection with personal data removed
  • the acceptance rate is calculated from qualified landlords actually asked
  • the result is copied into the scorecard and the go / narrow / stop memo

Evidence

This document is an EP10-T7 execution aid only. It records the approved pricing test, response log, and admin capture fields, but it does not claim willingness to pay has been validated.

Implementation evidence:

  • Backend integration commit 8358992 adds persistent pricing-test fields, validation, migration, OpenAPI schema, and the admin pricing endpoint.
  • web-admin integration commit 646ee0e adds the founding-pilot pricing controls and API client coverage.
  • Backend integration commit 12de0d8 and web-admin integration commit 1dc76b7 add global pricing-test summary metrics for scorecard and memo copy-out.
  • Backend integration commit ea0db65 and web-admin integration commit 52b2bea add Batch 1 pricing-progress summary metrics so EP10-T7 can be calculated from the accepted/onboarded pilot cohort instead of the full intake list.
  • web-admin integration commit 4154546 adds Copy pricing log, an anonymized Markdown snapshot action for loaded pricing-test rows, so the response log can be updated from participant IDs, unit bands, pricing response fields, and scrubbed objection notes without copying applicant PII.
  • Backend integration commit 7dc11bd and web-admin integration commit bdb4806 add Batch 1 rejected-pricing and objection-completeness counters to the validation summary and memo snapshot, so EP10-T7 can be checked from the accepted/onboarded cohort without relying on global intake rejection counts.
  • Backend integration commit fef70d6 and web-admin integration commit 1435272 add Batch 1 post-pilot next-step counters for start-paid, extend, downgrade, archive, churn, not-decided, and missing follow-up to the validation summary and memo snapshot.
  • Backend integration commit 2dd46e4 and web-admin integration commit 8cc0ecf add row-level action queue filtering for pricing, post-pilot, and refusal-blocker follow-up so EP10-T7 missing counters can be resolved from the admin intake list.
  • web-admin integration commit f89df80 makes Copy pricing log include Batch 1 rows with no pricing response yet as not_asked rows, so missing pricing evidence from the Needs pricing queue can be copied into this log without applicant PII.
  • web-admin integration commit 07d4e13 adds Copy action queue, an anonymized Markdown snapshot for the selected action queue, so pricing, post-pilot, and refusal-blocker follow-up rows can be copied as a worklist without applicant PII or support case identifiers.
  • web-admin integration commit 0bbbd74 makes Copy action queue reload all selected queue pages at size 100 and add Rows exported, so pricing follow-up worklists are not capped at the visible admin page.
  • web-admin integration commit 98ff1bc makes Copy pricing log reload every matching founding-pilot page at export size and add Rows exported, so pricing response logs are not capped at the visible admin page.

Deployment evidence:

  • backend pipeline 2631045725 succeeded for 7dc11bd on integration.
  • web-admin pipeline 2631053476 succeeded for bdb4806 on integration.
  • backend pipeline 2631197648 succeeded for fef70d6 on integration.
  • web-admin pipeline 2631197649 succeeded for 1435272 on integration.
  • backend pipeline 2631380073 succeeded for 2dd46e4 on integration.
  • web-admin pipeline 2631380022 succeeded for 8cc0ecf on integration.
  • web-admin pipeline 2631878561 succeeded for f89df80 on integration.
  • AWS Amplify job 55 succeeded for f89df80 on the integration admin branch.
  • Integration smoke on 2026-06-26 opened https://admin-integration.mamnajem.pl/?v=1435272#founding-pilot, confirmed the deployed admin bundle contains the Batch post-pilot labels, and confirmed the protected backend summary route returns 401 without admin credentials.
  • Integration smoke on 2026-06-26 opened https://admin-integration.mamnajem.pl/?v=8cc0ecf#founding-pilot, confirmed the deployed admin bundle contains the action queue labels and pilotAction, and confirmed the protected backend list route with pilotAction=NEEDS_PRICING returns 401 without admin credentials.
  • Integration smoke on 2026-06-26 opened https://admin-integration.mamnajem.pl/?v=f89df80-browser#founding-pilot, reached the admin sign-in screen, confirmed the deployed admin bundle index-D3U-NluZ.js contains Copy pricing log, Pilot Pricing Test Snapshot, not_asked, and the Batch 1 pricing-row predicate, and confirmed the protected backend summary route returns 401 without admin credentials.
  • web-admin pipeline 2632061405 succeeded for 98ff1bc on integration; AWS Amplify job 60 published the admin bundle.
  • Integration smoke on 2026-06-26 opened https://admin-integration.mamnajem.pl/?v=98ff1bc-browser#founding-pilot, reached the admin sign-in screen, confirmed the deployed admin bundle contains Copy pricing log, Pilot Pricing Test Snapshot, Rows exported:, not_asked, and Objection notes must be scrubbed, and confirmed the protected backend list route returns 401 without admin credentials.