MEES PORTAL

The description states that MEES Portal is a live, multi-tenant SaaS product built by one developer (Peter Mitala) and deployed at https://mees.epcscanpro.com. It integrates with the official UK government EPC register API to match property portfolios uploaded as CSVs.

Key features include:

• Risk scoring of properties into categories like urgent F/G, below-C action needed, review, and ready
• Generation of premium four-sheet landlord reports (HTML + PDF)
• Booking EPC assessments and retrofit work directly from a property record
• Production of branded Sales Intelligence Packs for green saleability
• Tenant referencing with identity, credit, and open-banking provider integrations
• API integration via scoped keys, OpenAPI 3 contract, branch-level access control

The product is described as not being a prototype but a production-ready system with agency approval workflows, trial/basic/pro/enterprise plan gating, branches, users, MFA, audit logging, billing with invoice PDF export, and rate limiting.

Inference The system appears to be a full-stack SaaS solution with backend (Express, SQLite), frontend (React/Vite), and AI-assisted development components.

The description positions MEES Portal as a compliance command centre for UK letting agents, helping them meet the government’s EPC C standard by 2030. It frames the problem as inefficiencies in current compliance tracking — where data is scattered across spreadsheets and agents discover expired EPCs at critical moments.

Key claims:

• The UK private rented sector is inefficient, with 52% of properties rated below EPC band C.
• Government policy requires all privately rented homes to reach EPC C by 2030.
• Agents currently track compliance in untrusted spreadsheets.
• MEES Portal provides a single live view of risk and enables proactive action.

The author also notes that the product was built using Codex, which they claim enabled rapid development and scalability beyond what would be possible manually.

Inference The positioning is rooted in climate policy compliance needs and inefficiencies in current processes. The use of AI tools like Codex is presented as a differentiator, though this is not independently verified.

The description identifies UK letting agents as the primary target customer. These are entities managing rental portfolios who must comply with EPC regulations.

It implies that these agents:

• Manage multiple properties
• Face pressure to meet EPC C standards by 2030
• Are currently using spreadsheets or fragmented systems for compliance tracking
• Need tools to generate reports, book assessments, and manage tenant referencing

The product is described as offering branch-level scoping, suggesting it caters to agencies with multiple locations or teams.

Inference The ICP likely includes mid-to-large-sized letting agencies managing portfolios across multiple branches, seeking compliance automation and lead generation tools.

The description states that MEES Portal operates a multi-tiered pricing model, including trial, basic, pro, and enterprise plans. It also mentions:

• Billing with invoice PDF export
• Plan gating
• Branch-level access control
• Audit logging
• Rate limiting

There is no mention of specific pricing tiers or revenue figures.

Inference The business model appears to be SaaS-based with tiered subscriptions, likely targeting agencies based on portfolio size or feature usage. However, no concrete pricing data is provided.

The product was built solo by one developer (Peter Mitala) using:

• Codex for full-stack development
• React + Vite frontend
• Express.js + SQLite backend
• GPT-5.6 for code generation and documentation rendering
• OpenAPI 3 for API specification
• A 6,800-line smoke-test suite that gates deployments

The author claims:

• The system includes full-stack feature construction, document rendering, test coverage, and refactors done via Codex.
• The product has undergone security hardening (MFA, rate limiting, upload validation).
• It supports multi-tenant architecture with branch-level access control.

Inference The technical stack is modern and scalable, with AI-assisted development being a key enabler. The use of Codex suggests an unconventional but potentially effective approach to solo SaaS development.

The description states that MEES Portal is live in production, hosted at https://mees.epcscanpro.com. It includes:

• Agency approval workflows
• Trial/basic/pro/enterprise plan gating
• Branch-level access control
• Users, MFA, audit logging, billing, and rate limiting

However, there is no evidence of actual customers or usage data beyond the author’s claims.

Inference The product shows maturity in terms of architecture and functionality. However, the lack of customer or revenue data makes it difficult to assess real-world traction.

No explicit competitors are named in the description. The author frames MEES Portal as solving a gap in compliance tracking for letting agents, particularly around EPC regulation.

The market context is tied to:

• UK government policy on EPC C standards
• Climate change goals and energy efficiency targets
• Private rental sector inefficiencies

There is no mention of existing tools or platforms addressing similar needs.

Inference The competitive landscape likely includes traditional spreadsheet-based systems and possibly niche compliance software, but no direct competitors are identified.

Several risks and red flags emerge from the self-reported description:

1. Solo Developer Risk: The entire product was built by one person (Peter Mitala). While impressive, this raises concerns about scalability, long-term maintenance, and support.
2. Unverified Claims: All claims are self-reported and unverified — no third-party validation of features, customers, or performance.
3. No Revenue or Customer Data: No evidence of actual users, revenue, or monetization beyond stated intentions.
4. AI Dependency: Heavy reliance on Codex for development may be fragile or unsustainable if access changes.
5. Regulatory Risk: The product operates in a regulated environment (EPC compliance). Misalignment with regulations could lead to legal issues.
6. Lack of External Validation: No external reviews, testimonials, or partnerships are mentioned.

Inference The lack of independent verification and external validation makes the product highly speculative.

1. What is the actual user base?
   • How many letting agents are currently using the platform?
   • Are there signed contracts or active paying customers?

1. How does the matching accuracy against the EPC register work in practice?
   • What percentage of addresses match confidently?
   • How are mismatches handled?

1. What is the current revenue model and how much do you earn per agent?
   • Is there a clear monetization path beyond subscription plans?

1. Can you provide evidence of agency approval workflows or pilot programs?
   • Are there case studies or references from early adopters?

1. How does the AI-assisted development impact maintainability and scalability?
   • What happens if Codex becomes unavailable or changes its API?

1. What are the risks associated with operating in a regulated environment (EPC compliance)?
   • How do you ensure legal alignment with evolving regulations?

1. Is there any internal testing or QA beyond the 6,800-line smoke test suite?