Skip to content

Pre-Release Charter

Date: 2026-06-12

Status: Approved for first paid pilot scope.

Source audit: Pre-Release Strategy And Scope Audit

Execution backlog: Pre-Release Delivery Epics And Tasks

Release Decision

MamNajem will not run a broad public paid launch before the founding pilot passes the release gates in this charter.

The first release is a controlled founding pilot for self-managing Polish landlords. Public launch can happen only after the pilot proves that landlords move real leases into the product, use the core workflows, accept realistic pricing, and can be supported without developer intervention.

First ICP

The first buyer is a self-managing Polish landlord with 2-5 active long-term residential rental units.

Secondary fit is a 6-10 unit self-manager if activation and willingness to pay hold during the pilot.

Initial geography:

  • Warsaw
  • Krakow
  • Wroclaw
  • Trojmiasto
  • Poznan

The tenant is a workflow participant, not the buyer. Property managers, agencies, PRS operators, short-term rental operators, and accounting-heavy portfolio teams are not the first release audience.

First Paid Promise

For a self-managing Polish landlord with 2-10 flats, MamNajem keeps every active lease organized from a phone:

  • property and lease setup
  • tenant invite
  • document vault
  • rent schedule
  • payment proof and mark-paid tracking
  • handover protocol
  • messages
  • reminders
  • final settlement evidence
  • simple in-app support/problem report submission when a tenant or owner needs support with the app or a rental workflow

The product may support more internally, but public copy must stay inside this promise until pilot evidence says otherwise.

In Scope

The first paid pilot may include:

  • owner-first onboarding and activation
  • property setup
  • lease setup
  • tenant invitation
  • document upload and organization
  • off-ledger rent tracking with payment proof and manual paid status
  • handover protocol and confirmation
  • final settlement support
  • basic owner/tenant messaging
  • reminders through supported delivery channels
  • support/problem report submission with OPEN and IN_PROGRESS treated as open support work, and RESOLVED and DISMISSED treated as closed support work
  • admin support tooling for allowlist, account diagnostics, problem reports, processed webhooks, and Stripe webhooks
  • Stripe web billing for subscriptions
  • founding pilot intake and qualification
  • pricing test for fixed monthly landlord SaaS plans

Out Of Scope

These are explicit non-goals for the first release:

  • property-manager suite
  • agency/team/accountant delegation workflows
  • legal notice automation
  • eviction automation
  • app-store-first billing
  • rent take-rate
  • marketplace/listing syndication
  • tenant screening
  • lease-linked repair management, contractor assignment, responsibility resolution, and full vendor maintenance suite
  • embedded BLIK/P24/PayU/Tpay rent collection
  • direct legal advice or legal guarantee
  • custom builds for a single large customer

Pricing And Pilot Posture

The public acquisition surface should be a 30-day no-card trial, not a permanent free tier. After the trial, users should choose a paid plan or fall back to read-only Archive.

Public pricing direction:

Plan Price Active property cap Active tenant cap
Solo 19.99 PLN gross/month 3 10
Portfolio 49.99 PLN gross/month 10 35
Plus 99.99 PLN gross/month 25 100

Archived properties, leases, and tenants do not count toward caps. Cap behavior: soft-warning at 80%, immediate hard-block for new creates over cap, 14-day grace only for migration or downgrade overages, and never remove access to already-created records.

The Founding Landlord Program is separate from public pricing:

  • first roughly 50 qualified landlords
  • 90 days free
  • migration help
  • 12-month founding price lock after pilot
  • 2-10 self-managed units
  • at least two live units activated within 30 days
  • weekly pilot check-in
  • testimonial or case-study consent

Owner-Only Activation

The first value path must not depend on tenant adoption.

Owner activation means the landlord can create meaningful operational value by setting up a property, lease, documents, rent schedule, handover information, and reminders before a tenant accepts an invite.

Tenant participation remains important, but tenant conversion cannot be the first proof that the product is useful.

Launch Rent Payment Posture

The first paid pilot uses off-ledger rent tracking only for tenant rent. MamNajem must not present embedded Stripe rent checkout as the default public rent-payment workflow.

Launch rent payment UX must prioritize:

  • landlord bank-transfer instructions
  • amount and due date
  • payment reference or title
  • tenant proof upload when payment evidence is needed
  • owner mark-paid and receipt tracking
  • reminders, overdue visibility, audit trail, and final settlement evidence

Stripe remains in scope for landlord SaaS subscription billing and internal webhook/support infrastructure. Stripe Connect rent checkout may remain in the codebase as a future optional pilot path, but the first paid pilot must hide or feature-flag it from ordinary tenant rent-payment UX unless Product Owner, legal, backend, and frontend explicitly approve a later embedded-collection pilot.

This decision satisfies the Off-ledger rent default accepted release gate for the first paid pilot. The payment-request implementation now makes bank transfer/proof the default tenant surface and hides Stripe rent checkout from public launch surfaces unless EXPO_PUBLIC_RENT_STRIPE_CHECKOUT_ENABLED=true explicitly enables a later pilot.

Release Gates

Gate Owner Evidence required Status
Charter approved Product Owner This document exists, links to the audit/backlog, and has approval note. Pass
Public positioning narrowed Product Owner, Designer Landing targets self-managing Polish landlords and removes broad manager/tenant-first positioning. Pass
Pricing and founder offer ready Product Owner, Designer, Frontend Developer Pricing, trial, caps, Archive fallback, and Founding Landlord Program copy are ready to publish. Pass
Pilot intake ready Product Owner, Frontend Developer, Backend Developer Intake captures city, unit count, self-managed status, current tools, live workflow timing, artifact readiness, and pilot commitment. Pass
Owner activation measurable Product Owner, Frontend Developer, Backend Developer Activation events are stored through POST /v1/activation-events; the web-admin Activation page is backed by GET /v1/admin/activation-overview, with weekly Product Owner review notes recorded in Activation event taxonomy. Pass
Legal review complete Product Owner Polish counsel review notes are recorded in Legal review response log, required product/copy changes are merged, and launch copy/workflows reflect the review. Open
Handover/deposit/settlement accepted Product Owner, Designer, Backend Developer, Frontend Developer Pilot-ready requirements are accepted in Handover, deposit, and final settlement release requirements; Epic 4 delivered confirmed protocol immutability, deposit ledger/refund reminders, final settlement statement hardening, and settlement evidence export. Pass
Off-ledger rent default accepted Product Owner, Designer, Backend Developer, Frontend Developer Public UX defaults to IBAN/proof/reminders/mark-paid; rent take-rate remains out of launch scope. Pass
Email delivery working Backend Developer, Infra Developer SES production access, sender domain, and simulator send are verified in Email infrastructure verification; backend delivery and workflow wiring are deployed to integration in Email delivery implementation and Email workflow wiring. Disposable workflow-level delivery smoke passed on integration with CloudWatch provider message id evidence. Pass
Admin support usable Product Owner, Backend Developer, Frontend Developer Admin allowlist, problem report triage/photo download, processed webhook lookup, Stripe webhook replay, support macros, and support operating procedure are verified in Admin allowlist contract verification, Problem report triage verification, Stripe webhook recovery verification, Pilot support macros, and Pilot support operating procedure. Pass
Privacy and retention aligned Product Owner, Backend Developer, Infra Developer Policy, export/delete behavior, bank-account protection, and retention automation decisions are consistent. EP8-T1 IBAN decision and EP8-T2 transfer-instruction implementation are recorded in IBAN storage policy decision. EP8-T3 retention periods, no-automation-before-pilot decision, active/pending lease deletion block, and legal/tax evidence exceptions are recorded in retention policy alignment. Pass
Production readiness checked Infra Developer Backups, alarms, admin auth, domains, release hygiene, and rollback procedure verified. EP8-T4 database recovery policy is recorded in production database recovery policy; EP8-T5 RDS alarm lookup is recorded in RDS alarm verification; EP8-T6 admin auth hardening is recorded in Admin Cognito hardening; EP8-T7 integration domains are recorded in Integration domain consistency; EP8-T8 release hygiene is recorded in Release worktree checklist. Pass
Pilot completed Product Owner Scorecard and go/narrow/stop memo show real workflow migration, owner activation, price acceptance, and support load. Open

Public Launch Rule

Public launch is allowed only if all P0 gates pass and the pilot memo says go.

If the memo says narrow, public launch is blocked until the narrowed scope is written into this charter and the affected gates are rechecked.

If the memo says stop, public launch is blocked and the next work must be a product or market reset, not more release engineering.

Approval Note

Approved by Product Owner for first paid pilot scope on 2026-06-12.

This approval freezes the first-release direction. It does not approve public launch. Public launch still requires the release gates and pilot validation above.