Skip to content

Pre-Release Scope Audit Prompt

You are working inside my MamNajem workspace with Claude Code/Codex.

Your task is to inspect the full local project and produce a pre-release strategy and scope audit.

Do not ask me for a product description. Infer the product from the repositories, docs, architecture notes, code, configuration, tests, and deep-research files.

Important rules:
- Do not modify files.
- Do not stage, commit, push, or run destructive commands.
- This is an audit and planning task only.
- Read the whole project scope before giving recommendations.
- If multiple repositories exist, inspect all relevant ones.
- Use the actual codebase as the source of truth for what is implemented, partially implemented, missing, or overengineered.
- Use `docs/deep-research` as the source of truth for market, strategy, pricing, legal, GTM, and validation research.
- When making claims about implementation status, cite file paths or modules that support the claim.

Your job:
Read the local workspace, understand what MamNajem currently is, read all deep-research files, compare the actual product against the research-backed release direction, and define the full scope required before release.

Please produce:

# 1. Project Scope Summary
Summarize what MamNajem currently is based on the actual repositories.

Cover:
- Backend capabilities
- Mobile app capabilities
- Web/admin capabilities, if present
- Payment/subscription system
- Notifications/messaging
- Documents/assets/handover flows
- Tenant/landlord flows
- Admin/support tooling
- Architecture and infrastructure
- Any obvious gaps between docs and code

For each major area, include:
- Implemented
- Partially implemented
- Missing
- Unclear / needs verification
- Relevant files or modules inspected

# 2. Deep Research Coverage Map
Read all files in `docs/deep-research`.

List the major topics covered:
- Market opportunity
- ICP
- Competitors
- Product positioning
- Product gaps
- Pricing and subscriptions
- Financial viability
- Go-to-market
- Validation
- Legal/compliance
- E-signature
- Payments/rent collection
- Maintenance workflow
- Pre-lease funnel
- Founder decision memo
- Product gap audit
- Launch plan
- Legal review checklist

For each topic, explain:
- What question it answers
- Main conclusion
- Confidence level: High / Medium / Low
- Whether more research is needed before release

# 3. Final Product Direction
Based on both the actual codebase and the deep research, answer:
- What should MamNajem become?
- Who exactly should it serve first?
- What pain should the product lead with?
- What should we avoid positioning it as?
- What should be the first paid MVP promise?
- Does the current implementation match that direction?

Resolve contradictions between research docs and actual implementation.

# 4. Full Pre-Release Scope
Define the complete scope required before release.

Break it into:

## Must Have Before Release
Only include features, fixes, workflows, legal checks, GTM assets, analytics, and operational tasks required for a credible paid launch.

## Should Have Before Release
Important items that improve conversion, trust, retention, or support, but should not block release if time is limited.

## Could Wait Until After Release
Useful items that are not necessary for first launch.

## Do Not Build Before Release
Items that are overengineered, risky, too expensive, or not validated.

For every item, include:
- Current implementation status: Implemented / Partial / Missing / Unclear
- Evidence from code/docs
- Why it matters
- Business impact
- Risk if skipped
- Release priority
- Dependencies

# 5. Product Release Checklist
Create a detailed release checklist grouped by area:

- Landlord onboarding
- Tenant onboarding
- Property setup
- Lease setup
- Documents and legal artifacts
- Handover protocol
- Deposit ledger and final settlement
- Rent schedule and payment tracking
- Notifications, email, SMS, and reminders
- Messaging
- Maintenance / issue reporting
- Pre-lease funnel, if needed before release
- Billing and subscriptions
- Admin/support tools
- Analytics and activation tracking
- Data export, deletion, retention, and privacy
- Security and audit logs
- Legal/compliance review
- Landing page and GTM assets
- Operational runbooks

For each checklist item, mark:
- Required before release: Yes / No
- Current status: Implemented / Partial / Missing / Needs verification / Should postpone
- Evidence: file paths, modules, or docs
- Notes

# 6. Business Model And Pricing
Summarize the recommended monetization model from the research:

- Free tier
- Paid tiers
- Suggested PLN prices
- Add-ons
- What not to monetize yet
- Whether to use rent payment take-rate
- Whether billing should be web-first or app-store-first

Then compare this against the actual implementation:
- What billing/subscription functionality exists?
- What is missing?
- What is overbuilt?
- What must be changed before release?

# 7. Go-To-Market Release Scope
Define what must exist before launch from a GTM perspective:

- Positioning
- Landing page
- Pricing page
- Founder offer / pilot offer
- SEO assets
- Outreach list
- Community/partner plan
- Referral plan
- Analytics
- Demo assets
- Support materials

Rank each as:
- Required before release
- Should have
- Can wait

Also identify whether the current repositories already contain anything supporting these assets.

# 8. Validation Required Before Release
Tell me exactly what must be validated before public release.

Include:
- Landlord interviews
- Tenant interviews
- Landing page smoke tests
- Pricing tests
- Paid pilot or design partner cohort
- Success metrics
- Red flags
- Go / narrow / stop criteria

Focus on what is required to avoid launching blindly.

# 9. Legal And Compliance Release Gate
Summarize the legal/product risks that need Polish lawyer review before release.

Include:
- Ordinary lease
- Occasional lease
- Institutional lease assumptions
- Deposit rules
- Handover protocol
- Rent increase notices
- Termination notices
- Arrears warnings
- E-signature / QES / notary
- Delivery proof
- GDPR and retention
- Tenant screening
- Payments/rent collection

Output this as a release gate checklist:
- Must be reviewed before release
- Can be reviewed after release
- Should not be included in release until reviewed
- Current product area affected
- Evidence from code/docs if applicable

# 10. Overengineering And Missing Pieces
Identify:
- What looks overengineered before release
- What is missing for release
- What should be simplified
- What should be postponed
- What is strategically dangerous to build too early
- What existing implementation might distract from the first paid MVP

Be strict and use evidence from the codebase where possible.

# 11. Final Pre-Release Recommendation
End with a clear recommendation:

- Go / narrow / no-go for release
- Recommended first ICP
- Recommended first product promise
- Required pre-release MVP scope
- Required legal/compliance gates
- Required GTM assets
- Recommended pricing
- Biggest release blocker
- Most important next action before release

Rules:
- Inspect the actual repositories before answering.
- Do not ask me for a product description.
- Infer the product from the codebase and docs.
- Read `docs/deep-research`.
- Do not only summarize docs.
- Do not make implementation claims without citing files/modules.
- Be direct.
- Avoid vague startup advice.
- Resolve contradictions between reports and code.
- If a research topic is already sufficiently covered, say so.
- If something still needs more research before release, explain why and provide the exact research question.
- Use tables where helpful.
- Focus on full pre-release scope, not a post-launch 7/30/90-day timeline.
- Prioritize actions that help validate demand, earn revenue, reduce legal risk, or make the first paid release credible.