u/Status_Mushroom1918

I originally built a visual flowchart editor for Discord bots.

Commands, workflows, events, variables, permissions, databases, interactions... everything already had a strict structure behind it.

At one point I caught myself thinking: "If humans can build inside this structure... what happens if AI can understand it too?"

That question ended up turning into Sefrum.

What I didn't expect was that generation itself would become its own engineering problem. The model wasn't the hard part, the hard part was getting consistent, usable output.

Keeping context broad enough for the AI to understand the full project, while not feeding it so much that it starts making bad assumptions, teaching it how commands relate to workflows, how state moves between systems, how variables stay consistent, how naming doesn't slowly drift halfway through generation.

At some point I even had to build a scoring system for the generation itself.

Not just "did it generate?"

But:

• Does the logic actually make sense?
• Are relationships valid?
• Are workflows connected correctly?
• Will this still scale after more features get added?
• Did the AI accidentally introduce weird edge cases?

Sometimes a small project is harder than a big one too.

One prompt like: "Create a playable Minesweeper Discord bot."

Only generated around 6 workflows.

But getting those 6 workflows right was harder than some full 30+ workflow moderation suites.

That's when I realized AI generation isn't really about prompts.

It's about architecture, and that architecture took longer than the entire platform itself.

Curious for other builders: What feature in your product looked straightforward... until you actually started building it?

If you want to try it for free: https://sefrum.com

I originally built a visual flowchart editor for Discord bots.

Commands, workflows, events, variables, permissions, databases, interactions... everything already had a strict structure behind it.

At one point I caught myself thinking: "If humans can build inside this structure... what happens if AI can understand it too?"

That question ended up turning into Sefrum.

What I didn't expect was that generation itself would become its own engineering problem. The model wasn't the hard part, the hard part was getting consistent, usable output.

Keeping context broad enough for the AI to understand the full project, while not feeding it so much that it starts making bad assumptions, teaching it how commands relate to workflows, how state moves between systems, how variables stay consistent, how naming doesn't slowly drift halfway through generation.

At some point I even had to build a scoring system for the generation itself.

Not just "did it generate?"

But:

• Does the logic actually make sense?
• Are relationships valid?
• Are workflows connected correctly?
• Will this still scale after more features get added?
• Did the AI accidentally introduce weird edge cases?

Sometimes a small project is harder than a big one too.

One prompt like: "Create a playable Minesweeper Discord bot."

Only generated around 6 workflows.

But getting those 6 workflows right was harder than some full 30+ workflow moderation suites.

That's when I realized AI generation isn't really about prompts.

It's about architecture, and that architecture took longer than the entire platform itself.

Curious for other builders: What feature in your product looked straightforward... until you actually started building it?

https://sefrum.com

Hey everyone, I'm a 19-year-old solo founder building Sefrum.

I got tired of seeing Discord communities spend hours setting up moderation, ticketing, verification, economy systems, chatbots, and custom workflows.

So I built a platform where you describe what you want in plain English, and it generates, hosts, and installs a production-ready bot in under a minute using AI + a visual workflow editor.

Built the infrastructure, generation pipeline, editor, and marketplace solo.

Would genuinely love feedback from other founders. Does the value click instantly, or would you position this differently?

I've been working with Discord bots for a while, and one recurring issue is how repetitive it becomes to rebuild the same core systems each time ( commands, ticketing, basic logic, etc. ).

To simplify that process, I built a platform that uses AI to generate complete bot functionality from a single prompt.

You describe the type of bot you want, and the system:

• Plans the overall structure
• Generates commands and logic
• Sets up systems such as ticket workflows
• Applies a consistent personality to responses

I tested it by generating a full-suite, and it was able to create a working setup end-to-end, including ticket handling, moderation, economy ( with a shop ), onboarding.

Demo attached and link is at https://sefrum.com