Pilot Scorecard¶
Date: 2026-06-25
Status: Accepted Product Owner scorecard for EP10-T4.
Related charter: Pre-release charter
Related pilot ops: Founding pilot ops
Related activation contract: Activation event taxonomy
Related backlog: Pre-release delivery epics
Purpose¶
This scorecard is the single weekly record for deciding whether the Founding Landlord Program should continue, narrow, pause, or stop.
It tracks the full pilot path: qualified demand, accepted pilots, activation, tenant participation, workflow completion, support load, price acceptance, and churn or refusal reasons.
Scorecard Rules¶
- Maintain one scorecard for the cohort.
- Update it at least once per week before the pilot review.
- Use participant IDs in the scorecard. Keep names, emails, phone numbers, and private notes in a separate controlled contact roster.
- Do not paste lease contents, tenant personal data, bank details, addresses, message bodies, document filenames, rent amounts, or screenshots into the scorecard.
- Count only real rental workflows. Demo data does not count toward activation.
- Record exact refusal or churn reasons in short text, but remove personal data.
Weekly Summary¶
Copy this table for each pilot review week.
| Metric | This week | Cohort total | Target / concern threshold | Decision note |
|---|---|---|---|---|
| Qualified applicants | Enough for next batch; quality matters more than volume. | |||
| Completed landlord interviews | At least 12 target interviews before launch memo. | |||
| Completed tenant interviews | At least 8-12 tenant interviews if tenant workflows are in scope. | |||
| Accepted pilots | Start with 3-5 landlords if support capacity is limited. | |||
| Activated landlords | Continue if activation is real, not founder-substituted. | |||
| Activated units | Founding pilot target is roughly 20-40 live units. | |||
| Owner-only activations | Owner value must exist before tenant dependency. | |||
| Tenant task completions | Continue if tenants complete real tasks; narrow if only one task works. | |||
| Workflows completed | Continue if 60%+ of pilot landlords complete 3+ workflows. | |||
| Support requests | Pause if support stop conditions trigger. | |||
| P0/P1 support items | Repeated P1/P0 items require pause or incident review. | |||
| Price acceptances | Continue if 30%+ accept or pre-commit to realistic fixed pricing. | |||
| Post-pilot start paid | Strongest pricing signal; reconcile against accepted fixed-plan rows. | |||
| Post-pilot extend / archive / churn | Extend means continue learning; archive or churn means no paid path yet. | |||
| Churns / refusals | Exact reason required for every churn/refusal. | |||
| Weekly decision | Continue / narrow / pause / stop. |
Participant Row Template¶
Use one row per applicant or pilot participant.
| Field | Allowed value / format | Notes |
|---|---|---|
participant_id |
stable short ID | No raw email/name in this sheet. |
source |
outreach, referral, landing, community, existing_user, other | Acquisition source. |
city_band |
warsaw, krakow, wroclaw, trojmiasto, poznan, other_poland, outside_poland | Use the launch city buckets. |
unit_count_band |
1, 2-3, 4-5, 6-10, 11-25, 26-50, 51+ | Band only. |
management_model |
self_managed, mixed, agency_managed, unknown | First ICP requires self-managed or clearly mixed. |
landlord_score |
0-10 | From Epic 1 applicant scoring. |
interview_status |
not_started, scheduled, completed, skipped | Landlord interview state. |
tenant_interview_status |
not_needed, not_started, scheduled, completed, skipped | Track if tenant evidence matters for this pilot. |
landlord_interview_completed_at |
YYYY-MM-DD | Use the admin Founding Pilot Interviews control as the timestamp source. |
tenant_interview_completed_at |
YYYY-MM-DD | Blank unless tenant evidence is in scope and complete. |
pilot_decision |
accepted, waitlist, nurture, declined, not_fit | Product Owner decision. |
accepted_date |
YYYY-MM-DD | Blank unless accepted. |
kickoff_date |
YYYY-MM-DD | First onboarding call. |
live_units_count |
integer | Real units in app, not demos. |
activated_landlord |
yes, no | Yes when 30-day activation rule is met. |
owner_only_activation |
yes, no | Yes when owner gets value before tenant participation. |
tenant_task_count |
integer | Count persisted tenant-side actions: accepted invite, tenant handover confirmation/decline, tenant final-settlement confirmation/decline, tenant-authored message, tenant-uploaded evidence, or tenant-submitted support report. |
workflow_count |
integer | Count completed target workflows. |
support_request_count |
integer | Total support items for this participant. |
p0_p1_count |
integer | P0/P1 support items. |
price_signal |
accepted, maybe, rejected, not_asked | Use actual post-pilot plan discussion. |
accepted_plan |
solo, portfolio, plus, custom_review, none | No percent-of-rent pricing. |
churn_or_refusal_reason |
blocker code + short text | Use interview blocker taxonomies where possible. |
weekly_status |
continue, narrow, pause, stop, closed | Current Product Owner recommendation. |
next_action |
short text | Owner and due date. |
Activation Definitions¶
Use these definitions consistently.
| Metric | Definition |
|---|---|
| Qualified applicant | Applicant fits the first ICP strongly enough to score 8-10, or Product Owner explicitly accepts a 6-7 applicant for interview because the evidence is strong. |
| Accepted pilot | Landlord has accepted the Founding Landlord Program terms and has a kickoff scheduled or completed. |
| Activated landlord | Landlord has at least two live units in MamNajem within 30 days and has completed at least three real target workflows in-product. |
| Activated unit | A real rental unit represented in MamNajem with an active lease or active rent workflow. |
| Owner-only activation | Owner creates useful operational value before a tenant accepts an invite: property, lease or transition event, document/evidence artifact, and at least one rent schedule, handover, reminder, message, support report, or settlement workflow. |
| Tenant task completion | Tenant completes a concrete task that is persisted in product: accepts invite, confirms or declines handover, uploads evidence, sends a lease message, reports a simple issue, or confirms/declines final settlement. |
| Workflow completed | A real target workflow completes in product: lease record, document vault, rent schedule/reminder, payment proof, handover, tenant communication, simple issue report, deposit review, or final settlement evidence. |
| Support request per landlord | Count of in-app reports, support emails, or check-in issues copied into the support log for that landlord. |
| Price acceptance | Landlord accepts or pre-commits to the tested post-pilot fixed monthly plan for their actual portfolio. |
| Churn/refusal reason | Primary reason the landlord refused, churned, paused, or failed to activate. |
Workflow Completion Matrix¶
Track each workflow as 0 or 1 per participant per week. Count only real
workflows.
| Workflow | Counts when |
|---|---|
property_setup |
Real property exists in the app. |
lease_record |
Real lease or transition event is represented. |
document_or_evidence |
At least one real document or evidence artifact is attached. |
rent_schedule |
Rent schedule or payment-follow-up workflow is created. |
payment_proof |
Payment proof or mark-paid evidence is captured. |
handover |
Move-in or move-out handover is started or completed with real details. |
tenant_invite |
Tenant invite is sent for a real lease. |
tenant_task |
Tenant completes at least one accepted task. |
simple_issue_report |
Owner or tenant submits a real simple issue/support report. |
deposit_or_settlement |
Deposit ledger, final settlement, or settlement evidence is reviewed. |
message_or_reminder |
Real message, reminder, or follow-up is sent or recorded. |
Admin Evidence Source¶
For accepted applicants, use the web-admin Founding Pilot row-level
Evidence control as the operational source for app-backed activation counts.
It matches the intake email to an app user and reports per-applicant counts for
properties, active leases, active rent schedules, payment requests, payment
receipts, tenant invites, tenant-task completions, handover protocols,
document/evidence assets, support reports, support-report status counts,
workflow-count categories, and owner-only activation readiness. Tenant-task
completions are counted from persisted tenant-side invite acceptance, handover
confirmation/decline, settlement confirmation/decline, tenant messages, tenant
uploads, and tenant support reports.
Use those counts to update the participant row and workflow matrix, but keep this scorecard anonymized. Do not paste raw emails, user IDs, lease details, addresses, document names, rent amounts, or tenant data into the scorecard. The Founding Pilot validation summary also exposes Batch 1 activation-gap counters for batched pilots missing matched users, owner-only readiness, 3+ workflows, or tenant-task evidence. Use those missing counters to audit the scorecard before marking the onboarding batch or memo evidence ready.
The same admin view captures per-applicant interview evidence in the
Interviews control. Record landlordInterviewCompletedAt when the landlord
interview is complete and tenantInterviewCompletedAt when tenant evidence is
in scope and complete. The validation summary exposes global completed
landlord/tenant interview counts and batch-scoped completed landlord/tenant
interview counts, so the weekly summary can be copied without manually
counting interview rows.
The Founding Pilot toolbar includes Copy interview log, which copies
row-level interview evidence as an anonymized Markdown snapshot. Use it to
reconcile participant IDs, city/unit bands, batch status, landlord interview
date, tenant interview date, recorded date, and next action before updating the
scorecard. The export reloads every matching founding-pilot page and includes
Rows exported, so interview reconciliation is not limited to the visible
admin table page.
Use the Needs interview action queue before updating the interview rows. It
isolates accepted applicants whose landlord interview completion timestamp is
still blank, so the weekly scorecard does not treat an accepted pilot as having
passed the interview gate without row-level evidence.
The Founding Pilot toolbar includes Copy scorecard, which copies the weekly
summary table from the loaded validation summary into this scorecard format.
It fills cohort-level values that are queryable from admin: qualified
applicants, completed landlord/tenant interviews, accepted pilots, owner-only
activations, tenant task completions, 3+ workflow participants, P0/P1 support
items, price acceptances, post-pilot start-paid intent, and churn/refusal
counts. It intentionally leaves activated-unit counts, support-request details,
and weekly decision notes blank when those values still require Product Owner
review outside the admin summary.
Price Signal Fields¶
Use these fields whenever price is discussed.
| Field | Allowed value / format |
|---|---|
price_asked |
yes / no |
tested_plan |
solo / portfolio / plus / custom_review |
tested_price |
19.99 / 49.99 / 99.99 / other documented |
price_response |
accepted / maybe / rejected |
objection_code |
value_gap / missing_workflow / trust / tenant_adoption / legal_confidence / cash / habit / too_many_units / other |
exact_objection |
short quote with personal data removed |
post_pilot_next_step |
start_paid / extend_pilot / downgrade / archive / churn / not_decided |
The web-admin Founding Pilot validation summary also exposes Batch 1 post-pilot next-step counters for start-paid, extend, downgrade, archive, churn, not-decided, and missing follow-up. Use those aggregate counters to audit this scorecard before copying pricing evidence into the go / narrow / stop memo.
The same summary exposes Batch 1 refusal/churn blocker completeness counters. Use them to confirm every refused or churned participant has both a blocker code and a short outcome note before copying the scorecard into the go / narrow / stop memo.
Support Load Fields¶
Use the support definitions from Pilot support operating procedure.
| Field | Meaning |
|---|---|
support_request_count |
Total support items for the participant. |
p0_count |
P0 incidents tied to the participant. |
p1_count |
P1 blockers tied to the participant. |
p2_count |
P2 support items. |
p3_count |
P3 feedback items. |
open_support_count |
Items still open at weekly review. |
support_hours_estimate |
Founder/Product Owner hours spent this week. |
support_status |
normal / watch / stop_condition |
For in-app problem reports, the web-admin Evidence control provides
participant-level total, open, in-progress, resolved, and dismissed counts for
the matched owner account plus tenant users linked to that owner's leases.
After the support log is reviewed, the web-admin Founding Pilot outcome
controls capture p0_count, p1_count, support_hours_estimate, and
support_status on the intake entry for the memo snapshot. P2/P3 detail
remains in the support log because in-app problem reports do not store
severity.
The web-admin Founding Pilot toolbar includes Copy outcome log, which copies
an anonymized Batch 1 outcome/support snapshot for final memo reconciliation.
The snapshot includes participant ID, batch status, post-pilot next step, final
outcome, refusal/churn blocker, outcome note, support status, P0/P1 counts,
support hours, and outcome recorded date. It excludes applicant names, emails,
phone numbers, free-form intake messages, review notes, and support case
identifiers. Before copying, the admin reloads every page matching the active
founding-pilot filters and includes Rows exported, so outcome/support
reconciliation is not capped to the visible admin page.
Pause new onboarding when any support stop condition in the support procedure is active.
Weekly Decision Rules¶
Use the scorecard to choose one of four decisions.
| Decision | Use when |
|---|---|
| Continue | Activation is real, support is manageable, tenant tasks are not blocking critical landlord value, and price signal remains credible. |
| Narrow | Demand exists, but usage clusters around one workflow, tenant adoption only works for a narrow task, price acceptance depends on a smaller promise, or support load is high in one area. |
| Pause | A support stop condition, legal/privacy concern, repeated P1 blocker, or unclear data-quality issue makes more onboarding risky. |
| Stop | Landlords will not move real workflows, tenant adoption blocks the required value, price is rejected even after scope is clear, or the product value exists only through founder manual work. |
Weekly Review Checklist¶
Before the weekly pilot review:
- Update every participant row.
- Confirm the support log matches the support-request counts.
- Confirm tenant task completions are real tasks, not just invites sent.
- Confirm workflow counts exclude demo data.
- Record every refusal/churn with a blocker code and short outcome note.
- Record every price discussion with a plan and response.
- Choose continue, narrow, pause, or stop for the week.
- Carry unresolved blockers into the next weekly review.
Evidence¶
EP10-T4 is complete because this scorecard tracks qualified applicants, accepted pilots, activated landlords, activated units, owner-only activation, tenant task completion, workflows completed, support requests per landlord, price acceptance, and churn/refusal reason. It also gives the Product Owner weekly decision rules from one scorecard.
Source records:
- Founding pilot ops
- Activation event taxonomy
- Pilot support operating procedure
- Landlord interview script
- Tenant interview script
- Poland launch validation pack
- Polish landlord tenant validation plan
Implementation support:
- web-admin integration commit
9631990addsCopy scorecard, a privacy-safe Markdown snapshot action for the weekly scorecard. The snapshot is built from the loaded Founding Pilot validation summary and excludes applicant names, emails, phone numbers, user IDs, lease details, addresses, rent amounts, and tenant data. - Backend integration commit
cd5a697, backend coverage follow-upc6d1406, and web-admin integration commit39b5d29add row-level landlord/tenant interview completion timestamps, global and Batch 1 interview counters, and scorecard snapshot rows for completed landlord/tenant interviews. - web-admin integration commit
60ee151addsCopy interview log, an anonymized full-export snapshot for row-level landlord/tenant interview evidence. - Backend integration commit
4e794beand web-admin integration commit36bc273add theNeeds interviewaction queue for accepted applicants missing landlord interview evidence. - web-admin integration commits
2611d67and0db165baddCopy outcome logand make it reload every matching founding-pilot page with aRows exportedcount for final memo reconciliation.
Deployment evidence:
- web-admin pipeline
2631570060succeeded onintegrationfor9631990withtest_buildandsecurity_auditpassing. - backend pipeline
2631782983succeeded onintegrationforc6d1406, includingmaven-test, API compatibility, security scans, environment contract, and integration deploy. - web-admin pipeline
2631761550succeeded onintegrationfor39b5d29. - web-admin pipeline
2632085157succeeded onintegrationfor0db165b. - web-admin pipeline
2632684605succeeded onintegrationfor60ee151. - backend pipeline
2632706952succeeded onintegrationfor4e794be. - web-admin pipeline
2632706932succeeded onintegrationfor36bc273. - AWS Amplify job
51for the F9-managed admin app and branchintegrationsucceeded for commit9631990. - AWS Amplify job
52for the F9-managed admin app and branchintegrationsucceeded for commit39b5d29. - AWS Amplify job
61for the F9-managed admin app and branchintegrationsucceeded for commit0db165b. - AWS Amplify job
64for the F9-managed admin app and branchintegrationsucceeded for commit60ee151. - AWS Amplify job
65for the F9-managed admin app and branchintegrationsucceeded for commit36bc273. - Integration smoke on 2026-06-26 opened
https://admin-integration.mamnajem.pl/?v=9631990-browser#founding-pilotand confirmed the admin shell loads behind the expected sign-in gate. - Integration smoke on 2026-06-26 opened
https://admin-integration.mamnajem.pl/?v=39b5d29-browser#founding-pilotand confirmed the admin shell loads behind the expected sign-in gate. - Integration smoke on 2026-06-26 opened
https://admin-integration.mamnajem.pl/?v=0db165b-browser#founding-pilot, confirmed the admin shell loads behind the expected sign-in gate, confirmed the deployed bundle containsCopy outcome log,Pilot Outcome Support Snapshot,Rows exported:,Outcome recorded, andsupport case identifiers, and confirmed the protected backend list route returns401without admin credentials. - Integration smoke on 2026-06-26 opened
https://admin-integration.mamnajem.pl/?v=60ee151-browser#founding-pilot, confirmed the admin shell loads behind the expected sign-in gate, confirmed the deployed bundle containsCopy interview log,Copy founding pilot interview log snapshot, andPilot Interview Log Snapshot, and confirmed the protected backend summary route returns401without admin credentials. - Integration smoke on 2026-06-26 opened
https://admin-integration.mamnajem.pl/?v=36bc273-browser#founding-pilot, confirmed the admin shell loads behind the expected sign-in gate, confirmed deployed bundleindex-BpjH9HBy.jscontainsNEEDS_INTERVIEW,Needs interview, and the accepted-applicant-missing-interview queue reason, and confirmed the protected backend list route withpilotAction=NEEDS_INTERVIEWreturns401without admin credentials. - The same smoke confirmed unauthenticated
GET https://integration.mamnajem.pl/v1/admin/founding-pilot/validation-summaryreturns401. - The same smoke confirmed unauthenticated
GET https://integration.mamnajem.pl/v1/admin/founding-pilot-intake/summaryreturns401. - Browser-side bundle inspection confirmed the deployed admin shell loads
index-DR3usjA1.js, and that bundle contains bothCopy scorecardandPilot Scorecard Snapshot. There was no saved admin auth profile available in agent-browser, so the signed-in button click remains covered by local web-admin tests rather than live browser interaction. - Browser-side bundle inspection confirmed the deployed admin shell loads
index-CLFya2Pu.js, and that bundle containsSave pilot interviews,Completed landlord interviews,Batch landlord interviews, and the/interviewsAPI path. There was no saved admin auth profile available in agent-browser, so signed-in interview saving remains covered by local web-admin tests rather than live browser interaction. - Browser-side bundle inspection confirmed the deployed admin shell loads
index-BaKF4FiW.js, and that bundle containsCopy interview log,Copy founding pilot interview log snapshot, andPilot Interview Log Snapshot. There was no saved admin auth profile available in agent-browser, so the signed-in copy action remains covered by local web-admin tests rather than live browser interaction.