Hey everyone! I’m Mark, and I’m building Site Optix UK, an operational software suite tailored for the B2B Facilities Management, commercial cleaning, and security sectors. My first core module is TUPE-Flow—a mobile-first onboarding utility that automates the chaotic 28-day window when a company wins a new multi-site contract and inherits a massive frontline workforce from an outgoing competitor. It handles personal data ingestion, right-to-work compliance, sector-specific certifications (like live SIA licence verification and BICSc logs), and holiday/payroll liabilities. The goal is to eliminate manual spreadsheets, stop day-one payroll errors, and protect commercial contract margins for operations directors. The Part I’m Least Sure About: Since I’m building this as a non-technical founder using AI app-builders (looking at full-stack environments like Hostinger Horizons and Lovable), the piece I am least sure about is structuring the multi-tenant user permissions and data segregation safely. Because TUPE involves highly sensitive employee data (passport photos, contracts, and legal IDs), I need to make sure that: 1. Inherited frontline workers can only see their own secure mobile upload form. 2. Incoming Mobilisation Managers have a high-level master dashboard to review documents and track completion metrics across multiple specific sites simultaneously. If anyone here has tackled secure document uploads and role-based user dashboards within an AI no-code/low-code setup, I’d love to hear how you structured your backend database to keep corporate data locked down safely. Looking forward to seeing what everyone else is building!

One of the biggest upgrades to my AI workflow has been spending more time planning before I start building. I'll usually have a back-and-forth conversation with ChatGPT or Claude to discuss my concept, pressure-test ideas, uncover edge cases, and shape the project into something that actually makes sense. Once the idea is solid, I turn it into an mvp_prd.md (Minimum Viable Product Product Requirements Document), which is a living source of truth document that captures the project's goals, scope, research, assumptions, and roadmap. From there, I convert the mvp_prd.md into plan.md, which becomes the actionable task list I work through while building. A few extra minutes of planning can save hours (or days) of rebuilding later. How do you ideate your projects before you start coding?