Best tweets about Indie Hackers
A curated collection of the sharpest, most-shared X posts about indie hackers—saved so you do not have to dig through the timeline yourself. Updated weekly.
Solo builders sharing real revenue numbers, launch days, and the projects that died quietly.
Best Indie Hackers tweets
Ranked 01–50
@starter_story ·
You don't need a BIG idea. @jonathanfishner generates $9,000 per month with a TINY one. 3 lessons from his micro SaaS: 1. Pick a weirdly tiny audience 2. Don’t monetize too early (or too late) 3. Distribute content where that audience hangs out
Watch video
@marclou ·
I met OG indie hacker @jessethanley in Japan 🇯🇵 He's living such a crazy life, and I don't know where to start, so here are random facts: - He's running his SaaS @Bento solo and makes a ridiculous amount of money - Unlike most founders, he knows how much is enough and works 4 hours/day - He started indie hacking in 2015 - He ran a marketing agency for 5 years before building a product - His SaaS was profitable from day 0 because he built it for his agency. - He designed his SaaS with a real human touch, and it feels like you're entering his world when you sign up - He taught himself how to code (pre-AI) - He speaks Japanese and has lived in Japan for 7 years - Being a dad made him more productive, not less - He bench presses 135kg - He's happy, positive, kind, and a great conversationalist Thanks for showing us around, Jesse 🙇❤️
@alexcooldev ·
If you’re an indie hacker without much capital (like me back then basically $0): Don’t reinvent the wheel. > Pick an app with a proven market > Build a version that’s slightly better, cleaner, more polished > Add small but clear differentiation > Market it on channels they ignore or underuse This path gets you to $5k–$10k MRR way faster. Once cash flow is there → go big on differentiation and scale. Simple. Boring. Works.
@marclou ·
My friend @AlexandruGlv is building a micro SaaS while working a 9/5, but the growth is very slow, so he asked for my opinion. (for context, his product is a database to find YouTube influencers to sponsor) I went to ChatGPT and asked: "How to find youtubers to sponsor?" It came up with DIY solutions or large generic databases, nothing that fit my use case. If I had to start a new SaaS today, I'd think "How will people interact with my product in 5 years?" In most cases, the answer is through AI assistants, so I'd set AI visibility as my North Star metric and build everything backwards. I'd do everything so that potential customers can 1. Find my product on ChatGPT 2. Onboard on ChatGPT 3. Get value from ChatGPT llms.txt, markdown files, get mentions on Reddit/YouTube, etc... It's still unclear what you need to do to get mentioned, but I'd try everything to become an AI agent first startup, as @wickedguro did with Postiz ($150K MRR). And who knows, maybe along the way I'd discover a new product worth 100x more than my current SaaS? Fuck Around and Find Out 😊
@dramaricic ·
Only way for solo founder like me, to distribute product is to build in public. After 40 days of building in public: - I wrote 2.5k posts - Got 1710 followers - Viewed by 1.4M people - Connected to other builders - Learned a lot I would say things are going great so far. Love it. Are you building in public? 👇
@maubaron ·
it took me 3 years to make $100,000 with software because i followed indie hacker advice - invest as little as possible - build everything yourself - focus on building, not selling i lived this way for years i used free zoho emails instead of paying $7/month for google workspace i waited too long to invest in ads and tools that would've 10x'd my results i told myself it was necessary because i was broke the moment i stopped pinching pennies i stopped obsessing over saving and started obsessing over making more funny how that works i've never spent more per month than i do right now i've also never made more
@ujjwalscript ·
Right now, every developer with Claude and an API key is trying to build a massive, world-changing generative tool. And 99% of them are becoming OBSOLETE in six months. The actual gold mine in 2026? Using AI to build hyper-niche, painfully boring software for industries that Silicon Valley forgot - Micro SaaS! Here is why the math works for solo developers today: 1. The Execution Gap is Gone Two years ago, launching a SaaS required a frontend dev, a backend engineer, and a DBA. Today, a single developer using Claude or Codex can orchestrate the entire modern stack in a week. You no longer need a team; you just need a problem. 2. Riches are in the "Boring" Niches Don't build a "general productivity app." Build a hyper-specific solution for a physical-world problem. Think about a dedicated venue booking platform specifically designed for local schools to reserve sports grounds. It sounds completely unsexy. It won't get you on the front page of Hacker News. But it solves a massive logistical headache (handling timezones, double-bookings, and admin access) for a specific group of buyers who are thrilled to pay a monthly subscription to make their pain go away. 3. You Compete on Empathy, Not Code When the cost of writing code drops to zero, your only moat is your understanding of the customer. Because the AI is handling the boilerplate and the repetitive syntax, you can actually spend 80% of your time acting like a business partner—talking to users, refining the product, and closing sales. The formula has never been clearer: Find a boring problem in a traditional, messy industry. Use AI to build the solution in weeks, not months. Charge $99/month to 1,000 businesses.
@1752vc ·
How to get your first 100 users 🚀 1. Build in public. Share wins, failures, lessons, and progress consistently. One post a day is okay; 3–4 is better. 2. Copy competitor distribution. Find where competitors get backlinks and mentions, then submit your product to the same places. 3. Engage with viral content. Reply to popular posts in your niche with genuine value. Mention your product only when it adds context. 4. Find people already feeling the pain. Search Reddit for complaints your product solves and join the conversation with helpful replies. 5. Go where your ICP hangs out. Communities, newsletters, podcasts, creators—find them and explore sponsorships or partnerships. 6. Launch everywhere. Product Hunt, DevHunt, BetaList, Peerlist, Indie Hackers—if you can list your product, do it. 7. Ride trends. Jump into relevant conversations and trends on X while they're hot. 8. Show, don’t tell. Record a quick product demo and post it on X and LinkedIn. People understand products faster when they see them. 9. Use your network. Reach out to friends, former coworkers, and relevant people on LinkedIn or email with a short, personalized pitch. 10. Work with small creators. DM 10–15 TikTok or Instagram creators. Offer a fixed fee ($15–$30/video) plus bonuses for performance.
@eliana_jordan ·
If I had a 9–5 and had to start my indie hacker journey from scratch, this would be my exact strategy: • Build a better version of a proven saas/app (1 core feature) • cursor codes while you work on your 9-5 • Ship in 2–3 weeks • Grow on X + SEO in parallel • No code changes until first $ → only marketing • No $ in 2 weeks? Fix marketing strategy • No $ in 4 weeks? Pivot Repeat until it works
@Layton_Gott ·
Step by step guide on how to validate your product idea... The RIGHT way. Step 1: Go where people complain. Reddit, X, App Store reviews, YouTube comments. Search your niche. If 10 different people in 10 different places are frustrated by the same thing, that's signal. Step 2: Check if people already pay for bad solutions. Find competitors. If they have thousands of users and charge $20/month, the market is validated for you. Your job isn't to invent a market. It's to build something better. Step 3: Build a simple MVP with a waitlist. Something that shows what the product does and lets people sign up for early access when the full version launches. Use AI to build it in hours, not weeks. You're collecting future users while proving the concept at the same time. Step 4: Post it everywhere your target audience hangs out. X, Linkedin, Reddit, Indie Hackers, relevant Discord servers, communities. Share the problem you're solving and ask for feedback. Step 5: Talk to the people who signed up. DM every single one. Ask what they're currently using, what they hate about it, and what they'd pay for a better solution. These conversations are worth more than any survey. Step 6: Look at the data. If 50+ people joined the waitlist and 5+ said they'd pay, you have something. If nobody signed up and nobody replied, the idea needs work or the audience isn't there. Most devs skip all of this and spend 6 months building and "marketing" something NOBODY wants. Test the idea before you build the product. Always. (Bookmark this for later)
@starter_story ·
He spent months emailing 300+ influencers and got ONE reply. Then Avneesh found two free platforms that took SaveWise from single-thousand users to tens of thousands - without spending a dime on ads. His product helps people stack credit card points and airline miles on stuff they already buy online. After Product Hunt, Hacker News, and Indie Hackers all flopped (95%+ bounce rate), he flipped his approach: stop posting where founders hang out, start posting where his actual users hang out. Reddit and niche Facebook groups about travel + credit card points. The Facebook unlock: he found a group called “Rakuten Stacks” where thousands of people were manually hunting for offers his app already aggregated. He wrote a SQL query, dropped the spreadsheet (with a link back to SaveWise), and pulled 1,500+ visitors from a single post. The Reddit unlock: he lurked for weeks, posted in weekly Q&A threads in the comments only, built features users were literally asking for over 3.5 months, then DMed the mod for permission to do a top-level post. It blew up. Now SaveWise does $25K/month with ~1,500 paying customers - and 97% of revenue comes from a lifetime plan he only added because users emailed him begging not to subscribe. Takeaway: don’t market where founders are. Market where your customer already is, and earn the right to pitch by being useful first.
@wickedguro ·
Going to reach $120k MRR soon. But here is the thing, it's not exciting anymore. Yes, I know it sounds pretentious, but I definitely understand indie hackers who build many products. Because once you reach that number, it becomes a game of scaling, it's boring, and you know you can't create a new product because you will start losing revenue for your current product. So I guess, let the grind continue.
@andrewzacker ·
Just hit 1,900 followers 🎉 I started posting my build in public updates just 4 months ago, and: • Got accepted to the biggest indie event of the year - Hacker Residency • Found an AMAZING co-founder with 200K followers (@FlorinPop17) • Grew my first SaaS to $1k MRR INSANE what building in public can do to your life. Back to HARD WORK. Next goal: 3K followers and $10K MRR 💪
@Hartdrawss ·
this is NOT the time to chill and keep building features nobody asked for in your vibe coded app... you're holding the biggest leverage you'll ever get in your life — a $200/month AI stack that can research markets, find paying customers, and automate distribution in the time it takes you to deploy one useless feature (short of winning the lottery tomorrow) the window won't last so lock in on DISTRIBUTION, on getting your app in front of people who will actually pay, nothing else here are 5 plays with drastic impact on how much revenue your app makes: - run deep research on App Store top gainers in your category, find the ones with 3-star ratings, build the one feature their users are begging for in their reviews - scrape 500 people who commented "I wish there was an app for X" on Reddit or X, cross-reference with active threads, DM them a link to your beta with "built this because of your comment" - create a launch checklist that ships your app to Product Hunt, Hacker News, and 3 niche directories in the same week — launch day momentum compounds - hack App Store SEO by finding low-competition keywords your competitors ignore, stuff them in your title and subtitle, watch organic downloads trickle in - deploy a "build in public" thread on X showing your daily numbers (downloads, revenue, crash reports) — transparency converts lurkers into users pick one tomorrow. stop building. start selling.
@joncphillips ·
The fear of building another SaaS that nobody uses is quietly keeping me stuck. I’d rather brainstorm domains than validate ideas because brainstorming feels productive without any risk of rejection or failure. At some point I need to admit that the newsletters are the fucking business, and everything else is me trying to build something that feels more “legitimate” for no good reason. Like, there’s a weird shame in the indie hacker world about making money from newsletters instead of a SaaS. As if it doesn’t count somehow or whatever. $10k/mo profit from a few email newsletters is a solid business by any measure. Why does my brain refuse to accept that? *proceeds to buy one more domain.
@wickedguro ·
Postiz is on $159k MRR. I don't think you should build in public to get customers for your business in the traditional way: talk about your work and make a lifestyle video about your work. Usually, to make money, you need to give value. So if you build in public + teach really valuable stuff, it can work. A few years ago (same as digital nomadism), building in public was not something everybody could do; it was new, and people wanted to try it, so it had a lot of value for people who didn't build in public. Today, everyone is building in public on X, so it's less attractive. So for me: 1. I make money posts to grow engagement, reach, and authority. Don't worry, those posts usually bring no customers; they do tend to bring people who want to interview you, so it's nice. 2. Once a week, I will release a video with tons of value you can implement. 3. Work with other creators to produce valuable articles.
@LoganTGott ·
The best advice I've ever given to SaaS and AI founders? Build in public. Shipping a new feature? Post it. Hit a revenue milestone? Post it. Pivoted your entire offer? Post it. Got rejected by an investor? Post it. The ones who build in public always close deals faster, hire better, and raise easier.
@tibo_maker ·
I flew 10,000km to feel normal 👀 I live in a tiny town in France and the closest indie hacker is 3 hours away by car so I flew to Da Nang, Vietnam to live and work with other indie hackers for a few weeks and it's been amazing 🤩 I still love my remote + no-call policy, but being around sharp people in real life gives you a different kind of energy I just have so many new ideas now new rule: - default remote - but make in-person energy non-negotiable once in a while 🔥
@T_Zahil ·
10K€ MRR in a year and a half. Solo. In real estate. We're continuing the resident introductions for the Uneed Residency. Today: @Pauline_Cx ! Her main project, IACrea, is a marketing solution for real estate agents. And the track record speaks for itself: going from zero to that milestone as an indie is no small feat. Today, IACrea is mostly known in France and Belgium. The next step? Going international. And that's exactly why the residency comes at the right time: a full week surrounded by builders from all over Europe is a pretty good playground to rethink your growth strategy 😎. What she's coming for: connect with other indie hackers, learn as much as possible, and have fun building. And if you're wondering why Pauline has a solid instinct about platform dependency risks... She once launched a project built on the X API. Two days after launch, X announces the API is now paid-only: $42,000/month. There you go 😅. Lesson learned. More coming soon, we'll introduce all the residents before the residency kicks off 😊.
@kylegawley ·
Indie hackers launch loads of products because they're shit at talking to people If you talk to lots of people and build up a network you will learn where the real business problems are It's hard work and it's much easier to just launch a bunch of random stuff, post about it on X and pray BUT the hit rate will be very low because you are now dependant on blind luck for something to take off Get out of your room Get out of your head Go talk to real people with real problems Then you can solve a real problem for people and get customers Much better than launching startup #25 and asking Reddit how to get your first user for a product no-one asked for
@Layton_Gott ·
Building an audience as a solo dev is brutal… You block off Monday to write a week of posts. Then Tuesday hits. Prod breaks. A feature slips. The video you promised never gets filmed. Support emails pile up. You forget about posting for a week and a half. Now engagement is completely gone. So you go hard, write 5 posts in a row, they all flop, and you quit. Meanwhile a worse product is in your audience's feed every day. Here's how to build an audience without it eating your week: → batch posts in one Monday session every week, not 15 daily minutes of slop → voice-note ideas between coding sessions → turn one real bug fix into 5 posts → fix your bio before driving any traffic to it → schedule ahead, you won't post mid-debug → sound like you explaining something to a friend, not a thought leader → post real receipts, token costs, failures, screenshots → reply to your comments, that's where it compounds → double down on what's already working → build in public while you build the product The audience compounds before you ship. I’ve seen so many devs quit right before it would've started working if they would have done those things.
@victor_bigfield ·
your marketing plan as an indie hacker is probably "post on twitter and hope" mine was too. for 9 products. the one that actually worked? i went where people were already searching for a solution. not where other founders were posting screenshots of their dashboards reddit > twitter for early users. i'll die on this hill
@elgermerlo ·
For the first 6 months I was selling to indie hackers when my product was clearly built for small agency owners Same pain, completely different willingness to pay Indie hackers would say "cool" and churn after trial. Agency owners paid without blinking and asked for invoices The product didn't change. The customer did. That's where the revenue was hiding the whole time Next time I'm doing 20 customer calls before I write a single line of code — not to validate the idea, but to validate who actually has the money and urgency
@rcmisk ·
how to validate, build, and ship your indie SaaS (fast, with AI): first, i'd kill bad ideas early. use Claude to stress-test your assumptions before writing a line of code. scrape Reddit and X for real complaints in your niche. build a fake landing page. measure clicks, not compliments. if nobody opts in, nobody cares. then i'd ship something ugly but real. spin up an MVP with Cursor or Replit in a weekend. one pain, one fix, one CTA. no perfect branding. no waitlist theater. just a working thing people can poke at. post it publicly. let strangers break it. then i'd automate the distribution. use Claude to turn one insight into a thread, a post, and a short demo video. repurpose your build log into content. every "i just launched X" post is a lead magnet if you frame it right. document the process, not just the outcome. then i'd become a testing machine. ship 5+ hook variations per week. let the algo vote. what gets bookmarked, copy that pattern. what gets ignored, kill it fast. treat distribution like a product. iterate on it. and i'd drop a lead magnet every few weeks. a free tool, a public dataset, a template, a calculator. something useful enough to share. value compounds. vanity doesn't. then repurpose like crazy. one build becomes a tweet, a demo, a blog post, and a microsite. build once. distribute forever. AI lets one indie hacker do what used to take a team. but you still need to know who you're building for and why they'd care. that's how i'd launch a SaaS solo today.
@sandislonjsak ·
Most indie hackers don’t understand that after you build an app there must be someone doing customer support and regular maintenance/regression testing. Building an app that manages itself is super complex and only some of them can actually pull it off. Most of the thing I try from indie hackers is buggy and gets shutdown in a year, which is bad if you actually depend on it. Having a team behind you is much better than being a lone wolf. I am not saying “don’t go for it” and “they all suck”. I am just saying it’s super hard when an app actually becomes a success.
@rcmisk ·
here's the actual irony of indie building: most founders spend 90% of their time on the product and 10% on distribution. but the product can be rebuilt in 3 months. a real audience takes 3 years. you're optimizing for the thing that's replaceable and neglecting the thing that isn't. building in public isn't cringe. it's the only compounding asset most indie hackers have access to without a budget. every week you ship without talking about it publicly is a week of distribution you'll never get back. the founders who win aren't always the best builders. they're the ones who shipped AND shouted, consistently, before they had anything to prove.
@ybouane ·
The biggest lie in the Indie Hacker world: Product Hunt. Today I launched Clawly on Product Hunt… and it got 0 upvotes. Not because nobody saw it — but because nobody could. We like to think PH is merit-based, where the best products rise to the top. In reality, visibility comes first. And visibility is curated. Products featured early get the exposure → exposure drives upvotes → upvotes justify ranking. Everything else gets buried. That’s not a leaderboard. That’s a feedback loop. I’m building an alternative over the next few weeks — one where distribution isn’t gatekept. Stay tuned.
@nikita_builds ·
The great filter of startups is gone and I find it a little sad we used to be a niche group on the internet called indie-hackers (thank you @csallen) we would grind our asses off to ship half a page in a day, it was fun because no one could do it. We were alone. The cost to start something is basically 0 now The filter that used to kill ideas was effort. Now the filter is quality and distribution. We still live in a time where it matters to be semi-technical, enjoy it while it lasts my friends, soon it wont matter.
@kylegawley ·
Building a funded business is 10x easier than bootstrapping Unlike most indie hackers on here posting anti-VC tropes without ever having raised capital, I have raised funding in the past Let me tell you why it's easier so you can make an informed decision not based on clickbait tropes. > 1. Salary I got a salary on day one. I was not worrying about money, paying the bills, side hustles etc I was 100% focused on the business every single day from DAY ONE. > 2. Advertising We could spend money on ads, paying $10/click with a half baked funnel was no problem. Try doing that with your life savings. > 3. Talent We hired talent on day one, my co-founder and I were no longer doing everything and could focus on growing the business. Doing everything solo is a serious disadvantage when you're competing with well-funded companies and big teams. > 4. Clout Enterprise customers took us seriously because we had funding and a team. Big customers simply won't take a solo indie hacker as seriously and view the risks differently. People are going to reply to this saying the trade off is freedom having a boss - those people clearly have absolutely no idea how a company actually works.
@chhddavid ·
day 1: FINALLY ready to build in public (a vibe coding tool for non-devs) today I set two goals: 1/ get to $10k MRR (now it's $0) 2/ start building in public think I finally understand what it's all about: showing up, showing your face (!!), and sharing the good AND the bad, not just the wins. journey's heavily inspired by @robj3d3, @gus_tiffer, @thepatwalls, @SherryYanJiang, and virtually everyone else who shows up every day. (100% encouraging everyone to do it) —— let's start with today's updates then: 1. soft-launched on reddit and... WOW, a complete stranger said they want to pay for my tool 2. cold DM'ing + talking to warm leads via reddit 3. recording a PH launch video 4. well, started building in public ✅ I think that's enough for day 1. more updates coming soon
@sergeynazarovx ·
I don‘t really understand how indie hacking works when you have co-founders Products built by indie hackers rarely reach unicorn valuation or achieve a strong exit. In most cases, scaling a product to that level is extremely difficult without venture capital. Of course, exceptions exist, but they are very rare. Most indie hackers are trying to make a living from their products without focusing on an exit. During the journey, one of the co-founders could lose interest in the product or find a bigger opportunity. What happens if the product generates some money, let’s say $10k/month, and one of the co-founders decides to leave? In an ideal world, the other co-founders should buy out his share. But what if they don’t want to do it, or they don’t have that amount of money? These cases should probably be discussed and explicitly specified in the agreement between the founders. But does it really happen?
@victor_bigfield ·
hot take: the best thing that happened to me was failing 3 times before making $1. most indie hackers ship once, it flops, and they quit. i shipped LearnFast and nobody came. i shipped YTFinder and nobody stayed. i shipped The Visual Hackademy and made some money but couldn't scale. by the time i built RedditGrow i already knew what a bad landing page looked like because i made 3 of them. i knew what no distribution felt like because i lived it for years. all that failure is the reason RedditGrow works. and now i'm building another one. DojoSales. a cold call training tool for french sales reps who want to practice their english pitch and close US deals. people keep asking me why i'd start something new when RedditGrow is working. because that's literally the point. RedditGrow taught me how to build something people actually want. now i get to do it again, faster, with all the scar tissue from the first 4 attempts. i didn't get smarter. i just ran out of ways to mess it up. and apparently that makes you want to build more, not less.
@HyperSalesman ·
Last year I got scammed by DocuSign. Woke up to my renewal jumping from $100 to $300 for the same garbage e-signature tool. Went on X to complain about it. @christomitov messaged me saying he'd built an alternative. We met. I fell in love with the product. He asked me to be a co-founder. Within one month we had 300+ signups. Just through organic content on LinkedIn and X. (The tool is still live today. People still use it. It's called https://t.co/7ldGTwxlh2 and it's completely free). Here's the playbook we used that works for any SaaS, even vibe-coded ones: Step 1: Pick your fight - Find an incumbent that's overcharging or underdelivering - Make them the villain in your story - Anger is the most shareable emotion Step 2: Build in public from day one - Share screenshots, struggles, small wins - People root for underdogs they watch grow - Your journey is the marketing Step 3: Post where your customers already complain - Search Twitter for "[competitor] sucks" or "[competitor] pricing" - Those people are pre-qualified leads - Reply with value, not pitches Step 4: Make your co-founder your content partner - One person builds, one person posts - Trade off based on energy and bandwidth - Two voices reach two audiences Step 5: Give it away first - Free users become your evangelists - Word of mouth beats ad spend every time - Monetize after you have momentum The bigger lesson here is about where software is heading. Anything that can be easily recreated will be recreated. DocuSign's stock is tanking for a reason. "We were here first" means nothing when a solo dev can ship a competitor in a weekend. This is the indie hacker moment. The tools are free. The distribution is free. The only cost is your time and willingness to post. Christo and I both got busy and moved on to other priorities. But the project lives on. That's the beauty of building something real and putting it out there. So feel free to check it out ✌️
@MakadiaHarsh ·
patterns in the work of builders who actually ship if you study enough founders, indie hackers, client projects - you start to see the same structures repeat. different stacks, same blueprint. here's what separates builders who ship from those who stay stuck: 1. a season of ugly work no audience. no validation. just you, a code editor, and problems nobody else cared about. that's where the real skill compounds. 2. one painful client or project something broke badly. deadline missed, scope exploded, client unhappy. instead of quitting, they built a system around it. that failure became their process. 3. obsessive simplification they don't add more features. they cut until the thing works. every sharp builder has a graveyard of over-engineered v1s nobody saw. 4. distrust of complexity they question the "standard" stack, the popular framework, the bloated tool. not to be contrarian - to ship faster. they rebuild the workflow leaner. 5. constraint as clarity limited time, limited budget, limited team. instead of complaining, they use it. constraints force the decisions that matter. 6. systems over heroics they stop solving the same problem twice. templates, automation, repeatable flows. the work gets faster without getting worse. 7. public proof they document what they built and why. not for clout - for trust. that's what turns a builder into someone clients seek out. shipping isn't luck. it's a pattern - repeated by different people, with different stacks, under different deadlines. once you see it, you can't unsee it. which part of this pattern are you in right now?
@bmykhaylivvv ·
built amplifresh to scratch my own itch - needed better social media automation for my side projects shipped mvp in 2 weeks, now sitting at $500 mrr with 47 paying customers the twitter growth was unexpected but posting daily about building in public really works most users found me through indie hacker communities and word of mouth referrals revenue breakdown: 23 pro plans at $19/mo, 24 starter plans at $9/mo biggest lesson learned - solve your own problem first, then find others with the same pain next milestone is hitting $1k mrr by end of q1, already have the feature roadmap planned the hardest part wasn't coding but learning to price correctly and talk to customers going from 50 to 2000 twitter followers happened mostly from sharing revenue screenshots and build logs amplifresh basically automates content distribution across multiple social platforms with smart scheduling
Best Tweets by Topic
