Collaborate with Build to Launch
Build to Launch has grown way beyond what I imagined when I started beginning of 2025. I’m genuinely grateful.
None of this happens without you, your replies, your engagement, your willingness to share what worked and what broke. That participation turned this into something real.
We’ve been quietly collaborating all along. Build to Launch Friday spotlights. Guest posts diving into frameworks and systems. Real conversations about shipping products with AI. But I never formally documented how any of this works or how you can join in.
With these features becoming regular parts of the newsletter, it’s time to open it up properly.
If you’re building something and want to share your journey, or if you have expertise that would help other builders, here’s how we can work together.
1\. Build to Launch Friday
What it is:
Every Friday, I feature a builder from the vibe coding builders collection who’s using AI to turn domain expertise into real products. These are in-depth conversations about your building journey: the origin story, the challenges, the wins, and what you learned along the way.
What you can expect from me:
I’ll send you a questionnaire covering your background, your product’s origin, building challenges, feedback you received, and advice for other builders
We’ll have a conversation (async or live) where I might ask follow-up questions to dig deeper into interesting parts of your journey
I’ll draft the full article, weaving together your unfiltered answers with my commentary and observations
You’ll review the draft and we’ll revise until it captures your story accurately
When published, you get full credit, links to your product and builder profile, and the article gets distributed across Substack, Medium, and Reddit for maximum visibility
Your story lives permanently in the Build to Launch Friday archive
What I need from you:
A public-facing product at any stage (MVP, beta, launched). Number of users doesn’t matter
Your honest answers about the building process, including what didn’t go smoothly
Openness about your non-technical or technical background
A profile on vibecoding.builders so people can find your project
Willingness to let me redistribute the article to Medium and Reddit (with your full credit)
Examples:
[
Build to Launch
Adapt or Die: How He Saw Film’s Collapse and Vibe-Built His New Way Out
Welcome to Build to Launch Fridays, where we meet the builders turning domain expertise into AI-powered products…
Read more
10 months ago · 47 likes · 28 comments · Jenny Ouyang and Kenny - Your Freelance Friend
[
Build to Launch
Why Not Try? How She Tackled 'Impossible' Tech and Built the Semantic Search Tool for Substack Readers
Welcome to Build to Launch Fridays, where we meet the builders turning domain expertise into AI-powered products…
Read more
9 months ago · 78 likes · 29 comments · Karen Spinner and Jenny Ouyang
How to start:
Leave a comment below any BTLF article or DM me. We’ll discuss your product and schedule the release. The whole process typically takes 1-2 weeks from first contact to finished draft.
2\. Guest Posts
What it is:
Guest posts are standalone articles where you share expertise, frameworks, or insights that help builders navigate a specific challenge. These typically publish on Mondays and dive deep into one focused topic: creating an AI policy, handling technical debt, pricing strategy, or anything else builders need to know.
What you can expect from me:
I’ll frame your piece with a personal introduction explaining why this topic matters and why I invited you to write it
You write the core content in your own voice and style
I’ll provide light suggestions for flow and consistency with Build to Launch’s tone, but the expertise and perspective remain entirely yours
When published, you’re credited as the author with links to your newsletter, product, or website
The article gets shared with the full Build to Launch audience
What I need from you:
A clear, actionable topic that addresses a real challenge builders face
Your expertise or lived experience with that challenge
A draft that’s conversational, practical, and specific (frameworks, steps, examples work great)
Willingness to collaborate on revisions to make sure it lands well with the audience
Examples:
[
Build to Launch
Don’t Let AI Fool Your Vision: The 6-Step Guide To Creating An AI Policy
In one of my recent notes, I shared an idea…
Read more
a year ago · 38 likes · 13 comments · Jenny Ouyang and Joel Salinas
[
Build to Launch
He Built an MCP Server So You Can Talk to AI About Any Substack Author
You know that feeling when you’re deep in a project, making real progress, and then you need to check one thing in another tool…
Read more
9 months ago · 55 likes · 13 comments · Jenny Ouyang and Alejandro Aboy
How to start:
Send me a pitch: What topic would you write about? Why does it matter to builders? What’s your connection to it? If it fits, we’ll move forward together.
The Spirit Behind This
I started Build to Launch because AI unlocked me from every status box I’d been put in. Scientist, parent, developer. AI connected all those dots and showed me I could ship products I never imagined possible.
That transformation? I want to help you find it too.
My goal is simple: help builders build smarter, launch faster, and grow systematically. Not through endless tutorials, but through practical systems that work in the real world. I share both the wins and the messy failures, because that’s how we actually learn.
When you’re featured in Build to Launch Friday or contribute a guest post, you’re sharing what you’ve learned in a space where builders connect authentically. No holding back. No gatekeeping. Just honest insights about what worked, what didn’t, and what you think matters, delivered to people who might need to hear it.
This is about the complete journey: BUILD → LAUNCH → GROW. And doing it together, not alone.
How to Reach Me
Leave a comment below or DM me on Substack. I read everything and respond to everyone.
If you’re building something, I want to hear about it. That’s what this is for.
— Jenny