The ROI Hides in the Feature Nobody Mandated

When a CEO asks me to justify a feature in a B2E app, I reframe the question. The mandated features — clock-in, compliance forms, the things head office requires — rarely move ROI on their own. Employees comply, but compliance isn't adoption. The return shows up in the features built on Reciprocity Design: the ones that give the field worker something back. An offline shift schedule they can check in a basement with no signal. A camera-based report that replaces minutes of typing. A payslip they can pull up without calling HR. I measure feature ROI in two directions: the cost the feature removes from the organization (fewer support calls, less re-keying into legacy payroll, cleaner data at the source) and the friction it removes from the employee, because that friction is what kills adoption of everything else in the app. A single high-value field feature often becomes the reason employees open the app at all — which is what finally makes your mandated workflows actually get used. So when you scope ROI, don't price features in isolation. Price the adoption they unlock across the whole product. The give-back feature is usually the cheapest engine of return you own.