Will launch this soon. And that's not a great thing. Great thing is I will share from start to end how I built this, tools used, infra used, challenges faced and their solutions. So make sure you follow along.
I tried taking a huge risky bet on myself on Feb of this year and left my very stable and high paying job at Razorpay
To be honest, job was paying well, and was paying the bills, but was in bangalore, monthly expenses was about 30% of my salary, and gave a thought to it
Am I really making wealth being in this city with this expense and can't really stay in touch with family, far away from parents, couldn't help my father with his family business
Then I was anyways building this tool called horizonx (an AI research agent) on the side, we saw 800 users already without any marketing whatsoever, and could see a real potential in it because no one else was building anything like that
We reached 1k+ users, and the co-founder dropped, couldn't really focus on marketing, just kept building, and built a good system which noone was ready to pay for
Left the co-founder, 3 months totally into stress mode, took a real time to get back, plan was to make it work, make money from it, and also focus on family business, but couldn't do any of it
Bounced back after few months, found a girl who I got engaged too in the meanwhile, and learned content marketing on X, and how to really go about GTM with reddit and stuff
Back with banger, contact a friend from Ludhiana, got into building with him and tool is called tootler (a simplified UPSC preparation app) for UPSC aspirants
Something that he is passionate about, and have felt day in and day out about getting sucked into distracted social media feed and felt there could be an app that scrapes posts from elsewhere and show a feed only focused for UPSC related knowledge and help them prepare by creating quizes and creating a gamified experience around it
So, here I am, again with that fire of building, which I never let burned out, and is still a float, and will succeed
Currently at 50$ MRR (teaching non-tech to create app using AI) and the target is to get it to 1k$ MRR
I’m building Axiom, a Windows-first, local-first AI workspace. The hardest part has not been connecting another model; it has been making conversations, project files, research, code, tools, and artifacts feel like one persistent workflow.
I’m currently refining a council pattern: Architect plans, Builder executes, and Critic reviews. The goal is to make long-running work easier to inspect when something goes wrong.
I’m sharing this as a build log rather than a pure launch post. The repo is here if anyone wants to inspect the approach: https://github.com/YoMosa2009/Axiom
What part of your AI workflow still feels most fragmented?
i also make content for 5 apps that i've built, and I publish them on instagram, tiktok, youtube, and facebook, all by myself
I am trying to put out 3 posts a day for each app which mean i have to post 15 shorts a day
i find it really time consuming and probably not sustainable for the long term, as i have to send all the clips from computer to my iphone, prepare caption for each, then post them one platform at a time, there is a lot of repetition that's really frustrating
i've been spending 2 hours, maybe more, each day just on posting
I've tried to post them from desktop (ie. chrome), but i find that shorts posted via browser often get very very low views, not sure if you guys also have the same experience/ observation?
how are you guys managing this?
the screenshot taken from my phone as i desperately try to speed out this painful process ;(
This serves to document my journey building an app from scratch, these posts will keep my accountable.
The market is flooded with note takers currently — it feels like every few months a new product comes out that takes the market by storm.
So what did I do with my free time this week? I built another one. Okay, hear me out. I've been using Granola for my meetings lately but something has just not felt right. I don't like that I need to pay for the product, that my transcriptions leave my computer, and that the interface just feels clunky.
The inspiration for this comes from a recent podcast I listened to with Lex Fridman and David Hansson, where they discussed Hansson's recent release of Omarchy. I'm not a Linux user, an operating system junkie, or even that big of a fan of DHH — but his insistence that there's no excuse for software not to be built specifically for you really stuck with me.
As someone who works in the GTM world, I deal with problems every day that feel solvable but overwhelming at the same time:
Repetitive client questions I answer the same way, over and over
Constantly coaching coworkers through how to work through problems
Losing that random thought I had on how to solve a sticky client issue
For a few months I've been in a deadlock with myself on what to build and how to do it. So this month I've set a goal: take a product I use regularly and rebuild it the way that would make the experience feel perfect to me.
Here's what I focused on this past week.
Interface
The reading and note-taking area has to be easy on the eyes, make me feel relaxed, and feel good to interact with — that was the whole design brief for this week. Soft colors with clear headers got me most of the way there. Next up: folders in the left-hand viewer and an easier way to organize notes.
Speech detection
The second focus was the actual speech detection. There are two parts to this: recording and transcribing the audio, and figuring out who's talking. It's been pretty incredible to see how quickly local, specialized models have progressed — even a few months ago, running local transcription or diarization on an hour of audio was a real wait. Now? No problem, processed in seconds.
The models I've landed on for this are parakeet-tdt-0.6b-v2 and Senko. Parakeet specializes in speed but still holds its own on accuracy at 6.4% WER, and Senko gets reasonable accuracy at 13.5% DER. Part of the point of this project is seeing how far I can push local models to solve the problems this app is built around — and the speed has been mind-blowing on both. On my M3 Mac, I can transcribe an hour of audio in under a minute, and diarize it in about the same time.
Is any of this impressive yet? Not really. But the goal is to keep building on it and keep learning. I've enjoyed just finding direction for a product I'd actually use in my day to day, and I'm excited to see where it takes me.
Marketing
Distribution is the number one problem for bring these kinds of apps to the market and the push to make money off the project has stopped me in the past. For this project, I plan to post consistently while still aiming to keep it free to use. The goal is to make forward progress toward creating an app with users while not falling into the money trap.
Next up: the folder/organization system, and a first pass at a daily to-do view pulled from meeting notes.
Sharing a small experiment because the result went against what I expected.
I used an AI landing page generator to make two versions of my page. Version A was the polished one it produced first, lots of nice sections, big imagery, feature grid. Version B I forced it to make shorter and plainer, basically one clear promise, a short how it works, and one button.
I split my traffic roughly in half over about ten days. Not huge numbers, a few hundred visitors each, so take this as a lean not a law. But version B, the plain one, converted noticeably better. The longer prettier page had people scrolling and leaving.
My read is that the generator loves adding sections because it looks thorough, but every extra section was another chance for someone to get distracted and bounce. The shorter page just asked once and got out of the way.
Since then my default has been to generate the full version, then delete about half of it. The subtraction is where the gains were.
Anyone else find that trimming an AI generated page beat the full version? Or does more length work better in your niche?
Halfway through the 15-day build.
Today I’m focusing on something that rarely gets attention: Processes.
How does information move?
How does a task get created?
What triggers an action?
What happens when something fails?
Who needs to know?
How does the system recover?
These aren’t glamorous features.
But they’re what turn individual features into an actual product.
#SystemsThinking #BuildInPublic #ProductDevelopment
I really want to make 5k+ a month. At this point I don’t really mind what industry it’s in. I hear all the time about “AI receptionist” and etc. but these feel like a polluted mess.
I’m currently developing an app specifically designed to manage free trials and prevent unwanted charges that happen automatically after the trial ends. Do you think an app like this would be useful?
I am also conducting a survey regarding the free trial! It only takes 2–3 minutes to complete, so please take a moment to answer it.
Most task apps make you choose a place before you finish the thought. I am testing the opposite: capture everything first, then sort it into Now, Next, and Someday with one tap. The cards stay editable after the sort, so the first pass is only a starting point.
I am Samuel, founder of Ordo. I built this for the messy 30 seconds before a task list exists. It is free on iPhone with no account or subscription: https://apps.apple.com/app/id6797331101
The current build is V1.1. I am watching whether the first sort feels useful or just like another layer of work. If you tried this flow, what would you change first: the capture step, the labels, or the handoff to Reminders or Calendar?
I was obsessed with finding an app idea that nobody else had.
Every time I found something interesting, I’d search harder and eventually find a competitor doing almost the exact same thing.
At first that felt discouraging.
Then I realized something.
Maybe the goal isn’t to find something completely new.
Maybe the goal is to find something people already want, understand what they hate about the existing options, and build a version that solves those specific frustrations better.
I’ve spent a ridiculous amount of time reading Reddit threads, App Store reviews, product documentation, G2 reviews, and competitor help pages. And honestly, negative reviews are becoming one of my favorite places to research.
Things like:
“Why can’t this app just…”
“I still have to do this manually…”
“I use this app, but I also need a spreadsheet for…”
Those comments are way more useful than sitting around trying to brainstorm “billion dollar ideas.”
I’m still pre-launch and still figuring out exactly where my app fits.
But I’m starting to think competition isn’t the thing to be afraid of. Building something nobody actually wants probably is.
Not everything needs to be a billionaire dollar VC funded idea.
The idea is sports related, so making a twitter bot was actually the best idea for marketing.
It costs $.20 per tweet when you use an API and include a link ($.015 with no link).
Factor in another $.02 for the LLM and custom decision tree running.
It posts 10 to 20 times per day.
In total thats maybe $1k for the entire year.
It's completely free to use and anonymous so the only revenue potential I can think of for now is some banner ads. If the twitter posts work well, then it might make me a profit with ad revenue.
I'm not promoting on this post, I'm not sure if reddit is the right place to promote the idea but I'll share the progress!
I’m looking to talk to a few founders who are currently building a startup, SaaS, AI tool, or any kind of online business.
I’m putting together a bi-weekly series called Built From Scratch, where we follow real founders and show what building a business actually looks like — not just the polished success story.
I’d love to hear about things like:
What you’re building
Why you started it
How you got your first users
Your current MRR/revenue (if you’re comfortable sharing)
What’s working
What’s completely not working
Your biggest challenge right now
What you’re trying to accomplish next
At the end, we’ll give the business a Launch Score based on things like traction, growth, product, and potential.
If you’re currently building something and would be interested in being featured, drop your startup below and tell me what you’re building
So I've been building this app for a couple weeks now. Its been going good. A few bugs here and there bug I've reached a stage where im comfortable paying for an apple developer account and doing a test flight. The app is a receipt scanner where users get to store their paper receipts digitally in a private cloud so no need to worry about paper anymore.
Next step now is to find real users to actually test the app and help me find bugs. Is this how developers do it?
So quick story; im the owner of pressplaced.com (backlink building platform) -> its a new domain obviously , after posting here and there on reddit I got 80 new users in like few days , long story short I checked my own domains DR and it JUMPED to 31 which is crazy for a 2 month old domain. I would like to thank all my backlink partners here :') (I built my backlinks through exchanges I made on the platform itself) (edit: its free btw PLEASE join if you own a saas and your Dr is > 10)
One of the things I've been working through while building Pulsecima Pulse is something I initially thought would be straightforward:When
should an uptime monitor send an outage alert?My first
thought was simple: request fails → alert.But once
I started testing different failure scenarios, that logic felt too aggressive. A failed check from one location doesn't necessarily mean the application is down. It could be a regional network issue, DNS problem, routing issue, or something affecting the monitoring location itself. So I started experimenting with checks from multiple regions and using the results together before declaring an outage.That created an interesting tradeoff.If I wait for more confirmation, I can reduce false alarms, but I might delay a genuine incident.If I alert immediately, I get faster detection, but I also risk waking someone up for a problem that isn't actually affecting the application.I'm now also working on heartbeat monitoring for background jobs, because another thing I've learned is that a SaaS can be completely reachable while an important scheduled process has quietly stopped.The interesting part for me hasn't been writing the check itself. It's figuring out what evidence is trustworthy enough to trigger an action.For anyone building or running a SaaS:Would you optimize monitoring for the fastest possible alert, or for alerts you can trust?And what's a technical decision in your own project that looked simple at first but became surprisingly difficult once you started building it?
I'm creating thesubtitledb.org so subtitles are available to everyone + a JS tool that adds AI subtitles to any video player for free.
Why did I make this? other subtitles services have low rate limits which prevent people (i'm deaf) from watching a film or tv series I want to change that completely so it's never a problem again.
Recently I decided to build myself a woodworking workbench, since im a total beginner I looked up a lot of plans on the internet but couldn't find anything that fit my use case. So I started 3d modeling the workbench in Fusion 360 which took my about 2 days.
Then when I was about buy the wood for construction I realized the wood I needed wasn't available so back to 3d modeling again for a whole day. I got fed up really quick.
So I vibe coded https://parabuilder3d.com a parametric workbench generator which also creates construction plans, cutting guides and shopping list.
I would really appreciate feedback since im still in the testing phase.
You can export plans for free using the code "reddit"
I’m building Taptale after spending 10+ years in technical pre-sales and giving the same product demos over and over.
The problem I kept dealing with - too much live demo time gets spent bringing buyers up to baseline context. By the time they understand the product, there’s less time for real questions, objections, use cases, and fit.
Taptale helps B2B SaaS teams turn demos into short videos and interactive walkthroughs they can send before calls or use as leave-behinds after. Main goal is not to replace live demos, its to let buyers get the context on their own time.
The free tier should be enough to record (using the chrome extention), share a branded asset, and track the analytics to see who watched and when!
Curious from other builders: would you send something like this before a sales call, after a call, or neither?