turtlely

vendor discovery & operational intelligence

what it is

turtlely is an institutional travel brain built for everyone involved in group travel operations: coordinators, program managers, directors, and group leaders. it turns vendor knowledge into a structured, searchable, self-improving asset that belongs to the organization, not to any individual on the team. discovery becomes curation. hours of vendor research become minutes of review.

why it exists

group travel operators spend hours finding vendors in unfamiliar cities, re-vetting places they have used before, and rebuilding context every time a new team member joins. institutional knowledge lives in email threads, spreadsheets, and individual heads, and walks out the door when someone leaves. no existing tool captures group-travel-specific intelligence: bus parking, group minimums, private dining capacity, historical performance by program type, or which contact actually picks up the phone.

what it does

natural language search parses trip intent, destination, group size, budget, and preferences into a structured query, with voice input supported on every field. multi-source discovery pulls from an internal database enriched with Google Places data, with chains, closed venues, and low-rated results automatically removed. vendors are ranked across five tiers: operator review history, google reputation, demographic fit, contact completeness, and program profile match.

every decision an operator makes (accept, reject, and why) feeds structured signal back into scoring. passive signals like dwell time, website clicks, and search abandonment are logged automatically. named vendor contacts persist across staff changes. institutional relationships survive turnover.

the data moat

the search layer is commoditized. any mapping tool can surface restaurants near a hotel. what no competitor can replicate is accumulated operational intelligence: which vendor was rejected because the bus could not park, which hotel charged a hidden fee, which museum has a group entrance not listed publicly. that data does not exist anywhere in the world. it is captured passively through normal coordinator workflow. every interaction makes the system more accurate. every coordinator who uses it contributes to a dataset their successors benefit from immediately. the longer it runs, the wider the moat. the software is the delivery mechanism. the data is the product.

built using ai-assisted development throughout. product decisions, ux design, feature prioritization, and operational logic came from direct experience running group travel programs.

system status →

turtlely

turtleden

review complete