[CER10TY]

It's important to find the problem _first_. To me, it sounds like you're already building a solution (which can be a fun project, no doubt!), but in search of a problem.

Most books / talks will advocate finding your customers first, which means listening for problems that they have. It doesn't mean there can't be a solution on the market already, because competition in itself is validation that there's a need, but it means you need to be better than your competition in executing 1-2 particular features your customers want.

A common example is a large enterprise product having so many features that certain customers are turned off from the bloat; you could step in here, execute 1-2 features well, and sell that (provided customers want that).

[dontoni]

You got me well. I am a user of translators but through their APIs, not interfaces, and something currently missing in the space are models capable of grasping the context and deliver very good translations. DeepL is the best on this but in my experience it fails 50% of the time. Google Translate only gets it right 20% of the time. My agent, like 90% of the time. That’s huge. And it actually costs a fraction of Google’s and DeepL’s prices.

That’s the 1-2 features you talk about for this project. I’d also like to be able to add (1) glosaries, (2) formal, informal and custom tone, and (3) infinite context windows. But seems less important than the rest.