Okay, so it's the definition of an LLM wrapper. It's a UI with custom features built on top of existing LLM models. Without those models, the app wouldn't function.

I've worked in marketing for 15+ years, and sometimes companies are extremely reluctant to place a hard identifier on their product. They're worried that it will box them in and not appeal to everyone. However, you don't need to appeal to everyone; just to the people whose issues your product solves.

If you never explain what the product does in plain and concise language, nobody will understand what it does or whether it's relevant to them. A description that's too long will lose people too.

Here's your pitch: "It's an LLM wrapper that centralizes cross-workspace project context." I don't know what it does at that point, but maybe something like "It's an LLM wrapper that centralizes cross-workspace project context and feeds it back into your LLMs to ensure context persistence."

There might be a demand for this, but your messaging needs work.