X posts

Umer

@UmerShips

I went from 0 to 8,241 users for my B2B SaaS in 50 days. No ads. No content agency. No editor. Just one Reel format, posted twice a day. Got 5.6M views. My best Reel hit 1M. The crazy part? The system is stupidly simple 👇 x.com/i/article/2103…

How they grewOne Reel format, posted twice a day

Marcos Placona

@marcos_placona

Built a new app, didn't do any marketing, and it's almost at $200 MRR 🙏🤡

How they grewno marketing

Naya

@bossnayamoss

Last year, I built SO many software products. I thought by now Id have at least $500 to $1K in MRR. I beat myself up over it so much. I felt like a failure. But really, I was just upskilling! A year later, I realize none of that work was in vain. It was all a stepping stone. 🚀

Imran.dev

@AMDIMRAN11

built 5 hours after my 9 to 5 0 caffeine day 3 of my own saas boilerplate done: api + web + cli + postgres tables target is $1.5k mrr too small or realistic?

Viraj Chandra

@virajchandra51

i have built 5-6 products so far as indie, and i released all of them as free ( big mistake ) so now, most of them have $0 MRR, 2 users, both are me on different accounts need to learn distribution

Alishan -AutoAiShorts.com

@MDALISHANALI2

$362 MRR. not crazy money. but i’ve never paid a single penny to build my apps. and now strangers are paying me for something i built. that feeling is different. no funding. no fancy team. just shipping every day. "small progress compounds." grateful for the indie dev community + @divyanshunegi we’re just getting started.

Nick

@Nick_333ch

day 13 of building postraid.com to $10k mrr we got a new customer 🕺 i still dance for every single one. you probably don’t believe me, but i actually do we’re at $388 mrr. one more subscriber and we cross $400. can we reach $1k in our first month? looking at the trend on trustmrr… i’m not so sure. the curve is starting to flatten, and that’s when the doubts get loud. is the product good enough? am i reaching the right people? how do i bring more traffic? how do i get someone who tried it once to give it another chance after the improvements? this week i updated the landing page and improved the content quality. spent a lot of time on the prompts to make the generated texts more relevant and less generic. the biggest thing i’m working on now is autopilot. but i keep wondering if i should spend tomorrow building that, improving seo, writing an article, or posting on reddit. every option feels important when you’re doing all of it yourself. anyway, 12 people are paying for something i built. that still feels pretty crazy. if you’ve been here before, how did you decide when to keep building and when to focus on getting more people through the door?

How they grewSEO, article writing, Reddit, and landing page updates

jack friks

@jackfriks

welp now i just have to give my wife full access to claude opus 5.5 and she can make shorts to promote my app 3x per day from her phone using claude code remote control and bring my mobile app to 10k MRR hopefully in record speed x.com/jackfriks/stat…

How they grewShorts made with Claude Opus 5.5 and Claude Code remote control

Samar Kundal

@thesamarkundal

I got 100M views on Reddit. Now I'm trying to make money from it. Today I launched Reddibee. Your AI agent reads Reddit and finds people asking for what you sell. Goal: $1k MRR in 30 days. If I can't, I kill it. Building in public, numbers every Friday.

Noorullah Jamakzai

@itzSaasified

day 5 check-in. whats actually happening: content: spent today turning agent work into something humans can steal. built a simple process for reddit + gtm content (short → article). then killed a fat outbound article that sounded like a robot wrote an sop. rewrote it as email infra only: domains → inboxes → dns → warmup. exact prompts. grokbot as employees for the boring tabs. ops: same bottleneck as day 2 honestly. inboxes still warming. cant pretend volume is live yet. linkedin avatars still slow. necessary. annoying. product: still cutting arnies. every feature i delete makes the offer clearer. still not clear enough. mrr: still ~$1k. flat. posting it again so i dont lie to myself. twitter: replies every day. notifications. follow backs. distribution is still the job. content is the side quest that makes the replies better. hardships in one line: writing the real playbook while infra is still warming, product still too fat, mrr still stuck. what im doing next: finish the email infra article until itd actually help someone copy it keep cutting arnies until one outcome is obvious wait out warmup → then real outbound stay in the replies. no disappearing after a good day if youre also building with agents as staff (not chat toys) — drop what you handed them this week. ill follow the ones doing real work. still early. still ugly. still going. day 5 to 10k.

How they grewTwitter replies and notifications; distribution is still the job

Nick Velkovski

@nikolak47

We hit $18M ARR at @heyreach_io Every milestone looks great from the outside. But there's always good and bad behind it. So here's both, plus what I learned along the way. if you're building a SaaS in 2026, hopefully some of it saves you time: THE GOOD: 1. We launched Voice Notes, the most requested feature For a year and a half, on the top of our most requested features was Voice notes. Our competitors had this feature long before us, but IMO, none of them executed it the right way. We lost a ton of deals because of that, and we still didn't prioritize it. Why? The technology wasn't there yet, and it would have been a clunky and messy execution. Every feature that's out in HeyReach, is really well-thought, and it's solving a problem. Now when the voice models became affordable and much better, we decided to do this feature. Bottomline...you don't have to build something just because your competitors have it. The main question you have to ask yourself is: "can we solve this for the user in a really good way right now?" if not, wait (even if you lose some deals). 2. We finally hired a product person One of the biggest bottlenecks at HeyReach was... me. I was the guy owning product since day one. At the start, that's normal. You're product, sales, marketing, ops and support, and we couldn't even get a single senior person to join full-time before $1M ARR. Then HeyReach kept growing, and I kept owning product. At some point, I started being the main problem. This summer, I did something about it. I brought in someone who's been doing product for 15+ years. Probably the best decision I could have done this summer. 3. We are slowly repositioning HeyReach toward being AI-first The industry is moving forward, and GTM teams are already becoming agentic. At one point our roadmap had an AI SDR, AI hyper-personalization, AI profile optimization... I'm super glad we didn't blindly follow that route. We wanted to do it the right way. A year ago we shipped our MCP, and customers started using agents with HeyReach in ways we hadn't even thought of. We are changing our positioning in the next few months, and considering the amount of data and know-how we have about the LinkedIn outreach space, I'm sure we'll nail it. 4. Our EBITDA is 73%+ (I don't think this needs any more explaining haha) 5. We have an exciting launch coming up next month (and a potential new product) As HeyReach is becoming more and more autonomous (we have an amazing team), I started feeling a bit obsolete. Then, in March this year I had an opportunity to meet a founder with a great product who was down to sell it to us. We acquired it, and changed the business model. Planning to launch it publicly mid-October. I think it has a potential to be 5-10x bigger than HeyReach. THE BAD: 1. Growth slowed down (seasonality + exhausting the TAM) We got used to 10-15% MoM growth last year, but this year, we are in the single digits (7% MoM being the average). The product is better than ever, the support is better than ever, more and more people are hopping into LinkedIn outreach, so what's the problem? I think we are slowly exhausting the TAM with the old positioning. Our feature-set so far was directed mainly toward agencies, and just in the recent months we started shifting it toward sales & GTM teams. But I'd still tell every early founder to niche down, it's literally how we got here (without having to raise). 2. I wanna turn HeyReach into a $50M ARR company, but I'm not sure the market is that big (or if it's gonna grow that fast) 3. My focus is torn between 2 products, and sometimes I feel like I'm not doing the best work On a good track to surpass $20M ARR this year (2x than what we were in January)! If you've been a user or a current customer, cheers for making it along the way. Watch out for our upcoming launch next month 💪🏻 Fin.

How they grewold positioning, then shifting toward sales & GTM teams

Parth Arora

@heypartharora

The product has hit $3M ARR since we built end-to-end from scratch. The current scale of the product: It has more than 15k daily active users, and the next phase of cost optimisations have started for both Infra as well as the AI usage (which is quite heavy right now). It has to be one of the most techincally challenging product we have worked upon and delivered in less than 2 months.

Marouane 🇨🇦🇲🇦

@RapidHodler

We finally launched the new Rapid website 🚀 TheRapidApps.com Super proud of how it turned out and this is only V1. Huge shoutout to @y_bou9sim, the mastermind behind the whole experience. He took the vision and turned it into something that finally represents where Rapid is heading. The crazy part is that we scaled Rapid to 7 figures ARR without ever having a proper, functional website. Now the foundation is there. The next chapter is much bigger: our ambition is to build Rapid into a $100M ARR company over the next 5–7 years, while building one of the strongest ecosystems for Shopify merchants. A lot more to come.

Shreyash Srivastava

@YesShrey

500 people have used something I built. 🥹 500 users. 5.4K events. IHate LovePDF started because I was tired of PDF tools being slow, cluttered and unnecessarily complicated. Still building. Still improving. 500 down. 🚀 ihatelovepdf.com

Jordan

@i7solar

i have over 7k followers BUT I built Jobbie, a mobile/web app that allows you to apply to jobs in one click or swipe - we've secured over 1000 interviews and we're on track to hit 10k users by Sunday. usejobbie.com x.com/hthieblot/stat…

Alberto Arena

@alberto_arena

I built a CLI tool in three days. Tests, CI, docs, zero users. I never asked whether it should exist. albertoarena.it/posts/the-effo…

Uriel Bitton

@uriel_builds

I joined Buildside as a founder exactly 2 months ago. Of course I was the only user on the platform. Then i built it in public and grew it to 299 users today ! #letsgoo !!!

How they grewBuilt in public

Chris Ani

@iamchrisani

When I started building ValoAi, I wasn’t trying to make the financial market more complicated. I was trying to make it simpler. I was thinking about the everyday person who wants to make money from crypto, stocks and the financial market, but does not have the luxury of sitting on TradingView all day watching 10–20 charts. You have a job. You have a business. You have a family. You have other things to do. You should not need to become a professional trader before you can make intelligent decisions in the financial market. That is what I wanted ValoAi to solve. Take all the charts. The market data. The technical analysis. The fundamentals. The risk. The opportunities. The millions of coins and stocks available. Process all that information and simply tell you: What should I be looking at? What can I buy? Where should I enter? Where should I sell? Where am I wrong? How much of my capital should I risk? What is the potential profit? That is ValoAi. I wasn’t building it only for professional traders and investors. They are part of our users, of course. But I was also building it for the banker. The entrepreneur. The student. The doctor. The engineer. The busy professional. The person who doesn’t understand all the trading jargon and doesn’t want to spend hours searching CoinMarketCap trying to figure out which of thousands of coins to buy. In fact, over 60% of our users are not professional traders. They simply use the intelligence ValoAi gives them to make better trading and investment decisions. Think about what AI has done for software development. Today, somebody who is not a professional developer can use AI tools to build things that previously required years of programming experience. That is how I see @ValoAi31561 for the financial market. You may not have years of trading experience. You may not understand every indicator. You may not know how to read 16 charts. But you can still use professional-grade market intelligence to trade with more structure, manage your risk and make better decisions. Crypto. Stocks. ETFs. Tokenized stocks. Commodities. One simple intelligence layer helping you understand what is happening and what action you can take. Trading the financial market can be hard. ValoAi is making it easier. That is why I built ValoAi for everyday people. valoai.app

Omkar Chebale

@omkarchebale

I served a 7B LLM on a free GPU, made it work with a coding agent, and pushed 3,000+ requests through it to see where it breaks. $0 cloud bill. Here's everything I learned 👇 What I built Qwen2.5-7B-Instruct (4-bit AWQ) on vLLM, running on a free Kaggle T4. It's exposed as an OpenAI-compatible HTTPS API, so Postman, my backend and even a coding agent (with tool calls) plug straight in. The journey (everything that broke) 1/ The model wouldn't start. A T4 has no bf16 support, and Qwen defaults to bf16. One flag, --dtype half, fixed it. The 4-bit AWQ weights take ~5.5 GB of 16 GB, leaving room for the KV cache. 2/ The server kept dying. "Background" processes die when a Kaggle notebook finishes, and a pushed notebook finishes right away. I wrote a supervisor that restarts vLLM and the tunnel, and exits cleanly before Kaggle's 12-hour limit so the logs are saved. 3/ My secrets disappeared. Kaggle Secrets vanish silently when you push a notebook from the CLI. The fix: a private dataset holding the keys, created by one setup script. 4/ My coding agent's first request failed. "auto tool choice requires --enable-auto-tool-choice". vLLM needs an explicit tool-call parser, and a 4K context is useless for an agent. With the Hermes parser and 32K context, tool calls worked. 5/ I couldn't see anything. I put a small proxy in front of vLLM. It adds API-key auth (vLLM's /metrics endpoint had been public), a full trace per request, and GPU and KV-cache metrics every 15 seconds. 6/ My benchmarks lied to me. The first results: 13 seconds to first token. Awful. Then I found three benchmarks had been running at once, and one of them fired 512 requests together. In isolation, the same load gave 1.1 seconds. Never benchmark two things at once. The numbers (GuideLLM, through the public URL, network included) ⚡ 1 user: first token in 0.8s, then up to ~38 tokens/s. Faster than you can read. 👥 ~4 users at once: ~1.1s to first token, ~25 tokens/s each. 🚦 12+ at once (rough, from an early run): requests queue, and waits grow to 10 to 20s. 📈 Peak: ~215 output tokens/s across 16 parallel requests (measured directly on the server). In real terms: about 40 casual chat users, or 2 to 3 people running coding agents, on one free GPU. The surprise Under load the GPU showed 100%, and I assumed I'd hit the ceiling. Wrong. The KV cache used 2.5% of its reserved memory on average, and Kaggle's machine had a second T4 sitting completely idle the whole time. "100% GPU" told me one chip was busy, not that I'd used my hardware. Measure before you scale. Honest limits 12-hour sessions, 30 GPU hours a week, ngrok free-tier caps, and about 15 minutes to boot. A 7B model is great for chat and simple agent tasks, but not for complex multi-step coding. This is for learning, demos and small teams, not public traffic. Try it yourself It's open source. With a Kaggle account and a free ngrok account, one python setup.py file gives you your own endpoint in about 25 minutes:

How they grewKaggle free GPU and ngrok free tier

ozzy

@ozzyxbt

I built an on-chain analytics page for @GrailCo , real-world collectibles turned into tokens on Base and Robinhood Chain. Grail is one of the few crypto apps where regular users make money without size, and the team is backed by a top web3 VC. I wanted to see behind the screen. Now anyone can. Every swap, pack, redeem and vault since day one: · 16.8k traders, $24.5M volume · 47% in profit overall, 67% for people trading through the Grail app · $196k in pack sales, 21k collectibles redeemed · who vaulted their own collectibles and whether it paid · what each launch did to volume, and which tokens rise with it ozzyxbt.github.io/grail-analytic…

surojit

@surojit

On the back of our Series B raise, I sent this note to our team internally. Someone suggested I post it here as well: Team, TL;DR: The announcement landed and the response was strong. Enjoy it, then get back to work. The praise and the skepticism are both noise. The plan has not changed, the opportunity in front of us is much bigger than a funding round, and the people in this company are what make it possible. What happened yesterday Three years ago I stood on a stage and said SaaS is dead. The room laughed. Yesterday we announced our Series B, and the response was very different. TechCrunch ran it under the headline that AI is starting to eat into enterprise software and services. SiliconANGLE, Yahoo Finance and most of the Indian business press followed. More than 50 posts tagged Ema on LinkedIn in the first day—investors, customers, advisors who were at the whiteboard with us three years ago, and many of you, writing about what you built in your own words. Thank you. Those posts meant a great deal to me. The facts, so we are all precise about them: $77M, led by Creaegis, with Accel, S32, Prosus, Hitachi Ventures and Wipro Ventures all increasing their investment. $140M raised in total, at more than 4x our last valuation. These are people who spent months in our data room, talked to our customers without us in the room, and stress-tested every number we have ever shown them. Every major existing investor came back, and every one of them wrote a bigger cheque. Fewer than 1% of startups ever raise more than $100M, and the median company takes 4.9 years to get from seed to Series B. We did it in two and a half, with 50x revenue growth in 24 months. They did not fund a story. They funded what you built: an MVP shipped in three months while others slipped weekly. ~98% of HR Tier 1–2 work automated with zero hallucinations. 50 use cases across 240,000 employees without a single third-party consultant. Customers who nearly double their spend after the first deployment. Every line of that has your fingerprints on it. About the noise The skeptics say the metrics are company-sourced, bookings are not ARR, most GenAI pilots never reach production, we still have to prove this scales, the frontier labs will compete with us, and the market is a bubble. Some of these are fair questions. We chose not to share ARR publicly, and every number in the press is ours rather than an auditor's. The proof that matters is whether customers renew and expand. So far they do: more than 90% have expanded beyond their first use case. The optimists say SaaS is dead, Ema has won, and this is a generational company. I appreciate the belief. But a raise is not an accomplishment in itself. It is a group of serious people looking closely at what we have built and deciding to back where it goes next. I am humbled by it. But the real accomplishment is still ahead of us. Both groups are forming a view from the outside, based on a press release and a few articles. We have something they do not: the data on how customers actually use Ema, and whether they come back. Our job is to keep adding to that data, not to argue about it. Outcome-based pricing keeps us honest here. We get paid when work gets done. Our customers hold us to a higher standard than any commentator will. Our values say it plainly: we have to earn our place in the world, and we celebrate our successes but never get carried away. That is humility, and a week like this is when it counts most. We have built something real, and we have a long way to go. Thank the people who congratulated us. Do not engage with the criticism, and do not get carried away by the praise. Neither changes what we need to do this quarter. The opportunity ahead I want to be clear about what this capital is for, because it is not for a bigger version of what we have today. We are going to change the entire enterprise software stack over time, not one category of it. For twenty years enterprise software has worked the same way: you buy the software, then you hire people to operate it. ServiceNow tracks the ticket; a person closes it. Workday holds the record; a person runs the process. Every large SaaS application is a system of record with thousands of people doing the work around it. AI Employees change that. When software can do the work itself, the work moves to the AI Employee and the system of record becomes a database. That is the SaaS-is-dead thesis, and it is now visible in our own customers. Some are already on the way to replacing large SaaS applications completely. Others are reducing their dependency one workflow at a time. The incumbents see the same shift. ServiceNow and SAP have moved this year to meter or restrict outside AI agents on their systems, and Workday has said charging for agent access is a business opportunity. These are formidable companies and they will fight to defend their position. It does not change where the work is going. So here is the vision, plainly: every enterprise will run on agentic AI, and Ema will be the platform they run it on. Our HR, IT and Finance Hubs are the first surfaces — HCM and ITSM, the territory Workday and ServiceNow occupy today. We have a real chance to replace them, and many others, at some of the largest companies in the world. And it does not stop there. Every SaaS application that exists to route work to a person will eventually be replaced by software that does the work. We intend to be the company that replaces them. Underneath the market logic is the reason we started Ema: we want jobs to feel wonderful again—less admin and copy-pasting, more of the work people actually signed up to do. At Wipro that means 3M queries a year answered in seconds instead of days. Multiply that across every enterprise and we are adding to the world's productive capacity, not just replacing software. This is why we believe in our mission 'Grow World GDP by Transforming Every Business with Universal AI Employees". It is supposed to be bold, supposed to be timeless. We won't do it in any other way. None of this happens in a quarter. It happens over years, one production deployment at a time. Very few companies get to attempt it with production proof, capital and the team already in place. We do. What it asks of us What we announced on Wednesday came from decisions made twelve and eighteen months ago, most of them on ordinary days. What we do this quarter is what gets highlighted by the external world in 2028. Three asks: Ship at a pace that feels slightly uncomfortable. Well-funded competitors will come for this market. Speed compounds faster than anyone can copy an idea. Stay close to the mess. Our edge is earned in rooms with customers, not in planning docs. Hold the bar when nobody is checking. Companies are defined by the ordinary Thursday, not the launch day. Our customers had the same tickets and SLAs on Wednesday that they had on Tuesday. Our job did not change. People are everything Capital does not build a company. People do. Everything in this note—the numbers, the customers, the coverage—was built by all of you across Mountain View, Bengaluru, London and Vancouver, most of it on days when nobody was watching. I do not want that lost in a week about money. As we grow, the one thing I refuse to lose is a direct line to each of you. The best ideas for making Ema better will not come from the top. They will come from the people closest to the work and closest to our customers. That is why I started the small-group coffee chats a few weeks ago: no agenda, no slides, just an open and confidential conversation about what is working, what is broken, and what you would change if you were in my seat. We will keep rotating until I have met with everyone, and I am acting on what I hear. Please keep bringing the hard truths. Nothing is off the table. We are here to build the best company in the world. That only happens if every one of us has a voice in shaping it, and if we protect the culture that got us here: honest feedback, real ownership, growing talent from within and hiring the best talent from outside, and helping each other. This round does not change any of that. It funds it. So, thank you. To the engineering, product and design teams who kept shipping through security reviews, complex integrations and go-lives at odd hours. To the forward-deployed and customer teams who stay with customers until the work is actually done. To sales, partnerships and marketing, who took Ema into rooms we could not have reached alone. To operations, finance, hr people, who keep the company running and rarely get the headline. And to your families, who share the cost of the hours this takes. None of this exists without you. One last thing To anyone who has wondered whether this is worth it: the people with the most information and the most to lose just said yes, louder than last time. I believe in this more today than I did on day one, and I did not think that was possible. The noise will fade by Monday. The opportunity will not. Let's go build! 📷 -Surojit (edited)

Viktorijan “Vick” Mucunski

@Vick_Mucunski

Back in February, 9 of every 100 dollars we earned at @heyreach_io were walking out the door, and part of every new signup went to replacing them. Plug the leak and the same signups start to compound. That makes retention the cheapest growth lever. And since then our success and support took that 9% down to 7% and got us our best retention month on record. Here are some of the retention and customer success motions we've run along the way: 1. Failed payments (the cheapest revenue you'll ever win back) We built an in-house delinquent recovery flow instead of waiting for cards to update themselves. 4 days after it went live, it had recovered 30% of what was failing. 2 of those days were the weekend, with nobody in the office. 2. Health signals (catch them before they tell you) We listed more than a dozen possible signals and shipped 7. Inactivity came first: last login older than 7 days, no API usage, no webhook activity, no actions in the platform, no outward engagement. At day 7 a silent account is a conversation. At day 30 it's damage control. 3. Onboarding (where churn starts) The pattern in our churn data was almost embarrassingly consistent. Users who get a real result in their first 2 weeks stay, and the ones who don't leave, whatever discount you offer them later. So we redesigned the first-touch guidance, cut the time to a first campaign, defined what a good first result looks like, and started nudging people before day 7. That gave us our lowest churn rate on record. 4. Cancellation and reactivation We reworked the cancellation experience (in July it saved about $17,300 in MRR on its own) and built a reactivation flow for clients who left 40 to 90 days ago, because sometimes churn just means "not right now." 5. Value over discounts In March, when everyone was calling it the SaaSpocalypse, we kept prices where they were and added value: extra seats, more usage. 100s of users expanded, and it was our best retention month on record. It's the main reason I think the room to grow is already inside our own accounts.

How they grewsuccess and support, onboarding, cancellation flow, reactivation, value adds

ilyos

@ilyosme

Day 4 of $1000 mrr by oct 7 made a reel for appx. one paragraph prompt, recipe app built in 5m 35s, 15 files, 29 credits. first 100 credits are free )

Deckard

@DeckardBuilds

AI didn't make building a SaaS easy. It made building the easy part I shipped Stashr in 2 months. 144 people signed up. 4 paying Currently at $36 MRR The code was never the hard part. Getting anyone to care is

ImNotAVirus

@ImNotAV1rus

3 months, 2 apps shipped, still $0 MRR I set myself a target of 1,000 followers and $1k MRR. Finished at 734 followers and no paying customers I honestly thought I'd have made the first sale by now. If you've been through this, how long did yours take? x.com/ImNotAV1rus/st…

Sardor

@Sardor_Rahim

Renewed my Apple Developer membership today. Paid $99 last year, then kept putting off launching my first app for 3 months. Launched in January. Now almost at $400 MRR across 2 apps, so it's already earned the $99 back many times over. Wish I hadn't lost those 3 months

Bagdex

@Bagdex

me building my app: 36-step onboarding account required 3 paywall variants A/B tested pricing exit discount 7-day free trial weekly + monthly + annual plans push + email sequences =$100 MRR some random countdown app: no onboarding no account works for free one €3.99 upgrade =$50K MRR we are overthinking the hell out of this

AJawhar

@alaajawhareng

AI didn't make building a iOS easy. It made building the easy part. I shipped Alarmifex in 2 weeks. 157 people signed up. 7 paying Currently at $166 MRR The code was never the hard part. Getting anyone to care is

Coldmax

@coldmaax

I’m Max. I’m 34, and I’m starting from zero again. I’ve been doing UI/UX for 15 years. Started freelancing at 15 and never had a 9-to-5 job. Back in 2017, I launched my previous product. It hit #1 Product of the Day, grew to 2M+ signups, and made over $1M. It’s still running today with a team of 5. But after years of waiting for code, refactoring the same things over and over, and watching simple ideas take weeks to ship, I wanted to try something different. So I started again. Now I’m building Stick mostly on my own, with AI. New product. New audience. Zero revenue. Goal: $1M ARR. I’m not really here to sell anything. My customers are somewhere else. I’m here because I want to meet more founders, share what I learned the tough way, and see what happens when you start from zero again after doing it once. If you’re building something too, say hi.

Daksh

@dkshbuilds

Day7 of $5k MRR: But why I am not smilling lol in this Today was all about making ScopeYes feel like a real product. Styled every major page. Polished the UI. Cleaned up the experience. Most of the MVP is finally coming together. Next up: Payments 💳 I used Dodo Payments in my last SaaS, but I'm deciding what to use for ScopeYes. Dodo? Stripe? Paddle? Razorpay? What would you pick for a SaaS built in India and selling globally? 👀 Day 7/15. Getting closer. 🔥 #buildinpublic #SaaS #indiehacker

Vaibhav

@Vaibhvjat

first post on here, so hi, i'm vaibhav 👋 launched my first saas ~3 months ago with 0 followers. it's now at almost 4k users and ~$2.7k mrr. not an expert, but i'll share exactly how i got here. (screenshot = new mrr only, mid-switch on payment gateway)

How they grew0 followers at launch

Nick Velkovski

@nikolak47

Nothing I've experienced as an entrepreneur has felt quite like hitting that first million. Back then we'd be around a whiteboard at 3am on a Saturday, drinking beer and designing features we hoped someone would actually use. All of us dreaming about building something big from Macedonia. Me and my co-founder Stefan drove 1,000+ km to a conference because we couldn't afford plane tickets. In Athens, we stayed in a cheap Airbnb with no AC in July. We'd come back with contacts, ideas, stuff we'd learned, and share everything with the team. Sometimes it felt like we had no idea what we were doing. Then we got to $1M ARR, and people were using something we'd built to make money and grow their own companies. That felt fckn unreal. I'm proud of where we are now. It's much more comfortable. But looking back at that scrappy team trying to figure it all out... those were the glory days.

Gladwyn

@gladwyn1_1

1600 Users! I launched my first micro Saas 3 months ago Knew nothing about startups I learned so much in this journey so far Should I start documenting my journey? Like posting everyday until i reach 5k mrr?

Hellyeah.ai

@hellyeah_ai

Yesterday our co-founder Jay Ma (@Doudoujay) asked a room of founders: has a post or a launch ever gotten you more attention than customers? Every hand went up. Then he asked them to keep it up if they could put a number on what that attention did to revenue. Most of the hands came down. We know the feeling. We were building @finalroundai before @hellyeah_ai, and it got to $1M ARR on viral alone. One post did 83 million views. Then we went after $10M and kept getting the views without the revenue. You can't schedule a viral post or buy another one. So we put paid next to it and scored every channel on what @stripe collected. $15M ARR in 12 months. 4.2x blended ROAS. @hellyeah_ai came out of that. We were customer zero, then other founders asked us to run the same playbook on their accounts. The first thing we find is broken measurement: 👉 One campaign we audited reported 2,757% ROAS on the platform. Stripe, net of refunds, said 48%. Same campaign. 👉 A client's dashboard counted 16 sales last month. Their database held 3. 👉 A streaming client paid $300 a sale bidding on purchases. 90% of their payers hit 12 streams on day one, so we moved the bid to that event and paid $80. We fix the data before anyone touches a bid. We got tired of doing this by hand on every account, so we built it into a product. The agent runs the audit and the budget moves, and it asks you before it spends. Google Ads today, more platforms after. Jay got into it with @unifygtm (@DurshtE ), @shanda_group (@bei_zhang01) and Press Club (@kwangaroo) afterward about GTM and which users are worth chasing in the first place. All three of us sell to founders who need customers to show up.

How they grewViral posts plus paid; scored each channel on what Stripe collected.

matt

@not_matt200

day 5 of building in public: - 0 users - 87 followers on x (+24%) - $0 mrr My churn rate didn't match Stripe's. Spent a chunk of the day finding out why: Stripe divides by everyone who paid during the month, not just who you had at the start. Now Scintero counts it Stripe's way. Also shipped: - Scintero connects to your Supabase with a read-only login. It can't change a single row, and Postgres itself enforces that. - Compare today with yesterday, or any day you pick - Plan mix over time: which plans are growing, which are dying What's the first number you check every morning?

How they grewX followers

Johnny

@johnny_schae

Day 43 of scaling my app to $5k MRR Last few days have been really good for views and trial starts. 73 active trials 83 active subscriptions $706 MRR Hoping I’m finally starting to crack the TikTok algorithm. Been testing a lot of different formats and diving deep into the analytics. How they convert, how long they take to create and how many installs they actually bring. Since doubling down on this and being stricter with posting, the results have been really good. Now let’s see how all those new trials convert. Next big focus is improving the conversion inside the app. A lot of work, but finally moving again.

How they grewTikTok; testing different formats and posting more strictly

Kemal · 30+ apps shipped

@kemal_codes

30-something apps live on both stores. last month ios brought in 82 dollars. posting it because the timeline is full of people who shipped one app with an agent last week and are showing you 8k mrr. volume is not income. took me a few years and a lot of apps to learn that.

Deepanshu Saini

@deepanshuliv

forgot to update here: Rescho just crossed 20+ users 😭 small number, but damn seeing real people actually use something i built feels different. rescho.deepanshu.live x.com/deepanshuliv/s…

Kevin L

@KevinFinnAI

Three days ago I launched FINN. Already: - 9 users - 23 sales calls processed - 8 organizations - 0 paid users… for now. And honestly, seeing people actually use something I built is pretty crazy. FINN is a real-time AI sales assistant that works directly inside your calls through a Chrome extension. It listens for what’s happening in the conversation and gives you the right insight at the right moment — without making you leave the call. If you’re a closer, try it: 👉 finnai.io

Efosa || Thecube

@_thefosaken

Last week, the @usemytally app hit a milestone - 200 signups. 200 actual human beings took their time to download something I built. Phew! 😅😅 web: mytally.xyz x.com/darasoba/statu…