Here's what we're thinking about building next. Help by upvoting your favorites or requesting features on our <a target="" rel="noopener noreferrer nofollow" class="link" href="https://product.koi.eco">Feedback page</a>. See <a target="" rel="noopener noreferrer nofollow" class="link" href="https://product.koi.eco/changelog">our Changelog</a> for recent updates.

Under Consideration

Works in Progress

Public Roadmap

Planned

Milestone: Users are recommended AI-generated models

Cassie Borish

We need a better way to organize collections. After adding many collections it becomes difficult to find what you’re looking for from the main collections page.

In Review

Ability to add labels (or tags) to forecasts and collections

Gilman Callsen

If you search an exact model name, for example “Engineered Enzymes For Biomanufacturing” it would be great if that appeared first. Currently it is appearing 4th. Another consideration is highlighting the result that is an exact match to the search term.

Search matches w/ exact model 1st

aurora.ginzburg

Milestone: Koi facilitates impact forecast task management

A step-by-step tutorial showing the in-app process and scientific logic for creating and interpreting an entirely custom model.

Tutorials for custom modeling

Expose the lifecycle subphase data through the UI for end users.

Science

Engineering

Product

Add Lifecycle Sub-phases

AmberGold

Include a page with solution details that outlines other impacts of the solution (e.g. waste, water, plastic) and potential risks (e.g. impact to workforce)

Show additional impact and risk factors

Once the refactor is complete and we have titles for each market capture ID, it would be suppppper helpful to see in the exec summary of a collection.

Title of market capture in collection summary

This is not a bug but more of a personal observation/suggestion. When searching using the “rooftop” keyword, multiple models appear with the same name. After selecting “preview,” I recognize they are slightly different (in terms of market capture, description, etc.), and I get that they’re probably generated based on different company IPs. From a UX perspective, it would save time and effort for a user to be able to distinguish between these models more easily. For instance, if there was an extra column listing those key differences, or if models would somehow be pooled into one master “Rooftop PV Systems” category (this one is especially helpful when a user is searching for something not solar PV related, yet getting so many irrelevant results).<img data-width="100%" data-align="left" data-featurebase-content-key="66b10bb4e917f953970f6ce5/post/690e02eba82580eb3671a05a/019a5eb3-993c-7663-ae9c-233fa903ff8a/b64u-aW1hZ2UucG5n.png" src="https://66b10bb4e917f953970f6ce5.featurebase-attachments.com/c/post/690e02eba82580eb3671a05a/019a5eb3-993c-7663-ae9c-233fa903ff8a/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260918T090000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260918%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=4084fcd8b6667706fa2a2ab0b60537cffe235538b51a11523937cddf96b891c3" data-featurebase-content-filename="image.png">

Adapt search bar to accommodate multiple models with same name

giedre.darg

When adding users to a group, if the user does not yet have a Koi account we need to either 1) let them be added anyway or 2) provide a useful error message. Right now it just doesn’t let you add (which is fine) but no useful message to user.

Add new member to group who does not have account

gilman.callsen

Expose Koi Data Lake over public API. Get in touch if you’d like to be a beta tester, <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="mailto:support@koi.eco">support@koi.eco</a>

In Progress

Milestone: Public API to Koi Data Lake

Koi engine 2.0 will revise the approach to calculating solution impact. Rather than assuming an intervention in the baseline value chain, by construct default in 1.0, it will attempt to model the solution’s distinct value chain based on credible research.

Koi engine 2.0

science

Limitation addressed: It is unclear to Koi users what data are verified in a model and what data are autogenerated. If they modify data it is up to them to remember what they changed and communicate it. If they are more comfortable working in a spreadsheet, they have no way of doing so.Develop tooling for Koi studio users to understand and manage the QA status of their model. Data should be appropriately tagged at the parameter level for communications of model quality and verified/unverified information.QA tooling to include streamlined “high-level” model refinement options as well as deep refinement using an exported Review.xlsx file that can then be reingested from an updated Google Sheet.

In-app QA process

Help Center

Improved

Fixed

Feature

Completed

Rejected

Needs Discussion

High Priority

Low Priority

Documentation

Recently completed

Down the Road

If you are reporting a bug, please include as much detail as possible, including any steps you took prior to finding the issue.