GTM Coord
A single milestone register where Marketing, Liaison, Design, and PMO read and write the same dates.
GTM coordination ensures the marketing launch date aligns with approval timelines (Liaison), rendered design package (Design), and site readiness (PMO). Today these timelines drift apart and the misalignment is discovered on the eve of launch. The module makes the project milestone register a shared object — marketing schedule, RERA filing, S1 receipt, design freeze, pre-launch teaser — all anchored to one timeline visible to all functions.
- ·New project registered in M03 — GTM planning initiated
- ·Approval timeline update from M04 Liaison
- ·Design freeze date confirmed by Design
- ·Pre-launch teaser campaign launched
- ·MD approval requested for GTM launch construct
- ·Project record with segment and product mix
- ·Approval timeline from M04 (RERA, S1, CC)
- ·Design milestone schedule from M07 (concept, detail, renders)
- ·Site readiness status from PMO
- ·Market intelligence from Marketing
- ·Renders and 3D walkthrough assets from Design
- ·Pricing strategy proposal from Sales
- ·Brand and creative direction from Marketing
- ·Sales kit content drafts
- ·Cross-function milestone register — Marketing + Liaison + Design + PMO write to one timeline
- ·GTM launch construct planning — sequencing of teaser, soft launch, full launch
- ·Channel mix planning across own offices, brokers, digital
- ·Pricing strategy aligned to segment, micro-market, and competitive intelligence
- ·Sales kit assembly from project record artefacts
- ·GTM policy per segment
- ·Pricing approval policy with MD sign-off thresholds
- ·RERA disclosure policy mandatory before sales open
- ·Brand guidelines policy for all marketing assets
- ·GTM date locked only after cross-function readiness confirmed
- ·Pricing change above threshold requires MD approval
- ·Sales open only after RERA registration received and CC issued
- ·Misalignment between Marketing date and approval date triggers immediate escalation
- ·GTM strategy document per project
- ·Marketing schedule and channel plan
- ·Render and asset package
- ·Pre-launch teaser campaign assets
- ·Sales kit (brochures, model unit, digital walkthroughs)
- ·Pricing card with MD approval
- ·Milestone register updated with launch dates and pre-launch milestones
- ·Cross-function dependencies anchored to GTM date
- ·GTM date locks dependent milestones across Liaison, Design, PMO
- ·Sales open triggers customer onboarding and BelleVie provisioning (M24)
- ·Pre-launch teaser triggers brand asset distribution
- MarketingOwns GTM strategy, launch construct, pricing, renders
- LiaisonApproval timeline as binding input
- DesignRender package and freeze dates
- PMOSite readiness and milestone consolidation
- MDGTM launch approval
- 01Brief from BD to Marketing and Sales
- 02Develop marketing strategy — channels, messaging, pricing, launch construct
- 03Renders and GTM deck
- 04Pre-launch teaser campaign
- 05Cross-check launch date against Liaison, Design, PMO milestones
- 06GTM launch — full launch with sales open
- 07Real-time schedule tracking against milestone register
GTM date is Marketing's; approval date is Liaison's; freeze date is Design's; they drift.
All four functions write to one milestone register; drift surfaces immediately.
Andheri GTM locked for 2 July. Cross-check passes — Approvals on track for receipt 18 June, Design renders ready 25 June, site cleared for pre-launch teaser shooting 20 June. Date locked in milestone register; all dependents auto-anchored.
- ·GTM strategy document
- ·Marketing schedule
- ·Render package
- ·Pre-launch teaser assets
- ·Milestone register entries
GTM date and approval timeline drift apart across owners. The mismatch is found in the launch week, by which time changing either is painful and expensive.
No external system integrations — module operates on internal records.