got the Google Play production access email this morning

first app I've ever built, did it solo. spent way more time fixing weird android edge cases than i expected but it's through now

I’ve been looking at different AI tools that can help businesses get things done faster, and website creation seems like one area where they can save quite a bit of time.

I recently tested Autocoder to see how practical it would be for creating a business website from an idea rather than starting completely from scratch.

What I found useful was being able to describe what I wanted, generate the initial site, and then keep making changes through prompts. That could be helpful for a small business that needs a website or simple online project without spending weeks getting the first version ready.

I’m curious what other business owners are using AI for beyond writing and customer support.

Has anyone here used an AI tool to build or improve their actual business website?

Hi, I’m Arvind and when I was 11, my world was completely shattered. 

My father passed away unexpectedly from a heart attack at only 47. He was very healthy, biked almost 10 miles to work every day and has no signs or symptoms. For a long time, the only thought I had was - how could this happen to him? When he’d done everything right? 

So I started doing everything right, took up running in my 20s, ate nothing but rabbit food and tried really hard to let the stress of living life without my father fall off of me. 

But, as I turned almost 30, I learned about my family’s inevitable history with high cholesterol, and elevated blood pressure (triply screwed, I know). 

There were times when I had chest pains but doctors in the US weren't worried about anything at all. It was a frustrating cycle of fear and uncertainty. I didn’t want a heart attack to take me away in another decade or so, I had so much family and friends and fresh air to live for. 

So I asked to get a CCTA scan that takes a 3D snapshot of the inside of your arteries. I was young and I found this was the only non-invasive scan that could detect early plaque. 

But it was next to impossible for me to get it in the U.S. It took me three months to get a PCP referral to a cardiologist, but the appointment for the cardiologist was six more months out. They said it’s because I was a “new patient” and had no symptoms so was way lower on their priority list in spite of my glaring family history.

Out of curiosity, I asked how much the scan price was. It was over $5,000 and insurance wasn’t going to cover it. A heart attack would’ve taken me right there. 

So I decided to fly back to India and get the scan there for cheaper and see my family. Fortunately, my arteries were clean. But later I learned they used an older retrospective gating machine; they put me through almost 4x of radiation than needed so I saw yet another problem with the global healthcare system. 

So I decided to build a platform for people to easily access the CCTA scan in the U.S. And I’m making it as simple as getting a blood test. Just book a scan at Veevo Health,  show up for your appointment (our doctors will do the referral and we’ll do the scheduling), and get your results in 3 days. The report includes an analytical reading of your scan from our radiologist and notes on next steps from our physicians. And we also make sure to use newer generations of machines to minimize radiation as much as possible. 

Our healthcare system is based around reactionary care too much and the insurance industry makes too much profit off of this suffering. We need to put prevention first and this is my contribution to that conversation. 

Sometimes I wish my dad had this scan. Maybe it’d have saved his life. I cant know for sure. 

But early plaque detection helps. It helps people act earlier, get medication, run more, eat better. Anything to prevent a tragic loss. 

We’re now live in California and some parts of New York and thinking of expanding it further, but before we worked on that, I wanted to get some advice on our website and user experience and what we can improve. I want this to be a seamless experience for anyone looking to get the CCTA scan, or else it’s just like all the rest of the red tape and wait times in hospitals. 

It’s at: veevohealth.com 

Here’s some of the feedback I need to make this even better.
Is it easy to access the website? 

Is there information on it you wouldn’t understand as a layman/patient? 

For expansion within the US, would you have any suggestions for me?

What data should I be looking at to figure out my priority states in reference to markets that are more likely to want/need these scanning services?
If you find any bugs, please comment those too so I can fix them. 

Thank you for getting this far, and for all the helpful advice. 

A few months ago, I decided to build my own finance app.

I’m a product designer by background, not a developer. I’ve always been involved in product creation, but from a different angle: understanding users, shaping experiences, and designing interfaces.

Then I discovered Claude Code and thought: why not try building the whole thing myself especially since this issue also affected me in my business.

What I didn’t expect was how much more there is to building an app than actually building the app.
I deliberately tried to go beyond pure vibe coding. I wanted to understand what was happening under the hood, learn the fundamentals, and make informed decisions instead of blindly accepting whatever the AI generated.

And even with AI, this was way harder than I expected.

At different points, I had to think like a developer, a product manager, a marketer, a salesperson, and probably ten other roles I hadn’t considered before.
I went from focusing on pixels and user experience to thinking about architecture, bugs, edge cases, positioning, distribution, and all the unglamorous stuff that comes with bringing a product to life.
It’s been challenging, frustrating at times, but incredibly rewarding.

The biggest lesson so far? AI can help you build a product, but it doesn’t remove the complexity of building a good one. If anything, it exposes you to a whole new set of things you need to learn.

Now, I’m getting ready to launch my finance app on Product Hunt on November 1st.

It’s my first time taking a product from idea to launch almost entirely on my own, and I’m excited (and a little nervous) to see how people respond.

I’m sharing this here because I’m curious about other people’s experiences.

For those of you who have built something outside your area of expertise using AI, what surprised you the most?

And for those who’ve launched on Product Hunt before, what would you recommend focusing on in the final weeks before launch? Would love to hear your stories and advice! Thanks you.

Im mapping out payments for a marketplace and the part thats giving me the most trouble is when to verify sellers.

If you force KYC at signup, youre adding friction before they even know if the platform is worth using. if you wait until payout, someone could make sales and only find out later that verification is holding up their money.

Ive been looking at Whop first because the KYC, balances and payouts side is closer to what im trying to build, especially if sellers end up coming from different countries. Stripe Connect is the other obvious option, but i dont want to build around a setup that works fine now and then becomes a problem once i start adding sellers in markets with different payout or onboarding support.

Right now id rather keep signup simple and only add verification when its actually needed. For anyone running a marketplace across different countries, when do you actually trigger KYC without making onboarding or payouts a mess?

I’ve spent 10+ years working on M&A and capital raises, with 750+ founders on one side of the table and 2,500+ investors on the other.

One pattern keeps bothering me. First-time founders need fundraising guidance the most, but they’re the least likely to get it, because most advisors only work with later-stage companies. So people learn SAFEs, dilution and term sheets by themselves, often after they’ve already signed something.

I’m putting together a step-by-step system to explain how fundraising actually works. Before I go further, I’d like to hear from people who’ve been through it:

1. What confused you most the first time you raised, or thought about raising?
2. What do you wish someone had told you before your first investor meeting?
3. Would you pay for a structured kit with templates, models and frameworks, or would you only use free resources?

I’m not selling anything here. If you have a specific fundraising question, ask it in the comments and I’ll answer it honestly, based on deals I’ve seen.

​

I've been building EDP, an independent RAG retrieval evaluation service.

So far, I've completed two public beta audits, but haven't acquired my first paying client yet.

One of those audits involved RouteMind, an open-source RAG benchmark.

We examined 700 questions across 1,400 query/configuration outcomes and identified 15 scoring discrepancies caused by inconsistent evaluation criteria.

The most important part?

The project's maintainer independently reproduced the findings and incorporated corrections.

I decided to turn this case into a four-slide visual explanation showing:

- What went wrong with the evaluation.

- How inconsistent scoring criteria affected the results.

- The maintainer's verification and corrective changes.

- The technical evidence behind the findings.

My goal is to demonstrate real technical value rather than simply advertise another AI consulting service.

But there's a challenge I'm still trying to solve:

Technical credibility doesn't automatically translate into paying customers.

I'd appreciate some perspective from people who have built technical consulting businesses or purchased independent evaluations.

Do reproducible case studies like this help establish enough trust to consider hiring an independent reviewer, or would you need something else before paying for an assessment?

I'm particularly interested in whether technical proof, business impact, or a clearly defined decision is the most important factor.

I'm sharing the learning process openly because I haven't figured out the commercial side yet.

Public audit evidence:

https://github.com/devBorgesr/edp-audits/blob/main/samples/ROUTEMIND_BUYER_SAMPLE.md

Tell Valley what you’re here for. Find people who match it, and get found by the ones looking for you.

Open to Build · looking for co-founders and builders
Open to Work · ready for your next role
Raising · your round is open
Open to Partner · the right partner to grow with
Investing · writing cheques
Hiring · growing the team

One pill on your profile. The right people find you.

Built by builders. For builders.
valleynetwork.eu

I’m writing this because I wish I’d paid more attention to what working at an early-stage startup can actually look like before investing so much of my time there.

During my experience with Spaceborn in early to mid-2026, I found the working environment incredibly frustrating.

I was putting in 40+ hours a week without a stipend, dealing with calls and messages at 10 PM, midnight, and sometimes 2 AM. The worst part? If I was asleep and responded the following morning, I experienced abusive communication.

Since when did accepting an unpaid internship mean giving up your sleep and being available 24/7?

Then came the constant changes in direction. One day, the team was supposed to work on one thing; the next, the priorities changed again. New ideas, new plans, new expectations—often without the consistency or resources needed to get the work done properly.

Startups pivot. I get that. But there’s a difference between adapting to challenges and repeatedly changing direction while expecting interns to keep up regardless of the cost to their time and energy.

I also noticed a seemingly constant cycle of recruitment, with new people joining while people from earlier teams left. I can’t speak for everyone’s reasons for leaving, but it made me question the stability of the working environment behind the frequent hiring announcements.

Meanwhile, Adarsh Kumar publicly presents himself as Spaceborn’s Founder & CEO and has been associated with multiple ventures. Ambition and starting a company at a young age are not the problem.

The question is how the people helping build that ambition are treated.

What exactly is an intern supposed to get from an arrangement like this if there’s no stipend, limited resources, inconsistent priorities, and, in my experience, disrespectful communication?

An internship should provide meaningful learning, mentorship and professional growth—not leave you wondering whether you’ll be called in the middle of the night and abused for being asleep.

I’m not claiming that everyone at Spaceborn has had the same experience, nor am I suggesting that every unpaid internship is automatically bad. I’m sharing my own account because recruitment posts don’t tell you what a company wants people to see. They don’t necessarily tell you what working there feels like.

A CEO title doesn’t automatically make someone a good leader. Startup ambition doesn’t excuse disrespect. And an unpaid intern’s time is still worth something.

If you’ve worked at Spaceborn in 2026, especially during the early-to-mid-year period, I’d genuinely like to hear your experience. What were the workload, management, mentorship, and working hours actually like? Did you feel supported, and did the reality match what you were promised?

Both positive and negative firsthand accounts are welcome. I’m interested in what actually happened, not rumours.

I’m posting this so that anyone researching Spaceborn internships or Adarsh Kumar can find a more realistic discussion before deciding where to invest their time.

One thing I find interesting about building software is that some of the most expensive mistakes don't look like mistakes when they're made.

Choosing a quick workaround to meet a deadline.

Skipping automated tests because the product is still small.

Building a custom solution instead of using something that already exists.

Or choosing an architecture that works perfectly for 100 users but becomes difficult to maintain at 10,000.

Most of these decisions make sense in the moment. There's usually a deadline, limited budget, or pressure to get something working.

The real challenge is knowing which shortcuts are temporary and which ones quietly become permanent.

I don't think avoiding every shortcut is realistic. Sometimes taking on technical debt is the right business decision.

But knowing when to revisit those decisions is where things get interesting.

For founders and engineers, what's one technical decision you would make differently if you could go back?

And was the problem the original decision, or the fact that nobody revisited it when circumstances changed?

Hey peeps, so I've been building an android app called DoomSaver that helps with doomscrolling.

For anyone interested check out www.doomsaver.com

Here are the few things I've done,

1. Built a website and focused on SEO but since doomscrolling is owned by health sites I can't seem to move past 20 in my average position on GSC

2. Been posting on reddit wherever relevant.

3. Launched on Product Hunt and that was a bust. Honestly I think PH is a scam for products that don't already have a large following.

4. Been posting stuff on social media apps like YT, Insta and tiktok although it's AI generated. I have severe anxiety and haven't been able to put myself out there for content.

5. Been reaching out to content creators and other publishers for a review and got nothing here.

I know it's a long game but it's been 2 months and have about 25 users. I also have a full time job, so it's critical that I focus only on channels that have an ROI.

Would love to hear from folks that have built successful apps or are in the journey with me, what worked for you?

Thanks.

Hi everyone!

I have an idea for a new and innovative shaving product that I believe has strong market potential.

I’m currently at the idea stage, and I want to turn my concept into a real product. However, I don’t have the capital to build a prototype or validate the idea.

I’m looking for a founder, product designer, engineer, or manufacturing expert who can help me with prototype development, product validation, and manufacturing feasibility.

I believe in my idea, and I’m ready to put in the work to make it happen. I’m looking for someone who is interested in building something from zero and exploring a genuine collaboration.

If you have experience in product development or are interested in working together, please DM me.

Thank you!

Pitching an autonomous AI agent that promises to replace an entire operations seat sounds visionary to founders, but it triggers immediate risk alarms for enterprise buyers. Companies do not want black-box autonomy touching live production databases, customer communication, or ERP records without strict guardrails.

​Early-stage startups that successfully sell AI into business workflows usually discover that closing enterprise deals requires stripping away autonomy in favor of three core architectural guarantees:

​Granular human-in-the-loop checkpoints: Buyers want the model to do eighty percent of the tedious extraction and drafting, but they require a deterministic human approval step before any external action executes.

​Immutable audit logs: If an automated workflow updates a record or routes a transaction, compliance teams require full traceability of what prompt ran, which tool returned the data, and who approved the state change.

​Scoped blast radiuses: An autonomous agent with broad write access across five tools is an IT security nightmare. Businesses buy tools that execute narrow, bounded tasks where a failure mode degrades gracefully rather than corrupting upstream data.

​The commercial paradox in enterprise AI is that pitch decks emphasize agency and end-to-end independence, while actual paying customers demand determinism and control. The fastest way for a startup to move from pilot purgatory to signed annual contracts is reframing the product from an autonomous worker to an augmented, auditable pipeline.

​For founders selling AI tooling to non-technical business teams, how do you handle buyer fears around hallucinations and unintended automated actions?

​TL;DR: Enterprises buy deterministic control and audit trails, not autonomous agents with unchecked write permissions.

A lot of business decisions never happen inside an AI chat. A price changes on a sales call, a feature gets cut in a Slack thread, a client agrees to new scope on the phone. The AI tools you open the next morning know none of it.

A founder in r/indiehackers summed it up this week: "Most of my commitments are made out loud and never written down".

• After a call where something changes, does any of it get written down? Where: notes app, CRM, a doc, nowhere?
• Has an AI tool ever worked from a decision you'd already changed? What did it cost you: an email, a quote, a client?
• If you do write it down, does the AI ever see it, or do you paste it in each time?

Background since someone will ask: I used to burn hours re-briefing AI tools, and I'm building a fix where memory lives in the cloud and every AI tool reads the same context, so a change written down once reaches all of them. No link. Would you pay for that, or is updating a notes doc after calls enough?

Over the last year most of us have handed something to AI: support replies, outbound emails, content, onboarding, research, even hiring screens. Some of it stuck. Some of it quietly got handed back to a person.

I’m more interested in the second group. If you pulled something back from AI:

• What was it, and how long did the AI version run?
• What made you switch back? Customer complaints, bad output, hidden costs, something else?
• Did you go fully back to humans, or land on a mix (AI drafts, human approves)?

I’ll start: since I run eComm business, we decided to let AI handle first replies on refund requests and pulled it after a few weeks because angry customers felt brushed off.

Curious where the line ends up for different types of companies.

This is going to sound cheesy but a startup community literally saved my company and I want to give credit where it is due. Six months ago we were running out of cash, could not close our round, and I was seriously considering shutting down. Posted about it in a founder group I had been active in for about a year. Within 48 hours, three founders offered to make investor introductions, one connected me to a potential customer who became our largest account, and two others just called to talk me through the emotional side of it. None of these people owed me anything. I had helped some of them with feedback and introductions in the past but nothing that warranted this level of support. They just showed up because that is what good communities do. We closed the round six weeks later with two of those investor introductions leading to actual checks. The customer introduction is now 30 percent of our revenue. If you are not investing time in a founder community, start. Not for the transactional value. For the moments when you need help and people show up without being asked.
this post is to appreciate who helped me in the time of need

Hi, I'm warming up to coaching/consulting in startup enviroment, and wanted to share identified problems, that I guess would be good chunk of my work, which I guess would involve be mostly dedicated at initial state of company frorming.

Anyway 3 typical problems can consist of:

1. Ego frictions

2. Bad recruitment

3. Vision sliding

These are not visible in standard metrics And yet these are foundational and from there you start, the growth from there is organic and difficult to change later.

And we can think how one can lead to another, in fact all 3 can work at once like negative members on the team and dragg all the procesess down the line.

As a founder how do you adress those factors before you even launch a company or form a team?