{ "title": "Upper Kharadi — management interpretation and operating controls", "asOf": "2026-10-15", "status": "Narrative prepared; final strategy and forecast metrics to be joined by root", "strategyFile": "work/data/strategy.json", "sections": [ { "id": "evidence_audit", "title": "Evidence supports a decision process, with explicit coverage limits", "what_data_says": "The core research comprises five distinct files from two providers: two CRE Matrix registration datasets and a PropEquity report with two workbook supplements. The combined CRE warehouse retains 11,909 source rows. The broader Gmail discovery exhausted 10 result pages across five all-history searches, classified 602 unique message matches, and fully read 12 relevant candidate messages. The consolidated register has 47 files or access-attempt entries; it does not represent 47 independent research studies.", "why_it_matters": "A large source register does not create independent corroboration. Registration records, research absorption estimates, unit specifications, media inventories and land drawings answer different questions and require separate denominators.", "recommended_action": "Use the current CRE cohort for observed registration activity, the dated PropEquity study for market structure and benchmark context, and the supplementary archive for narrowly defined planning evidence. Keep source, date, page or row and processing status beside every decision. Preserve raw records and exclusions so the result is reproducible.", "confidence": "High for extraction counts; limited for completeness of the entire market.", "evidenceRefs": [ { "sourceId": "CRE-2026", "rows": "2–8840" }, { "sourceId": "CRE-2025-M", "rows": "2–3071" }, { "sourceId": "TARUSH-PE-20260525-PDF", "pages": [ 1, 91 ] }, { "sourceId": "TARUSH-PE-CHECKLIST-XLSX", "scope": "all three sheets" }, { "sourceId": "TARUSH-PE-RERA-XLSX", "scope": "all sheets" } ], "auditFiles": [ "work/discovery/broader/search_audit.json", "work/discovery/broader/inventory.json", "work/discovery/tarush/source_conflicts.json" ], "limitations": [ "Nine supplementary DWG attachments were catalogued but could not be opened by the connector.", "Incomplete scanned permission/drawing documents are explicitly marked not fully studied in the source register.", "Two contact-registration CSVs and one electrical template were excluded as irrelevant.", "173 operator bookings from 2012 remain a separate historical archive and never enter current demand." ], "metricBindings": [ "data.audit", "analysis.qualityCounts" ] }, { "id": "geography", "title": "Define the catchment around the supplied site", "what_data_says": "The user pin is 18.551876, 73.966402. CRE Matrix labels the recent cohort Kharadi, Wagholi and Manjari; it does not supply a separately verified Upper Kharadi boundary. PropEquity uses its own Kharadi–Upper Kharadi–Wagholi catchment. These labels cannot be substituted without a project-level crosswalk. The JLL Pravin Sanghavi land opportunity is approximately 2.128 km north of the user pin by straight-line distance, so it is a different site. The S. No. 39 permission package has not been spatially matched to the user pin.", "why_it_matters": "A neighborhood premium or a sanctioned area from another site could materially change the proposed product and pricing. Manjari, Mundhwa and Hadapsar can be buyer-substitute areas, but their different geography and observation dates must remain visible.", "recommended_action": "Use the pin as the center of a project-by-project catchment register. Obtain the proposed survey numbers, access road, usable approach width and developable boundary before importing site-specific conclusions. The PropEquity report subject site has not been matched to this pin; its 43-acre site, road, distance and pricing adjustments are not adopted as facts about the current proposal. Keep the older Mundhwa dataset as a separately dated comparator. Resolve the single Kharadi/Fursungi description conflict in CRE before geographic aggregation.", "confidence": "High for supplied pin and distinct JLL location; unresolved for parcel matching and comparable travel catchments.", "evidenceRefs": [ { "sourceId": "USER-SITE", "url": "https://maps.app.goo.gl/srjt3WC34J2pqmTUA" }, { "sourceId": "BRO-00", "emailId": "1a0fceef88066f67" }, { "sourceId": "BRO-13", "pages": [ 1, 2 ] }, { "sourceId": "TARUSH-PE-20260525-PDF", "pages": [ 19, 24, 52 ] }, { "sourceId": "CRE-2026", "field": "Micromarket and Description" } ], "metricBindings": [ "site.latitude", "site.longitude" ], "distanceMethod": "Haversine using Earth radius 6371 km. Straight-line distance only; no road travel time is inferred." }, { "id": "provider_trends", "title": "The five-year provider series shows a slower 2025 after the 2023 peak", "what_data_says": "Within the PropEquity workbook catchment, reported absorption rises to 9,200 units in 2023 and then declines to 7,457 in 2024 and 5,620 in 2025. New launches are 8,942 in 2024 and 5,233 in 2025. The report describes a higher carpet-based weighted absorption price in 2025 than in 2021 and a larger 3 BHK share in the 2025 configuration mix. These are provider-reported historical measures, accessed in February 2026, not an October 2026 inventory census.", "why_it_matters": "Higher prices and a larger premium share can coexist with fewer units absorbed. Launch planning should therefore test both the depth of the buyer pool and the attainable ticket, rather than assuming price appreciation implies a faster sales pace.", "recommended_action": "Show the 2021–2025 provider trend in its own panel. Use exact workbook annual unit totals for that series and display the PDF reconciliation alongside it. Compare it directionally with the 12-month CRE observation period, without joining the two into one transaction series or adding provider absorption to registrations.", "confidence": "Moderate for the direction within the reported catchment; reduced by source inconsistencies and dated scope.", "evidenceRefs": [ { "sourceId": "TARUSH-PE-CHECKLIST-XLSX", "sheet": "Catchment BHK Split", "rows": "4–8", "columns": "H and Q" }, { "sourceId": "TARUSH-PE-20260525-PDF", "pages": [ 19, 20, 21, 24, 26, 91 ] } ], "limitations": [ "Exact workbook totals are 34,534 launches and 36,440 absorption, while PDF headlines are 34,500 and 36,430; some differences exceed ordinary rounding.", "Provider absorption is not IGR registration volume and includes apartments, independent floors and villas under its stated scope.", "The printed price CAGR uses an unclear interval convention; prefer endpoint total change with dates rather than silently copying the CAGR.", "The report is named FINAL but its disclaimer calls it a draft; it records no primary interviews or physical site visit." ], "metricBindings": [ "providerAnnual", "providerPriceHistory" ], "annualValuesSource": "work/discovery/tarush/aggregate_evidence.json" }, { "id": "recent_registration_and_product_coverage", "title": "Recent registrations guide product hypotheses; carpet coverage constrains precision", "what_data_says": "The newer CRE source contains 8,839 registrations dated October 2025 through September 2026; the older Mundhwa source contains 3,070 dated April 2024 through June 2025. Raw area labels across both sources are 5,349 carpet, 5,640 usable carpet and 920 unspecified. Traceable literal-description extraction adds 4,559 explicit carpet figures and 269 explicit configurations without overwriting source carpet labels. After comparable-sample exclusions, the recent residential cohort contains 8,836 records, including 6,912 eligible carpet-price observations; its source-coded P cohort has 8,181 records and 6,330 eligible carpet-price observations. Configuration remains unspecified in 6,076 normalized warehouse records. Two and three BHK dominate known configurations, but each exact size band still requires its own sample and project-composition check.", "why_it_matters": "The whole dataset is not a uniform carpet-price sample. Missing labels are unlikely to be random across projects and periods, so a small exact-size cluster can understate products whose source records use usable carpet. A low observed count does not by itself prove weak demand or a supply gap.", "recommended_action": "Present raw coverage, valid price eligibility and each filtered sample size separately. Use explicit source-labeled carpet or a traceable carpet figure stated in the source description for derived carpet rates. Keep the original area and exact extraction evidence; do not convert usable carpet by an assumed multiplier. Compare product bands within matched geography, period, sale-type code and project type; validate promising bands against dated supply and actual released units before fixing allocation.", "confidence": "Moderate directional product evidence after explicit-text enrichment; source definitions, project mix and site-price transfer remain material limits.", "evidenceRefs": [ { "sourceId": "CRE-2026", "rows": "2–8840", "fields": [ "Registration Date", "Configuration", "Area", "Area Type", "Consideration", "Sale Type" ] }, { "sourceId": "CRE-2025-M", "rows": "2–3071", "fields": [ "Registration Date", "Area", "Area Type", "Consideration" ] } ], "limitations": [ "Carpet is source-labeled, not independently checked against deeds or sanctioned RERA plans.", "Source codes P and S must retain their original values unless their primary/resale interpretation is documented.", "Ten zero-area records, eight values below ₹10 lakh, the geographic conflict and non-apartment products require transparent comparable-sample flags, not silent deletion.", "Whole-cohort medians should not be compared across the disjoint observation windows as if they measured same-period location premiums.", "The extraction was manually checked against 44 source-description examples across 37 projects, not against original government deed scans; this is a bounded quality review, not independent registry verification." ], "metricBindings": [ "analysis.currentAll", "analysis.currentPrimary", "analysis.productOpportunities", "analysis.areaTypeCoverage", "analysis.qualityCounts" ], "metricBindingPolicy": "Root supplies final comparable-sample counts and prices. Raw source counts in prose are retained only as audit facts." }, { "id": "supply_and_57_avenue", "title": "Competitive supply must be dated and reconciled before calling an opportunity underserved", "what_data_says": "The research contains competitor launches, cumulative absorption and RERA unit specifications, but those measures do not establish today’s released and unsold stock. The PDF gives a 5,400-unit unsold snapshot in one section and completion cohorts totaling 10,405 elsewhere. Their scope is unresolved. Panchshil’s official 57 Avenue page advertises 398 residences in four towers, including 3.5 BHK, 4.5 BHK and 3 BHK duplex formats. Its 1.1 million sq. ft. project-area claim has no explicit area basis.", "why_it_matters": "Supply-adjusted product rankings are only as strong as the released-stock denominator. A large luxury project can compete for higher-ticket buyers without validating demand for that ticket. Project total units and current unsold units are different quantities.", "recommended_action": "Maintain a dated competitor stock sheet by project, phase, tower and typology, distinguishing sanctioned, launched, released, booked, cancelled, registered and unsold units. Keep 57 Avenue in the luxury-substitute watchlist with unconfirmed release dates, prices and unsold units. Exclude land offers and conceptual drawings from committed future supply.", "confidence": "High for official 57 Avenue marketing disclosure; low for present unsold stock and exact competitive timing.", "evidenceRefs": [ { "sourceId": "TARUSH-PE-20260525-PDF", "pages": [ 25, 28, 29, 38, 49 ] }, { "sourceId": "TARUSH-PE-RERA-XLSX", "scope": "unit and tower sheets" }, { "sourceId": "BRO-WEB-57", "url": "https://www.panchshil.com/57avenue" }, { "sourceId": "BRO-26", "emailId": "19d439eccba077ca" } ], "limitations": [ "The 57 Avenue official map script pin is 18.5291662, 73.9283494, approximately 4.740 km southwest of the user pin, but its map info window says Wakad while the main page says Mundhwa. Treat placement as provisional pending independent validation.", "The March 31, 2026 email establishes marketing by that date; it does not prove the launch date.", "RERA identifier PR1260002503013 is displayed in developer material and has not been independently matched to a current RERA record.", "RERA workbook rows describe units, not bookings or registrations; missing Gera tower detail and Dolce Vita count differences must stay visible." ], "metricBindings": [ "competitorBenchmarks", "sourceConflicts", "supplementarySupply" ] }, { "id": "buyer_hypotheses", "title": "Buyer personas are testable hypotheses, not observed attributes", "what_data_says": "The transaction evidence records property and registration characteristics, not buyer income, occupation, current residence, commute, family needs or purchase motivation. The provider interprets the higher 3 BHK and premium-ticket shares as a shift toward larger homes. MyGate supplies society-level media inventory, not verified households currently seeking to buy.", "why_it_matters": "A product mix can fit the measured ticket distribution while the assumed acquisition message targets the wrong buyer. Treating residents of a premium society as verified prospects would overstate the sales funnel.", "recommended_action": "Test three propositions through consented enquiries and structured visits: compact two BHK for a first ownership or cost-controlled upgrade; efficient three BHK for a household needing another room; larger three or four BHK for a premium upgrade. Record budget, acceptable carpet size, current locality, destination commute, purchase horizon, financing readiness and reason lost. Report buyer shares only from completed, deduplicated questionnaires.", "confidence": "Hypotheses only until measured through current CRM cohorts.", "evidenceRefs": [ { "sourceId": "CRE-2026", "scope": "field availability" }, { "sourceId": "TARUSH-PE-20260525-PDF", "pages": [ 26, 27, 91 ] }, { "sourceId": "BRO-21", "sheet": "Sheet2", "rows": "2–161" } ], "hypotheses": [ { "segment": "First ownership / cost-controlled upgrade", "test": "Compact versus regular two BHK at a matched all-in ticket; measure visit-to-net-booking and finance qualification.", "avoidClaim": "Do not infer household income or employment from registered ticket." }, { "segment": "Additional-room upgrader", "test": "Efficient three BHK versus a larger two BHK; measure willingness to trade extra carpet for layout and ticket.", "avoidClaim": "Do not label all three BHK buyers families or end users." }, { "segment": "Premium upgrader", "test": "Larger three BHK / four BHK with privacy, finish and amenity propositions; measure depth at the full payable ticket.", "avoidClaim": "Do not infer a high-volume luxury opportunity from marketing inventory or a small CRE sample." } ], "metricBindings": [] }, { "id": "pricing_and_elasticity", "title": "Price benchmarks support negotiation ranges; they do not identify elasticity", "what_data_says": "CRE allows registered consideration divided by eligible source-labeled carpet, plus matched project and monthly comparisons. PropEquity supplies dated carpet-price benchmarks and quoted all-inclusive comparisons. Its ₹13,700 per sq. ft. recommendation relates to the study’s client site assumptions and May 2026 assessment. None of these sources supplies a controlled change in price, simultaneous released stock and measured enquiry conversion for the proposed project.", "why_it_matters": "A negative relationship between price and registrations may reflect launch timing, unit mix, floor premiums, construction stage, discounts or registration lag. A positive relationship may reflect premium project mix. Neither estimates the sales response to changing the proposed price.", "recommended_action": "Build an opening-price corridor from comparable project medians and percentiles, record carpet basis, effective date and included charges, then convert it to the proposed unit’s full customer ticket. Show sensitivity at several explicit price points as a scenario. Test actual offers through controlled release cohorts and review net bookings, lost reasons and net realization before escalating.", "confidence": "Moderate for matched historical benchmarks; no causal elasticity estimate.", "evidenceRefs": [ { "sourceId": "CRE-2026", "fields": [ "Consideration", "Area", "Area Type", "Registration Date", "Project" ] }, { "sourceId": "TARUSH-PE-20260525-PDF", "pages": [ 21, 24, 52, 54 ] } ], "controls": [ "Separate base rate, floor/view premiums, parking, club and other charges, tax and government charges.", "Compare equivalent carpet definitions and possession stages.", "Track the realized net price after incentives and cancellations, not brochure rate alone.", "Keep cross-sectional correlation, source price history and modeled price sensitivity in different fields." ], "metricBindings": [ "analysis.markets", "analysis.projects", "analysis.productOpportunities", "strategy.pricing" ] }, { "id": "execution", "title": "Build the launch around measurable weekly capacity", "what_data_says": "The 25 lakh sq. ft. development and 10 lakh sq. ft. launch objective are planning constraints. Historical market records do not establish the proposed project’s lead cost, qualification, visits, booking conversion, cancellations or registration lag. The available MyGate email is a vendor quotation, with no measured campaign outcomes.", "why_it_matters": "A mathematically sufficient funnel can fail because of inadequate visit capacity, poor finance qualification, duplicated channel leads, release delays or agreement processing. Gross bookings, net bookings, agreements, registrations and collections must be tracked separately.", "recommended_action": "Run a four-week pilot before scaling the launch allocation. Use the editable channel and staffing assumptions below, instrument every stage and replace assumptions with observed weekly cohorts. Stage inventory releases around verified net booking and agreement performance. Keep a weekly management review of price realization, cancellations, stage ageing, channel concentration and unsold mix.", "confidence": "Operational plan and editable assumptions; no forecast probability is claimed.", "evidenceRefs": [ { "sourceId": "BRO-MEDIA-EMAIL", "emailId": "19e1c383b7e043e4" }, { "sourceId": "BRO-20", "sheet": "Sheet1", "rows": "2–84" }, { "sourceId": "BRO-21", "sheet": "Sheet2", "rows": "2–161" } ], "metricBindings": [ "strategy", "model", "scenarioPlan" ], "metricBindingPolicy": "Final product counts, saleable allocations, monthly forecasts and funnel totals must be joined from strategy.json and the final model. This narrative deliberately contains no forecast totals." }, { "id": "data_requisites", "title": "Resolve the few missing inputs that change the investment decision", "what_data_says": "The main limitations are comparable area coverage, unmatched catchments and source periods, unresolved competitive stock, and absent current CRM conversion evidence. The source report also uses a smaller project potential and inconsistent unit arithmetic, so its proposed inventory cannot be copied into the user’s 25 lakh sq. ft. plan.", "why_it_matters": "These inputs determine whether the recommended size, price and release plan are achievable. They matter more than collecting additional general newsletters or repeating the same provider tables.", "recommended_action": "Prioritize the requisites below, keep their owners and decision impact visible, and rerun the product and launch model as each is resolved. Proceed with a clearly labeled planning recommendation while withholding unsupported claims of guaranteed velocity, verified unsold stock or measured elasticity.", "confidence": "Specific, actionable data gaps.", "evidenceRefs": [ { "sourceId": "TARUSH-PE-20260525-PDF", "pages": [ 25, 28, 52, 54, 55, 91 ] }, { "sourceId": "TARUSH-PE-RERA-XLSX", "scope": "all sheets" }, { "sourceId": "CRE-2026", "scope": "field definitions and row provenance" } ], "metricBindings": [ "openQuestions", "sourceConflicts" ] } ], "channelPlan": [ { "channel": "Channel partners", "owner": "Channel head", "pilotAction": "Invite a selected local partner roster to product and full-ticket briefings; use one partner ID and one household ID for attribution. Review qualified visits and net bookings weekly.", "editableAssumptions": { "partnersBriefedPerWeek": 20, "activatedPartnerSharePct": 40, "qualifiedVisitsPerActivePartnerPerWeek": 3 }, "capacityFormula": "weekly qualified visit capacity = briefed partners × activated share × visits per active partner", "evidenceStatus": "Planning assumptions; no existing partner productivity data supplied.", "scaleGate": "Scale only partners with traceable attended visits, finance-qualified buyers and acceptable net realization; reconcile duplicate direct leads." }, { "channel": "Search and direct digital", "owner": "Performance marketing lead", "pilotAction": "Separate campaign groups by configuration and complete ticket. Use dedicated enquiry forms and tagged landing pages. Test one material offer or message change per cohort.", "editableAssumptions": { "pilotWeeks": 4, "weeklyBudgetINR": 150000, "costPerLeadINR": 1500 }, "capacityFormula": "weekly paid leads = weekly spend / observed cost per deduplicated lead", "evidenceStatus": "Budget and cost are editable planning assumptions, not a supplied campaign benchmark.", "scaleGate": "Judge cost per qualified visit and per net booked unit after a defined follow-up window; do not scale from click-through rate alone." }, { "channel": "Society and workplace outreach", "owner": "Direct sales lead", "pilotAction": "Use approved resident or employer channels to run two invitation-only product sessions per week; collect explicit enquiries and preferred appointment slots. Start with eastern Pune societies that match the ticket and commute hypothesis.", "editableAssumptions": { "sessionsPerWeek": 2, "qualifiedAppointmentsPerSession": 10, "attendedVisitSharePct": 60 }, "capacityFormula": "weekly attended visits = sessions × qualified appointments × attended share", "evidenceStatus": "Activity and conversion assumptions; MyGate site lists describe possible media locations, not verified demand.", "scaleGate": "Expand locations only after attended-visit quality and net-booking outcomes justify the spend." }, { "channel": "MyGate media test", "owner": "Marketing procurement", "pilotAction": "Reconfirm the vendor’s current eastern Pune targeting, unique reach, overlap, creative deliverables and quotation before buying a small tagged campaign.", "editableAssumptions": { "sourceQuoteCostINRExGST": 190000, "sourceQuoteDays": 30, "sourceQuoteImpressions": 172727 }, "capacityFormula": "Leads and bookings remain unestimated until tagged response and conversion are measured.", "evidenceStatus": "Vendor quote dated May 12, 2026 for another brand; not current committed pricing. No actual results supplied.", "sourceRefs": [ { "sourceId": "BRO-MEDIA-EMAIL" } ], "scaleGate": "Reconcile delivered impressions and unique reach, then compare qualified-visit and net-booking acquisition cost with direct channels." }, { "channel": "Referral and owned database", "owner": "Customer relationship lead", "pilotAction": "Segment only the company’s authorized current customer and enquiry records; deduplicate households, record referral relationships and track fresh conversion cohorts.", "editableAssumptions": { "outreachAttemptsPerAdvisorPerDay": 35, "workingDaysPerMonth": 26 }, "capacityFormula": "monthly contact capacity = assigned advisers × daily attempts × working days", "evidenceStatus": "Capacity assumption; old operator-booking names and event-contact CSVs are not imported as a prospect pool.", "scaleGate": "Use current opt-in, response and qualification data; report referrals separately from partner-sourced leads." } ], "capacityAssumptions": [ { "role": "Pre-sales response", "assumption": 35, "unit": "fresh lead responses per person per working day", "workingDaysPerMonth": 22, "requiredHeadcountFormula": "ceil(monthly fresh leads / (35 × 22))", "control": "Queue by enquiry time; measure first-response time, attempted contacts and qualified conversations. Attempts do not equal unique leads.", "status": "editable assumption" }, { "role": "Site sales adviser", "assumption": 2, "unit": "attended site visits per person per selling day", "workingDaysPerMonth": 22, "requiredHeadcountFormula": "ceil(monthly attended visits / (2 × 22))", "control": "Reserve time for follow-up and negotiation; add weekend capacity separately after measuring visit concentration. Consistent with the final strategy staffing gate.", "status": "editable assumption" }, { "role": "Agreement and registration coordinator", "assumption": 50, "unit": "completed customer files per person per month", "requiredHeadcountFormula": "ceil(monthly agreements due / 50)", "control": "Track documentation readiness, loan sanction, agreement date, registration appointment and ageing by unit.", "status": "editable assumption" } ], "crmControls": { "recordKey": "One household/enquiry identity linked to one or more interested units; retain source-channel history instead of overwriting it.", "stages": [ "new enquiry", "contacted", "qualified", "appointment", "attended visit", "negotiation", "gross booking", "cancellation", "net booking", "agreement", "registration", "collection" ], "minimumFields": [ "lead/household ID", "channel and partner ID", "campaign and consent source", "created and stage timestamps", "configuration and carpet size", "full ticket and offered terms", "budget and financing readiness", "purchase horizon", "current locality and commute destination", "unit ID and release status", "reason lost or cancelled", "net consideration", "agreement and registration dates", "collection amount and date" ], "weeklyReview": [ "deduplicated fresh leads and stage conversion by entry cohort", "attended visits and adviser capacity", "gross/net bookings and cancellation lag", "agreement/registration ageing and finance readiness", "net realized price after incentives", "channel spend per qualified visit and net booked unit", "released and remaining stock by typology", "collections against due schedule" ], "triggerPolicy": "Set thresholds in the model and review two consecutive comparable weekly cohorts before changing allocation or spend. Investigate price, qualification and availability jointly; do not lower price solely because raw lead count declines.", "outboundActionStatus": "Plan only; no messages, campaigns or outreach sent." }, "unresolvedDataRequisites": [ { "priority": 1, "owner": "Project development", "request": "Survey numbers, parcel boundary and current approved plan for the user pin; reconcile the approved design to the confirmed 25 lakh saleable area, 10 lakh saleable launch objective and 1.4 planning multiplier.", "decisionImpact": "Confirms the proposed scheme and prevents attribution of another site’s entitlement." }, { "priority": 1, "owner": "CRE Matrix / research", "request": "Area-type and sale-type code dictionary; clear distinction between carpet and usable carpet; apartment/villa or other property flags; matched 36-month exports for all selected localities.", "decisionImpact": "Improves eligible sample coverage and allows comparable trend and configuration analysis." }, { "priority": 1, "owner": "PropEquity / research", "request": "Reconcile catchment launch and absorption totals, the 5,400 versus 10,405 unsold cohorts, project/tower counts, conflicting completion dates and Casagrand area labels.", "decisionImpact": "Makes supply-adjusted product ranking and competitive timing defensible." }, { "priority": 1, "owner": "Competitive intelligence", "request": "Dated released/booked/cancelled/unsold inventory and current all-in terms by typology for the key nearby projects, including 57 Avenue; independently confirm locations and RERA phase IDs.", "decisionImpact": "Identifies actual buyer substitutes, available competition and opening-price corridor." }, { "priority": 1, "owner": "Sales operations", "request": "Current deduplicated lead cohorts with channel, stage timestamps, product, ticket, booked unit, cancellation, agreement, registration and collections; acquisition spend and staffing capacity.", "decisionImpact": "Turns the launch funnel from a scenario into a calibrated operating forecast." }, { "priority": 2, "owner": "Finance / project controls", "request": "Construction and selling costs, channel fees, taxes, payment plans, debt terms and phase cash-flow timing.", "decisionImpact": "Allows margin, liquidity and return comparison rather than revenue alone." }, { "priority": 2, "owner": "Buyer research", "request": "Structured, consented current buyer interviews and lost-enquiry reasons for the proposed product bands.", "decisionImpact": "Validates personas, layout trade-offs, ticket limits and objections." } ], "interpretationRules": [ "47 register entries are files or access attempts, not 47 research reports.", "Use source-labeled carpet for CRE; independent RERA validation is pending.", "Do not merge source windows into one market trend.", "Registration counts, provider absorption, sanctioned units, launched units and unsold stock are separate metrics.", "Do not apply the proposed project’s planning multiplier to competitors with unknown area bases.", "Every strategy, channel capacity and forecast assumption remains editable and visibly separate from observed facts." ] }