Good morning all,
I'm curious if anyone out there has a process they use to "justify" new integrations/recipes using the Recipe-Based Pricing that Workato uses. We're still new-ish to the platform and so are only now approaching the max number of recipes we were allotted before we have to start paying for new ones. So I'm curious how others make a business case to justify the cost of additional recipes, in order to decide whether using Workato is the "best" option for a given integration, or if it's cheaper to build something in-house.
The business risk of having automations/integrations fragmented across multiple platforms / in-house custom scripts would be one primary point to consider, from a Workato vs. DIY perspective.
In terms of justifying the recipe itself, a few lenses to look through:
- Time Saved: people time per year * average salary
- Incremental [X], where [X] is the business goal that the stakeholder wants to solve for - more candidate pipeline for the HR team, more revenue pipeline for the marketing team, faster month-end for the finance team, or whatever. This obviously involves some guestimation sometimes, but can at least show a reasonable line of thought.
There's always a possibility the ROI is not there and something shouldn't be integrated or automated in the first place.
I like to use a matrix (workato vs other) for these type of scenarios and use the criteria that is important to your business.
Things that would matter to us would probably be:
. How long to build a solution?
. How many resources to build a solution?
. How much time for maintenance?
. How many resources to maintain?
. How many systems/apps/languages involved?
. Will it generate revenue? How much?
. How long to start generating revenue?
. How long to ramp up a new resource on this automation?
Hope this helps!