Skip to content

Pilot Onboarding Batch Log

Date: 2026-06-25

Status: Ready execution log for EP10-T6. This does not complete EP10-T6 until real pilot landlords are accepted, onboarded, and measured.

Related pilot ops: Founding pilot ops

Related scorecard: Pilot scorecard

Related outreach list: Founding pilot outreach list

Related backlog: Pre-release delivery epics

Purpose

This log is the source of record for the first Founding Landlord Program onboarding batch.

Use it after outreach and interviews produce accepted pilot landlords. Do not count demos, seed data, internal test accounts, or founder-entered substitute work as activation evidence.

Batch 1 Status

Field Value
Batch status not_started
Target landlord count 3-5
Accepted landlords 0
Kickoffs completed 0
Landlords with one real lease in product 0
Landlords with property setup complete 0
Landlords with lease setup complete 0
Landlords with one document/evidence artifact uploaded 0
Landlords with rent schedule or payment-follow-up workflow created 0
Landlords with three real target workflows completed 0
Current blocker No real pilot landlords accepted yet.
Next Product Owner action Contact EP10-T5 outreach targets and schedule landlord interviews.

Batch Start Rule

Start Batch 1 only when all conditions are true:

  • 3-5 landlords are accepted into the pilot
  • every accepted landlord has a participant ID in the scorecard
  • every accepted landlord has at least one real lease or transition event ready
  • every accepted landlord has agreed to weekly check-ins
  • no active support stop condition is open
  • the Product Owner can attend every kickoff personally

If fewer than three accepted landlords are ready, continue interviews and do not start the batch. If more than five are ready, waitlist the excess until support load from the first batch is known.

Admin Intake Support

The web-admin Founding Pilot view shows a readiness strip above the applicant table. The first metric, applicants on page, is page-scoped; the remaining validation metrics come from the backend summary across all founding-pilot applicants:

  • applicants on the current page
  • 2-10 unit applicants
  • real-lease confirmations
  • batch-ready applicants
  • accepted applicants
  • accepted batch-ready applicants
  • completed landlord interviews
  • completed tenant interviews
  • pilot batch records
  • kickoff scheduled
  • week 1 active
  • paused/exited batch records
  • batch landlord interviews
  • batch tenant interviews
  • 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
  • memo matched users
  • memo owner-only ready
  • memo 3+ workflows
  • memo tenant-task participants
  • memo tenant-task completions
  • batch outcomes recorded
  • batch outcomes missing
  • batch refused/churned
  • batch support watch/stop
  • batch P0/P1 incidents
  • batch support hours

Each applicant row also shows a Pilot readiness label. A lead is Ready for batch only when they are in the 2-10 unit band and confirmed willingness to move a real lease. Use this as an operational filter before copying accepted participants into the batch rows below.

Admin reviewers can now record per-applicant review state directly in the Founding Pilot table:

  • pilotDecision: ACCEPTED, WAITLIST, NURTURE, DECLINED, or NOT_FIT
  • landlordScore: whole number from 0 to 10
  • reviewNote: short internal review note
  • reviewedAt: backend timestamp from the latest saved review

Use ACCEPTED only for landlords the Product Owner has approved for Batch 1. Do not treat Ready for batch alone as acceptance evidence.

The admin list can be filtered by review decision. Use the ACCEPTED filter as the source view for copying approved landlords into the participant rows. Use WAITLIST, NURTURE, DECLINED, and NOT_FIT filters to keep non-batch leads out of Batch 1 planning.

The Founding Pilot toolbar also has an action queue filter for finding the specific rows behind the aggregate readiness gaps:

  • Needs batch: accepted applicant has no saved Batch 1 status
  • Needs interview: accepted applicant has no saved landlord interview timestamp
  • Needs pricing: batched applicant still has no pricing response
  • Needs post-pilot: pricing response exists but post-pilot next step is empty
  • Needs outcome: post-pilot next step exists but final pilot outcome is empty
  • Needs refusal blocker: refused or churned batched applicant is missing a blocker code or short outcome note

Use Needs batch while filling the Batch 1 rows. Use Needs interview before starting or expanding Batch 1 so accepted applicants do not bypass the landlord interview evidence gate. Use the other queues during pricing and memo closeout so aggregate "missing" counters can be resolved at row level. After filtering a queue, use Copy action queue to copy an anonymized worklist with participant ID, queue reason, review decision, batch status, pricing response, post-pilot next step, outcome, blocker code, and next action. The queue snapshot excludes applicant names, emails, phone numbers, free-form intake messages, review notes, and support case identifiers. The copy action reloads every page in the selected queue before copying and includes a Rows exported count, so a queue larger than the visible admin page is not mistaken for a complete worklist.

Before acceptance, use the admin qualification counters and row details to prioritize applicants. The Founding Pilot admin view now shows global counts for self-managed applicants, artifact-ready applicants, pilot-committed applicants, and fully qualified applicants. A fully qualified applicant has 2-10 units, is self-managed or mixed-management, is willing to show real artifacts, can move a real lease, can activate two live units within 30 days, can join weekly check-ins, gives testimonial/case-study consent, and consents to pilot contact.

Admin reviewers can also record per-applicant Batch 1 execution state directly in the Founding Pilot table:

  • pilotParticipantId: anonymized participant ID, for example PILOT-001
  • pilotBatchStatus: ACCEPTED, KICKOFF_SCHEDULED, KICKOFF_DONE, WEEK_1_ACTIVE, THIRTY_DAY_ACTIVE, PAUSED, or EXITED
  • pilotBatchAcceptedAt: acceptance timestamp
  • pilotKickoffAt: kickoff timestamp
  • pilotFirstWorkflow: first target workflow
  • pilotCurrentBlocker: current onboarding blocker
  • pilotNextAction: next Product Owner action
  • pilotBatchRecordedAt: backend timestamp from the latest saved batch update

Use the admin row as the live operational source for per-applicant batch state. Copy only anonymized participant IDs and non-PII status notes into the docs rows below when preparing weekly reviews.

Admin reviewers can also record completed interview evidence directly in the Founding Pilot table:

  • landlordInterviewCompletedAt: landlord interview completion timestamp
  • tenantInterviewCompletedAt: tenant interview completion timestamp, only when tenant evidence is in scope
  • pilotInterviewsRecordedAt: backend timestamp from the latest saved interview evidence update

Use these timestamps to reconcile the scorecard's completed landlord/tenant interview rows before starting or expanding Batch 1. Interview counts alone do not complete EP10-T6; they only prove that the pre-batch evidence is no longer being tracked manually.

The Founding Pilot toolbar includes Copy interview log, which copies an anonymized Markdown snapshot from rows that have landlord, tenant, or recorded interview timestamps. The snapshot includes participant ID, source row, city band, unit-count band, batch status, landlord interview date, tenant interview date, interview recorded date, and next action. It excludes applicant names, emails, phone numbers, free-form intake messages, review notes, and interview notes. Before copying, the admin reloads every page matching the active founding-pilot filters and includes Rows exported, so interview reconciliation is not capped to the visible admin page.

The Founding Pilot toolbar includes Copy batch log, which copies an anonymized Markdown snapshot from the loaded batch rows. The snapshot uses only participant ID, source row, city band, unit-count band, accepted date, kickoff date, first workflow, batch status, current blocker, and next action. It intentionally excludes applicant names, emails, phone numbers, free-form messages, review notes, and other raw lead details. Before copying, the admin reloads every page matching the active founding-pilot filters and includes Rows exported, so Batch 1 reconciliation is not capped to the visible admin page.

For accepted applicants that still have no saved Batch 1 status, Copy batch log also includes the row with batch status empty. Use this from the Needs batch queue so accepted-but-unbatched gaps remain visible in this log instead of being omitted from the snapshot. Wrocław city values are normalized to the wroclaw city band in copied snapshots.

Each applicant row also has an on-demand activation evidence control. Use Evidence only after the accepted applicant has created or been matched to a real app account. The control matches the intake email to an app user and shows per-applicant counts for:

  • matched app user and role
  • owner-only activation readiness
  • property setup
  • active lease setup
  • active rent schedule setup
  • payment request and payment receipt evidence
  • tenant invite evidence
  • tenant task completions: accepted tenant invite, tenant handover confirmation/decline, tenant final-settlement confirmation/decline, tenant-authored lease message, tenant-uploaded evidence, or tenant-submitted support report
  • handover evidence
  • document/evidence uploads
  • deposit/final-settlement evidence
  • lease message and payment-reminder evidence
  • in-app problem/support reports, including total, open, in-progress, resolved, and dismissed counts for the matched owner account plus tenant users linked to that owner's leases
  • workflow-count categories with at least one real record

Copy only anonymized participant IDs and counts from this evidence into the Activation Log. Do not copy raw emails, user IDs, addresses, document names, rent amounts, or tenant data into this docs repo.

The Founding Pilot toolbar also includes Load evidence, which bulk-loads activation evidence for all currently visible applicant rows that are not already loaded. Use it when previewing activation evidence on the current admin page. This uses the same per-row evidence endpoint and does not change the anonymized snapshot fields copied into this docs repo.

Use Copy activation log to copy an anonymized Markdown snapshot for the Activation Log. Before copying, the admin reloads every page matching the active founding-pilot filters, loads missing per-row activation evidence, and includes Rows exported, so activation reconciliation is not capped to the visible admin page. The snapshot includes participant ID, property setup, lease setup, document/evidence, rent schedule, payment proof, handover, tenant invite, tenant task, issue report, deposit/settlement, message/reminder, and total workflow count. The deposit/settlement and message/reminder cells are measured by the activation evidence endpoint. Tenant invite is owner-created invite volume; tenant task is tenant-side completion volume from the concrete actions listed above. The cohort-level Memo 3+ workflows summary counter uses the same deposit/settlement and message/reminder workflow categories as the row-level activation evidence, so the weekly review and final memo do not undercount real pilot usage in those areas.

Participant Rows

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 Source row City band Unit count band Accepted date Kickoff date First real workflow Batch status Current blocker Next action
PILOT-001 empty Awaiting accepted landlord.
PILOT-002 empty Awaiting accepted landlord.
PILOT-003 empty Awaiting accepted landlord.
PILOT-004 empty Optional capacity slot.
PILOT-005 empty Optional capacity slot.

Allowed batch statuses:

  • empty in this docs table only, when no admin batch status is saved yet
  • ACCEPTED
  • KICKOFF_SCHEDULED
  • KICKOFF_DONE
  • WEEK_1_ACTIVE
  • THIRTY_DAY_ACTIVE
  • PAUSED
  • EXITED

Kickoff Checklist

Complete this checklist for every accepted participant.

Step Required evidence Done
Confirm eligibility and no excluded workflow Scorecard participant row has pilot_decision=accepted.
Confirm one real lease or transition event Participant confirms artifact exists before kickoff.
Confirm legal boundary Participant accepts MamNajem does not provide legal advice.
Confirm support channel Participant knows in-app report and support email path.
Create or allow account Account is available for kickoff.
Set up first property Real property exists in product.
Set up first lease or transition event Real lease/transition event is represented in product.
Add document or evidence artifact At least one real artifact is uploaded or attached.
Create rent schedule or payment-follow-up workflow Schedule/reminder/follow-up exists in product.
Decide tenant invite timing Owner-only value path and tenant timing are recorded.
Record first-week target Next unit or workflow is recorded.
Schedule weekly check-in Date/time or written-update deadline is set.

Activation Log

Count only real workflows.

Participant ID Property setup Lease setup Document/evidence Rent schedule Payment proof Handover Tenant invite Tenant task Issue report Deposit/settlement Message/reminder Workflow count
PILOT-001 0 0 0 0 0 0 0 0 0 0 0 0
PILOT-002 0 0 0 0 0 0 0 0 0 0 0 0
PILOT-003 0 0 0 0 0 0 0 0 0 0 0 0
PILOT-004 0 0 0 0 0 0 0 0 0 0 0 0
PILOT-005 0 0 0 0 0 0 0 0 0 0 0 0

Blocker Log

Use one row per onboarding blocker.

Date Participant ID Blocker type Severity Product area Owner Resolution target Status Note
activation / tenant / support / legal / privacy / pricing / product / habit P0 / P1 / P2 / P3 open / closed

Weekly Batch Review

Use this table before the weekly pilot review.

Metric Week 1 Week 2 Week 3 Week 4 Decision note
Accepted landlords 0
Kickoffs completed 0
Live units in product 0
Landlords with owner-only activation 0
Landlords with 3+ workflows 0
Tenant task completions 0
Support requests 0
P0/P1 support items 0
Price discussions completed 0
Batch decision continue / narrow / pause / stop

EP10-T6 Completion Rule

EP10-T6 can be marked complete only when:

  • Batch 1 has 3-5 accepted real pilot landlords, or the Product Owner documents why a smaller batch is the only supportable start
  • each accepted landlord brings at least one real lease or transition event
  • each accepted landlord completes property setup
  • each accepted landlord completes lease setup
  • each accepted landlord uploads at least one document or evidence artifact
  • each accepted landlord creates a rent schedule or payment-follow-up workflow
  • each accepted landlord completes at least three real target workflows during the pilot, or exits with an exact blocker reason
  • blocker notes are recorded in this log and the scorecard

Evidence

This document is an EP10-T6 execution aid only. It records that Batch 1 is ready to run once real pilot landlords are accepted, but it does not claim the first pilot onboarding batch has happened.

Implementation support:

  • backend integration commit f42e9cf adds persistent applicant review state, the admin PATCH /v1/admin/founding-pilot-intake/{id}/review endpoint, OpenAPI contract, migration constraints, and integration coverage.
  • web-admin commit f8c411b adds Founding Pilot batch-readiness metrics and row-level readiness labels for the existing admin intake list.
  • web-admin integration commit 75fe580 adds review controls, accepted-count metric, API client coverage, and admin app coverage for saving pilot review decisions.
  • backend integration commit 2babd1f and web-admin integration commit a97825a add review-decision filtering so the Product Owner can isolate ACCEPTED applicants before filling Batch 1 participant rows.
  • 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 integration commit 3a14d26 and web-admin integration commit 63d8f20 add batch-scoped outcome/support summary counters and memo rows for outcomes recorded, outcomes missing, refused/churned participants, support watch/stop status, P0/P1 incidents, and support hours.
  • backend integration commit 12de0d8 and web-admin integration commit 1dc76b7 add a global Founding Pilot validation summary for Batch 1 readiness and pricing-test evidence.
  • backend integration commit 0fd5f95 and web-admin integration commit 0c74ae2 add per-applicant activation evidence so the Product Owner can verify matched account, owner-only readiness, workflow counts, and blocker signals before copying anonymized counts into this log.
  • backend integration commit 3a5302c and web-admin integration commit 41144cc extend that evidence with in-app support-load status counts for the matched owner account and linked tenant accounts.
  • backend integration commit 198b293 and web-admin integration commit 9a6ac48 add admin outcome/support fields for copying the reviewed support log into the intake entry: final outcome, refusal/churn blocker, P0/P1 counts, support hours, and support status.
  • backend integration commit 5f5ee63 and web-admin integration commit 8eb3ad8 add persistent per-applicant Batch 1 state, the admin PATCH /v1/admin/founding-pilot-intake/{id}/batch endpoint, OpenAPI contract coverage, admin summary counters for batch status, and web-admin controls for participant ID, status, accepted/kickoff timestamps, first workflow, blocker, and next action.
  • web-admin integration commit 70ebd60 adds Copy batch log, an anonymized Markdown snapshot action for the loaded Founding Pilot batch rows, so Batch 1 docs rows can be updated from participant IDs, city/unit bands, dates, workflow, status, blocker, and next-action fields without copying applicant PII.
  • web-admin integration commit 15eb1cf makes Copy batch log include accepted applicants that do not yet have a saved Batch 1 status as empty rows, and normalizes Wrocław to the wroclaw city band, so Needs batch gaps can be copied into this log without applicant PII.
  • web-admin integration commit 5f3de7d adds Copy activation log, an anonymized Markdown snapshot action for loaded per-applicant activation evidence, so Activation Log rows can be copied from participant IDs and measured app-backed counts without copying applicant PII or matched user IDs.
  • web-admin integration commit d43ccac adds Load evidence, a toolbar action that bulk-loads activation evidence for visible Founding Pilot rows before Copy activation log, so batch reconciliation no longer requires clicking Evidence on every row.
  • web-admin integration commit 5fd6e6e makes Copy activation log reload every matching founding-pilot page, load missing activation evidence, and add Rows exported, so Activation Log rows are not capped at the visible admin page.
  • backend integration commit 81f24bc adds measured deposit/settlement and message/reminder counters to per-applicant activation evidence and includes those categories in the activation workflow count.
  • web-admin integration commit f039241 exports those measured deposit/settlement and message/reminder counts in Copy activation log snapshots while retaining not_measured as a fallback for older backend responses.
  • backend integration commit d2529ed and web-admin integration commit 6f6f2be add tenant-task completion counts to row-level activation evidence, split Copy activation log into separate tenant invite and tenant task columns, and add memo tenant-task participant/completion counters.
  • backend integration commit 2dd46e4 and web-admin integration commit 8cc0ecf add the Founding Pilot action queue filter so the Product Owner can isolate rows that need batch, pricing, post-pilot, outcome, or refusal blocker follow-up.
  • backend integration commit 4e794be and web-admin integration commit 36bc273 add the Needs interview action queue so accepted applicants missing landlord interview evidence can be isolated before Batch 1 starts or expands.
  • web-admin integration commit 07d4e13 adds Copy action queue, an anonymized Markdown snapshot for the selected Founding Pilot action queue. It copies participant ID, queue reason, review decision, batch status, pricing response, post-pilot next step, outcome, blocker code, and next action without applicant PII or support case identifiers.
  • web-admin integration commit 0bbbd74 makes Copy action queue reload all pages for the selected action queue at the backend's 100-row page cap and add Rows exported to the snapshot, so copied worklists are not limited to the visible admin page.
  • web-admin integration commit 34550f3 makes Copy batch log reload every matching founding-pilot page at export size and add Rows exported, so Batch 1 logs are not capped at the visible admin page.
  • backend integration commit cd5a697, backend coverage follow-up c6d1406, and web-admin integration commit 39b5d29 add row-level landlord/tenant interview timestamps, global completed-interview counters, Batch 1 completed-interview counters, and admin controls for saving interview evidence.
  • web-admin integration commit 60ee151 adds Copy interview log, an anonymized full-export snapshot for row-level landlord/tenant interview evidence.

Deployment evidence:

  • backend pipeline 2629703531 succeeded for f42e9cf on integration.
  • web-admin pipeline 2629716193 succeeded for 75fe580 on integration.
  • backend pipeline 2629749586 succeeded for 2babd1f on integration.
  • web-admin pipeline 2629758524 succeeded for a97825a on integration.
  • backend pipeline 2630258855 succeeded for 81f24bc on integration.
  • web-admin pipeline 2630268247 succeeded for f039241 on integration.
  • backend pipeline 2631162540 succeeded for d2529ed on integration.
  • web-admin pipeline 2631162539 succeeded for 6f6f2be on integration.
  • backend pipeline 2631380073 succeeded for 2dd46e4 on integration.
  • web-admin pipeline 2631380022 succeeded for 8cc0ecf on integration.
  • backend pipeline 2631782983 succeeded for c6d1406 on integration.
  • web-admin pipeline 2631761550 succeeded for 39b5d29 on integration.
  • backend pipeline 2632706952 succeeded for 4e794be on integration.
  • web-admin pipeline 2632706932 succeeded for 36bc273 on integration.
  • web-admin pipeline 2631853329 succeeded for d43ccac on integration.
  • web-admin pipeline 2631905926 succeeded for 15eb1cf on integration.
  • web-admin pipeline 2632108038 succeeded for 34550f3 on integration.
  • web-admin pipeline 2632137296 succeeded for 5fd6e6e on integration.
  • web-admin pipeline 2632684605 succeeded for 60ee151 on integration.
  • AWS Amplify job 52 succeeded for 39b5d29 on the integration admin branch.
  • AWS Amplify job 54 succeeded for d43ccac on the integration admin branch.
  • AWS Amplify job 56 succeeded for 15eb1cf on the integration admin branch.
  • AWS Amplify job 62 succeeded for 34550f3 on the integration admin branch.
  • AWS Amplify job 63 succeeded for 5fd6e6e on the integration admin branch.
  • AWS Amplify job 64 succeeded for 60ee151 on the integration admin branch.
  • AWS Amplify job 65 succeeded for 36bc273 on the integration admin branch.
  • Integration smoke loaded https://integration.mamnajem.pl/v1/subscriptions/plans through agent-browser and confirmed the protected review route returns 401 without admin auth. Full review-form verification requires admin credentials.
  • Integration smoke loaded https://admin-integration.mamnajem.pl/#founding-pilot through agent-browser and reached the admin sign-in screen. Full review-form verification requires admin credentials.
  • Integration smoke loaded https://admin-integration.mamnajem.pl/?v=f039241b#founding-pilot through agent-browser, confirmed the deployed admin bundle contains depositSettlementCount, messageReminderCount, deposit/settlement item, and message/reminder item, and confirmed the protected activation evidence route returns 401 without admin auth.
  • Integration smoke loaded https://admin-integration.mamnajem.pl/?v=6f6f2be#founding-pilot through agent-browser, confirmed the deployed admin bundle contains tenantTaskCount, Memo tenant-task participants, Memo tenant-task completions, Tenant task completions, and the split Tenant invite | Tenant task snapshot header, and confirmed the protected backend summary route returns 401 without admin auth.
  • Integration smoke loaded https://admin-integration.mamnajem.pl/?v=8cc0ecf#founding-pilot, confirmed the deployed admin bundle contains Founding pilot action queue, all five action labels, and pilotAction, and confirmed the protected backend list route with pilotAction=NEEDS_PRICING returns 401 without admin auth.
  • Integration smoke loaded https://admin-integration.mamnajem.pl/?v=39b5d29-browser#founding-pilot, confirmed the deployed admin bundle index-CLFya2Pu.js contains Save pilot interviews, Completed landlord interviews, Batch landlord interviews, and the /interviews API path, and confirmed the protected backend summary route returns 401 without admin auth.
  • Integration smoke loaded https://admin-integration.mamnajem.pl/?v=d43ccac-browser#founding-pilot, reached the admin sign-in screen, confirmed the deployed admin bundle index-_jUIho0J.js contains Load activation evidence for visible pilots, Loaded activation evidence for, and Copy activation log, and confirmed the protected backend summary route returns 401 without admin auth.
  • Integration smoke loaded https://admin-integration.mamnajem.pl/?v=15eb1cf-browser#founding-pilot, reached the admin sign-in screen, confirmed the deployed admin bundle index-hCfaL1PJ.js contains Copy batch log, Pilot Batch Log Snapshot, empty, the accepted-row predicate, and wroclaw, and confirmed the protected backend summary route returns 401 without admin auth.
  • Integration smoke loaded https://admin-integration.mamnajem.pl/?v=34550f3-browser#founding-pilot, reached the admin sign-in screen, confirmed the deployed admin bundle contains Copy batch log, Pilot Batch Log Snapshot, Rows exported:, Batch status, and Current blocker, and confirmed the protected backend list route returns 401 without admin auth.
  • Integration smoke loaded https://admin-integration.mamnajem.pl/?v=5fd6e6e-browser#founding-pilot, reached the admin sign-in screen, confirmed the deployed admin bundle contains Copy activation log, Pilot Activation Log Snapshot, Rows exported:, Deposit/settlement, Message/reminder, and activation-evidence, and confirmed the protected backend list and activation-evidence routes return 401 without admin auth.
  • Integration smoke loaded https://admin-integration.mamnajem.pl/?v=60ee151-browser#founding-pilot, reached the admin sign-in screen, confirmed the deployed admin bundle contains Copy interview log, Copy founding pilot interview log snapshot, and Pilot Interview Log Snapshot, and confirmed the protected backend summary route returns 401 without admin auth.
  • Integration smoke loaded https://admin-integration.mamnajem.pl/?v=36bc273-browser#founding-pilot, reached the admin sign-in screen, confirmed the deployed admin bundle index-BpjH9HBy.js contains NEEDS_INTERVIEW, Needs interview, and Accepted applicant is missing landlord interview evidence, and confirmed the protected backend list route with pilotAction=NEEDS_INTERVIEW returns 401 without admin auth.