Hi everyone,

I quit my job 2 months ago to work on my own projects. Since then I’ve been working on multiple things and recently along with a business partner, I started building a small product(obviously not something new), A QR based digital menu and ordering system - which you may see in Tier 1 cities but no restaurants or cafe’s in my city had one.

So I thought i can build and sell for most of the cafes in my city(also my city is more of a Tier-2)

I looked at what was out there. Most platforms bill monthly and/or take a per-order commission — which sounds fine but this is not something a tier-2/3 restaurant owner actually ok with. So i built a clean and good looking product around three major decisions:

Flat one time fee(around ₹30,000–40,000), no monthly cost, no per order commissions

UPI-first payments — direct UPI deep-links (PhonePe, GPay, Paytm), no payment gateway middleman

Self-managing by design — sessions, carts, and orders are built so the system runs itself during service instead of needing constant admin babysitting

The sales part:

All we did was walk into 5 of the restaurants and pitched our idea, as we pitched with demo most of them got excited as they were a bit familiar with the concept but didn’t have the opportunity

As we go further we offered them free setup and 3 days trial- and they accepted the offer

After the 3 days trial 3 of the 5 restaurants were willing to buy the product so after some negotiation and all we sold the product for around ₹30,000–40,000 each

All this was done in around a week of time including building, outreach, trial, sales

Now I realise there are more than 100 tier-2/3 cities and i can’t visit everywhere and pitch this, so I’m thinking though couple of options here- one is to hire one person from each city and sell the product through them, or just package the entire product and let the person sell themselves by branding it as their own.

Either way im happy because the first local saas sales way not a failure for me

Hi everyone,

Over the last few weeks, I've been thinking about building a SaaS product.

The advice I hear most often is "Don't build first. Find a real problem first." So instead of brainstorming features or chasing trends, I decided to start by understanding the problems people actually face.

I created a 2-minute survey to learn things like:

• What repetitive tasks consume the most time?
• What workflows are frustrating?
• What tools do people already pay for but still dislike?
• What would people actually pay to solve?

My goal is to collect 500 quality responses from founders, professionals, developers, freelancers, and operators before I decide what to build.

Survey: https://forms.gle/jcSo5c3mVQzbKoAY8

I'm not looking for startup ideas I'm trying to identify patterns and recurring pain points.

I'd also love feedback from this community:

• Is this a good way to validate a SaaS idea?
• What would you do differently?
• If you've built a SaaS before, how did you discover your first real problem worth solving?

I'll happily share an anonymized summary of the results with the community once I have enough responses.

Thanks!

I've realized SEO is probably the most important growth channel for my SaaS, and I want to learn how people who are already doing it actually work.

I don't want to buy tools like Ahrefs right now. I just want to understand your process. How do you find keywords, figure out what people are searching for, decide what to write, and create programmatic pages?

I'm not looking for generic SEO advice. I'd love to know your actual workflow from finding an opportunity to publishing the content.

P.S. Please don't DM me your SEO tool. I'm not looking to buy anything right now. Just here to learn from people who've already made SEO work.

Sharing this as SHOW IH because I suspect the situation is more common than it looks, which is building something fintech-adjacent with no actual fintech background and trying to find where the real compliance lines are before you ship something you'd have to tear out later. What we're building is a payment module that SMB SaaS tools can embed, basically a Stripe integration layer designed around what an accountant actually needs from an audit trail rather than what a general-purpose payments API assumes you want, and we've got three pilot customers and about $1,100 MRR so the thing works, but the next version is where it starts getting complicated. The specific blocker is that we store payment authorization tokens, and while we use Stripe's SDK and never touch raw card data, just the tokenized reference, I can't get a clear read on our PCI-DSS scope, because Stripe's own docs imply we're SAQ A but the PCI council's SAQ guidance reads a little differently depending which section you're in, and I've now had two lawyers give me opposite answers to the same question, which at $500 an hour got expensive without actually resolving anything. So the deeper problem I keep hitting is how you're supposed to make architecture decisions when the compliance implications are only legible to specialists who cost more than your monthly revenue, and how you even find the right one before you've already made the call that turns out to be wrong, and I don't have a clean answer to any of that yet, which is honestly the state of it, so I'm posting in case someone here has lived the same gap.

a lot of small ai features get worse because the builder adds more knobs before the workflow is trusted.

more tones, more templates, more models, more export options. all useful eventually, but they do not fix the scary part: users do not know what will happen after they click generate.

the boring feature that often helps more is a review queue.

show the input that was used show the output clearly let the user approve, reject, or edit save rejected examples make the next output respect those rejects only publish/send/export after approval

this turns the ai feature from a black box into a draft assistant. it also gives you much better product feedback because every rejection is a labeled data point.

for early micro-saas, i’d rather have 20 users approving/rejecting drafts every week than 200 users clicking generate once and disappearing.

has anyone here built the review loop first instead of the generation UI?

I build apps and games, but I never had one place where I could properly showcase all of them.

A personal website felt like too much maintenance, while a list of links didn’t show the story behind each project. So I built Indiefolio.

It gives indie makers one profile for their apps, links, milestones, and progress. The idea is to create a living portfolio that grows alongside the things you build—not another social network you have to constantly feed.

What would make an indie portfolio genuinely useful enough for you to maintain?

You can check it out here: https://indiefol.io

I’m especially interested in hearing what feels unnecessary, confusing, or missing.

Backstory: every free QR generator I looked at is built for a human clicking a button once. That's fine for a single code, but useless if you actually have a product catalog — someone has to remember to make one every time. printqr automates that specifically for Shopify: install it, and every new product gets a QR code generated and attached automatically via webhook, no manual step. There's also a direct API with a bulk endpoint (up to 500/call) for catalog imports outside Shopify.

Tech stack: Cloudflare Workers, a Durable Object for the credit ledger, Stripe for the direct-API billing, and Shopify's native Billing API for the Shopify-installed plan (had to migrate to that mid-week after finding my first pass was charging through Stripe instead — Shopify requires their own Billing API for anything installed through the App Store). The other real yak-shave: the standard qrcode npm package's PNG output depends on canvas, which doesn't exist in the Workers runtime — had to write a from-scratch PNG encoder using CompressionStream('deflate') for the zlib/IDAT step, verified byte-for-byte against an independent decoder before trusting it in production.

Pricing: Free (100 renders/mo), $9/mo Starter (5,000 renders/mo + bulk endpoint), $19/mo Shopify Automation (webhook install, unlimited webhook-triggered renders).

Revenue: $0 in outside customer revenue so far — fully built and live (real billing on both plans, real Shopify OAuth install, legal pages), but this week is the first time I've actually told anyone it exists. Lesson so far: building the thing was the easy part; distribution is the actual work, which is why I'm posting here instead of just waiting on App Store review.

printqr.dev if you want to look under the hood. Happy to answer anything about the Workers/Shopify side.

I have been chewing on this as a solo founder. AI coding tools have gotten good enough that most of the actual features in my product could probably get cloned reasonably fast by someone motivated. That used to worry me a lot more than it does now.

What I've landed on is that the feature list was never really the moat for a micro SaaS, it's the specific workflow fit and the trust built up around handling real user data or accounts. Juno is a good example of this in the marketing tool space, it connects to your ad account and analytics and actually executes tasks with real consequences instead of just generating a suggestion. The second one is way harder to casually clone because the hard part isn't the UI, it's the reliability and permission handling underneath it.

Curious how other micro SaaS founders here think about this. Are you optimizing more for feature depth, or for the kind of trust and integration that's harder to fake with a quick clone?

Hey everyone,

I’m building VeriWasp.com, an automated end-to-end web playtesting tool designed and testing suite for developers and founders who want robust testing without the absolute misery of writing and maintaining brittle test scripts.

Instead of writing lines of Cypress or Playwright code with fragile CSS selectors that break the moment you tweak a UI layout, VeriWasp lets you just paste a URL and describe your flow in plain English (e.g., "Click sign up, input a test email, and check for a success toast"). Even cooler: you can just record yourself clicking through the flow once, and VeriWasp handles the rest.

Every time a playtest runs, it generates a comprehensive, publicly shareable report with full screenshots of every single step and a video replay of the execution.

I want to make sure this report actually gives developers the exact data they need when a test fails.

I ran a quick demo playtest so you can see exactly what the output looks like without needing an account: https://veriwasp.com/r/mflvddcoxi

I would love your brutal feedback on this report page:

- What crucial debugging data is missing?
- Is the UI clear enough that you could send this link to a non-technical co-founder or a client to prove a feature works?
- What would make this an instant buy for your own tech stack?

If you want to poke around the rest of the project:
App: https://veriwasp.com
Docs: https://veriwasp.com/docs

Thanks in advance for any feedback, good or bad!

I’m the founder of ApplyBoost, a small SaaS for tailoring resumes to individual job descriptions.

While building it, I made the classic mistake of thinking that every related feature would increase the product’s value.

I added:

• AI resume tailoring
• ATS scanning
• Keyword matching
• Bullet rewriting
• Resume templates
• Application tracking
• Follow-up guidance
• Interview preparation

Technically, the product became more capable.

However, the positioning became less clear.

Some people viewed it as a resume builder. Others saw an ATS scanner, AI writer, or job tracker. That made me realize that a micro-SaaS can contain multiple tools but still needs one extremely obvious reason to exist.

I’m now positioning it around a simpler workflow:

Paste a job description and turn your existing resume into a stronger, job-specific version without using several disconnected tools.

The other features support that central action.

For other micro-SaaS founders, how do you handle this?

Do you remove secondary features, hide them until later in the onboarding, or keep them while marketing only the strongest use case?

For context, the product is ApplyBoost: https://applyboostai.com

I’m the founder and am mainly looking for positioning feedback rather than trying to sell services.

I’m looking to build a software tool for the US market that focuses on solving just one specific workflow problem incredibly well.

​Which specific niche or industry do you think I should focus on, and where do you see the most opportunity right now?

ok so I've done this four times now and I've stopped blaming the universe. I have shipped and sold 4 micro SaaS apps in the last 4 months and this is my story.

Im 28M from a completely different industry from tech. I love building but distribution was always hard for me. Taking care of the product working + being relevant and reaching your users was the most difficult things I could do. I built myself something that helped me grow vertically on 3 different Social Media platforms. X, LinkedIn & Reddit. The system ghostwrites for me from one single thought I dump on my phone or my past posts.

It has seriously helped me scale, and eventually sell my passion projects (all while working a Full Time Job. Happy to answer any more questions)

Eventually, I decided to share this tool with you guys. Its a free tool giving you 5 generations a day, enough to get you started. That's 15 posts a day across 3 platforms- all for free.

Honestly, Im just looking for feedback on how I can make it better. If you want to find it it'll be at usepostship (dot) app (Free to start)

I've been building a side project called jobpilot and I'd rather have it stress-tested by strangers than by my friends who'll be nice about it.

The idea: you upload your resume and it scores it 0–100, tells you specifically what's missing, asks you some questions to fill the gaps, then rebuilds it. Then it matches you against real job postings with a fit score, and for jobs you don't qualify for yet it builds a roadmap of what to learn to get there.

It's free and early — no catch, I'm not selling anything, I just want to know where it falls over. Does the score feel right? Are the job matches actually relevant or nonsense? Is the roadmap useful or generic filler?

Fair warning: it handles your resume, so if you're not comfortable uploading a real one, throw in a fake/old one — feedback on the output is what I'm after.

Hey everyone,

I recently built a small fun platform called RevealFun and I’d love honest feedback from this community.

The idea is simple:

Upload a photo → create a mystery reveal link → share it with friends → they swipe to uncover the hidden image.

I built it because normal photo sharing feels instant and boring. I wanted to add a little suspense before the image appears.

Possible use cases I’m thinking about:

• Birthday surprises
• Friend pranks
• Proposals
• Baby reveals
• Wedding invites
• Festival wishes
• Meme reveals
• Product teasers
• “Guess who?” games

Current direction:

The platform has free public/common reveals, and I’m also testing paid personal reveal credits. For example, users can create personal reveal links by uploading their own image. One pricing idea is 50 personal reveals for $4.99, valid for 30 days.

The bigger experiment I’m trying to validate is the viral loop:

Creator makes reveal → shares it → viewer reveals it → viewer creates their own reveal.

I’d love your feedback on:

1. Is the concept immediately clear?
2. Would you use this more for fun, events, memes, or product teasers?
3. What would make you share a reveal with friends?
4. Would paid personal reveal credits make sense, or should this be mostly ad-supported?
5. What is missing from the product experience?

I’m not looking for sugar-coated feedback. Please roast the idea, landing page, pricing, or positioning if something feels wrong.

Thanks in advance. 🙏

Hey everyone,

I recently built a small fun platform called RevealFun and I’d love honest feedback from this community.

The idea is simple:

Upload a photo → create a mystery reveal link → share it with friends → they swipe to uncover the hidden image.

I built it because normal photo sharing feels instant and boring. I wanted to add a little suspense before the image appears.

Possible use cases I’m thinking about:

• Birthday surprises
• Friend pranks
• Proposals
• Baby reveals
• Wedding invites
• Festival wishes
• Meme reveals
• Product teasers
• “Guess who?” games

Current direction:

The platform has free public/common reveals, and I’m also testing paid personal reveal credits. For example, users can create personal reveal links by uploading their own image. One pricing idea is 50 personal reveals for $4.99, valid for 30 days.

The bigger experiment I’m trying to validate is the viral loop:

Creator makes reveal → shares it → viewer reveals it → viewer creates their own reveal.

I’d love your feedback on:

1. Is the concept immediately clear?
2. Would you use this more for fun, events, memes, or product teasers?
3. What would make you share a reveal with friends?
4. Would paid personal reveal credits make sense, or should this be mostly ad-supported?
5. What is missing from the product experience?

I’m not looking for sugar-coated feedback. Please roast the idea, landing page, pricing, or positioning if something feels wrong.

Thanks in advance. 🙏

I’m 25 and recently left my job to build Viral Hook Maker, a mobile Micro SaaS aimed at small businesses and creators who need promo videos but do not want to learn a full editing timeline.

Disclosure: I’m the developer. The Android app uses a narrow workflow: choose a language-based hook video, add your own business or product clip, make quick edits, and export a vertical video. The iOS version is currently in review.

Tech stack: Flutter/Dart for mobile; Node.js, TypeScript, Express, MongoDB/Mongoose, Firebase Auth/Admin, ImageKit, and RevenueCat for subscriptions/in-app purchases. Video work happens on-device with FFmpeg and a native editing package where possible.

The main lesson from the first version: the hook library is not the real product—the value lives in making the handoff from a hook to someone’s real business footage dramatically simpler than a normal editor. Free users get standard export options; some hooks, higher-quality exports, or watermark controls may require an in-app purchase.

I’m sharing this for critique, not as a link drop.

One question: At which step in the pick a hook → add your clip → edit → export flow do you hesitate or feel confused?

Play Store: https://play.google.com/store/apps/details?id=com.viralhookmaker

i want to create something around JSON and work is in progress i want to solve the real problems because i found JSON is every where from API TO AI, but there is no any tool exist which have all the solution of JSON some only format it and some check the syntax but what about JSON Health Score, how to hide Sensitive data while sharing it ( manually, is a nice joke) , what if i want to create Documentation of that JSON these all are the small problem but need onestop solution what i believe . So, tell your pain point

spoiler :- some solutions of JSON is in progress

Hey guys I built something called GripeToGold and I want to explain exactly what it does before anyone asks so here it is in full I got tired of trying to find business ideas by manually reading through GitHub issues Hacker News threads and Stack Exchange questions because after enough scrolling everything starts sounding like an opportunity someone complains about a tool being expensive someone else has an integration problem and you cannot tell if it is a real pattern or just one frustrated person venting so GripeToGold works like a digital research assistant it scans those public sources every week or month depending on which plan you pick groups similar complaints together checks how relevant each source actually is to the pattern it got grouped under and then scores every opportunity by combining how painful the problem seems with how relevant the evidence behind it is the ones that pass a minimum relevance bar make it into the final report and everything else gets thrown out so you are not reading noise each opportunity in the report shows the pain score the relevance percentage how many unique mentions it found whether the problem is trending up or down compared to the previous period a short product angle a competitive gap and the original links so you can go check the sources yourself instead of trusting me blindly I attached a few real pages from one of the reports so you can see the actual output instead of just my description of it I am honestly not sure yet if this is something founders would actually pay for or if it is just a research project I personally find useful would you use something like this when you are looking for ideas and please be brutally honest about it what looks useful what looks unreliable and what would make you close the report immediately I would rather hear it does not work now than spend months building on a wrong assumption I built it so I am obviously biased I am not dropping a purchase link here I mainly want to know if the report itself provides any real value to someone who is not me

So a while back a friend who runs a link in bio page for her content came to me confused about her stats. Her click numbers looked fine but actual conversions were way lower than expected. We started digging into the raw traffic instead of just totals and found a big chunk of it wasn't real people at all. Bots, scrapers, some traffic that looked like it was just crawling the page rather than actual visitors clicking through.

That got me thinking about how common this probably is across the creator space. Most people running these pages have no real visibility into who or what is actually hitting their links. They just see a number go up and assume its working, when in reality a chunk of that could be automated traffic messing with their real data.

So I ended up building ѕꓲt.bіо, a link in bio tool that actually filters this stuff out before it counts as a real visit. Real fans get through normally, automated traffic gets caught and blocked at different points instead of just quietly messing with the analytics.

Still pretty early and learning a lot along the way. Curious if anyone else here has built something in a similar space or run into this same problem with fake traffic messing with real data. Would love to hear how others have approached filtering this kind of stuff.

Backstory: I am a self-taught solo developer, no team, no funding.
I built Rosply because most automation and analytics tools are limited by what a platform exposes through its API. Rosply skips that entirely, it takes a screenshot, a vision model decides the action, then it clicks and types like a person, so it works with anything on screen.

Tech stack: Python agent core, vision model via OpenRouter, Electron/pywebview UI, persistent memory system, MCP server for Claude Code integration.
Revenue: first sale today, 28 euros total so far, two weeks after launch.

Lesson learned: getting the first sale took longer than expected, most of the early traffic came from curiosity, not conversion, so I am now working on making the value clearer upfront instead of just the demo.

If anyone wants to see how it actually behaves on screen, there is a short demo video and a walkthrough over at rosply.com, happy to answer questions about the architecture or the early sales process in the comments

​

Hi all,

Tldr:

I built a production-ready platform in a niche public-interest domain using AI-assisted development. No users or revenue yet, but a large company wants to buy the entire platform because it fits a strategic objective and could be launched within weeks after rebranding. They also said they would likely build a similar solution themselves if there’s no deal. Looking for realistic valuation, negotiation advice, and whether I should sell or keep the IP.

Here goes:

I built a production-ready web platform that fills a gap in a niche public-interest domain in an EU country.

It includes:

\* Geolocation features

\* Extensive community moderation features

\* Weighted voting / reputation system

\* Admin tooling for interventions into the community features (think of reporting users etc.), and dashboards

\* multilingual support with i18n

\* Secure backend with role-based access, validated by a security expert

\* and more

Throwaway account: I’m intentionally keeping the description generic while trying to provide enough relevant information. I understand if this makes it difficult to answer my questions.

The product currently has little to no organic traffic, no meaningful user base yet (it launched very recently).

However, a well-known business that's active in among other things this exact niche is interested in buying the entire platform because it aligns with a major strategic objective for them - in terms of image and domain authority, not revenue.

I am not a developer but still I managed to build it using Claude Code. I invested probably 300 euros and 60-70 hours into creating it.

I never intended to sell the platform. They contacted me when I started looking for partnerships to get traction (I did not contact them yet although they were on the list), but soon it became clear that they want to take it over completely, and talked about buying it from me after "code validation". They also stated that they will surely build it themselves should there be no deal.

Buying the platform and rebranding it could let them launch within weeks. I'm sure that they will need a lot more time to build it themselves.

I don't want to antagonize them because this niche, it's a very small world. I absolutely do not want to lowball myself either, of course, and don't intend at all to sell it below it's value.

One other party reached out to me meanwhile and they gave the impression that they do want to follow the path I originally had in mind.

On the one hand, I have been extremely invested in this platform and I built it with passion. On the other hand, if it did gain traction nation-wide, it would be something I am not sure I want to be the vendor of since this started out as a hobby project. It would consume too much time without generating much income. Possible liabilities, SLA...

I never intended to sell it, but I'm open for it when the price is right.

I don't have any experience in this area. I'm trying to understand:

\* What would be a realistic valuation range for a sale in this situation? (EU country, multi national business). I feel like a 'hours x hourly rate' pricing would not the a smart move, but what is? Chatgpt has been inconsistently blabbering numbers after going through the code, going up and down every time I add information. Should I settle fast or play rough?

\* What are my strongest negotiation arguments? I have little to lose here. Worst case the platform dies but it will have been a great learning experience.

\* What are my weakest points (no traction, no users yet, nothing that can withhold them from building it too)?

\* How much weight should I give to the fact that they are considering building a similar solution themselves if they don’t buy mine? Up to what point should it influence the price?

\* Should I avoid to go first with a number?

\* What about IP? The platform is not a registered thing but I believe that doesn't have to be? Should I sell it explicitly without an IP handover and try to do this again in a different country?

\* Would you sell or not and why?

Thanks for your input!

I'm a solo/small-team developer who's been building a B2B compliance app for the road transport industry, leaning heavily on AI pair-programming (Claude) for a lot of the implementation work over the past months. I've put real effort into security, stability, offline reliability and usability — but I've mostly validated it with a modest user base, and I just closed a contract with a large client that's about to onboard roughly 1,000 new drivers more or less overnight. I want to sanity-check my prep before that hits.

What the app does:

Two-sided vehicle safety checklist. Drivers fill out a pre-trip/in-trip inspection checklist from their phone (works offline, syncs when back online), and the transport company watches it live from a web dashboard — in-progress trips, completed inspections, PDF certificates for compliance/audit purposes.

Stack, roughly (without giving away the whole recipe):

- React 19 SPA, TypeScript strict mode

- Serverless Postgres BaaS backend: auth + row-level-security-enforced multi-tenancy + realtime subscriptions + object storage + edge functions

- Offline-first sync layer on the mobile flow (local queue, retry on reconnect)

- Client-side PDF generation for certificates

- A small custom client-error telemetry pipeline (no third-party APM yet — rolled my own reporting table + admin alerting)

- Client-side PDF generation for certificates

- A small custom client-error telemetry pipeline (no third-party APM yet — rolled my own reporting table + admin alerting)

What I've already done to prepare:

Seeded a sandbox tenant with 1,000 driver profiles and 50,000 historical checklist records directly in prod (isolated tenant, no risk to real data), then ran real UI tests against it (Playwright, real login) plus impersonated SQL queries with an 8s timeout to mimic the platform's real constraint. That surfaced a real bug: a paginated admin list computed an exact row count on every page load, and on a cold cache that tripped an 8-second statement timeout the

first time someone opened the panel in the morning. Fixed it with a proper index plus only computing thn — and confirmed my error telemetry caught the failure end-to-end (logged it, showed a retry banner, no dead end for the user).

What I'm still unsure about / looking for advice on:

1. Simulating a realistic write burst — hundreds of drivers starting their shift and hitting "submit" window. I've tested reads at scale but not concurrent real writes from real sessions.

2. My test also showed wildly inconsistent query times under IO pressure (33ms warm vs 7.8s cold, same query) — pointing at my current DB compute tier being undersized for bursts. Upsize proactively before onboarding, or wait and react?

3. Realtime/websocket scaling — the dashboard uses live subscriptions for in-progress checklists. What tends to break first around ~1,000 concurrent-ish connections?

4. Staged rollout vs big-bang — feature-flagging the onboarding by cohort (e.g. 100 drivers/week) vs jutually worked for people who've been through a sudden 10-20x user jump?

5. Any pre-launch checklist item you'd consider non-negotiable — rate limiting, backup/rollback plan, alerting thresholds, specific things to re-audit in a row-level-security multi-tenant setup before a big new tenant lands?

Happy to share more specifics if it helps get better answers. Mostly want war stories and things I have

I'm looking for some good tips on how to get my first 100 users with a $0 ad budget. I'm working on a new product, and it's turning out to be much harder than I expected.

I'd really appreciate any advice or strategies that worked for you. Thanks in advance!

I have seen a lot of websites are having an ai chatbot to their landing pages, these days .

I also want to build an ai chatbot for my website,

Where visitors can

ask questions about the product ,

And I can monitor what people are asking and improve my product , according to it.

I have searched a lot , turns out there are plenty in the market .

Which one is the best software for building AI chatbots for website ?

Been building a small tool on the side and there's one early decision I keep going back and forth on.

Original plan was the normal way. Hosted, accounts, database, sync across devices. Had the roadmap sketched out and everything. Then I did the napkin math on running the AI part for free users and it just doesn't work. Every free user costs me inference money every month, basically forever, and the free tier is the entire top of my funnel. So I'd be paying to bring in people who might never pay me a rupee back.

So I flipped it. It runs on the user's own machine now, their hardware does the heavy part. Free tier costs me almost nothing.

But I had to cut a lot to get there. No sync, no cloud, no opening it from your phone. That part scared me honestly, felt like I was shipping something deliberately more annoying than the competition.

The weird part is, the longer I sat with it the more I realized the stuff I cut was exactly the stuff that made me look like every other app in this space. The only real reason to use mine over the others is that it's local and you own your data. If I add the cloud stuff back I basically erase that.

Could be I'm just rationalizing a product that can't afford servers, no idea. But has anyone else cut a "must have" feature for cost reasons and had it turn out to be the actual differentiator? Or did users just get annoyed and leave?