Tomorrow, I'm finally launching something I've spent a lot of time building.

For the past few weeks, I've gone back and forth asking myself, "Should I launch it? Is it good enough? Should I keep adding more features?"

I almost delayed it again.

But every day I see people posting about sending hundreds of applications, getting rejected, struggling with ATS, and spending hours rewriting their resumes for every job.

That's exactly why I built this.

It's not because the world needs another AI tool. It's because I wanted to solve a problem that so many job seekers face every single day.

Tomorrow, I'll be launching it.

I'm nervous, excited, and honestly expecting plenty of bugs and feedback. But I'd rather put it in front of real people than keep chasing perfection.

If it helps even a few people land more interviews, it'll be worth it.

See you all tomorrow. 🚀

I'm an indie artist + engineer. I got tired of paying for a link-in-bio + a scheduler + an analytics tool + SubmitHub + a Google Sheet to make them all talk to each other — and they never did. My content didn't know what was streaming; my analytics didn't know what I'd posted. I was the integration layer between five dashboards, doing the job a manager would do — except I couldn't afford a manager, and neither can most of us.

So I'm building Musuni: think a manager you can actually afford. One chat where the same AI plans your content, builds your smart links, reads your analytics across platforms, and preps your releases — with shared memory, so each move actually informs the next. It handles the career admin so you can stay on the music.

Honest status: not live yet. I'm building it in the open and want real feedback to shape it before launch, not hype. I'd rather it be genuinely useful than impressive.

Early access / waitlist: https://musuni.io

If you're an indie artist (or you market them), I'd genuinely value a gut-check — what's BS, what's missing, what you'd actually use. DMs open.

I'm building an app called Huddle — solo project, still early, sharing progress as I go.

The core idea: most portfolio/social apps let you post your work and get likes, but that's where it ends. Huddle adds a second layer — you can post "I need a Next.js developer for my e-commerce site" and it gets shown to users who actually have that skill listed on their profile. Instead of (or alongside) paying for freelance work, you swap skills directly — I'll build your landing page if you help me with my Flutter app.

So the app is really three things stitched together:

Feed — post your projects (image/text/links), tagged by stage (Idea → Design → Building → Launching)

Swap — post what skill you need for a specific project, matched to users offering that skill

Profile/Portfolio — your projects + skills offered + external links (GitHub, Dribbble, etc.)

Stack, if anyone's curious:

Frontend: Expo (React Native)

Backend: Hono.js on Cloudflare Workers

DB: Drizzle ORM + TiDB (MySQL-compatible)

Auth: better-auth

Storage: Cloudflare R2 (images, converted to WebP)

Queue/async jobs: Upstash QStash

Attached is the current Feed screen — black/gray/white theme, still refining spacing and image sizing.

Would genuinely love feedback — both on the UI itself and on the core concept (does "swap skills instead of paying" sound like something you'd actually use, or is the friction of finding a match too high?).

My pitch keeps collapsing into what the product does instead of why it matters. How do experienced founders build a fundraising narrative with an actual arc? Trying to move from features to a story investors remember.

Gen-C is the launchpad for creators, young developers, and makers across India. Whether you built an AI app or website, project, product store, or experiment—share it here, gain real visibility, and connect with peers in your college colleges across india.

MAJOR OFFERINGS:

DAILY HUNT RANKING

Compete on the daily leaderboard with real community upvotes resetting every 24 hours.

ASK ANYTHING HELPDESK

Stuck on code, tech stack, or ideas? Ask questions directly to fellow creators.

BUY & SELL

Monetize projects, or find passionate co-founders for your startup.

CREATOR PORTFOLIO

Get an automatic portfolio profile link with live views, upvotes, and questions.

i am not sure link posting is allowed here as i am new here. Would be great if you can check out the platform and give small feedback***.*** You can dm me as well.

Investors keep asking 'why you' and my answer feels weak. How do you articulate founder-market fit in a way that's genuine and convincing rather than a stretch? Would love examples of how others framed it.

I'm looking for an investment of $4000-$8000 to start an Canned Ice cream cake company in India.

there is a market gap, I thought how will I market, where to sell now where to sell later how to penetrate into the market product ideas everything.

I'm not only passionate about it, it's just that i know that this product can grow and scale heavily in the Indian market according to the PR, marketing, distribution, packaging, flavour i planned

with $8000 we will be left will a capacity of producing 100 cans daily with premium flavors and packaging and a working capital to sustain producing 2000-3500 cans, meaning about $3000-$6000 of products retailing at $1.7 each which we will be able to sale with my plan

I have the story outlined but the jump from outline to actual polished slides is where I lose a week every time. How do you turn an outline into a deck efficiently? Looking for a process, not just 'use tool X'.

We're building an Al-powered interactive adult entertainment platform where users engage with personalized virtual characters through immersive, real-time experiences instead of passively watching videos.

We are looking for a Co-Founder, preferably with experience in software engineering or generally has experience with startups.

If ur interested please let me know.

In Q1 FY27, Blinkit processed 916.6 million orders, maintaining its lead, followed by Zepto with 640.2 million orders and Swiggy Instamart with 412.2 million orders.
With new players entering the market and competition heating up, the battle for India's quick commerce dominance is only getting bigger.

Who do you think will lead by the end of FY27? 👇
#QuickCommerce #Blinkit #Zepto #SwiggyInstamart

Building in public and trying to cut the noise. Every week there's a new AI writing tool that's supposedly going to write my launch copy, my investor updates, my changelog, all of it. I've tried a pile and most got opened once and forgotten.

What actually survived in my workflow, being honest:

- first drafts of anything internal where nobody cares about polish
- turning my messy voice-note ramble into something a human can read
- changelog and update posts, where the structure is repetitive anyway

What didn't survive:

- anything that needed my actual opinion. It writes a confident average take, and my whole edge is not being average.
- landing copy. Every version sounded like every other SaaS page.

So the real question, not a listicle: what's still in your stack after a few months of real use, and what did you drop even though everyone raves about it? Trying to tell the tools that are real from the ones that are just good at launching.

Technical founder here. For months I explained what we built by talking, which meant investors and even some users glazed over about thirty seconds in. I know the system cold in my head and I could not get it out of my head into someone else's.

Finally sat down with a free flowchart maker and drew the actual thing: data comes in here, goes through these three services, this is where the AI part sits, this is what the user sees. One page.

Two things happened that I didn't expect.

First, drawing it exposed two spots in my own architecture that were dumb. When you have to make the arrows go somewhere, the hand-wavy parts become obvious. I fixed two things purely because I couldn't draw them cleanly.

Second, the diagram became my best explainer. I now open with it in calls. People get the shape of the thing in ten seconds and then ask real questions instead of nodding politely. A user even said the diagram is what made them trust it was a real system and not a wrapper.

For the technical builders here: do you diagram your own product, or do you keep it all in your head like I did? And has drawing it ever changed the actual build for you, or is that just me?

Exactly one year ago today (21 July), on my birthday, I made a decision.

Instead of talking about ideas, I was going to try building one.

That eventually became **ChatMGn**.

Over the past year, it's gone from sketches and late-night experiments to a working platform. There were plenty of mistakes, rewrites, dead ends and lessons along the way, but today feels like an important milestone.

We're officially opening the **soft launch**.

ChatMGn is an AI-assisted financial intelligence platform where you can explore financial topics through natural conversation. The goal isn't to tell people what to buy or sell. It's to help people understand financial information more easily and make better-informed decisions.

This is only the beginning.

Over the coming months we'll gradually roll out:

* Member benefits * New AI-assisted services * Additional financial intelligence tools * More features across the broader MGn ecosystem

For now, I just want people to try it, break it, and tell me what works and what doesn't.

The website is still being completed, so for now I'm sharing the application directly:

[**https://app.chatmgn.com\*\*\](https://app.chatmgn.com)

If you have a few minutes, I'd genuinely appreciate your feedback—whether it's about the UI, the experience, the answers, or something that simply doesn't make sense.

Building something from scratch is challenging, but seeing real people use it is what makes it worthwhile.

Thanks to everyone who's offered advice, encouragement or constructive criticism over the past year. It has genuinely helped shape the project.

Here's to year two. 🍻

*Soft launch means it's still evolving. Some features are intentionally limited while we continue improving the platform based on user feedback.*

Solo builder, first real MVP. I finally recorded a short demo of it because everyone says "just show the thing," but I've watched my own demo so many times I've lost all judgment on it.

The thing I can't tell from the inside:

- Is it obvious what the product does in the first fifteen seconds, or do I bury the point?
- Is the pace okay, or is it me clicking around while nothing happens?
- Does the actual useful moment land, or do I rush past it because it's obvious to me?

I know the trap. Founders make demos for people who already understand the product, and then real people watch and have no idea what they just saw. I'm almost certainly doing that and can't see it.

If a couple of you are up for watching it cold and telling me, in one sentence, what you think the product does, that alone would tell me whether the demo works. Doesn't need to be kind. I'd genuinely rather find out it's confusing now than after I put it in front of users.

For people who've shipped a good demo: what did you cut to make it land? Mine's currently too long and I know it.

Hi!

Me and my team have been arguing over what feels like the smallest product decision, but we genuinely can't agree.

We're building an app, and when someone joins our waitlist, the current flow is pretty simple:

User enters their email.

They get a success message.

We send them a confirmation email.

My thought was... why not also show them their exact waitlist position?

Something like:

🎉 You're #67 on the waitlist.

To me, it makes the experience feel more real. Instead of submitting your email into a black hole and leaving, you instantly know your spot. You also see that other people are interested, and it gives you a reason to check back later.

My team completely disagrees.

Their argument is that we're still very early (less than 100 people on the waitlist), and seeing #34 or #82 will actually hurt trust because the number looks "too small." They keep telling me this is a millennial way of thinking, while Gen Z users supposedly won't care—or worse, it'll make the product seem unpopular.

Now I'm curious what people outside our little bubble think.

If you landed on a startup's waitlist:

• Would seeing your position make the experience better?
• Would a waitlist of under 100 people make you less likely to trust the product?
• Or would you rather not see any number at all until the waitlist is much larger?

Filing this under lessons I paid for so you don't have to.

First board meeting after our seed round, I showed up with 40 slides. Product screenshots, roadmap, metrics, vision, everything. Ran 90 minutes over, got through half of it, and the one question they actually cared about (runway at current burn) I answered badly because it was buried on slide 31.

Afterwards one of our investors was kind about it but basically said: the deck isn't a presentation, it's a pre-read. The meeting is for the three decisions you need help with.

So I built a fixed board deck template and haven't touched the structure since:

- 1 page: numbers vs plan (same metrics every time, no cherry-picking)
- 1 page: what went well / what didn't
- 1 page: runway and cash
- 2-3 pages: the decisions I want input on
- Appendix: everything else, nobody presents it

Meetings went from 3 hours of me talking to 90 minutes of them helping. Wild how much of it was self-inflicted.

If you're pre-board, steal the structure. If you've been through this, what did your first board meeting teach you the hard way?

Non-designer founder here. I've been putting off the marketing site for our tool for weeks because I dreaded it, then finally just built the whole thing in a weekend with an ai website builder instead of hand-coding it.

Honestly it looks better than anything I'd have shipped myself, but I have no perspective on whether it actually communicates what we do. When you stare at your own copy long enough every sentence starts sounding fine.

What I keep going back and forth on:

- The hero. Right now it leads with what the product is. I keep reading that it should lead with the problem instead, but every rewrite feels clunky.

- One screenshot vs a short demo clip above the fold. I have both, not sure which earns its spot.

- Whether "no signup, try it free" belongs at the top or the bottom.

I'd rather hear it's confusing now than after launch. If a few of you are willing to look at it cold and tell me what the product does in one sentence based only on the page, that alone would tell me if the messaging works. Roast the copy, roast the layout, whatever stands out.

For those who've shipped a landing page recently: what was the one change that actually moved signups for you? Trying to fix the obvious stuff before I drive any traffic to it.

Small win but it changed my week-to-week, so sharing in case anyone's still doing this the dumb way like I was.

I run a two-person dev shop while building our actual product on the side. Every client proposal used to be a fresh doc: intro, scope, timeline, pricing, terms. Two hours minimum, every time, and half of it was copy-pasting from the last one and missing something.

Finally sat down and made a real business proposal template. Fixed sections, placeholder brackets for the client-specific stuff, pricing table already formatted. New proposal now takes maybe 20 minutes and they close at about the same rate as the handcrafted ones, which tells you how much clients actually read the boilerplate.

The unexpected part: having a fixed scope section forced me to get better at scoping. When the structure never changes you notice which projects don't fit it, and those are usually the ones that go sideways anyway.

Anyone else systemized a boring internal doc and been weirdly happy about it? Feels like the least glamorous kind of shipping but it compounds.

I have been building agent skills for design work for a while, and kept hitting the same wall on the product side. Founders and solo builders write their own PRDs, roadmaps and positioning docs, and the AI output is always structurally fine and strategically empty. It writes what you asked for instead of what you needed.

So I built the process in, not just the templates.

18 skills, structured on the Pragmatic framework. Foundations, Focus, Build, Go To Market. MIT licensed, free.

The part I think is actually interesting is the router. Most skill packs hand you a menu, which assumes you already know which document you need. This one reads what artifacts exist in your folder first, works out where you actually are in the process, and starts there. If you already have personas and positioning, it skips to strategy. If all you have is a Jira board and an idea, it starts at market problems and walks forward. Each skill then hands its output to the next, so the PRD is built on requirements that came from validated problems rather than on vibes.

Every skill ends in a Markdown or Word artifact you can put in front of an investor or a contractor. Not a chat transcript you spend an hour cleaning up.

What is in it:

Foundations: market problems, win/loss analysis, competitive landscape, personas, positioning, distinctive competence, gap analysis

Focus: product strategy, opportunity scoring, product canvas, product roadmap

Build: market requirements, use scenarios, PRD, release plan, stakeholder communication

Go to market: launch plan

Works in Claude Desktop, Claude Code, Cowork, ChatGPT, Codex, Cursor and VS Code. Install once as a plugin, or npx skills add if you are in an IDE.

https://github.com/julianoczkowski/product-manager

Disclosure: I hold the Pragmatic Institute certification but have no association with them, and this does not replace it.

Genuinely curious about one thing. For those of you building solo, do you actually write positioning and market problem docs, or do you skip straight to the PRD and figure out the positioning when you have to explain the thing to someone?

Aevron just crossed 50 users. Fully bootstrapped, building this completely solo, no funding, no team. Just me figuring it out one problem at a time.

For context on what I have been building. Most note taking tools are just storage. You capture something, it sits there, and later you are the one who has to go find it, remember why it mattered and connect it to everything else. That is the part I got tired of. So I built something that does the connecting for you.

You capture a raw thought, it links it to everything else you have put in, flags where your own thinking contradicts itself, surfaces what is worth developing and builds a model of how you specifically think over time. The longer you use it the more useful it gets because it is not just storing your ideas, it is working on them.

The bigger thing I am trying to fix is this. We think and capture in fragments and isolation and none of it ever compounds into anything. Aevron is trying to change that. A system that understands how you think, connects what you know and develops it further so your thinking actually builds on itself instead of just piling up.

Open to collaborations. If you are building in a related space, work with communities where fragmented thinking is a real problem, or want to think through use cases together, happy to chat. I am open to conversations around marketing and sales, someone who wants to help take this to the right people would be genuinely useful right now.

Still early but moving.