An audit ending in a proposal is a sales document. One worth paying for ends in something you could hand to a different supplier tomorrow.
What you should be holding at the end
- A costed plan, priced per piece of work rather than as one number
- The risks, written plainly, including the ones that argue against going ahead
- A map of the systems and where the integration points are
You keep all of it either way. That is the test of whether the audit was work or a pitch with an invoice attached.
Wondering what this would take against your own systems?
The review is a fixed price, and you keep the costed plan and the risks whether you go ahead or not.
Book an automation reviewHitasoft engineering
LinkedInHitasoft has built software since 2008, for companies that mostly do not have an IT department. These pieces are written by the people who do the integrations rather than by anybody in marketing.
