Request new features, report bugs, or provide general feedback—we appreciate it all. If you are reporting a bug, please include as much detail as possible, including any steps you took prior to finding the issue and screenshots when possible.
We want your feedback!
API Unit param
Probably a heavy lift because of the order in which conversions happen, but it would be great to be able to specify units in the API.
Faster Add Forecast to Collection
Would be ideal to more quickly add a forecast to a collection in two specific spots: On your list of /analyses/ page - have a quick actions button to add to collection. Would need to include a custom modal that allows user to select the specific baseline/solution/market/capture from the analysis (and which collection to add it to). On the /collections/ page in My Collections list and in Contents tab. Would need dialog to select specific baseline/solution/market/capture.
Title of market capture in collection summary
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.
Search matches w/ exact model 1st
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.
Add (or make more clear) how to get to top-level portfolio after clicking in to a portfolio subgroup
When I am in a top-level collection that has multiple sub collections, and then I click on one of the sub collections, the only option I see is to go back to All Collections (rather than the parent collection)
"duplicate baseline scenario" for solution editing button
It came up on a call that if a consultant wanted to very simply duplicate a baseline, set it as the soln scenario, and then ask the startup what % they are reducing phases by, that is not always possible. The limitation comes from the available soln scenarios to duplicate being limited to records set to be available as “solutions”. Could be useful to have a “duplicate baseline” as the soln scenario for consultants who want to have simple way of asking startups where they are interfering in a baseline scenario.
Model market size with CAGR
Being able to model (in-app, so in the editing mode) a market size based on a current market size and CAGR. More broadly this would be about adding extrapolation techniques into the market size edit mode. (Suggestion originally from Prime folks).
Retain view settings after saving edit
Nice to have, if this is a big ask developmentally it can be ignored. It would be convenient to retain the view settings (e.g., years and units) that were used in edit mode once a new model version is saved and that new version loads.
Expose UpdateNote from cluster fields as Analysis Notes on frontend
Allow bespoke modeling notes intended for the front end to be exposed with this parameter. Can be on datasheet and/or executive summary page. Ingestion notebook needs updates to implement. Aurora has a prototype ready to go from the data side.
Unique Collection Editing
Currently, if you edit a collection it edits ALL instances of that collection. This is a mess for translating collections between use cases and stakeholders. There should be the option, and if not the option the default, of only editing a given instance of a collection. In a similar light, there should be the ability to clone a collection.
Link to related company domains from a model
On the solution detail page, it would be helpful to see companies doing work related to a given model.
Milestone: Refactor engine and start moving to .py
Q3+ Simplify GPT and engine flow logic to use less prompts and produce clean results with fewer artifacts. Stabilize sections of the code. Consider switching Chat Completions to Responses. Overall, prepare scripts for platform and RAG integration. Completed as part of another goal: Refine tech_library approach and simplify all artifacts to be high-value and utility.
Milestone: Engine auto-updates to v0 models
Develop QA rules and routing for automated re-running of old AI models with the latest approaches, while retaining original IDs and traceability to old approach.
Animated Model Walkthrough
Models have an animated walkthrough to orient new users to what they are seeing. See mockup: https://drive.google.com/drive/folders/1C67ux-TZx26NAxoTfUbfFGGv0_WLcGND?dmr=1&ec=wgc-drive-hero-goto
Display reference on hover
Feature request: it would be great to see the reference of data points on hover (e.g. in popup below), especially for your prebuilt models since the first thing I would want to do when inspecting a model is getting a sense of whether I can trust these values - i.e. where they come from.
Remember preferred solution scenario
When I open a forecast with two solution scenarios, it always defaults to the first of the two—even if my latest edit was selecting the second scenario. This was confusing to me because I was on the “Solution Summary” tab and read an annual impact of X, and then, by simply leaving the page and returning to it, the value changed to Y for no apparent reason. I would think that the last selected solution scenario should be the default, or that before displaying the forecast, the user is prompted to pick a scenario.
User home page shows recommended models, GHGs, incumbent markets based on what we know of user profile
I imagine this could replace the search home page and immediately direct users to (hopefully relevant) data and encourage them to simply start poking around. Search could still be available on a separate page, but the home screen would be like the Netflix menu of recommended “media”.
Improved & expanded tagging/flagging of models
Intuitive QA tagging and potential for other tags/flags - for example on models with a focus on energy efficiency we might want to have flag that says “You may want to consider rebound effects” that links to a doc page. Other uses as well, imagining a flexible system.