← Back to work
Web App · Sustainability · Live on bevolve.ai
Turning a carbon-emissions form into a two-minute conversation with a guide named Eco.
A conversational carbon calculator for physical, virtual, and hybrid events. Attendees and organisers answer one question at a time about travel, venue power, food, and accommodation, and get back a shareable emissions report. Live at bevolve.ai/eventzero.
Research into existing calculators found the same pattern: long forms asking for data an organiser doesn't have on hand, so most people abandon them before reaching a number.
I designed a conversational flow led by Eco, a guide persona who asks one question at a time (event basics, venue power source, how attendees travel, what they eat, where they sleep), validating each answer before moving to the next, so it reads as a conversation rather than a form.
Shipped as EventZero with a free quick-estimate tier and a Premium tier for attendee-level QR tracking and branded reports.
Event organisers are increasingly asked what their events emit. The calculators they found asked for dozens of inputs on one long page, in units and terms they did not use, so most people gave up before they saw a number.
The brief was a free calculator on bevolve.ai that a real organiser would finish. I took it solo from research to a live, fully responsive front end, over 3 months.
I reviewed existing event carbon calculators and compared what they asked for with what an organiser has on hand. I also walked through the inputs with Bevolve's sustainability team, to keep only the questions the model really needs.
They know headcount, venue, menu and where guests travel from. They do not know emission factors, and should not have to.
Long forms showed the whole effort up front. One question at a time hides the length and keeps people moving.
Organisers want to know what to change next time, so the result has to show where the emissions come from and what could be saved.
I built two personas in the same FigJam format as the platform modules: the organiser who answers the questions, and the sustainability lead who needs the number. They came from organiser conversations and Bevolve's client work.
| Get asked | Gather | Calculate | Read | Improve | |
|---|---|---|---|---|---|
| Doing | A client or manager asks for the event's footprint | The organiser collects headcount, venue, travel, food and hotel details | They look for a calculator and enter the data | They read the result | They plan the next event |
| Pain | Usually close to the event date | Data sits with different vendors | Long forms in unfamiliar units | A single number with no explanation | No idea what would make a difference |
| Design response | Start with just an email, no sign-up | Questions follow the order organisers already think in | One question at a time, led by Eco, checked live | Totals by category, emissions next to savings | Potential savings and how to improve your score |
The first ask was an accurate calculator. Accuracy was never the problem; finishing was. The model could only be as good as the answers people were willing to give.
How might we get an accurate footprint from an organiser who has no carbon background and two minutes to spare?
I sketched the conversation before building it. The notes in the margins are the job of each screen: ask one thing, explain the choices, check the maths, then lead with the total.
Eco asks one question at a time and each answer appears as a reply, like a chat. Choices carry a one-line explanation, so nobody needs to know what grid electricity emits to pick the right option.
Splits must add up to 100%, and the bar fills as the sliders move. Mistakes show up on the step where they happen, not as an error on the last screen.
The report opens with two numbers: what the event emits and what it could save. The breakdown by category sits underneath, for anyone who wants the detail.
I ran the research, designed the flow and the UI in Figma, and built the fully responsive front end with Claude Code and Codex. Building in code cut static-screen work from days to hours, and every step was tested in the browser as it was built.
Eco asks one question, waits for the answer, then moves on: event basics, venue power, travel, food, and accommodation. It follows the back-and-forth rhythm of a chat app people already use every day, not a wall of form fields. The first screen below is a recording of the real product; every screen after it is captured from the live app, ending with a shareable emissions report broken down by category.
EventZero is live at bevolve.ai/eventzero, with a free quick-estimate tier and a Premium tier for attendee tracking and branded reports. It gives Bevolve a simple, public way into its platform.
The hardest part of a calculator is not the model, it is the questions. Cutting and reordering them did more for completion than any visual detail.
Design the attendee-level QR flow from the Premium tier, so every guest can see their own footprint, not just the organiser.