OpenAI 2026 hackathon

MoveOutDocs

A multi-agent lease documentation system that helps small landlords to claim damages during 'tenant move-out' while adhering to statute rules.

Solo project by Mohammad Alam · 0 likes · 0 comments

Archive position — measured, not model output

0 likes on Devpost

2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #5,408 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

What the company appears to be

MoveOutDocs is a self-contained, AI-powered system designed to help small landlords (2–75 units) generate legally defensible documentation for lease move-out disputes. It uses structured photo capture, visual comparison, and statute-specific wear-and-tear classification to produce itemized deduction letters that can withstand legal scrutiny.

What changed

The project was built as a hackathon submission by one developer (Mohammad Alam), using AI tools like Codex and GPT-5.6 for development, with no evidence of prior traction or revenue.

Single most important open question

Is there sufficient legal rigor in the statute-based classification engine to make the generated documents legally defensible? The description states that the system avoids hallucinations by relying on pre-verified data, but does not provide evidence of how this has been tested or validated in practice.

Back to contents

What The Product Actually Is

The description states that MoveOutDocs is a multi-agent lease documentation system. It runs two photo sessions per unit: one at move-in and one at move-out. These sessions are designed to be directly comparable by inheriting the room list from move-in, ensuring consistent coverage. Each photo is hashed (SHA-256) and timestamped (EXIF or upload time). The system then processes these photos through a six-stage pipeline:

  1. Intake integrity
  2. Visual comparison
  3. Wear-and-tear classification against actual state statute
  4. Cost estimation
  5. Landlord review
  6. Document drafting

The output is a PDF deduction letter with evidence links, and a tenant-side acknowledgment feature.

Evidence The author describes the system architecture, including backend (FastAPI, Postgres via Supabase), frontend (Next.js), AI agents (OpenAI SDK), and tools like Codex for development.

Inference The system is built to be legally robust by avoiding LLM hallucinations in legal reasoning and enforcing human review of uncertain items.

Back to contents

Positioning & Claim Evolution

The description states that MoveOutDocs targets "self-managing landlords with 2 to 75 units who have no in-house counsel or property manager." It positions itself as solving a gap between having photos and having a defensible case in small claims court.

Claim

The system helps landlords avoid penalties (2–3x the deposit) by producing legally sound documentation.

Inference The product is positioned for small, non-professional landlords who lack legal support but need to comply with state-specific laws.

Back to contents

Target Customer & ICP

The description states that MoveOutDocs targets "self-managing landlords with 2 to 75 units" and excludes those with in-house counsel or property managers. It also notes that the tool is built for users with just a phone camera and an ending lease.

Evidence The author explicitly defines the user base as small landlords without legal support, and describes the tool’s simplicity (e.g., using only a phone camera).

Inference The ICP is narrow: small landlords who are not part of larger property management firms.

Back to contents

Business Model & Pricing Evidence

The description does not state anything about pricing or monetization. It also does not mention any revenue, customers, or sales channels.

Evidence Not evidenced.

Back to contents

Technical & Delivery Signals

The system uses a combination of AI agents (via OpenAI SDK), structured code coordination (Python-based pipeline), and a frontend (Next.js) with backend services (FastAPI). It includes:

  • SHA-256 hashing and EXIF timestamping for photo integrity
  • A six-stage pipeline with human checkpoints
  • Statute-specific legal reasoning via pre-verified data
  • Tenant-side acknowledgment link
  • Use of Supabase, Codex, FastAPI, Vercel, Resend, ReportLab

Evidence The author describes the stack and architecture in detail.

Inference The system is built with a focus on testability and auditability, especially around legal compliance.

Back to contents

Traction & Maturity Signals

There is no evidence of revenue, customers, or adoption beyond the hackathon submission. The project was built in a single developer’s time and has not been deployed for real-world use beyond testing.

Evidence Not evidenced.

Back to contents

Competitive Context

The description states that existing tools like AppFolio, Buildium, TurboTenant, RentRedi, and others store photos and track leases but do not reason about condition change or apply state-specific wear-and-tear law. MoveOutDocs is positioned as filling this gap.

Evidence The author explicitly compares MoveOutDocs to these tools.

Back to contents

Key Risks & Red Flags

  1. Legal validity of output: The system avoids hallucinations by using pre-verified data, but there is no evidence that the legal framework has been tested or validated in court.
  2. Limited state coverage: Only six states are supported (Arizona, California, Florida, Oregon, Texas, Washington), which may not be enough for broad adoption.
  3. Single developer: The team size is listed as one person, raising questions about scalability and long-term maintenance.
  4. No revenue or customer data: No evidence of monetization, traction, or user feedback.

Evidence Not evidenced.

Back to contents

Diligence Questions To Ask The Founders

  1. How was the statute data verified for accuracy and completeness?
  2. Has the system been tested in real-world legal scenarios or court settings?
  3. What is the plan to expand beyond the six supported states?
  4. How does the system handle edge cases like poor-quality photos or misaligned angles?
  5. Is there any evidence of user feedback or testing with actual landlords?
  6. What are the plans for scaling beyond a single developer?

Back to contents

Investment/Partnership Verdict

The description indicates that MoveOutDocs is a hackathon project built by one developer, with no revenue, customers, or traction data. It is positioned as solving a niche problem in small-landlord legal documentation.

Confidence Low — the evidence is limited to self-reported claims and technical architecture.

Verdict Not ready for investment or partnership without further validation of legal efficacy, user testing, and business model development. The system shows promise in terms of technical execution but lacks commercial proof-of-concept.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.