The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Vibe coding has made it easier than ever to turn an idea into a working website, app, or internal tool.
But building the product is only one part of the process.
The real value comes when you connect that product to the systems running your business.
Imagine a website that automatically captures leads, qualifies them with AI, sends personalized follow-ups, updates your CRM, notifies your team, and tracks everything without someone manually moving data from one platform to another.
That’s where vibe coding meets AI automation.
You can use vibe coding to build the front-end experience and custom tools your business needs, then use automation to connect those tools with your CRM, email, databases, payment systems, and other business processes.
#AIAutomation #VibeCoding #BusinessAutomation #Automation #NoCode #LowCode #WorkflowAutomation #AITools #SaaS #Productivity
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
Klaviyo Email Flow Setup & Automation
I designed and structured automated Klaviyo flows for ecommerce brands to engage customers at key moments throughout the buying journey.
The flows are built around customer behavior, with strategic timing, segmentation, messaging, and conversion-focused email design.
Flows include:
Welcome Series
Abandoned Cart
Browse Abandonment
Post-Purchase
Winback
Customer Review
Cross-Sell & Upsell
The goal is simple: deliver the right message at the right time, recover missed opportunities, and create more repeat purchases through automation.
AgentFlow10 — AI Agent & Automation Platform
Lead Engineer · Self-hosted AI agent platform with a visual workflow builder
The problem
Automation tools are built for businesses that already have a card on file, reliable bandwidth, and a Slack workspace. That leaves most of the world out. In markets where WhatsApp is the customer channel and mobile money is the payment rail, the standard automation stack either doesn't connect or is priced in currencies that make it a non-starter.
There was a second problem. Every serious automation platform is someone else's cloud. If your data is sensitive, or your compliance rules keep it in-country, or you just don't want to hand your customer records to a vendor, your options run out fast.
What I built
AgentFlow10 is an AI agent and automation platform you can run on your own infrastructure. A visual builder lets you compose agents and multi-step workflows without writing code, connect them to the tools you already use, and deploy them where your data lives.
The design goal was to make AI agents something a small team can actually operate — not a research project requiring an ML engineer on staff.
What I did
I built and run it end to end: product direction, backend architecture, LLM orchestration, integration layer, the workflow engine, frontend, brand system, and go-to-market. Everything from the database schema to the landing page copy.
Notable pieces of engineering:
A workflow execution engine that handles branching, retries, and failure states — because an agent that dies silently mid-run is worse than no agent
LLM orchestration with prompt management and output validation, so results are structured and usable rather than free text
A self-hosting path that a non-specialist can actually deploy
Integration architecture designed for channels that matter outside Silicon Valley, including WhatsApp and mobile money flows
Why it matters for clients
This is the project I point to when someone asks whether I can build AI systems rather than just call an API. Running a platform means I've dealt with the parts that break in production — cost control, rate limits, non-deterministic model output, failure recovery. That experience is what I bring to client work.
Built with: Python, TypeScript, React, Next.js, Node.js, PostgreSQL, LLM APIs, Docker
Recently I tried something new: I became a founder of my own pet project.
Over my 6 years in design, I've worked with all kinds of companies: from big tech to startups, across very different business types. Some clients were in love with their product and wanted to build only their own ideas, so I leaned hard on soft skills to hold space for both the business and the users. Others were open to suggestions and design-led decisions.
From a designer's side, it's always a challenge and a balancing act. But when I started my own pet project (a product for expat women), something shifted. This time I was the one fully in love with the idea, and I wanted to learn vibe-coding and Cursor hands-on.
With Claude, I quickly shaped the idea, positioning, competitor analysis, and other pieces of product research. I even validated my hypotheses through surveys on Reddit, Facebook, and with my friends — and they held up. Happy and motivated, I jumped into building the landing page and core flows in Cursor…
…until I caught myself. I was about to sink a lot of time into building, and this time, there was no team whose hours I needed to justify but my own.
So I stopped and asked: what's the cheaper, faster way to test this? I had two options:
Build a Telegram bot — faster than full development.
Test manually and gather feedback from participants directly.
Here's the thing: cheap, early hypothesis-testing wasn't new to me. I knew it well, but always from the designer's seat, as one good practice among many. What changed with my own project is that the trade-off finally became mine. It wasn't a team's roadmap or a client's budget on the line, it was my own time, my own money, my own idea I was tempted to over-build.
And that's exactly what made it click, the way the Lean literature I'd been recommended frames it (The Lean Startup by Eric Ries, Lean UX by Jeff Gothelf): the cheapest way to test a hypothesis before you build isn't just a nice principle. As a founder, it's the best decision.
Being on the founder's side, even briefly, shifted what I want to get better at. Understanding founders: their state of mind, what drives them, why they're so attached to building things a certain way. And from there, being the person who can offer the simpler, cheaper path before anyone sinks weeks into the wrong thing. Now that I've felt that pull to over-build myself, I understand it from the inside, and I think that makes me a better partner to the founders I design with.
If you've made the leap from designer to founder (even for a side project), I'd love to hear what shifted for you.