Multi-Tenant Interactive Plot-Finder Web App (Property Site Plans) — Flutter/Firebase or React

We're a UK architectural CGI and visualisation studio producing photoreal renders, animations and marketing materials for residential property developers, architects and estate agents. We already produce all the imagery in-house. What we need is the software product that wraps our renders — a reusable, embeddable plot-finder we can resell to multiple housebuilder clients. This is not a one-off website. We are commissioning a multi-tenant product that we own outright and can stand up for a new development by uploading new images and plot data — no fresh build each time, and no developer involvement for routine new sites. --- What we're building An embeddable web app that shows a residential development's site plan with clickable plots. Each plot displays live status (Available / Reserved / Sold / Coming Soon / Not Released), price, house type, beds, baths, CGI images, floorplans and a street-view image. Plot data lives in a database and is editable by non-technical sales staff through a simple admin panel — changes appear live on the public site with no redeploy. We have inspected several live examples of exactly the product we want. They are built as a **shared platform with one codebase serving many developments** (each development is a dataset; assets are served from a CMS). We can share reference URLs with shortlisted candidates. Reference technical stack (for context — propose your own if better) The reference builds use: Flutter Web front end, Firebase / Firestore real-time database, Firebase Auth for the admin login, Firebase Hosting, served via a CMS asset structure. You may propose an equivalent modern stack (e.g. React + Firebase, or React + Supabase) — just justify the choice. **We own all source code and IP on delivery.** --- THE CORE REQUIREMENT: a true self-service, multi-tenant platform This is the single most important part of this brief. Please read it carefully — bids that don't address it directly will not be considered. We are buying a **platform**, not a website. Once the platform is built, **we must be able to create a brand-new, fully working development ourselves — a non-technical admin, in a browser, with no developer involvement and no code changes.** Everything that differs between developments must be **data and assets**, never code. Specifically, an admin must be able to, entirely through the admin interface: - Create a new development as a new record/dataset. - Upload the site-plan imagery (see "Site plan" below). - **Visually place plot hotspots** by dragging numbered pins onto the plan — NOT by editing coordinates in a file. This visual, in-browser hotspot editor is a hard requirement. - Define the house types and enter/import plot data. - Toggle which plot-detail modules are shown (see "Per-development feature toggles" below). - Go live, with no redeploy and no developer. **Acceptance test (paid-milestone gate):** a non-technical member of our team will create a complete, working development from scratch — uploading plans, placing hotspots visually, defining house types, entering plot data, and toggling modules — with zero developer involvement and zero code changes. If this can't be demonstrated, the multi-tenancy requirement is not met. Note to bidders: building a genuine visual hotspot editor and a clean tenant/house-type data model is the hard part of this job, and the part most easily skipped by hardcoding the first development. A build that demos perfectly for one site but requires a developer to add a second site does not meet this brief. --- ## Site plan — three fidelity tiers (commission in order) The site-plan view can be built at three levels. We want these in order, not all at once: 1. **2D site plan** — a flat plan image with clickable plot hotspots. 2. **Multi-angle pre-rendered "3D" plan** — we supply **four pre-rendered aerial angles** of the development that the user rotates between; plot hotspots must be correctly positioned on **each** angle. **This is our Phase 1 target.** It delivers the 3D "wow" using our render pipeline without the cost of live 3D. 3. **True navigable 3D (WebGL)** — a real fly-around 3D scene. **Phase 2 / separate quote only.** Key technical point for tier 2: hotspots are defined **per angle**, so a plot stays aligned as the user flips between the four rendered views. The admin places the pins for each angle through the visual editor described above. We supply the four images. --- ## House types as reusable objects (data model) On a real development the same house type (e.g. "The Avebury", "The Saxondale") repeats across many plots — same floorplans, beds/baths, CGI and spec. The data model must reflect this: - **House type** is defined ONCE per development: name, beds, baths, dwelling style (e.g. detached / semi-detached), floorplans, gallery images, street-view image, specification, dimensions. - **Plot** references a house type, and only carries plot-specific data: plot number, status, price, position/hotspot on each plan angle, and any per-plot overrides. This turns data entry from "fill in everything for 80 plots" into "define ~6 house types, then tag ~80 pins" — essential for keeping per-site setup to an afternoon of admin. --- ## Per-development feature toggles (plot-detail modules) Each plot has a detail view with a menu of modules. The following are the **core modules**, and **each must be individually toggleable on/off per development** through the admin panel — because not every client supplies every asset (e.g. no street-view CGI, no dimensioned drawings, or they don't want a Compare tool): - Floor plans - Images - Street view - Specification - View on siteplan - Compare - Details & dimensions When a module is toggled off for a development, it must be **cleanly hidden** from the plot menu and UI — never shown empty, greyed, or broken. The set of core modules above should be defined centrally so it's consistent across all developments, with the on/off state configured per development. --- ## Phase 1 — deliverables (2D + four-angle pre-rendered, multi-tenant) - Interactive site plan: we supply the plan and the four pre-rendered angles; you implement clickable plot hotspots with hover and selected states, status colour-coding, and a rotation switcher between angles with per-angle hotspot positions. - **Visual, in-browser hotspot editor** in the admin panel (drag pins onto each angle, link to plot records). - Scrollable, filterable plot list synced to the map (filter by status, beds, price). - Plot detail view with the toggleable core modules listed above. - Favourites / shortlist, and a Compare view (itself a toggleable module). - Real-time data layer: plot fields stored in a database; the public site updates live when status changes. - Admin panel for non-technical staff: create developments, define house types, add/edit plots, upload assets, place hotspots, set module toggles, change status. - Multi-tenant architecture meeting the acceptance test above. - Responsive (desktop + mobile touch), iframe-embeddable into client microsites, basic analytics, and cookie consent. --- ## Phase 2 — separate quote (rough ballpark only) True navigable 3D masterplan (Three.js / WebGL or equivalent) with a 2D/3D toggle, fly-around camera, and street-view drop-pin. We supply the 3D scene / CGI assets. --- ## What we need from you to quote 1. Your proposed stack and why. 2. Phase 1 timeline and fixed cost (or milestone breakdown). 3. Phase 2 ballpark. 4. The asset specs and formats you need from our CGI team (image resolution, naming convention, how hotspot coordinates are captured, floorplan format, etc.). ## Please answer these when applying 1. Share prior work involving interactive maps, plot selectors, product configurators, or similar clickable-overlay apps. 2. How would you structure data so a non-technical admin can create a whole new development — including **visually placing hotspots** — with no developer and no code changes? 3. How would you handle hotspots staying aligned across four pre-rendered angles? 4. How would you implement per-development module toggles (Floor plans, Images, Street view, etc.) so unused modules are cleanly hidden? 5. For Phase 2, what's your approach to an in-browser 3D scene, and what asset formats would you need from us? --- ## Engagement notes - Fixed-price, milestone-based preferred. Suggested milestones: 1. Working 2D plot-finder with admin + live data for one sample development. 2. Four-angle rotation with per-angle visual hotspot editor. 3. **Multi-tenancy proven** — our non-technical team creates a second development from scratch, no developer (the acceptance test above). 4. Per-development module toggles + house-type data model. 5. Embedding, polish, analytics, handover + documentation. - We provide all imagery, plot data, and brand assets. - Source code, repository access, and full IP transfer on final payment are required. - A short paid trial task (a single clickable-hotspot prototype on one of our plan images) is welcome before committing to the full build.