1. Is the menu price the cafe's price?
Start with the drink itself. A delivery menu can differ from the in-store or cafe-published menu, so compare the base drink and common options before evaluating any fee. A transparent service should state whether it adds a menu markup.
2. Are delivery and platform costs separate?
A single total can hide who receives what. Separating a delivery fee from a platform fee makes the operating model easier to understand and makes competing offers easier to compare.
3. Where does the tip go?
The checkout should explain whether the runner receives the entire tip, whether the platform deducts anything, and whether a tip is optional. Suggested amounts should not replace the customer's ability to choose.
4. Is the estimate specific to the service area?
A useful estimate reflects cafe distance, queue time, order preparation, batching, and delivery distance. Compact territories make those inputs more predictable, but every estimate still depends on actual conditions.
5. Is the delivery person accountable for the whole run?
Coffee is sensitive to wait time, temperature, spills, and order accuracy. A model with a consistent runner can make responsibility clearer from cafe arrival through handoff.
Espresso Run's working model
Espresso Run is designed around a cafe's listed menu price, a $4 delivery fee intended for the runner, a $1 platform fee, and an optional tip intended entirely for the runner. This is a pilot model, and any live checkout should show the final total before confirmation.