The everyday problem
Two proposals can use the same RCM language while assigning work to different people. One gives your staff software; another supplies a team; a third automates defined tasks. Comparing their prices before understanding those responsibilities can produce a misleading conclusion.
A practical approach
Ask who performs routine work, who resolves exceptions, and who maintains the process. Document the internal roles that remain necessary under each model. Compare the operating arrangement first, then evaluate the technology and commercial terms within that arrangement.
Try this with your team
Draw a responsibility table for two fictional proposals. Include setup, daily execution, exception handling, quality review, reporting, and ongoing maintenance.