Built a content repurposing tool as a solo founder using Lovable + Claude. No code. Launched in days.
Hey IH. Wanted to share what I've been working on.
The problem: I write content (blog posts, newsletters), but I almost never repurpose it. Turning one post into 9 platform-specific versions is boring work, and I always skip it. Which means I'm leaving a ton of distribution on the table.
What I built: OncePost (oncepost.ai). Paste any content in, get 9 platform-ready posts out. Twitter/X, LinkedIn, Bluesky, Instagram, Facebook, Email, Thread, and Blog Summary. Takes about 60 seconds. There's a voice training feature, so it actually sounds like you, not like ChatGPT wrote it.
How I built it: Lovable for the frontend, Claude for the AI layer. I'm a solo founder with no engineering team. The AI tooling available right now made this possible in a way it wouldn't have been a year ago. Total build time was measured in days.
Business model:
- Free: 3 repurposes/month
- Creator: $19/mo
- Pro: $49/mo
Where I'm at: Pre-revenue. Just launched. Trying to find early users and figure out if the pricing makes sense.
What I'm not sure about:
- Is voice training a real differentiator or a nice-to-have?
- Should I go freemium or trial-based?
- I'm terrible at self-promotion. Building the product was the easy part. Getting people to try it is the hard part.
Would love feedback on the product, the positioning, or the pricing. Happy to share more about the build process if anyone's curious about using Lovable + Claude together.
Your move from Lovable + Claude to bringing in Claude Code or Rork as complexity grew is unusually relevant to something I’m researching. When those tools surface conflicting choices or a change touches auth, data, or product behavior, how do you decide which questions genuinely need you as Founder and which should be handled and documented by the AI workflow? I’m still doing early problem research and have nothing to sell. If OncePost is now being used with real users or live data, would you be open to a short 20-minute interview or a few async questions here?
I hit the same wall with blog posts, getting one source piece live is easy, doing the channel-native rewrite nine times is what I kept skipping. I still use ChatGPT for rough angles and Buffer once the queue is ready, but I built PostPilot because that ugly in-between rewrite pass kept eating the week, tbh. Curious if your early users care more about voice training or just getting the first usable draft fast?
Love seeing more solo Claude stories. I'm vibecoding @getkeptapp (home inventory AI with smart reminders) as a dad of 3 from the couch, started with one HTML file, now mixing Claude + Supabase and debating PWA vs native.
You went Lovable + Claude for speed. Curious how you handled the transition when things needed more custom logic (auth, data, notifications)? Any point where you had to move beyond "no code" and what that looked like?
This is why I combine Claude Code with Lovable or Rork. As the layer of complexity grows, I ask Claude to help me develop prompts. I have had times when Claude built the prompt, which included some code for specificity. I feel like it enhances what is already there on Lovable and Rork.
The distribution skip makes total sense. I'm building two products right now, and I notice I don't repurpose content for a different reason: I'm not confident enough in what I said to put it everywhere.
So I'll write a post, hit publish, then think 'but did I actually get at the thing that matters here?' and suddenly the last thing I want to do is broadcast it again. So guess what, I have a pile of posts that sit dormant not because of friction but because I'm still uncertain they're worth the amplification.
I feel OncePost solves the friction part beautifully. But I wonder if a lot of creators are stuck earlier in the loop i.e. second-guessing whether the content deserves distribution in the first place or not. You know what I mean?
I feel your pain as I still second-guess myself when writing or developing an app. I can validate the idea and question the results over and over. I am not an overtly open person, but I have pushed myself to do things I normally don't. Like voicing my opinions on app ideas, regulations, pricing, writing content....I just do it and realize later that it wasn't painful at all.