I built a 9-agent creative operating system on Melius that turns one KURA brand brief, product image, and problem image into a complete ecommerce campaign funnel.

The canvas runs a market researcher, creative strategist, funnel strategist, copywriter, art director, ad creative suite, landing page visual agent, creative QA agent, and video director, all orchestrated by Mel.

Input: One strategic brand brief for KURA, a premium stainless steel cutting board brand.

Output: Funnel map, ad copy, static ads for each funnel stage, PDP hero images, a QA-reviewed creative report, and a Seedance 2.0 motion video.

All in one afternoon.

This is the creative stack a solo founder wishes existed. Now it does.

Process Steps

1. Wrote the KURA master brief covering the product, customer psychology, brand voice, and funnel goal.

2. Briefed Mel to orchestrate a 9-node agentic workflow on the canvas:

- Agent 1: Market Research - mapped pain points, desires, objections, and awareness stages.

- Agent 2: Creative Strategist - built 3 campaign angles with hooks and emotional direction.

- Agent 3: Funnel Strategist - mapped creatives to funnel stages, audiences, and sequences.

- Agent 4: Copywriter - wrote headlines, body copy, CTAs, and text overlays.

- Agent 5: Art Director - created visual direction and GPT Image 2 prompts.

- Agent 6: Ad Creative Suite - generated cold, warm, and hot static ads.

- Agent 7: Landing Page Visual Agent - generated the 4-image PDP visual suite.

- Agent 8: Creative QA - reviewed assets for brand voice, visual consistency, conversion potential, and funnel fit.

- Agent 9: Video Director - produced a cinematic brand video via Seedance 2.0.

3. Refined each node by editing prompts directly in the canvas until the outputs matched the campaign direction.

Feedback on Melius

Melius made the creative process feel surprisingly connected. Instead of moving research, strategy, copy, visuals, video, and QA across different tools, I could build and understand the whole system on one canvas.

The node-based flow was the most intuitive part. It made it easy to see how one agent’s output shaped the next, so the process felt less like prompting one AI model and more like directing a small creative team.

One improvement I’d love to see is stronger history management. As the canvas became more complex, I wanted a clearer undo/redo flow or a way to revisit previous versions of a node. Version history would make experimentation safer and help users compare different creative directions.

I’d also love more canvas organization controls. For larger workflows, it would be helpful to hide nodes, collapse related nodes into one unified group, and copy/paste full groups across the canvas. That would make it easier to keep complex systems clean and reuse useful agent structures.

Overall, Melius felt strongest as an orchestration layer. The real value is not just generating one asset, but connecting multiple creative decisions into a repeatable workflow.

Project link | Walkthrough video