Use a common workload: named users, eligible bid volume, pages and document types, integrations, support hours and contract term. Each bidder must price that workload and state exclusions.
| Cost/term | Packaged software | Bespoke build or integration |
|---|---|---|
| Initial setup | Configuration, migration and training | Discovery, development and acceptance |
| Recurring | Seats, modules, usage and content | Hosting, usage, support and maintenance |
| Internal | Training, catalogue ownership and review | Product ownership, testing and change decisions |
| Failure exposure | Vendor outage or feature change | Application failure, key-person loss or upstream change |
| Exit | Usable export and deletion | Data, rules, documentation, code rights and deployability |
The public ServiceTitan page uses requested pricing. Treat an unpriced dependency as a clarification item rather than substituting an internet estimate. Compare three-year totals only after separating one-off and recurring costs; do not average incomparable subscription and implementation figures into a “market price”.
Sources cited on this page
- ServiceTitan pageservicetitan.com