How do you allow non-technical folks to edit prompts?

[wallawe]

I feel like many companies probably have this problem: you have a bunch of prompts in your codebase and you want to allow non-technical folks to edit or iterate upon them to make them better.

In our case, we help our customers with local SEO so we hired someone to help us refine them. He's great at prompting and SEO but does not code.

So we need a playground like environment, except that takes in different records from our database as params and that uses structured JSON outputs.

Is there a company tackling this? Would happily use them if so! If not, startup idea!

[codingdave]

This sounds like basic content management. Give them an admin UI - Put an editor on-screen, load/save the various data, pull the saved value into your code as appropriate. Include some input validation on your editor, and it is a basic CRUD form. Maybe a little more complex if you include a workflow so that their changes get tested before going live.

[apothegm → codingdave]

This. A database field and a textarea, with old versions preserved in the DB.

[wallawe]

If anyone finds this in the future, we found three solutions we're evaluating:

https://www.promptlayer.com/

https://freeplay.ai/

https://www.helicone.ai/

[colegottdank → wallawe]

Hi! I'm a co-founder of Helicone.ai! We let non-technical teams create, edit, and version prompts in our UI. You can also run A/B tests with production inputs before rolling out new versions.

Check out the prompt docs here: https://docs.helicone.ai/features/prompts

Feel free to reach out with any questions!

[djaouen]

> He's great at prompting and SEO but does not code.

Why would anyone want to hire such a person?

[wallawe → djaouen]

Many of the best SEO understand technical aspects but don't actually code. The vast majority. Source: built and sold company on the back of SEO and worked with many great SEOs.