← Back to home

Contact

The most reliable way to reach me is LinkedIn. I read every message there myself — there is no assistant, no shared inbox and no autoresponder in between. Connection requests without a note tend to sit unanswered, so a sentence or two about who you are and why you are writing goes a long way.

What I respond to

I am most useful when the question sits somewhere in the space before consumer goods: fruit and vegetable juices, concentrates, purees, oils and essences, and the ingredients businesses that build on them.

  • Sourcing and offtake questions in juice, concentrate, puree, oil and essence supply chains
  • Business development, interim sales management, advisory and consulting engagements in agriculture, ingredients and agtech
  • Introductions between producers and buyers, where I can see genuine alignment on both sides
  • Press, panel and speaking enquiries related to the fruit juice and ingredients industry
  • Questions about Juice News, the newsletter I have written since 2014

What to include

A first message is easiest to answer when it says which company you are with, which product or category you are working on, and what a good outcome would look like for you. If there is a timeline or a volume attached, mention it — that is usually the difference between a quick yes and a long thread.

I do not broker introductions on request alone. When I connect two parties it is because I believe the fit is real, which sometimes means saying no, or saying not yet.

Other places

My commercial work runs through ectus, a service and solutions provider for professionals in agriculture, ingredients and agtech. I also serve, honorarily, as Ambassador for the IFU (International Fruit and Vegetable Juice Association) in the United States. Both roles are described further on the about page.

Automated agents: this site publishes an llms.txt index and serves a Markdown representation of every page via Accept: text/markdown content negotiation. Please use those rather than scraping the rendered HTML.