Artem Belov

1. I've always been on the personal brand side. More and more founders are building it now (sometimes even before the product is ready while it's still in development, before seed fundraising). The CEO builds their position so the product sells more easily at the official launch.

2. But I have experience with people who built the product, scaled it, and only then did we discover who was behind it.

Honestly, with the first approach, I'd be concerned that people invest more in me as a person than in the product. People would idealise the founder and overlook the product's flaws (which could hurt development and constructive feedback).

+ I noticed the most common mistake that many people who started building a personal brand first, connected their product to their personal accounts (emails, social media, etc.) and started having a problem selling these things, because they cannot "give someone keys" to their personal profiles.

If I'm being honest, I'm online (and on PC in general) more than is healthy. Never less than 12 to 14 hours a day.

In practice, I use it most often for:

creating graphics

I just fixed and rebuilt an entire AI automation flow without opening the flow editor once.
Here's what happened:
We have a YouTube script generation pipeline on Serenities. It takes a keyword (or YouTube URLs), generates  an outline, then writes each section with precise word counts. Two branches one for URLs, one for direct topics.
The URL branch was broken. Not obviously broken. Subtly broken it was jumping straight from transcript cleansing to a single Claude call with no outline step, no section iteration, no word count targeting. Just a raw prompt that guessed at length every time.
I asked Claude to check it via MCP.
Within seconds it had read the entire flow every node, every edge, every config. It found:
- A broken template variable resolving to [undefined] instead of the word count
- Extended thinking enabled on a cleansing node (pointless, just burning tokens)
- The URL branch missing 7 nodes that the keyword branch had
- The MCP help guide serving 5 thin topics with almost no real documentation
Then still without me touching the UI it:
Added 7 new nodes to the URL branch (outline prompt, Claude outline generate, JSON cleaner, iterator,
section prompt, section writer, text aggregator)
Rewired all the edges correctly
Updated the webhook response to pull from the new pipeline
Rewrote all 5 MCP help topics with complete documentation utility node configs, template variable syntax,
Claude toolInputJson templates, debugging guides, everything
One conversation. Zero UI clicks. The flow went from broken to production-ready.
This is what MCP actually unlocks. Not just "ask AI to explain your code." Ask AI to read your live
infrastructure, reason about what's wrong, and fix it programmatically, precisely, at the API level.
We built MCP support into Serenities so AI agents can build and manage flows on behalf of users. Today I used
it on our own platform. It worked exactly as intended.
The future of automation isn't drag-and-drop. It's conversational.