Skip to content

Pilot Go Narrow Stop Memo

Date: 2026-06-25

Status: Memo template for EP10-T8. This does not complete EP10-T8 until the pilot scorecard contains real activation, pricing, and support evidence.

Related pilot ops: Founding pilot ops

Related onboarding log: Pilot onboarding batch log

Related pricing log: Pilot pricing test log

Related scorecard: Pilot scorecard

Related backlog: Pre-release delivery epics

Purpose

This memo is the final Product Owner decision record for the first Founding Landlord Program cohort.

It must choose one of three launch paths:

  • go
  • narrow
  • stop

Do not complete this memo from opinion, internal demos, signups, or polite interest. Complete it only from scorecard evidence produced by real pilot landlords moving real workflows into MamNajem.

Current Decision

Field Value
Decision not_ready
Reason No real first-batch pilot activation, price-test result, or support-load data is recorded yet.
Next action Run EP10-T6 onboarding batch, then EP10-T7 pricing test, then complete this memo from the scorecard.

Required Evidence

Evidence area Required for go Current status
Real workflows moved into product Accepted landlords moved real leases, documents, schedules, handovers, support reports, payment proof, or settlement evidence into product. missing
Owner-only activation Landlords got value before tenant participation: property, lease/transition event, document/evidence, and at least one owner workflow. missing
Realistic price acceptance At least 30% of qualified pilot landlords accepted or pre-committed to a fixed monthly plan, or exact rejection reasons are documented. missing
Support load Support requests, P0/P1 counts, open support count, and support hours are manageable under the support procedure. missing
Tenant task evidence when in scope Tenants completed real tasks if tenant workflows were required for the pilot wedge. missing
Churn/refusal reasons Every refusal, churn, or failure to activate has a primary blocker code and short exact reason. missing

Scorecard Snapshot

Copy the final scorecard values here before deciding. Use the web-admin Founding Pilot validation summary for cohort-level applicant, interview, Batch 1 readiness, pricing-test counts, and memo evidence counters, then reconcile those values with the participant-level scorecard rows before making the memo decision. The summary counters named Completed landlord interviews, Completed tenant interviews, Batch landlord interviews, and Batch tenant interviews come from the admin row-level interview timestamps. The summary counters named Memo matched users, Memo owner-only ready, Memo 3+ workflows, Memo tenant-task participants, and Memo tenant-task completions measure the batched pilot cohort against real product evidence once accepted landlords have matching accounts and app activity. Memo 3+ workflows uses the same workflow categories as row-level activation evidence, including deposit/settlement and message/reminder activity. Tenant-task completions count tenant-side actions that are persisted in product: accepted invite, handover confirmation or decline, final-settlement confirmation or decline, tenant-authored message, tenant-uploaded evidence, or tenant-submitted support report. For each accepted applicant, use the Founding Pilot row-level activation evidence before copying owner-only activation, tenant-task, workflow-count, and in-app support-load status values into the snapshot. The support status counts cover the matched owner account plus tenant users linked to that owner's leases. After reviewing the support log, record final outcome, blocker code, P0/P1 counts, support hours, and support status in the web-admin Founding Pilot outcome controls so this memo uses one queryable source. Use the web-admin Copy memo snapshot action to paste the current aggregate table below, then reconcile it with anonymized participant rows and the support log before choosing go, narrow, or stop. The memo snapshot includes Batch 1 pricing asked, accepted, rejected, missing, rejected-with-objection, and rejected-missing-objection counters so the decision can separate real price rejection from incomplete pricing follow-up. It also includes Batch 1 post-pilot next-step counters for start-paid, extend, downgrade, archive, churn, not-decided, and missing follow-up so the memo can distinguish paid intent from continued pilot learning or loss. It also includes batch-scoped final outcome/support counters so global intake outcomes do not distort the cohort decision. It also includes explicit Batch 1 activation gap counters for batched pilots missing matched users, owner-only readiness, 3+ workflows, or tenant-task evidence, so incomplete onboarding evidence is visible without manual subtraction. It also includes refusal/churn blocker completeness counters so every Batch 1 refusal or churn can be audited for both a primary blocker code and short outcome note before the decision is made. The snapshot also includes a computed Memo Readiness section. It maps the same aggregate counters to the memo evidence areas and labels each row missing, review, or ready, with a concrete next action. Keep the decision as not_ready while any row is missing; use review rows for Product Owner judgment before choosing go, narrow, or stop. Use the Founding Pilot action queue filter before finalizing this memo: Needs outcome finds batched rows with a post-pilot next step but no final outcome, and Needs refusal blocker finds refused or churned rows that still need blocker evidence. After filtering a queue, use Copy action queue to copy an anonymized row-level worklist with participant ID, queue reason, review decision, batch status, pricing response, post-pilot next step, outcome, blocker code, and next action. This keeps memo cleanup tied to exact admin rows without copying applicant PII or support case identifiers. The copy action reloads every page in the selected queue before copying and includes a Rows exported count, so final memo cleanup queues are not limited to the visible admin page. Before copying final interview evidence into the scorecard inputs for this memo, use Needs interview to find accepted applicants whose landlord interview completion timestamp is still blank.

Metric Final value Decision note
Qualified applicants 0
Completed landlord interviews 0
Completed tenant interviews 0
Batch landlord interviews 0
Batch tenant interviews 0
Accepted pilots 0
Batched pilots matched to users 0
Activated landlords 0
Activated units 0
Owner-only-ready batched participants 0
Batched participants with 3+ workflows 0
Batched participants with tenant tasks 0
Tenant task completions 0
Batched pilots missing matched users 0
Batched pilots missing owner-only readiness 0
Batched pilots missing 3+ workflows 0
Batched pilots missing tenant tasks 0
Workflows completed 0
Support requests 0
P0/P1 support items 0
Price acceptances 0
Churns / refusals 0
Batch outcomes recorded 0
Batch outcomes missing 0
Batch refused or churned 0
Batch refusal/churn blockers complete 0
Batch refusal/churn blockers missing 0
Batch support watch / stop 0 / 0
Batch P0/P1 support items 0 / 0
Batch support hours 0
Batch post-pilot start paid 0
Batch post-pilot extend / archive 0 / 0
Batch post-pilot downgrade / churn 0 / 0
Batch post-pilot not decided 0
Batch post-pilot missing 0

Decision Rules

Decision Choose when
go Real workflows moved into product, owner-only activation is proven, realistic fixed-price acceptance exists, support load is manageable, and no unresolved legal/privacy stop condition is active.
narrow Demand and activation exist, but value clusters around one workflow, one city, one portfolio band, one owner-only path, or one price point.
stop Landlords will not move real workflows, value depends on founder manual work, tenants block core value, support load is not manageable, or landlords only accept free use.

Memo Draft

Use this structure when evidence is ready.

Decision: go / narrow / stop

Evidence:
- Real workflows moved:
- Owner-only activation:
- Tenant task evidence:
- Pricing result:
- Support load:
- Churn/refusal pattern:

Decision rationale:

Scope changes:

Pricing changes:

Launch path:

Next 30 days:

Stop Conditions

Do not choose go if any of these are true:

  • no accepted landlord moved a real workflow into product
  • owner-only activation exists only because the founder did the work for the landlord
  • qualified landlords reject every realistic fixed monthly price and only want free access
  • P0/P1 support items remain open or repeat across the cohort
  • data privacy, legal-boundary, or support stop conditions are active
  • the cohort evidence is only interviews without product usage

EP10-T8 Completion Rule

EP10-T8 can be marked complete only when:

  • the scorecard has final pilot evidence
  • the onboarding batch log has real participant activation and blocker notes
  • the pricing test log has qualified landlord price responses
  • the memo states go, narrow, or stop
  • the decision cites real evidence for activation, owner-only value, price acceptance or rejection, support load, and refusal/churn pattern

Evidence

This document is an EP10-T8 memo template only. It records the decision criteria and current not_ready state, but it does not claim a launch decision has been made.

Implementation support:

  • Backend integration commit 12de0d8 and web-admin integration commit 1dc76b7 provide global validation summary inputs for the memo snapshot.
  • Backend integration commit 0fd5f95 and web-admin integration commit 0c74ae2 provide per-applicant activation evidence inputs for the memo snapshot.
  • Backend integration commit 3a5302c and web-admin integration commit 41144cc add in-app support-load status counts to that per-applicant evidence.
  • Backend integration commit 198b293 and web-admin integration commit 9a6ac48 add final outcome/support evidence capture for outcome, blocker code, support status, P0/P1 counts, and support hours. Real pilot entries are still required before this memo can be completed.
  • Backend integration commit e8e874e and web-admin integration commit 8923ba3 add cohort-level memo evidence counters for batched pilots matched to users, owner-only-ready participants, and participants with at least three app-backed workflows. Real pilot entries are still required before this memo can be completed.
  • Backend integration commit a17a79e aligns the cohort-level memo 3+ workflows counter with row-level activation evidence by including deposit/settlement and message/reminder workflow categories. Backend pipeline 2631073656 succeeded and deployed this summary behavior to integration.
  • web-admin integration commit 5a7d2a0 adds a Copy memo snapshot action that formats the aggregate Founding Pilot validation summary as a Markdown table for this memo. Real pilot entries are still required before this memo can be completed.
  • Backend integration commit 7dc11bd and web-admin integration commit bdb4806 add Batch 1 rejected-pricing and objection-completeness counters to that memo snapshot, so price rejections without documented reasons are visible before choosing go, narrow, or stop.
  • Backend integration commit 3a14d26 and web-admin integration commit 63d8f20 add batch-scoped final outcome/support counters and memo snapshot rows for outcomes recorded, outcomes missing, refused/churned participants, support watch/stop status, P0/P1 incidents, and support hours. Backend pipeline 2631105131 and web-admin pipeline 2631105099 succeeded on integration.
  • Backend integration commit d2529ed and web-admin integration commit 6f6f2be add tenant-task participant/completion counters to the memo snapshot and split tenant invite volume from tenant task completion volume in the activation log. Backend pipeline 2631162540 and web-admin pipeline 2631162539 succeeded on integration.
  • Backend integration commit fef70d6 and web-admin integration commit 1435272 add batch-scoped post-pilot next-step counters to the memo snapshot for start-paid, extend, downgrade, archive, churn, not-decided, and missing follow-up. Backend pipeline 2631197648 and web-admin pipeline 2631197649 succeeded on integration, and smoke verification confirmed the deployed admin bundle contains the new labels.
  • Backend integration commit 63565bc and web-admin integration commit e3e3f20 add batch-scoped activation gap counters to the memo snapshot for batched pilots missing matched users, owner-only readiness, 3+ workflows, or tenant-task evidence. Backend pipeline 2631248886 and web-admin pipeline 2631248812 succeeded on integration, and smoke verification confirmed the deployed admin bundle contains the new labels.
  • Backend integration commit 7e70f61 and web-admin integration commit 9d2f528 add batch-scoped refusal/churn blocker completeness counters to the memo snapshot. Backend pipeline 2631299011 and web-admin pipeline 2631298985 succeeded on integration, and smoke verification confirmed the deployed admin bundle contains the new blocker labels while the protected backend summary route returned the expected unauthenticated 401.
  • Backend integration commit 2dd46e4 and web-admin integration commit 8cc0ecf add row-level action queue filtering for batch, pricing, post-pilot, outcome, and refusal-blocker follow-up. Backend pipeline 2631380073 and web-admin pipeline 2631380022 succeeded on integration, and smoke verification confirmed the deployed admin bundle contains the action queue labels while the protected backend list route with pilotAction=NEEDS_PRICING returned the expected unauthenticated 401.
  • Backend integration commit 4e794be and web-admin integration commit 36bc273 add the Needs interview action queue for accepted applicants missing landlord interview evidence. Backend pipeline 2632706952, web-admin pipeline 2632706932, and AWS Amplify job 65 succeeded on integration, and smoke verification confirmed deployed bundle index-BpjH9HBy.js contains the queue labels while the protected backend list route with pilotAction=NEEDS_INTERVIEW returned the expected unauthenticated 401. Real pilot entries are still required before this memo can be completed.
  • Backend integration commit cd5a697, backend coverage follow-up c6d1406, and web-admin integration commit 39b5d29 add completed landlord/tenant interview counters and Batch 1 interview counters to the memo evidence path. Backend pipeline 2631782983 and web-admin pipeline 2631761550 succeeded on integration, AWS Amplify job 52 published the admin bundle, and smoke verification confirmed the deployed bundle contains the new interview labels while the protected backend summary route returned the expected unauthenticated 401. Real pilot entries are still required before this memo can be completed.
  • web-admin integration commit 98eca3b adds a computed Memo readiness metric and a Memo Readiness table to Copy memo snapshot. The table maps existing Batch 1, activation, pricing, support, tenant-task, outcome, and refusal/churn counters to missing, review, or ready rows, plus the overall memo readiness state. web-admin pipeline 2631817891 succeeded on integration, AWS Amplify job 53 published the admin bundle, and smoke verification confirmed the deployed bundle contains Memo readiness, ## Memo Readiness, First onboarding batch, and Overall memo readiness while the protected backend summary route returned the expected unauthenticated 401. Real pilot entries are still required before this memo can be completed.
  • web-admin integration commit d43ccac adds the Founding Pilot Load evidence toolbar action for bulk-loading visible rows when previewing activation evidence. web-admin pipeline 2631853329 succeeded on integration, AWS Amplify job 54 published the admin bundle, and smoke verification confirmed the deployed bundle contains Load activation evidence for visible pilots, Loaded activation evidence for, and Copy activation log while the protected backend summary route returned the expected unauthenticated 401. Real pilot activation evidence is still required before this memo can be completed.
  • web-admin integration commit 5fd6e6e makes Copy activation log export all matching founding-pilot pages, load missing activation evidence, and include a Rows exported count. web-admin pipeline 2632137296 succeeded on integration, AWS Amplify job 63 published the admin bundle, and smoke verification confirmed the deployed bundle contains the activation full-export markers while the protected backend list and activation-evidence routes returned the expected unauthenticated 401. Real pilot activation evidence is still required before this memo can be completed.
  • web-admin integration commit f89df80 makes Copy pricing log include Batch 1 participants with missing pricing responses as not_asked rows, so pricing gaps remain visible when reconciling the scorecard and final memo. web-admin pipeline 2631878561 succeeded on integration, AWS Amplify job 55 published the admin bundle, and smoke verification confirmed the deployed bundle contains the pricing snapshot strings while the protected backend summary route returned the expected unauthenticated 401. Real pilot pricing answers are still required before this memo can be completed.
  • web-admin integration commit 15eb1cf makes Copy batch log include accepted applicants missing Batch 1 status as empty rows and normalizes Wrocław city values to wroclaw. web-admin pipeline 2631905926 succeeded on integration, AWS Amplify job 56 published the admin bundle, and smoke verification confirmed the deployed bundle contains the batch snapshot strings while the protected backend summary route returned the expected unauthenticated 401. Real pilot onboarding evidence is still required before this memo can be completed.
  • web-admin integration commit 34550f3 makes Copy batch log export all matching founding-pilot pages and include a Rows exported count. web-admin pipeline 2632108038 succeeded on integration, AWS Amplify job 62 published the admin bundle, and smoke verification confirmed the deployed bundle contains the batch full-export markers while the protected backend list route returned the expected unauthenticated 401. Real pilot onboarding evidence is still required before this memo can be completed.
  • web-admin integration commit 2611d67 adds Copy outcome log, an anonymized Batch 1 outcome/support snapshot for 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. web-admin pipeline 2631937361 succeeded on integration, AWS Amplify job 57 published the admin bundle, and smoke verification confirmed the deployed bundle contains the outcome snapshot strings while the protected backend summary route returned the expected unauthenticated 401. Real pilot outcome and support evidence is still required before this memo can be completed.
  • web-admin integration commit 07d4e13 adds Copy action queue, an anonymized Markdown snapshot for the selected Founding Pilot action queue. web-admin pipeline 2631996084 succeeded on integration, AWS Amplify job 58 published the admin bundle, and smoke verification confirmed the deployed bundle contains the action-queue snapshot strings while the protected backend summary route returned the expected unauthenticated 401. Real pilot row cleanup and final evidence are still required before this memo can be completed.
  • web-admin integration commit 0bbbd74 makes Copy action queue export all selected queue pages and include a Rows exported count. web-admin pipeline 2632024385 succeeded on integration, AWS Amplify job 59 published the admin bundle, and smoke verification confirmed the deployed bundle contains the full-export marker while the protected backend summary route returned the expected unauthenticated 401. Real pilot row cleanup and final evidence are still required before this memo can be completed.
  • web-admin integration commit 98ff1bc makes Copy pricing log export all matching founding-pilot pages and include a Rows exported count. web-admin pipeline 2632061405 succeeded on integration, AWS Amplify job 60 published the admin bundle, and smoke verification confirmed the deployed bundle contains the pricing full-export markers while the protected backend list route returned the expected unauthenticated 401. Real pilot pricing answers and final evidence are still required before this memo can be completed.
  • web-admin integration commit 0db165b makes Copy outcome log export all matching founding-pilot pages and include a Rows exported count. web-admin pipeline 2632085157 succeeded on integration, AWS Amplify job 61 published the admin bundle, and smoke verification confirmed the deployed bundle contains the outcome full-export markers while the protected backend list route returned the expected unauthenticated 401. Real pilot outcome, support, and refusal/churn evidence are still required before this memo can be completed.