Hey Nik,

Thanks for coming back to me. On subfolders, the ideal outcome would be something closer to Google Drive, where folders can contain nested folders and projects can be organised in a way that reflects how people actually work. Even one extra layer would be a meaningful improvement, but the broader need is to organise by project, topic, or client without everything sitting flat in a single directory.

On stopping generation, the issue is mainly credit efficiency and workflow control. There are times when Gamma clearly misreads the brief and starts generating something unrelated, and if that brief was set up for a large deck with images, the credit cost can become significant before the mistake is obvious. There are also cases where the theme preview does not reveal enough upfront, or where the user realises mid-generation that something important was missed in setup, such as the slide count, additional instructions, or other generation parameters. In those moments, a stop option would let the user halt the process, preserve what has already been generated if possible, make the correction, and continue without wasting credits on an output they already know they will discard.

On SOP-style formatting control, what I am looking for is persistent instruction-level consistency across outputs. I use detailed SOPs in ChatGPT and Claude to control structure, formatting, tone, hierarchy, and other document rules, and that gives me continuity across a large body of work. I am building a Macro Trading Curriculum in Gamma, so that same continuity matters here as well. The most useful solution would be either the ability for a Gamma project to carry its own standing generation rules, or the ability to upload and attach an SOP that Gamma can follow as part of the generation process. That would make output more reliable, more consistent, and much easier to manage across a long-term project.

Hope that helps. I'll almost certainly have more ideas moving forwards, so feel free to keep in touch.

Jan

Hey Jan Franklin, thanks for the thoughtful list, super helpful. I’ll pass these along to the team.

Quick couple questions so we capture it right:

1) Subfolders: what’s your ideal structure (nested folders a few levels deep, or just one level), and is the main goal organizing by client/project or something else?

2) Stop generation: when do you usually realize it’s going off the rails (wrong prompt direction, formatting, hallucinations), and would “stop” also keep whatever’s already been generated so far?

3) SOP formatting control: what kind of control are you after (templates, strict headings, spacing, tables), and do you have an example SOP format you’d want to match?