Begin with the scope, not the tool list
A single follow-up rule and a platform for several teams can use similar technology while requiring very different amounts of work. Define the trigger, the people involved, the required actions and the stopping point. A written scope should also say what is excluded. That boundary makes competing proposals easier to compare and changes easier to discuss.
Count the connections and the uncertainty
A documented API with test access is different from a system with incomplete exports or no supported integration. Ask which tool owns each record, how duplicates are handled and what happens when either side is unavailable. Reviewing these constraints before the quote reduces avoidable surprises. Some work needs a short discovery phase before a fixed build price is sensible.
Include the work around the feature
Testing, permissions, monitoring, documentation and handover are part of delivery. So are the exception paths: an email with missing information, an unavailable booking slot or a job updated twice. A proposal that includes only the happy path can look cheaper while leaving your team with the harder operational work. Ask for acceptance checks you can understand and try yourself.
Separate build cost from running cost
Hosting, third-party subscriptions, AI usage, telephony and maintenance may continue after launch. Ask which accounts you will own, which charges are usage-based and which support tasks are covered. You should be able to distinguish a one-time build from an ongoing service without having to decode the proposal.
Treat estimated time savings as an assumption
In the calculator’s example, five people each spend five hours a week on repetitive tasks. At a 50% automation share, that is 12.5 hours a week, or 650 hours across 52 weeks. Valued at $25 an hour, the annual labor value is $16,250. Those are example inputs, not a customer result or a promise of cash savings. Compare the project and running costs with observed time freed, quality and the work people can take on next.
TRY THIS NEXT
A useful proposal names the deliverables, acceptance checks, exclusions, recurring costs and handover. Start there before comparing the headline prices.
See how we scope and price work