Four months after Lighthouse acquired HotelRank.ai, no rep has a ready answer for "why not just use Profound."

The Pitch: Where I'd Start

I'd start with exactly what I already built: a battlecard positioning HotelRank.ai/Connect AI against the three general-purpose AI-visibility tools a hotel group's marketing team might already be evaluating, each card scored on the axis that actually matters here, booking-path attribution and OTA leakage, not just brand-mention volume. Read the battlecard →

Bridging product and sales for a technical, data-heavy tool is work I've already done. At Marketing In Action, I built the demo and funnel infrastructure for MIA's own DIME product from scratch, a custom webinar room and prefill lead capture, because the bought tools couldn't give me the tracking control the sales motion needed. That's the same instinct a GTM Engineer needs here: build the thing a rep pulls up on a call instead of waiting for a template that fits.

In the first weeks, I'd want to know what demo tooling already exists, whether "GTM teams" now runs through Lighthouse's sales org or a dedicated HotelRank.ai team, and whether a signed reference hotel exists yet to build a real proof loop around.

The Proof

I built a real battlecard for this exact competitive set, Profound, Otterly.ai, and Scrunch AI, with every pricing and positioning claim linked to its live source. Read the battlecard →

I also built the Marketing Agent Skills library, 81 skills in daily use, 34 open source on GitHub, and the Prospect & Outbound Engine, a self-built cold outbound pipeline that scrapes, enriches, verifies, and personalizes real data before a message goes out, the same mechanical shape as turning a hotel's own AI-visibility data into something a rep can show a prospect.

Let's talk about HotelRank.ai.

If this is the right problem for you, I'd like to talk about it directly.