phoenix
phoenixPhoenix - Your AI Assistant
Inactive session will be ended in 24 hours
End Session

Conspection – Full Stack SaaS Developer Needed

  • Posted:
  • Proposals: 62
  • Remote
  • #4497018
  • OPPORTUNITY
  • Awarded
Andrew A.Yasir Ali M.Huzaifa M.Khalid H.KARTIK S. + 57 others have already sent a proposal.
  • 3

Description

Experience Level: Intermediate
Conspection – Full Stack Developer Needed for SaaS Prototype Review & Backend Setup

Project Description
I have built an early prototype of a construction site management SaaS platform called Conspection using Loveable.

The platform is aimed at UK housebuilders and includes:

* Plot tracking
* Site progress dashboards
* Inspection management
* Contractor/material tracking
* Programme management
* Reporting and analytics

I am now looking for an experienced full-stack developer to help assess and professionalise the platform for production use.

Phase 1 requirements:

* Review existing Loveable-generated codebase
* Advise whether the current structure is suitable for scaling
* Set up GitHub properly
* Set up Supabase backend/database/authentication
* Connect frontend securely to backend
* Improve structure/security where needed
* Prepare the app for deployment and future development

Preferred skills:

* React / Next.js
* Supabase
* SaaS platform development
* Dashboard systems
* Production deployments
* Security best practices

Important:
I am looking for someone experienced and honest who can advise the best route forward technically — not just someone who says yes to everything.

Please provide:

* Examples of similar SaaS projects
* Your recommended approach after reviewing the prototype
* Estimated timeline for Phase 1

Potential for ongoing long-term work if successful.

New Proposal

Login to your account and send a proposal now to get this project.

Log in

Clarification Board Ask a Question

  • Naresh S.

    Hi Eddie, before Phase 1 starts, could you please let me know whether the current Loveable-generated prototype already has stable business workflows/data models that you want preserved, or are you open to partially restructuring the architecture if the review shows limitations around scalability, Supabase integration, or long-term maintainability?

    Thanks
    Naresh

  • Muhammad Ather A.

    Hi Eddie,

    Thanks for the invite.

    A few quick questions before I can send an accurate estimate:

    1. Was the current platform built entirely in Loveable, or has custom development already been added to the codebase?

    2. Is the current application architecture based on React/Next.js, and do you already have GitHub/version control configured?

    3. Which modules are currently functional versus prototype/demo-only (plot tracking, inspections, reporting, dashboards, etc.)?

    4. Do you envision Conspection as a multi-tenant SaaS platform where multiple housebuilders manage separate projects/accounts?


    5. What user roles and permission levels are expected initially (admin, site manager, contractor, inspector, client viewer, etc.)?

    6. Will the platform require file uploads such as inspection photos, drawings, reports, or compliance documents in Phase 1?

    7. Are you looking primarily for:
    a technical audit/stabilisation of the current prototype,
    or a partial architectural rebuild if scalability/security issues are identified?

    8. Do you have a target timeline for MVP deployment or investor/client demonstrations?

    Looking forward to your answers.

    Eddie L.21 May 2026

    Hi Vconn,

    Thanks for the detailed questions.

    At a high level, the current platform is a Lovable-based MVP/prototype built around construction site management workflows including plot tracking, inspections, dashboards and reporting concepts. The long-term goal is a scalable multi-tenant SaaS platform for multiple housebuilders with role-based permissions and file/document management.

    I’m currently looking for:
    - technical review/audit,
    - backend architecture guidance,
    - scalability/security assessment,
    - and support transitioning the prototype towards a production-ready MVP.

    Some modules are functional while others are still prototype/demo stage, so I’d prefer to go through the current setup and roadmap properly on a call.

    I’d be interested to hear how you would approach architecture, backend structure and scaling for a platform like this.

    Thanks,
    Eddie

  • Shobi K.


    A few quick questions:
    1. Is the current prototype already connected with any database or backend service?
    2. Are you planning multi-user roles/permissions in future phases?
    3. Which hosting/deployment environment are you considering currently?