Re: SOW - value case wording
From: lena.fischer@acme-org.example
To: marco.rossi@relexsolutions.example
Cc: robert.kahn@acme-org.example, henrik.sorensen@relexsolutions.example
Surrounding conversation
This email originated from outside of RELEX. Be careful of attachments and links from unknown senders. Report suspicious emails using the report button. That wording is in. Signed version going out this week. Mit freundlichen Grüßen Lena Fischer Head of Supply Chain +49 151 2244 8830 Acme Org GmbH | Hansaring 82, 50670 Köln acme-org.example [cid:image001.png]
"RELEX anticipates" is fine, it says the same thing. On the baseline, agreed, it cannot be defined yet. Can we word it as "a baseline to be agreed in writing prior to go-live of the fresh phase"? That gives your legal team a commitment and gives us room. Marco Rossi Account Executive Image +351 912 447 026 | CET/CEST marco.rossi@relexsolutions.example Rua do Ouro 42, 1100-063 Lisboa Connect with me Image Image Plan better. Sell more. Waste less relexsolutions.example Image LinkedInYouTube Image
Robert, Lena, Draft wording for the value case section, per our conversation. "The primary value driver for this engagement is the reduction of fresh food waste, measured as a percentage of fresh net sales against an agreed baseline. Both parties expect a return on the initial investment within twelve months of contract signature." I have deliberately written "expect" rather than "guarantee", because delivery depends on data readiness and resourcing on both sides. If your legal team wants to tighten it, I would rather discuss than receive a redline. Also added: a quarterly business review with a written report, as an obligation on us. Marco Rossi Account Executive Image +351 912 447 026 | CET/CEST marco.rossi@relexsolutions.example Rua do Ouro 42, 1100-063 Lisboa Connect with me Image Image Plan better. Sell more. Waste less relexsolutions.example Image LinkedInYouTube Image
This is the application's current source record. Local dates from the archive retain their original timezone ambiguity. Source IDs and positions connect this passage to its document.