Residential home-building trust platform
OVERSITE

Oversight of your site — the homeowner's agent for building a house in Bengaluru.

ProjectOverSite — PMC & compliance platform
LocationBengaluru — BBMP / BDA / Gram Panchayat
Prepared forSivaram Kuppachi & Vaseem Ahmed
Drawn fromInternal strategy blueprint
DateSeptember 2026
StatusV1 — Baseline for build
PurposeThe working reference the two of you ideate against, argue with, and overwrite as real decisions get made. Nothing here is final — it's the first mark on the drawing.
Read me first

This is v1, not gospel. Treat every number as a placeholder for the real one you'll get from a pilot, and every open gap (Section 12) as a blocking task, not a footnote. When you and Vaseem change your minds on something here, that's the plan working — cross it out and move on.

01 — Executive summary

Nobody stands on the homeowner's side of the table.

Individual home building — an owner directly appointing an architect, contractor, carpenters, plumbers — is a real, large slice of Indian construction, and it runs on trust, hope, and WhatsApp threads. OverSite is the neutral, tech-enabled "trusted lieutenant" that gives the homeowner visibility, compliance guidance, and PMC oversight — without ever becoming their contractor.

$265.7B
India residential construction market, 2025 (IMARC)
~46%
Implied single-family / individual-home share of that market
6–10%
Typical PMC fee, as % of construction cost — our core revenue line
15–20%
Typical cost overrun on unsupervised, owner-managed builds
02 — The problem, broken down

Four deficits. Fix one, and the other three still burn the owner.

Solving only tracking, or only compliance, doesn't close the trust gap. All four compound each other.

Trust deficit

No accountability layer

Vendors are hired on referrals with no neutral party to answer to when things go wrong.

Visibility deficit

No shared system of record

Owner rarely knows real schedule vs. plan, real cost vs. budget, or what's done vs. pending.

Compliance complexity

Jurisdiction is non-obvious

Owner doesn't know if their land needs BBMP, BDA, or Panchayat approval — or what e-Khata, EC, CC, OC even mean.

Fragmentation

No single point of coordination

Architect, contractor, carpenter, plumber, electrician are all sourced independently, with no one owning the journey.

03 — Positioning

The one strategic choice everything else depends on

We are the homeowner's agent, not their contractor. OverSite never becomes the general contractor or design-build firm — the owner always appoints and pays their own vendors.

Trust is earned by staying structurally on the owner's side. Fee logic, escrow design, and incentives should never quietly convert OverSite into an advocate for the vendor.

04 — Platform architecture

Eleven modules, one journey — built in parallel, launched with intent

Every module works as an independent entry point. The four flagged BUILD FIRST are the trust wedge — the ones that need to be right before anything else earns attention.

01
Land & Legal Compliance Checklist
Sale deed, EC, khata upload → flags gaps and next documents
Build first
02
Jurisdiction Mapper
GPS pin → determines BBMP / BDA-layout / Gram Panchayat path
Build first
03
Approvals Guidance Engine
Step-by-step plan approval, CC, NOCs, OC — who to approach and when
Build first
04
Home Loan Tab
Eligibility pre-check, lender referrals, construction-linked disbursement docs
05
Architect Marketplace
Segmented by specialty — conventional, earth/natural, green/sustainable
06
Contractor Marketplace
Vetted database with capacity, specialization, verified track record
07
Plan Upload & Digital Record
Sanctioned drawings become the reference for tracking and PMC checks
08
Project Tracking
Schedule, cost, work done / pending / upcoming — one dashboard
09
PMC Oversight Layer
Milestone visits, quality checklists, payment certification gates
Build first
10
Vendor Coordination Hub
Shared thread across owner, architect, contractor, sub-trades
11
Document Vault & Payment Ledger
Contracts, invoices, payment milestones, warranty documents
05 — The compliance engine

BBMP, BDA, Gram Panchayat — the jurisdiction nobody explains

This is the hardest-to-replicate module, and it's also where every existing competitor stops short.

JurisdictionWho controls itWhat it means for the owner
BDA
Bangalore Development Authority
Approves layouts, not individual house constructionEven inside a BDA-approved layout, the house itself still needs individual plan approval from BBMP.
BBMP
Bruhat Bengaluru Mahanagara Palike
Building plan approval, Khata (A & B), Occupancy Certificate, inside city limitsThe primary path for most in-city plots — requires a licensed architect, e-Khata (mandatory since July 2025), and FAR/setback compliance via BPAMS.
Gram Panchayat
outside BBMP limits
Governs fringe areas — Sarjapur, Hoskote, Devanahalli, Kanakapura outskirtsHigher risk: GP khata can mean loan rejection, resale difficulty, and OC denial if the area is later absorbed into BBMP — a disclosure the product must surface clearly, never bury.
06 — Competitive landscape

Not empty. But nobody owns the full journey.

PlayerModelWhere they stop short
BuildNext, PrithuVertically-integrated design-build contractor with an app layerThey are the contractor — owner isn't appointing independent vendors, they're buying a build.
Brick&Bolt
Bengaluru-founded, VC-backed
Neutral marketplace + escrow + tech-driven quality checks — closest peer modelConstruction-phase only. No pre-construction land/legal due diligence, no specialty architect discovery, no loan tab.
BuildControlB2B SaaS sold to contractors / PMCs for their own opsNot homeowner-facing at all — no trust layer for the owner.
OverSiteNeutral platform + PMC, starting at land due diligence through to marketplace and loan tabGoes earlier (land/legal) and wider (specialty architects, loans) than any of the above.
07 — PMC service design

The revenue engine, priced against a real benchmark

6–10% of construction cost is the industry norm — and it's a net saving against the 15–20% overrun an unsupervised build typically eats.

TierTriggerFee logic
Compliance-onlyOwner just wants the land/legal/jurisdiction checklist doneFlat fee per checklist — low-ticket, high-volume funnel entry point
PMC — StandardOwner already has an architect/contractor, wants oversight only% of construction cost, lower end of the 6–10% band
PMC — Full ConciergeOwner wants vendor sourcing from our marketplace + full oversight + payment certification% toward the higher end, reflecting sourcing + coordination + oversight combined
08 — Go-to-market, Bangalore phase 1

Compliance is the wedge. PMC is the monetization event.

Supply side first, narrow and deep
20–30 verifiably good architects (across specialties) and contractors — quality over quantity, since trust is the product.
Demand side via the compliance wedge
Free/low-cost land & jurisdiction checklist as the acquisition hook — highest-anxiety, highest-trust moment.
Convert checklist users into PMC clients
Compliance (high volume) → marketplace matching → PMC fee (the actual funnel).
Cover all three jurisdictions, concentrate effort in 2–3 corridors
Jurisdiction-agnostic coverage is the promise — but focus vendor recruitment and PMC visit capacity around high-growth, GP-fringe areas like Sarjapur and Devanahalli first.
09 — Risks & mitigations

Where this breaks, and the guardrail for each

CategoryRiskMitigation
Market / adoptionOwners won't pay a PMC fee before seeing valueLead with the free/low-cost compliance checklist as the trust-building wedge
Execution / vendor qualityOne bad marketplace recommendation damages trust irreversiblySmall, deeply-vetted founding vendor cohort; PMC oversight as a check even on our own picks
Regulatory / liabilityWrong compliance guidance creates real legal exposureLegal review before any guidance ships; clear disclaimers; human-in-the-loop on edge cases
Incentive driftContractor-side commission alongside owner-side fees could bias us against the ownerKeep fee logic transparent; avoid stacking incentives that reward the vendor relationship over the owner's
CompetitiveBrick&Bolt or a fast-follower extends upstream into compliance firstMove fast specifically on Modules 01–03 — that's the differentiation window
FinancialPMC fee collects in milestones over a 6–18 month build; platform cost is upfrontModel fee-collection timing explicitly against burn before over-building
10 — What's still missing

Being direct: what this blueprint still owes you

Before this is investor-ready or execution-ready, these are open — not footnotes, blocking tasks.

Open

Unit economics model

Actual CAC, PMC take-rate at scale, vendor-side economics, and a real financial projection — not built here since this was scoped as a strategy/product blueprint, not a financial plan. Worth a dedicated follow-up once pilot data exists.

Open

Legal opinion on RERA applicability

Whether RERA applies to an individual homeowner building on their own plot in Karnataka (as opposed to a developer/promoter) is unresolved — get a definitive legal read before the product states anything as fact in-app.

Open

Payment / escrow architecture

Whether funds route through OverSite or are simply gated by our sign-off has real money-transmission and GST implications — needs a decision before Module 11 is built.

Open

Bangalore-specific TAM

Annual BBMP/BDA/Panchayat individual building-plan approvals aren't cleanly published — likely needs an RTI request or industry-body data (CREDAI Bengaluru).

Open

Entity structure & founding roles

Legal entity, cap table, and how you and Vaseem split ownership and responsibility aren't addressed in this document.

11 — The name

OverSite: chosen, checked, and why it sticks

OverSite
The pun does the positioning: it sounds like "oversight," it means literal sight into your site, and it's clean of collisions in Indian construction/proptech registries — checked, not guessed. It also stretches past PMC into loans and marketplaces later (OverSite Compliance, OverSite PMC) without needing a rename.
Runner-up: Sitewalla Runner-up: Kattada Avoided: Neev (taken — Neev Buildtech, Neev Infrastructure) Avoided: Basera (taken — Basera Infra, TheBasera) Avoided: Bandobast (taken — registered co. + existing app)
12 — Next 90 days

What to actually do with this document

Legal review — RERA applicability + escrow architecture options
2–3 weeks. Blocks Module 04 and Module 11 decisions.
Recruit the founding vendor cohort
20–30 vetted architects and contractors across target Bangalore corridors. 4–6 weeks, run in parallel.
Build the compliance engine v1 — Modules 01–03
The highest-priority build item and the trust wedge. 6–8 weeks.
Run the PMC service manually with 3–5 pilot homeowners
Ops-heavy, minimal tech — validate the fee, the workflow, and the payment-gating mechanism before over-building around it.
Build the real unit economics model
Once pilot data exists — closes gap 10.1.
Re-scan the competitive set
Fresh, current data on Brick&Bolt and any fast-movers before finalizing GTM messaging.