I'm not a developer by background. I'm a solo founder building Vendozo — an AI-powered SaaS that generates SEO-optimized content for e-commerce sellers — and I'm doing it with n8n, Supabase, and Lovable while working a separate job from 3pm to 9pm every day.
This is a behind-the-scenes look at what I'm building, why, and the technical choices I made as a non-dev founder figuring it out as I go.
The Problem
If you've ever sold products on Etsy or WooCommerce, you know the SEO grind. Writing optimized titles, tags, and descriptions for every product is tedious, time-consuming, and — if you're not an SEO person — pretty confusing.
Most sellers either ignore it entirely or copy-paste from competitors. Neither works. The result? Great products that nobody finds.
Vendozo solves this. You give it a product, it gives you back:
- A keyword-rich title
- A full set of tags
- An SEO-optimized description All tuned to how search actually works on each platform.
The Stack
I'm a solo founder, not an engineer. So the stack had to be one I could actually move fast with.
n8n — the backbone of everything. All my business logic lives in n8n workflows: OAuth flows, product syncs, AI generation, pushing SEO data back to stores, and dashboard management. I have five separate workflows for the WooCommerce integration alone. n8n lets me build real backend automation visually, which means I spend time on logic, not boilerplate.
Supabase — my database and auth layer. I'm running two Supabase projects (different regions for latency reasons). It handles user data, store connections, generated SEO content, billing status — everything. The Postgres + REST combo is honestly perfect for this use case.
Lovable — my frontend. It's a React-based AI UI builder. I describe what I want, it generates the component. Not perfect, but it's how I shipped a functional dashboard without writing a line of React myself.
Claude (Anthropic) — the AI doing the actual SEO generation inside the n8n workflows. I use it for content generation via API calls within my automation chains.
What I've Built So Far
Etsy Integration
The first version focused on Etsy. A seller connects their store, selects a listing, and Vendozo generates a new title, tags, and description optimized for Etsy search. The workflow pulls listing data, runs it through Claude with a custom SEO prompt, and returns structured output.
Debugging this was a journey — binary deserialization issues, field name mismatches in n8n, expression syntax edge cases. The kind of stuff that takes a week when you're learning as you go.
WooCommerce Integration (Just Completed)
This was a five-phase build:
- OAuth Connection — Secure WooCommerce store linking via REST API credentials
- Product Sync — Pulling product catalog into Supabase
- AI SEO Generation — Running Claude on each product with WooCommerce-specific SEO rules
- SEO Push — Writing optimized content back to the WooCommerce store via API
- Dashboard Management — User-facing controls for managing connected stores and generated content Five n8n workflows. Each one handles one phase. The separation keeps things debuggable — when something breaks, I know exactly where to look.
The Honest Part
I haven't launched yet. Zero paying customers. Pre-orders are live at $9/month for founding members, but I'm still in the testing and debugging phase of the WooCommerce backend.
My hard deadline is July 27 — I'm applying to YC's Summer batch, and I need traction before then. That's the thing driving every decision right now.
I'm also exploring a channel that most SaaS founders ignore: WooCommerce/WordPress freelance developers. These are people who set up stores for small business clients and are always looking for tools to add value without adding work. Instead of targeting individual sellers at scale (which requires ads or massive content), I'm trying to build relationships with developers who can refer Vendozo to their clients directly.
What's Next
- Finish testing the WooCommerce backend
- Onboard first free beta users (targeting WP devs for feedback)
- Get first paying customer before July 27
- YC application
Why I'm Writing This
I'm building in public. Not because it's trendy, but because documenting the process keeps me honest and creates a trail that might actually help someone else who's in a similar position — technical enough to build, not so technical that any of this comes naturally.
If you're building something similar, or you work with WooCommerce stores and want to try Vendozo when it's ready for beta, drop a comment. I'm here.
Top comments (0)