Founder

Rafael Lima

I build Zynta Flow, and I am its heaviest user. That is not a slogan, it is the reason the product looks the way it does.

I am a designer. For most of my career the job has been building brands and then feeding them: identity, positioning, and then the part nobody puts in the portfolio, which is producing the content that keeps a brand alive week after week.

At some point I was running that for more than a dozen brands at once. A drinks company with several labels of its own, an agency's clients, a partner's wine imports, my own things. Each one with its own colors, its own fonts, its own voice, and each one needing posts on Monday.

The bottleneck was never the idea. It was that one idea had to become six different-looking posts, and doing that by hand is an afternoon per brand. Design tools would draw a slide but had no idea what my client's brand was. Scheduling tools would publish a file but would not make it. The AI writers wrote copy that read like everyone else's.

So Zynta Flow is the tool I wanted: write the brief once, and get it back in the identity of whichever brand you name, ready to schedule. It writes, designs and publishes, which is the whole job rather than a third of it.

Built by using it

The brands I run are still the ones it is tested on. That is deliberate: a social media tool built by people who do not post is easy to spot, because it gets the last ten percent wrong, and the last ten percent is where the work actually is.

It also means the unglamorous things got built. Client approval links that do not ask the reviewer to create an account. A brand kit strict enough that output is on brand by default instead of by discipline. Publishing that runs on each platform's official API, because an automated tool that risks a client's account is not a tool, it is a liability.

Where to find me

I write the posts on this blog. If something here is wrong, or you want to argue with it, I would rather hear it than not: contato@zyntaflow.com.

Read the blogTry Zynta Flow