We’re building the operational backbone for a fast-growing, tech-enabled cleaning logistics company operating in London. Right now, we have a live website and active lead generation, but we need to build the structured backend that connects sales, operations, dispatch, cleaners, and invoicing into one seamless system. This is not a generic cleaning company project. We’re building a logistics-driven operation designed to reduce vacancy time, minimise travel inefficiencies, and deliver structured, data-backed handovers for property managers. We need someone to design and implement an MVP operational architecture that includes: • CRM integration (HubSpot or similar) • Operations database (Airtable or scalable alternative) • Job creation and dispatch system • Cleaner workflow (mobile-friendly interface) • Automation layer (Make.com or similar) • Messaging (SMS/WhatsApp/email notifications) • Stripe invoicing integration • Clear documentation and handover The goal is that: 1. A lead submits via our website 2. The lead enters CRM automatically 3. When marked closed-won, the client and properties are created in the Ops database 4. Jobs can be created and assigned in under 2 minutes 5. Cleaners receive notifications, complete checklists, and upload photos 6. QC triggers automated invoicing Everything must be structured, reliable, and scalable. ⸻ What We Expect From You • You can think in systems, not just tools. • You understand relational databases and workflow logic. • You can design clean automations with proper error handling. • You can explain what you’re building clearly. • You deliver documentation, not just setup. We are not looking for someone who just “connects tools together.” We want someone who understands operational efficiency and long-term scale. ⸻ Work Relationship We want someone proactive, structured, and honest. If something is overkill, tell us. If something won’t scale, flag it. If there’s a better way to architect it, propose it. This will likely evolve into a long-term relationship as we build routing logic and analytics layers later. ⸻ What Makes This Project Different We are building toward a logistics-first model. Our long-term vision includes: • Smart scheduling based on location and time windows • Reduced cleaner travel time • SLA tracking • Performance analytics • Deposit dispute reduction through structured photo documentation We want to build this correctly from the start so we don’t have to rebuild everything later. ⸻ If you’re applying, please include: • Examples of similar systems you’ve built • A brief outline of how you would structure this MVP • The stack you’d recommend and why • Timeline estimate We value clarity and strategic thinking over buzzwords.