🎯 The One‑Job MVP
Goal: Validate demand by automating the free audit experience — the first two touchpoints a syndic has with us.
Why this matters: If syndics won't even sign up for a free, automated analysis of their building's solar potential, they certainly won't pay €1,200 for full‑service project management.
1. Core Capabilities (User‑Facing)
From the syndic's perspective, here's what the MVP must deliver:
📄 Instant Audit Request
A simple web form where syndics enter their name, professional email, and number of buildings they manage. No address collection required at this stage.
✉️ Immediate Confirmation
A welcome email sent within seconds, explaining what happens next and setting clear expectations (24‑hour turnaround).
📊 Personalized PDF Report
A professionally designed, data‑driven PDF delivered to their inbox within 24 hours, showing which of their buildings have solar potential and estimated savings.
📞 Clear Next Step
A follow‑up email (Day 2) with a simple CTA to schedule a 15‑minute discovery call about taking the next step.
2. Business Logic Required
Behind the scenes, these are the functional pieces needed:
✓
Lead capture & storage – Capture syndic contact info and store it somewhere accessible (database, spreadsheet, Notion).
✓
Email automation – Send transactional emails (welcome, report delivery, follow‑up) with professional templates.
✓
Report generation – Create branded PDFs with mock/sample data for now (real geodata integration can come later).
✓
Background processing – Queue report generation jobs so the syndic gets their PDF within promised timeframe.
✓
Basic analytics – Track sign‑ups, open rates, click‑throughs to understand what's working.
3. What Stays Manual (For Now)
Key insight: The automated audit is the hook. Everything after can be manual while we validate demand.
For MVP, use mock/sample building data. Once we have paying customers, integrate with IGN API for actual cadastre analysis.
Manually create Word/PDF templates for the first few customers. Automate once we see consistent demand.
Email 3‑4 installer partners manually, compile their quotes into a comparison PDF.
Use Notion/Linear/Spreadsheets to track ABF permits, Enedis paperwork, subsidy applications.
4. What a Coding Agent Can Realistically Deliver
Given a competent coding agent (Claude Code, Cursor, etc.) with web‑development experience:
Day 1–2
Foundation & Infrastructure
Set up repository, hosting, database, email service. Build the landing page with lead‑capture form. Implement welcome‑email automation.
Day 3–4
Report Generation System
Create PDF template engine (can use any PDF library — the choice is implementation detail). Build background job processor to generate and email reports within 24h.
Day 5–6
Follow‑up & Analytics
Implement Day 2 follow‑up email with calendar scheduling link. Add basic tracking (sign‑ups, opens, clicks).
Day 7
Testing & Polish
End‑to‑end testing, error handling, mobile responsiveness, documentation.
Total time: 1 week for a working, deployable MVP.
Cost: Essentially €0 (free tiers of modern cloud services cover everything at this scale).
5. The Strategic Decision Points
🔧 Technical Choices Don't Matter (Yet)
The library used for PDF generation (Puppeteer, PDF‑Kit, etc.) is an implementation detail. What matters is:
- Can it produce a professional‑looking, branded PDF?
- Can it insert dynamic data (building addresses, savings estimates)?
- Can it run reliably in a background job?
Same for database (Supabase, PostgreSQL, Airtable), email service (Resend, SendGrid, Postmark), or hosting (Railway, Render, Vercel). The coding agent should pick whatever they're most productive with — we can always migrate later.
🎯 The Real Validation Questions
This MVP helps us answer:
- Will syndics sign up for a free solar audit? (Conversion rate)
- Will they open/read the PDF? (Engagement)
- Will they schedule a discovery call? (Interest in paying)
- What questions/objections do they have? (Feedback for iteration)
Everything else (scalable architecture, real geodata, installer integrations, regulatory automation) is premature optimization until we know syndics want this.
6. Next Steps
→
Hand this to a coding agent – Give them this business‑requirements document and let them build it in their preferred stack.
→
Launch the €200 acquisition tests – Run Google Ads (pain‑point keywords) and LinkedIn outreach simultaneously.
→
Measure for 2 weeks – Do we get 10+ sign‑ups? Do any convert to discovery calls?
→
Decide: Pivot or Double‑Down – If validation fails, pivot to a different wedge or customer. If it works, invest in automating the next layer (AG documents).
Bottom line: A coding agent can build this MVP in a week. The technical stack is irrelevant — what matters is validating whether Paris syndics want software‑managed rooftop solar.