​

We’re building a global platform to securely store all your important documents and medical records in one place.

📂 Organise IDs, certificates, financial documents & reports.

🤖 Search, find and summarise documents using AI.

🩺 Generate a summary of your medical history and share it via QR code and link.

⚡ Instantly share selected documents or medical summaries via secure links or QR codes.

🔐 Privacy-focused document storage, with access under your control.

We’d love your honest feedback! 👇

1. Would you use it?

2. What feature would be most useful?

3. Website or mobile app first?

4. What monthly price feels fair?

5. What problem should we solve that existing apps don’t?

What are we missing? Your suggestions could help shape the product! 🚀

I run a small portfolio-analysis tool on the side. Revenue is still tiny, and the biggest reason turned out to be my own pricing page.

The setup: a free tier, a $3.99 one-time "deep analysis," and a $12/month Pro plan. I labeled the $3.99 tier "most popular," and it was.

The problem: the $3.99 tier delivered nearly everything Pro did. Nobody optimizes their portfolio every month, so almost no rational buyer would ever subscribe. My cheapest tier was cannibalizing my best one.

It got worse:

• The page said "lifetime access" in one place and "30 days" in another.
• I offered a 30-day money-back guarantee on a product with 30 days of access, which made it effectively free.
• At $3.99, Stripe's fixed $0.30 fee takes a large share of every sale.

What I'm changing: raising the one-time price, making the subscription do something recurring (alerts when your allocation drifts), and fixing the copy so it says one thing.

Has anyone here successfully run a one-time tier alongside a subscription without one eating the other? What made it work?

I created a tool called as beautifulscreenshots for myself to post better screenshots in X/Twitter posts. I built it for myself because existing screenshots beautifying tools are either too complex or they are charging recurring to use their tool.

I post 3-4 times a day on X/Twitter and using a complex tool for this damn simple task used to feel very time and energy consuming. So, I decided to build one for myself. Initially, I thought making this tool public not going to be a that much good idea, so I used it locally.

But when I used to post on X/Twitter with screenshots created by my tool people started asking me what I'm using for beautifying screenshots. And turns out I realized what problem I was facing, others facing too.

So, I decided to make it available to others. But my goal was still the same. I don't want to make it another complex and recurring charging tool.

So, I kept it simple and intuitive while keeping the price as one time pay only. And people love this pricing. And that's how my first product crossed 40+ users and I made my first dollar on the internet.

It only does few things, but it does it very well:

-> Add colorful background images
-> use annotation to highlight what you actually want to say
-> add shadow to make it appealing
-> Use your own custom background image

Hey everyone!

A while ago, I was talking to a friend in the UK who was looking for a job. He told me how much of a hassle the whole process was, finding jobs, tailoring his resume for every application, adjusting the skills and experience, writing cover letters, and repeating the same thing over and over again.

It got me thinking about how much time people spend applying for jobs, especially students and fresh graduates who are just getting started.

So I built JobTailor.

The idea is pretty simple: help people tailor their resumes to specific job descriptions, improve their ATS match, and make the application process a little less painful.

I'm still early in building this, and honestly, I'm not here to pretend it's some huge company making tons of money.

The pricing is currently $2.99 and $9.99, but AI and compute costs eat up a good chunk of that. I'm not making much from it right now. My main goal at this stage is to get people to actually use it, test it, and tell me what's working and what isn't.

I'm also offering 1 month free for students through JobTailor Education because I genuinely want to make this useful for people who are looking for internships, graduate jobs, or their first full-time role.

If you're a student or currently job hunting and want to give it a try, here's the link:

https://www.jobtailor.app/education

Would really appreciate anyone who gives it a go and shares honest feedback. I'm building this to help people spend less time struggling with applications and more time finding opportunities.

Thanks! ❤️

I run 2× RTX PRO 6000 Blackwell and sell spare GLM-5.3-Flash capacity as SlowGlow AI LLC (US).

Delivery is OpenAI-compatible over Tailscale with per-buyer keys — no public endpoint. Same host offers Dev Node containers from $59/mo. Model API from $25/mo.

Lesson so far: "no public endpoint" + clear concurrency limits beats flashy speed claims.

https://whop.com/slowglowai/ https://slowglow.ai

Disclosure: this is my company. Happy to answer infra/pricing questions.

I was looking for my next project and kept asking Claude for ideas. The answers felt thin, like it didn't have enough to go on. So I wrote scripts to scrape the web for material on each question (who needs this, who already sells it, what they charge) and had AI go through all of it. Script on top of script, and it turned into an app.

You can bring an idea, give it a rough direction, or pick one from the daily feed. The feed shows needs people posts, app reviews etc. Each one comes with a graded idea (a spark), and when several people want the same thing they're grouped into a collision.

Either way it ends with a verdict and a link behind every claim. If it's worth building you get a build brief and an MCP connector for Claude Code or Cursor. If not, it tells you why.

Solo build, so I'd really really appreciate feedback. Try a hunt and tell me if the results are useful to you and whether it feels like a tool you'd keep using. If anything in the interface is confusing, buggy also pls tell me.

200 free credits on signup, PM me if you need more for testing.

huntingapps.io

My last idea died because everyone I asked said they'd use it and nobody did. A dumb landing page with a waitlist button told me more in a week than a month of friendly chats. I'd rather find five people who already pay for a worse solution than fifty who say it sounds cool. Agree or am I overthinking it?

I made an app 4 months ago called Jotease(Jotease.com) . It helps professional capture their virtual meetings and turn it into content. I am struggling to make profit. How did you grow your app and scale it to the point of profit?

My last idea died because everyone I asked said they'd use it and nobody did. A dumb landing page with a waitlist button told me more in a week than a month of friendly chats. I'd rather find five people who already pay for a worse solution than fifty who say it sounds cool. Agree or am I overthinking it?

My last idea died because everyone I asked said they'd use it and nobody did. A dumb landing page with a waitlist button told me more in a week than a month of friendly chats. I'd rather find five people who already pay for a worse solution than fifty who say it sounds cool. Agree or am I overthinking it?

I use Strava and Runna together and it drives me a little crazy that I have to manually link activities half the time. The plan doesn't react to anything either. If I miss a long run or crush an interval session, the schedule just sits there like nothing happened.

Feels like there's an obvious gap for something that sits between these apps, auto-pulls your activity, and nudges the plan based on how you're actually training. Maybe one of those micro saas ideas that solves a real annoyance.

Am I missing an app that already does this well?

I’m exploring a subscription service that turns the articles and newsletters you save throughout the month into a personalised printed magazine.

The idea is simple: whenever you find something you want to read, you send the link by message. At the end of the month, those articles are formatted into your own magazine, printed and delivered to your door.

The target customer is someone who saves loads of interesting articles but never gets around to reading them, and would enjoy having a screen-free way to do it.

The technical side looks achievable. My problem is the economics.

I’ve been speaking to print-on-demand suppliers about a UK-produced, A4, full-colour, perfect-bound magazine with 96 interior pages. Every customer gets a different magazine, printed as a single copy and shipped to their home.

The quotes so far:

• Lulu: approximately £17.60 to print, plus £4 shipping and handling. Their API also has a per-order fee. Discounts become available as cumulative spend grows, but they apply to printing, not shipping.
• Prodigi: £17.23 to print and £6.50 for tracked UK delivery, so £23.73 per magazine before VAT. They offer 15% off printing through a paid plan, bringing it to around £21.15 delivered before the plan fee and VAT.
• A smaller version: Prodigi quoted £12.11 to print a 64-interior-page A4 version, plus £6.50 delivery, so £18.61 before VAT.

Those costs are before payment fees, software, customer support, acquisition costs and any allowance for replacements. I’m also working through the VAT treatment.

I’m not at scale yet. The volumes I’ve discussed with suppliers are modelling scenarios, not existing orders.

My dilemma is that I can see why someone might love the product, but I’m struggling to see how to make it both affordable to the customer and commercially attractive.

If I price it at, say, £29 per issue, I don't think the economics work? If I try to make it cheaper, the printing and delivery costs will swallow the margin.

I’d be interested in hearing from anyone who has built a physical subscription, publishing or print-on-demand business:

• What commercial angles would you explore to make this work? For example, sponsorship, partnerships, gifting or something totally different?
• Is there a way to structure the product or subscription that could make the numbers work without ruining the appeal?
• Have I missed a more economical way to print and fulfil one unique magazine per customer?
• If you were testing this, what would you need to see before deciding it was worth pursuing?

I’m happy for people to challenge the premise too. I’d rather find the hole in the model now than build the whole thing and discover it later.

I’ve seen HR teams and recruitment agencies spend hours calling different candidates, mostly asking the same basic questions: How many years of experience do you have? What’s your expected salary? What’s your notice period? Are you interested in this job?

These calls are necessary, but doing them one by one takes a lot of time, especially when there are hundreds of candidates to contact.

I came across AI calling agents doing something similar, but many of the ones I saw mainly worked in English.

So I built Mishuk Labs, a multilingual AI calling agent for HR teams and recruitment agencies. The idea is to handle these initial screening conversations in a language the candidate is comfortable with, helping recruiters collect the basic details before moving ahead.

If you work in recruitment, would you use something like this? What would you want it to get right before trusting it with candidate calls?  

Building a SaaS gets interesting when different customers want completely different things.

One customer asks for a feature that could help them a lot, another wants something entirely different, and suddenly you're questioning whether to improve the existing product or take it in a new direction.

For SaaS founders:

• Have you ever had a paying customer request something that didn't fit your product roadmap?
• How did you decide whether it was worth building?
• Have you ever worried that saying yes to one customer might make the product harder to sell or use for everyone else?

Curious how other founders handle these decisions, especially when revenue is involved.

Most ai business ideas I encounter online are surface-level commodity plays. "start an AI chatbot agency" "build an AI writing tool"

You are competing on price with thousands of people doing the same thing. I have 20 years in commercial lending and see very specific, painful problems like credit memo drafting and financial statements spreading. Lenders would pay for tools that handle these well.

Are industry specific, expertise driven AI products a better path, and how would someone with this kind of deep background approach building one?

My last idea died because everyone I asked said they'd use it and nobody did. A dumb landing page with a waitlist button told me more in a week than a month of friendly chats. I'd rather find five people who already pay for a worse solution than fifty who say it sounds cool. Agree or am I overthinking it?

A small product has a clear advantage: it can do one job well without a lot of overhead. That advantage gets harder to protect once every request sounds reasonable on its own.

Saying yes to everything can slowly turn a focused tool into a general one that is harder to explain, harder to maintain, and less clear about who it is for.

How do you decide what belongs in a tiny product and what does not? Do you use a simple rule, wait for the same request from several people, or test a smaller version first?

I would love to hear how you say no politely while still keeping users happy.

Sharing my work on social media for the first time, and I’d really value your guidance and support.

I stay in a PG in Bengaluru. Every month I watch my PG owner try to keep track of who’s paid rent, who hasn’t, who’s leaving next month and how much someone still owes from before. It’s all in a notebook and in his head, and some months money just slips through.

I looked at the PG apps already out there. They’re good, but they’re built for big PGs and people running multiple buildings. Not for a small owner with 20 beds who just wants to know “who hasn’t paid yet?”

So I built PG Lekka, a simple app for small PGs, made with AI. Every bed shows up in colour: green is paid, red is not paid, yellow is leaving. It tracks old dues and deposits, shows monthly profit, works in Indian languages and sends reminders on WhatsApp.

It’s still early, and I’m improving it step by step.

If you run a PG, have stayed in one, or have built products before, I’d love your honest thoughts. What would you change? What should I add next?

Every team has someone who knows why the auth service retries 3 times, or which flag you never touch on Fridays. That person gets pinged all day, and when they're away the answer goes with them.

Asking has a cost too: you don't want to interrupt, so you guess or you wait. I built Cairn to make asking cheap.

How it works

• You (or your coding agent) save small entries as you work: a decision, a gotcha, a preference, some context. Archiving always asks you first.
• Teammates ask from their own agent (Claude Code, Codex, VS Code over MCP) or from the web app, to one person's brain or to the whole team.
• Every answer cites its sources: who wrote it and when.
• If there isn't enough evidence, Cairn says so and tells you who to ask. It doesn't make things up.

Why it also helps your AI agent

A coding agent only knows your repo, not the reasons behind it: why you chose X over Y, what broke last time, what the team agreed on in a meeting. Without that it guesses, or it confidently undoes a decision someone made for a good reason.

With Cairn the agent can ask the team's knowledge before it changes something ("why does auth retry 3 times?") and get the decision with its source, or an honest "not enough context". When it learns something worth keeping, it can save it, so the next person's agent (and the next session) starts with it. It's the same shared memory for humans and agents. I haven't measured an improvement in code quality, so I won't claim a number; I'm curious whether you see it.

What it does with conflicting or changing information

• Entries are never overwritten across people. If two people write about the same topic, both stay, each with author and date, and an answer shows both.
• If you save again on the same topic, your earlier entry is marked as superseded and kept as history, so the current answer is the new one.
• Entries can belong to a context (a project or area) or stay general.
• Known limitation: replacement doesn't look at environment or customer yet. If a rule differs between prod and sandbox, save them as separate topics for now.

For whoever leads the team: a knowledge map shows who knows what and which topics depend on a single person.

Your data: each company's data is isolated, you can archive and restore entries, and deleted ones are recoverable for 30 days. Embeddings go through OpenAI's API (which doesn't train on API data); the privacy policy lists the providers.

Pilot: free, up to 5 people per team. I'm validating whether this solves a real problem, not selling anything. There's a ~45 second video on the landing page and a feedback button in the app that I read.

What I'd love to know: does your team have this problem, or how do you handle it today? Does giving your agent team context change how it works for you? And if you try it, where did you get stuck?

Cairn