What we shipped, why we built it and what comes next. Written by the team building Alchemyst with food scientists and product developers.
Our biggest update since launch: a redesign in light and dark, answers that know your markets, a Monday Briefing email with EU RASFF alerts, six interface languages and Word downloads.
Why: testers told us the app did a lot but hid it. This update is about making the good parts obvious.
Read the full notes →
Why: a quiet summer on features. Most of our time went into talking to pilot teams and planning the September redesign.
Why: R&D is a team sport. Answers are only useful if the people who make the decision can see them too.
Why: we wanted real questions from real R&D work as early as possible. Most of what shipped since came out of that feedback.
We rebuilt Alchemyst from a chat window into a workspace.
Why: one chat box can't serve a formulator, a regulatory manager and a PhD student equally well. Each of them needed their own way in.
Why: real R&D questions come with context: a spec, a supplier sheet, a study. The tool had to make room for it.
Why: not glamorous, but a tool people rely on at work has to feel dependable before it can feel clever.
Why: food scientists don't trust an answer they can't check. Citations were the first thing we built, and they are still the heart of every answer.
Why: we had spent years watching R&D teams lose days to literature searches and regulatory lookups. We wanted to see if an assistant could give them that time back.