The first driver is scope. Answering every inquiry quickly, day or night, is a narrower job than a system that also books tours onto your calendar, drafts vendor coordination emails, and works a list of stale leads on a schedule to see if they are still deciding. A single workflow that just handles fast inquiry response is a smaller build than a system covering all four. A full booking portal with online payments, contracts, and multiple staff logins is a different category again, closer to a real product than an automation.
The second driver is whether you want it built and handed off, or built and run. Build-only means we design and deploy the system and you take it from there. Build-and-operate means we keep watching it: checking that inquiry replies still sound right as your pricing or packages change, catching a vendor email that went to the wrong address, adjusting the follow-up cadence for stale inquiries as your season shifts. Operate work costs more over time because it is ongoing attention, not a one-time build.
We do not run a price list because two venues asking the same question can need very different systems. One might only need faster first replies. Another might be losing tours to a calendar nobody is checking or slow vendor confirmations. We quote each engagement on the value the system creates for that specific venue. A sensible way to judge it for yourself: count how many inquiries sit unanswered for hours, how many tours get scheduled and confirmed without a person chasing details, and how many stale leads never get a second touch. If those numbers are real, a short conversation about your actual booking process is the fastest way to find out what it would take and whether it is worth it.