There's a specific frustration that only builders understand.
You're deep in a codebase. You just refactored the auth flow, fixed three edge cases, and deployed a feature that changes how the whole thing works. You close your laptop, feel good for about ten minutes, and then realize nobody saw any of it.
Not your followers. Not the people who'd actually use the thing. Not the recruiter who looked at your GitHub once and moved on because there was no narrative attached to the green squares.
That was me for months. Shipping consistently, building things I was proud of, and watching people with half the output get ten times the visibility because they wrote a LinkedIn post about it.
I didn't have a posting problem. I had a friction problem.
The gap isn't motivation. It's timing.
Right after I push a meaningful commit, there's a five-minute window where I could articulate exactly what I built and why it matters. The context is loaded. The excitement is there.
But I never write the post in that window. I'm already onto the next thing, or I tell myself I'll do it later and "later" turns into "never."
By the time I sit down to write, I'm staring at a commit history trying to reverse-engineer what I was thinking three days ago. So I don't post. Again.
What if something caught that moment for me?
Building the thing I kept wishing existed
That question turned into Tamagrow. I started building it with two teammates, we'll call them A and N, with a simple premise: what if your work spoke for itself, automatically?
Connect your GitHub repo or an RSS feed, and Tamagrow watches for updates. When you push something significant, it drafts a post tailored for LinkedIn, X, or wherever your audience lives. You get an email, review the draft, and approve with one click. The whole loop takes about ten seconds.
No context switching. No staring at a blank LinkedIn editor at 11 PM trying to sound professional about a commit you made at 2 AM.
The moment it clicked
We'd been showing Tamagrow at hackathons and campus events, getting solid reactions but nothing that made me think okay, this actually works. Then my partner A demo'd it at Startup Village talks at a pitch event.
Mid-presentation, a guest speaker in the audience pulled out their laptop, connected their own repo, pushed a commit, and watched a draft appear in real time. Unprompted. On their own code.
They didn't ask permission. They just wanted to see if it was real.
That was the moment I stopped thinking of Tamagrow as a side project and started thinking of it as a product.
What Tamagrow actually does
For the builders who skipped the story (no judgment):
- Connect your sources. GitHub repos for commit monitoring, RSS feeds for blog/article tracking. Same pipeline.
- Significance rating. Not every commit deserves a post. Tamagrow rates updates 1–5 and only drafts the ones worth talking about.
- Platform-tailored drafts. Tuned for LinkedIn, X, and more. Different norms, different formats, same story.
- One-click approval. Review from your dashboard or directly from email. Nothing publishes without your say-so.
- Tone and voice controls. Set a voice per account so posts sound like you, not a bot.
Your work deserves an audience. Tamagrow makes sure it gets one.
Who this is for
We built this for the version of me who was pushing code every day and had nothing to show for it publicly. Turns out that problem is everywhere:
Solo devs and indie hackers who want to build in public but can't stop building to write about building.
Job seekers and students doing the work but not getting credit. Your GitHub activity is impressive. Most hiring managers just never see it.
Technical writers who publish tutorials but forget to promote them. Connect your RSS feed and let Tamagrow handle distribution.
What's next
Tamagrow is live at tamagrow.app. Free to start, no credit card required.
We're early. The product works, the core loop is solid, and we're shipping improvements based on real feedback. If you try it and something feels off, or something clicks, I want to hear about it.
I'm building this in public too (with Tamagrow's help, obviously). Follow along here on dev.to, or come say hi in the comments.
If you've ever closed your laptop after a great session and thought I should really post about that and then didn't, this is for you.
Top comments (0)