Acquisition & Licensing Positioning — TLCengine / commutingcost.com

Owner: Krishna Malyala · Date: 2026-06-25 · Status: DRAFT — gated (admin/portal only). Never publish this document. Builds on: gtm/GTM-STRATEGY.md, gtm/PITCH.md, gtm/CAMPAIGN-PLAN.md · Numbers: see CAMPAIGN-PLAN §0 (verified proof points only)

Internal-only. This is the corp-dev / strategic-buyer thesis. It is the close behind the public campaign in CAMPAIGN-PLAN.md. We do not say "acquire us" in public; we manufacture the signals (press, traction, a credible round) that make a buyer connect the dots, and we put this in front of corp-dev via warm intro.

1. The one-paragraph thesis (what we are to a buyer)

We are the true-cost + multiuser layer for trip intelligence — the dimensions every mapping/geospatial/proptech platform is structurally missing. They all solved time, for one or two modes, for one person. We compute the dollar cost of any trip across 9 modes (including chained Park&Ride / Kiss&Ride / Uber+Ride), for two commuters at once, across 32 US+Canada metros, repriced in seconds on a single GPU. The defensible asset isn't the algorithm (RAPTOR is public) — it's (a) the curated national price database (723 GTFS fare feeds, tolls in 36 states, 1,515 CBD garages, 194 GBFS systems, per-ZIP fuel, utility rates) that takes years to assemble and clean, (b) the GPU pipeline that makes refresh free (so the cost layer is live, not a stale annual index), and (c) the multiuser household math that no incumbent's data model can even express. A buyer acquires a capability + dataset + freshness moat they would spend 2–3 years and a team rebuilding — or they license the feed and ship it next quarter.

2. The moat, framed as capabilities the buyer lacks

The frame for every buyer conversation is not "we're better at maps." It's: "Here are four things your platform cannot do today, that families are screaming for, that we already ship national and instant."

The compounding point for a buyer: any one of these is a feature; together they're a category. And they all sit on the same engine + dataset — a buyer gets the whole stack, not a point solution.

3. Comparable acquisitions & valuation framing

These comparables are for framing the strategic logic and magnitude, not a precise valuation. Use them to anchor "buyers in this category pay for capability + data, not just revenue."

Valuation logic to present (not a number, a frame): - Acquisition is priced on capability + dataset + time-to-rebuild, not current ARR. The question a buyer answers is "what does it cost us to build this in-house, with the data, and how many quarters do we lose?" Our answer: a curated 723-feed price DB + GPU pipeline + multiuser engine = a multi-year, multi-person build they skip. - Strategic premium comes from defensiveness: if a competitor (Zillow vs. CoStar; Google vs. Apple Maps; Esri vs. a startup) gets the cost+multiuser layer first, it's a listing-page / map-product differentiator the loser can't quickly match. - The traction signal (from the campaign — consumer reach + press + a credible round) is what moves the price from "acqui-hire" to "strategic acquisition." That's the entire point of running CAMPAIGN-PLAN loud.

4. Per-buyer fit (one page each)

For each: strategic fit · which product it slots into · the pitch · the risk/objection.

4.1 — Google (Maps / Geo / Search)

Strategic fit: Google owns time in mapping and is the canonical "how long" answer. They have repeatedly acquired data/capability layers their own map lacked (Waze for community traffic; ITA for flight pricing; Zagat/local data). Trip cost across modes is a structural blank in Maps — they show a single fare sometimes, never the full stack (tolls+parking+CRZ+fuel), never a 9-mode cost comparison, never a two-person answer. Their ToS even forbids the storage/display that a cost-on-listings product needs, which is the tell that they haven't built the layer.

Slots into: Google Maps directions (a "true cost" tab next to time/route options); Google Search real-estate & local "what does it cost to get there" answers; Google's affordability/commute features in housing search; potentially Waze (cost-aware routing).

The pitch: "Maps answers 'how long.' Families are now asking 'how much' — with $5 gas it's the question that moves the decision. We've built the cost answer across 9 modes, national, repriced in seconds, plus the one thing no map can do: solve for a two-commuter household. It's the next axis of the directions product, and the data moat (723 fare feeds, national tolls/parking/fuel) is years of work you'd skip."

Risk/objection: "We'll build it ourselves." Counter: the algorithm is public, the data is not — the curated, cleaned, national price DB + the freshness pipeline is the multi-year part, and we've done it. Also: NIH culture at Google is real; this is more likely a licensing/data-partnership play than an acquisition unless the consumer traction is undeniable. Position as license-first, with acquisition as the escalation if it moves the needle on Maps engagement.

4.2 — Esri

Strategic fit: Esri is the GIS platform of record for government, planning, real estate analytics, and retail siting. ArcGIS already has Network Analyst (routing, service areas, OD cost matrices) and Business Analyst (demographics). What they have is time/distance network analysis; what they lack is a true-dollar-cost, multimodal, household network layer with a national curated price database underneath. MPOs, transit agencies, planners, and real-estate analysts on ArcGIS would consume a "true commute cost" layer immediately.

Slots into: ArcGIS Network Analyst (a cost-impedance + multimodal extension), ArcGIS Business Analyst (affordability/access variables), the ArcGIS Marketplace and Living Atlas (our hex cost layer + H+T+U index as a published dataset), ArcGIS Urban (planning scenarios with real cost).

The pitch: "Your Network Analyst computes time and distance impedance beautifully. Planners and analysts increasingly need cost impedance — what a trip actually costs across modes — and the household version (two earners). We have it, national, validated against CNT's H+T at r=0.90, as a hex layer that drops straight into Living Atlas and a network extension that drops into Network Analyst."

Slots best as: a data + capability acquisition or a Living Atlas / Marketplace licensing deal. Esri's customer base (public sector, planning, CRE analytics) is exactly who values cost-of-access analysis, and Esri historically extends the platform via both build and acquire. This may be the cleanest strategic fit of the five — least channel conflict, most native product slot.

Risk/objection: "Our customers want a tool, not your consumer brand." Counter: we license the engine + data into ArcGIS; the consumer brand is irrelevant to the deal. Procurement/integration is the slow part — frame it as a Marketplace dataset first, deeper integration second.

4.3 — Inrix

Strategic fit: Inrix sells mobility/traffic analytics (speeds, flow, parking data, trip analytics) to agencies, automakers, and enterprises. They are deep on time/flow and even have a parking product — but they price the road, not the household trip. A true-cost, multimodal, consumer-and-planner layer extends their analytics from "how traffic moves" to "what mobility costs people."

Slots into: Inrix Trip Analytics (add a cost dimension), Inrix Parking (we already curate 1,515 CBD garages — complementary/enriching), their agency & automaker dashboards (cost-of-mobility KPIs), in-vehicle routing (cost-aware route options for OEMs).

The pitch: "You own how traffic moves and what parking costs. The missing layer is what the whole trip costs a household across modes — the number that's now driving where people live and how they commute with $5 gas. We've built it national and instant; it makes your analytics answer the affordability questions agencies and OEMs are getting asked."

Risk/objection: Inrix is enterprise/agency-facing, not consumer — our consumer brand is less of an asset to them. Position as B2B data/engine acquisition or feed license that enriches their existing analytics + parking products. Likely a smaller, more tactical deal than Google/Esri — but a fast one, because the fit with their parking/trip-analytics products is concrete.

4.4 — Mapbox

Strategic fit: Mapbox is the developer-first maps/navigation platform (SDKs, Directions API, Isochrone API, Matrix API). They sell time-based isochrones and matrices to developers. They are the most natural licensing partner of the five: our cost+multiuser layer is literally a new API alongside their Isochrone/Matrix APIs — a "Cost Matrix" and "Dual-Isochrone" endpoint their developer base would adopt to build affordability and relocation apps.

Slots into: Mapbox Directions/Matrix/Isochrone API suite (add a cost matrix + a dual-isochrone endpoint), Mapbox's automotive & logistics customers (cost-aware routing), their real-estate/proptech developer customers (true-cost listing layers).

The pitch: "Your Isochrone and Matrix APIs return time. Developers building relocation, real-estate, and affordability apps need the cost matrix and the two-traveler intersection — we return both, national. It's a new product line in your API catalog that you don't have to build the data for."

Risk/objection: Mapbox builds infrastructure, not curated content — they may prefer to license our feed and resell it rather than acquire. That's fine: a Mapbox API-licensing / revenue-share deal gives us distribution to their entire developer base. Acquisition only if they decide cost-intelligence is a strategic pillar. Treat Mapbox as the licensing flagship, not the acquisition flagship.

4.5 — Zillow (and Zillow-class proptech: Redfin, CoStar/Homes.com)

Strategic fit: Zillow is in an affordability + differentiation war (BuyAbility; the broader "can I afford this home" push). Listings show commute time but never commute cost, and never for two earners. The single highest-relevance consumer fit: "what does this home actually cost to live in and commute from — for both of us." Redfin owns Walk Score (the score incumbent we're the dollars-upgrade to); CoStar/Homes.com is in a head-to-head with Zillow and hungry for a listing-page differentiator.

Slots into: Zillow listing pages (a true-cost + dual-commute module under each listing), BuyAbility (commute & utility cost as affordability inputs), Zillow's search filters ("homes that work for both our jobs ≤ $Y/mo"), Redfin/Walk Score (dollars layer next to scores).

The pitch: "You changed home search with BuyAbility by pricing the mortgage. The next number is the commute — rail saves the average tri-state family $1,924/month, and nobody shows it on the listing. We compute true commute + utility cost per listing, and the one thing that wins the household: the home that works in time AND money for both partners' jobs. It's a listing-page differentiator your competitor can't match."

Risk/objection: "We'll license a feed, not acquire." Likely true — proptech buyers often start with a data/API license (per-listing TLC + true-cost feed) and acquire only if it drives engagement. That's the GTM-STRATEGY motion already. The acquisition path opens if the multiuser finder becomes a demonstrated consumer draw (hence the campaign). Channel-conflict note: these are also our customers (GTM-STRATEGY segment 3) — pursue licensing first; acquisition is the upside, not the opening ask.

5. Licensing vs. acquisition — the decision

The right structure differs by buyer. Map each target to its most-likely path and run that play:

The framing rule: Always open with licensing. Licensing is non-threatening, has a real revenue path (GTM-STRATEGY pricing), keeps optionality, and — critically — a license relationship is the on-ramp to acquisition. Once a buyer's product depends on our feed, the build-vs-buy-vs-keep-licensing math tilts toward acquire (they can't afford the feed disappearing to a competitor). So: license to get in the door and create dependency; let the campaign's traction + press signals raise the strategic premium; acquisition is the escalation, not the cold open.

Decision tree for any inbound: 1. Is it a developer/infra platform (Mapbox)? → License/rev-share, distribution is the win. 2. Is it a platform-extension buyer with a clean product slot (Esri, Inrix)? → Acquisition or Marketplace license, whichever moves faster; the dataset is the prize. 3. Is it a consumer giant that's also a customer (Google, Zillow, Redfin, CoStar)? → License-first to create dependency, then let traction + competitive pressure pull the acquisition. Never lead with "buy us."

What raises our number, in priority order: 1. Consumer traction (the campaign's whole point) — turns acqui-hire into strategic acquisition. 2. Press / category authority ("Losing Ground 2026") — makes us the obvious name in commute affordability. 3. A credible round on the cap table — investors of repute de-risk the buy and set a price floor. 4. A licensing dependency — once their product ships on our feed, the cost of us walking away to a competitor is the acquisition premium. 5. The multiuser flagship, built and demonstrated — the single capability no competitor can replicate; build it (greenlight pending) to make Lane B real.

6. What NOT to do

• Never publicly signal "for sale." It caps the price and spooks investors. Lane B runs through signals + the gated one-pager only.
• Don't pitch acquisition cold to corp-dev. It dies in the inbox. The order is: press + traction → warm intro → this document.
• Don't disparage the buyers. Google/Esri/Inrix/Mapbox are the platforms we extend; the frame is "capability you're missing," never "you're behind."
• Don't promise the multiuser demo before it's built. It's the Lane-B wow and it's spec-only today. Build it (or honestly demo the concept) before it carries an acquisition conversation.
• Don't conflate the licensing customer with the acquirer too early. Zillow/Redfin/CoStar are customers first; let the commercial relationship mature before raising acquisition.