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,017 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
What the company appears to be
Liquidimmo is a self-reported SaaS product for French real-estate professionals that aims to help them prioritize property opportunities earlier in the market cycle by structuring and gating commercial actions based on verifiable evidence.
What changed
The project description states that during OpenAI Build Week, the team extended an existing MVP into a testable extension of its core workflow. This involved implementing an “evidence-gated” pipeline where forward progression of property cases is restricted unless verifiable property evidence is attached — effectively enforcing responsible decision-making before moving to next stages like Contacted, Offer, or Signed.
The single most important open question
Is there any evidence that Liquidimmo has traction, revenue, customers, or adoption beyond the founder’s own account and a live product built during a hackathon?
What The Product Actually Is
The description states that Liquidimmo is an evidence-first SaaS for real-estate prospecting. It transforms fragmented signals into prioritized opportunities for French agents.
It supports an operating loop:
- Detection → Verification → Prioritization → Action → Pipeline → Measurement
Each opportunity record includes:
- Predictive potential
- Verifiable property attachment
- Evidence strength and freshness
- Market status
- Contact qualification
- Next commercially responsible action
The product separates these elements to avoid fictional properties or unsupported decisions. When evidence is incomplete, it states what remains unknown.
It also implements a rule-based pipeline progression where:
- Cards can only move forward if verifiable property evidence is attached.
- Certain types of data (e.g., company events, scores, opaque identifiers) are not treated as proof.
- A canonical probable SCI, SCCV, or SCIA liquidation case may progress from Detected to Qualified only with valid SIREN.
- Progression beyond Qualified requires verified property evidence.
Backward transitions remain available for all cards, including legacy incomplete records.
Inference The product appears to be a structured tool for managing real-estate leads and pipeline stages, built around the principle of “evidence before action.”
Positioning & Claim Evolution
The description states that Liquidimmo began as an MVP observing that by the time a property is publicly listed, every agent can see it — so the advantage lies earlier in identifying which properties may reach the market next.
It positions itself not as a tool for generating more leads but as one that helps reduce unsupported decisions made later.
The claim evolution shows:
- From MVP to industrialized SaaS
- From general prospecting to evidence-gated pipeline progression
- From manual inference to automated rule enforcement
Inference The positioning evolved from solving a problem (early identification) to enforcing responsible behavior (evidence before action).
Target Customer & ICP
The description states that Liquidimmo is for French real-estate professionals, specifically those involved in prospecting.
It targets users who need to:
- Identify which properties may reach the market soon
- Separate credible opportunities from noise
- Turn uncertainty into responsible commercial actions
Inference The target customer is likely a small-to-medium-sized real-estate agent or broker operating in France, with a focus on lead generation and pipeline management.
Business Model & Pricing Evidence
Not evidenced.
The description does not mention:
- Revenue model
- Pricing structure
- Customer acquisition costs
- Unit economics
- Monetization strategy
Inference No evidence of business model or pricing exists in the provided text.
Technical & Delivery Signals
The project was built using:
- Tools: Codex, GPT-5.6, Firebase, Firestore, Node.js, JavaScript, Playwright, Vercel, Vite, Vitest
- Methodology: Multi-agent system using Codex and GPT-5.6 for parallel analysis across product rules, data boundaries, tests, audits, etc.
- Implementation approach:
- Evidence-gated pipeline progression
- Local and server synchronization
- Unit, integration, and browser tests
- Release readiness checks
The team used Git to track changes, with a baseline commit (c93ddb582db43a9b2750ac059d67bd1dd896529b) and diff for judging purposes.
Inference The technical stack suggests a modern web application built in a rapid development environment, possibly using AI-assisted engineering tools. There is evidence of structured testing and version control practices.
Traction & Maturity Signals
Not evidenced.
The description does not include:
- Revenue figures
- Customer base or adoption metrics
- Usage data
- Product maturity indicators beyond MVP status
- Any form of traction or growth metrics
It mentions that the product was live before Build Week and that they are now deploying the event commit, but no user engagement or performance data is shared.
Inference No traction or maturity signals are evident from the description.
Competitive Context
Not evidenced.
The description does not mention:
- Competitors
- Market size
- Competitive positioning
- Differentiation strategy
- Industry trends
Inference No competitive context is provided in the self-reported description.
Key Risks & Red Flags
- No independent verification of claims: All information comes from a single founder, with no third-party confirmation.
- Unproven traction or adoption: The product is described as live but lacks any evidence of real-world usage or customer feedback.
- Unclear monetization path: No pricing or revenue model is mentioned.
- Limited team size: Only one member (François MONDAMERT) is listed, raising questions about scalability and execution capacity.
- High reliance on AI tools: The use of GPT-5.6 and Codex raises concerns about reproducibility, auditability, and long-term maintainability without human oversight.
- Narrow scope of implementation: The Build Week extension is described as “deliberately narrow” — this may limit its perceived value or impact.
Inference Risks stem from lack of external validation, unclear business model, limited team, and unproven market fit.
Diligence Questions To Ask The Founders
- What is the current stage of product development beyond Build Week?
- Have you validated the core assumption that real-estate agents want to act earlier based on evidence?
- How do you plan to scale this solution beyond one founder and a hackathon prototype?
- Is there any customer feedback or early user testing data?
- What are your plans for monetization and pricing?
- How does your evidence-gating mechanism integrate with existing real-estate workflows?
- Are there any legal or regulatory considerations in France related to handling property data?
- What is the long-term vision for expanding territorial coverage or improving evidence freshness?
Investment/Partnership Verdict
Not evidenced.
The description provides no information on:
- Valuation
- Funding history
- Investor interest
- Partnership opportunities
- Strategic fit for potential partners
Inference There is no basis in the provided text to assess investment or partnership viability. The project remains unproven in terms of traction, business model, and market validation.
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.

