This is a promising validation candidate, primarily because you have direct domain experience and a concrete workflow pain. But your biggest risk right now is assuming that because the problem is severe for you, it is equally severe across commercial property management. Your immediate objective should therefore not be building the SaaS or finding an investor. It should be determining whether 20–30 other commercial property managers independently describe essentially the same problem and demonstrate enough economic pain to justify changing their workflow. 1. Idea Clarity & Hypothesis Definition Refined problem statement > Commercial real estate property managers spend significant time turning maintenance information—photos, voice notes, emails and contractor updates—into structured documentation, repair-cost comparisons and contractor communications. This manual administrative work is repetitive, inconsistent and difficult to keep organized, taking approximately 2–3 hours per week and reducing time available for higher-value property-management activities. Notice that the problem is broader than "generating summaries." The underlying job is: Capture maintenance issue → understand it → document it → evaluate repair options → communicate with contractors → maintain records. That's important because your eventual product may solve a larger workflow than your initial concept suggests. --- 2. Sharpen the Initial Customer Don't initially target: > "Commercial property managers." That's too broad. Your first hypothesis should be something like: > Commercial property managers responsible for multiple properties/buildings who personally coordinate recurring maintenance requests and communicate directly with contractors. Then segment them. Segment Hypothesis Small independent PM firms ⭐⭐⭐⭐⭐ Property manager at regional CRE firm ⭐⭐⭐⭐⭐ Large enterprise CRE company ⭐⭐⭐ Facility managers ⭐⭐⭐ Residential property managers ⭐⭐ Building owners managing their own properties ⭐⭐⭐ I'd initially investigate independent/regional commercial property management companies, particularly managers handling enough properties to experience meaningful maintenance volume but without large administrative teams. --- 3. Your Core Value Proposition Your initial hypothesis: > Turn maintenance photos and voice notes into complete maintenance documentation and contractor communications in minutes instead of hours. But don't lock yourself into this positioning yet. There are potentially three different products hiding inside the idea: Product A — Documentation assistant Photos + voice memo → maintenance summary + record. Product B — Maintenance coordination assistant Photos + voice memo → summary → contractor request → updates → completed record. Product C — Maintenance cost intelligence Photos + voice memo + contractor quotes → repair comparison → cost history → recommendation. C could ultimately be much more valuable than A. But you should validate which part customers actually care about. --- 4. Key Assumptions I'd rank your assumptions this way: Assumption Risk Why PMs experience the problem 🔴 Fundamental Problem consumes meaningful time 🔴 Determines value Documentation is actually painful 🔴 Determines product demand Existing tools don't solve it 🔴 Competitive risk PMs trust AI-generated documentation 🔴 Critical Cost comparison is valuable 🟠 May be unnecessary Voice/photo input fits workflow 🟠 Product hypothesis Companies will pay for it 🔴 Business viability Riskiest assumption I'd phrase it as: > Commercial property managers consider maintenance documentation/coordination painful enough to adopt a new tool rather than continuing with their existing combination of email, spreadsheets, property-management software, phone calls and manual notes. That is what you need to attack first. --- 5. What You Should NOT Do Yet Do not: hire developers build an AI prototype spend months learning to code approach investors create elaborate branding build integrations develop a complete pricing model search for a technical co-founder based only on the idea Instead: > Become the person with the strongest evidence that this problem exists. That evidence will make finding a technical co-founder dramatically easier. --- 6. Your 20 Interview Questions I would modify the generic interview guide specifically for CRE. Current workflow 1. How many properties do you personally manage? 2. Approximately how many maintenance issues do you deal with in a typical week? 3. Walk me through the last maintenance issue you handled from start to finish. 4. How did you initially receive the request? 5. Where did the photos, notes or other information come from? 6. How did you document the issue? 7. Where did you store that documentation? 8. How did you communicate with the contractor? Pain discovery 9. Which part of that process takes the most time? 10. What part do you find most frustrating? 11. How often do you have to recreate information you've already received? 12. How often do you have to chase contractors for information? 13. How often do maintenance records end up incomplete? 14. What happens when documentation isn't complete? 15. Have you ever made a decision based on incomplete maintenance information? Existing solutions 16. What software do you currently use for maintenance? 17. What does it do well? 18. What doesn't it do well? 19. Have you tried anything else to make this process easier? 20. If you could eliminate one part of your maintenance workflow tomorrow, what would it be? Do not mention your proposed AI solution until late in the conversation. --- 7. The Most Important Interview Technique Don't tell them: > "I spend 2–3 hours a week documenting maintenance. Do you?" Instead ask: > "How much time do you spend dealing with maintenance documentation?" Then: > "Walk me through the last one." You want unprompted evidence. If you say "photos and voice memos," you've already planted the answer. --- 8. Interview Recruitment Strategy Your existing CRE experience is a major advantage. Start with: Tier 1 — Your professional network Former: colleagues property managers asset managers facilities people contractors property-management executives Aim for 10 interviews. Tier 2 — Second-degree introductions Ask: > "Who is the most operationally hands-on property manager you know?" Aim for another 10. Tier 3 — Cold outreach Find property managers through: LinkedIn commercial property-management associations local CRE organizations property-management firms CRE communities Aim for another 10–20 conversations. Your initial target: 30 interviews. You don't need 1,000 survey responses. --- 9. Your Interview Scorecard After every conversation, score: Factor 1–5 Maintenance volume Documentation burden Time consumed Frustration Financial impact Existing workaround Existing software dissatisfaction Desire to change Willingness to test Willingness to pay Also record the exact workflow they described. You're looking for patterns. --- 10. The Critical Discovery Question Near the end ask: > "If you had a tool that could take your maintenance photos and voice notes and automatically turn them into a complete maintenance summary and contractor communication, how would that fit into your current workflow?" Don't ask: > "Would you use it?" Instead ask: > "What would prevent you from using it?" That exposes: trust issues security concerns integration requirements workflow friction AI skepticism procurement barriers --- 11. Investigate the Existing Software Stack This is especially important in CRE. For every interviewee, document: Property-management platform → maintenance workflow → communication → documentation → accounting You may discover that the opportunity isn't a standalone SaaS. For example: > Existing PMS → your AI layer → contractor → existing accounting workflow. That's potentially a much stronger product strategy. You should specifically ask what they use for property management, work orders, accounting, communication and document storage. --- 12. Competitive Landscape Hypothesis Don't assume your competitors are other AI tools. Your competitive landscape is likely: Direct AI-powered maintenance/work-order assistants. Adjacent Property-management platforms with maintenance/work-order functionality. Substitutes spreadsheets email phone calls WhatsApp/SMS shared drives templates administrative assistants property-management software manually written reports The biggest competitor > Existing property-management software + human effort. That is the competitor you must beat. --- 13. What You Need to Discover About Competitors Don't just compare features. Ask interviewees: > "What do you use today?" Then: > "What's the one thing you wish it did better?" You may discover an underserved niche such as: > Existing CRE software manages the work order, but not the thinking and documentation around the work order. That would be a much stronger positioning opportunity. --- 14. Potential Differentiation Your strongest potential differentiation isn't: > "We use AI." Everyone can say that. Instead: > "The maintenance intelligence layer for commercial property managers." Potential moat eventually comes from: Proprietary maintenance data Historical: repair types costs contractors properties recurring problems repair outcomes Workflow integration Become part of the manager's daily maintenance process. Contractor intelligence Over time you could know: typical repair cost contractor response time job history recurring issues quote differences Property-specific context The system could learn: > "This HVAC unit has had three similar issues in the past 18 months." That is considerably more defensible than simply generating text. --- 15. MVP Hypothesis Do not start with the full vision. Your first MVP could be incredibly simple: Input Upload: 3–5 photos voice memo Output Automatically generate: 1. maintenance issue summary 2. suggested repair description 3. contractor communication draft 4. structured maintenance record That's enough to test whether the fundamental workflow creates value. Leave out initially contractor marketplace automated contractor selection accounting integration predictive maintenance advanced cost intelligence mobile app dashboards multi-property analytics complex permissions automatic sending Those can come later. --- 16. A Better MVP Experiment for You Because you're nontechnical, don't build software yet. Run a concierge MVP. The process: Property manager sends you: 📷 Photos 🎤 Voice memo ↓ You manually/AI-assisted process it ↓ Send back: maintenance summary repair description contractor email structured record Then ask: > "Would you use this every week?" And eventually: > "Would your company pay $X/month for this?" You can test the entire business proposition before writing a line of software. --- 17. Cost Comparison Needs Special Validation I would not make repair-cost comparison a core MVP feature yet. Why? Cost comparison sounds valuable, but it introduces significantly more complexity. You need to determine: Where cost data comes from Whether quotes are standardized How repair scope is interpreted Whether regional pricing differs Whether historical data exists Whether PMs actually want AI recommendations Whether liability/trust concerns arise First validate: > "Can we dramatically reduce maintenance documentation and communication time?" Then investigate: > "Would comparing repair costs create additional economic value?" --- 18. Your First 10-Week Validation Roadmap Week 1 — Interview preparation Goal: Prepare the research system. Create: interview script interview scorecard CRM/spreadsheet target-user definition hypothesis list Recruit your first 10 people. Deliverable: 10 scheduled interviews. --- Week 2 — Problem interviews Conduct: 10–15 interviews. Don't sell. Look for recurring language. At the end of the week ask: > "What are the three biggest administrative headaches in your maintenance workflow?" Compare their answers against your hypothesis. --- Week 3 — Expand interviews Conduct another: 10–15 interviews. Now compare: small vs large portfolios experienced vs newer PMs different property types different software stacks different company sizes Decision If only you experience the problem: Pivot/research further. If the problem repeatedly appears: Continue. --- Week 4 — Concierge prototype Select 5–10 highly interested PMs. Ask them to send you real, anonymized maintenance examples. You manually produce: > Photos + voice memo → documentation + contractor draft. Measure: time saved usefulness editing required accuracy trust frequency of use --- Week 5 — Pricing Now introduce money. Test something like: Starter $49/month Professional $99/month Team $199+/month These are hypotheses to test, not recommended final prices. More important than asking which price sounds good: > "Would you be willing to run this on your next 10 maintenance requests?" Then: > "Would your company approve paying for this?" --- Week 6 — Acquisition test Test one acquisition channel. I'd start with: Founder-led outreach through your CRE network + LinkedIn. Your advantage is credibility. You're not an outsider saying: > "I built AI software for property managers." You're a property manager saying: > "I've been dealing with this problem myself and I'm researching whether it's common across the industry." That's much stronger. --- Week 7 — Technical co-founder preparation Only now start approaching technical co-founders seriously. Your pitch becomes: > "I've interviewed 30 commercial property managers, tested the workflow with 8, documented the current software stack, and X% reported this as a significant recurring problem. Five want to continue using the prototype and three are willing to pay." That's dramatically more compelling than: > "I have an idea for an AI property-management app." --- Weeks 8–10 — Lightweight MVP With a technical co-founder—or a very small outsourced build—create: Input → AI processing → structured maintenance output Keep it extremely narrow. Test with: 10–20 real users. Measure: requests processed/week activation completion rate edits per generated document time saved repeat usage willingness to pay referrals --- 19. Your Validation Scorecard At the end of the process, calculate: Problem GO if: ≥20 relevant interviews ≥60% report meaningful maintenance-administration pain ≥40% describe it as one of their significant recurring administrative burdens multiple users independently describe similar workflows clear evidence of time/cost/friction Solution GO if: users successfully use the concierge workflow meaningful time is saved outputs require relatively little editing users request continued access Commercial GO if: multiple users express willingness to pay at least several agree to a paid pilot or equivalent commercial commitment price is meaningful relative to the value created Distribution GO if: you can consistently reach relevant PMs interviewees introduce you to other PMs outreach generates conversations --- 20. Your Biggest Strategic Question There's one question I'd prioritize above everything else: > Is the valuable product actually "AI maintenance documentation," or is that merely the entry point into a much larger maintenance-management intelligence platform? Imagine the evolution: Phase 1 Photos + voice → documentation. ↓ Phase 2 Documentation → contractor communication. ↓ Phase 3 Contractor quotes → cost comparison. ↓ Phase 4 Historical maintenance → property intelligence. ↓ Phase 5 Maintenance data → predictive maintenance and budget forecasting. That could eventually become a much more substantial B2B SaaS business. But don't assume Phase 5 exists until Phase 1 is validated. --- 21. Your Immediate 14-Day Mission Forget the SaaS build for the next two weeks. Your entire objective is: Days 1–2 Define your target segment and prepare interview materials. Days 3–7 Conduct 10 interviews. Days 8–10 Conduct another 5–10 interviews. Days 11–12 Analyze recurring workflows and pain points. Days 13–14 Select 5 highly interested PMs for a concierge test. At the end, you should be able to answer: 1. How common is the problem? 2. How severe is it? 3. How much time does it actually consume? 4. What do PMs currently use? 5. What do existing systems fail to do? 6. Which part of the workflow is most painful? 7. Do PMs trust AI to handle it? 8. Would they actually use your proposed workflow? 9. Would their company pay? 10. Which customer segment has the strongest pain? Only after those answers are positive should you invest serious effort in a technical co-founder, MVP, or investor pitch. And in your particular situation, your 12 years of commercial real-estate experience is a significant asset. The absence of technical skills isn't currently your biggest weakness. At this stage, your domain expertise, access to potential users, and ability to obtain high-quality customer evidence are more valuable than being able to code the prototype yourself.