Quartz 5

TDW Tech Ecosystem: Strategic Architecture & Visual Matrix

Properties1
tagsintelligence--active

5 min read

TDW Tech Ecosystem: Strategic Architecture & Visual Matrix

This strategic playbook serves as your thought partner and architectural framework for managing the TDW franchise technology narrative. It translates the high-level principles established in your drafted email into a structured system that empowers HQ, protects your fractional bandwidth, and provides a clear path forward for front-line conversations with highly motivated, technical owners like Thiago.

🗺️ The Core Strategic Philosophy

IMPORTANT

The Fractional CTO Mandate: Protect Kevin’s 1:1 bandwidth. HQ must act as the primary operational and marketing shield. Tech requests are business-case decisions, not individual support tickets.

The Golden Law: New technology capabilities require new financial and operational investments. There is no such thing as “free automation” at scale.

graph TD
    A[Franchisee Request: RevOps & AI] --> B{Does it belong in Core?}
    B -- Yes: Standardizing is Expensive --> C[Option 1: Increase Network Tech Fees]
    B -- No: Keep Fees Flat --> D[Option 2: Individual Add-ons / HQ-Optional]
    B -- No: Let Owners Build --> E[Option 3: Open Sandbox / Owner-Optional]
    
    style C fill:#f96,stroke:#333,stroke-width:2px
    style D fill:#9cf,stroke:#333,stroke-width:2px
    style E fill:#bbf,stroke:#333,stroke-width:2px

📊 TDW Tech Ecosystem Matrix (The A/B/C Tiers)

This visual matrix clarifies exactly where technology elements reside, who is responsible for funding them, who owns the support burden, and how integrations are handled.

TierEcosystem LayerIncluded ElementsFunding ModelSupport & MaintenanceIntegration Status
AHQ-Core
(The Operational Minimum)		• Google Workspace
• Quo (1 account/user, 1 main #)
• PocketSuite (1 account/location)
• QuickBooks Online
• Standard KPI Dashboard datastream
• National & Local marketing spend		Included in standard, flat franchise tech fees.HQ Supported: 100% managed and maintained by HQ operations and vendors.Hard-wired, automated, and pre-configured out of the box.
BHQ-Optional
(The RevOps Accelerator)		• HubSpot CRM accounts (for sales reps)
• Gemini Advanced (AI Power Users)
• Data Studio Pro (Custom dashboarding)
• Zapier accounts (Individual)
• Segmented/Additional Quo numbers		Owner Paid: Individual unit-level add-ons billed directly or via HQ pass-through.Co-Shared: HQ provides templates & vendor access; owner manages day-to-day use.Supported plug-and-play APIs, standardized Webhooks, and HQ templates.
COwner-Optional
(The Open Sandbox)		• Task Managers (Asana, Monday, ClickUp)
• Custom CRM platforms
• Third-party AI/Agent automations
• Custom local website builders		Owner Paid: 100% funded individually by the local franchise owner.Owner Supported: Zero HQ support. Franchisee owns the technical debt.Open Integrations: Hook into Tier A/B via Zapier (connecting to 9,000+ tools since Dec 2025).

👥 HQ Internal Sync Agenda (Grant + Savanna + Kevin)

Before interfacing with Thiago, HQ must align. Here is the recommended structure for your internal sync.

1. Unified Narrative Alignment (10 mins)

  • The Goal: Shift the conversation from “Why hasn’t HQ built this?” to “How can HQ help Thiago leverage our open sandbox to build what he needs, while protecting the network from fee increases?”
  • The Stand: HQ remains lean to keep franchise fees predictable. If we built an end-to-end custom HubSpot/AI machine for everyone, fees would double.

2. Marketing vs. Product Distinction (10 mins)

  • Lead Generation (Savanna’s Domain): National brand building and local ad spend execution.
  • Lead Conversion (Owner’s Sandbox): What happens after the lead lands. PocketSuite and Quo are the core capture mechanisms. Custom CRM pipelines are local operational choices, not marketing defaults.

3. Roadmap Disclosure Boundaries (5 mins)

  • Define exactly what is “In Flight” versus what is “Visionary.”
  • Do not promise custom integrations. Instead, show how Thiago can deploy Zapier today to link his PocketSuite and HubSpot/CRM systems.

🛡️ Front-Line Talking Points for Savanna (HQ Voice)

Savanna needs to lead this conversation. These talking points arm her with strategic clarity without diving into deep code.

  • On Automation Requests:

    “Thiago, we love how deeply you’ve thought about this funnel. The beauty of the TDW infrastructure is that we’ve purposely left the ‘middle’ of the funnel as an open sandbox. Since December 2025, our entire HQ-Core can be instantly connected to over 9,000 tools—including HubSpot, Asana, and custom AI tools—via Zapier. This keeps your core fees low while giving you unlimited power to customize your business.”

  • On “Why doesn’t HQ just pay for CRM/HubSpot for everyone?”:

    “To build, license, and support an all-in-one platform for the entire network would require a massive, permanent increase in technology fees for every single franchise owner. Many owners want to keep their operations simple and overhead low. We choose to keep our core fee flat and affordable, providing the essential infrastructure and letting power users like you layer on premium tools as add-ons.”

  • On the Feedback Loop:

    “Your feedback is incredibly valuable for our roadmap. We track how many owners utilize Tier B and C solutions. If a specific automation or tool becomes a widespread standard that a majority of the network is willing to fund, we then evaluate moving it into the HQ-Core layer.”

🚀 Recommended Next Actions

  1. Deliver the Draft: Your email to Grant is exceptionally strong. It establishes the “financial reality of requests” perfectly and sets the stage for Savanna to lead.
  2. Schedule the Internal Sync: Use this document to run the prep session with Grant and Savanna.
  3. Deploy the Matrix: Use the TDW Tech Ecosystem Matrix as a visual slide or PDF handout during the internal sync and, if appropriate, share a simplified version of it with Thiago to illustrate HQ’s structural boundaries.

Graph View

Backlinks