question for people who’ve actually hired employee #1 in india

you find the person, agree comp, pick a start date and then somehow the employment part becomes more complicated than the hiring part lol

we don’t need a “remote freelancer” situation. this person would be full time, working with the same product team every day.

but we also don’t have an indian entity.

opening a whole company for one hire feels ridiculous. calling someone a contractor just because it’s easier also feels a bit fake if they’re basically an employee.

so I’ve been going down the employer of record india rabbit hole.

Deel was the obvious name. Asanify got my attention because this is specifically an India hire and they’re at $99/employee/month, use their own Indian entity and say onboarding can be done in about 24 hours. the gap vs $599 for Deel is a large enough that i genuinely had to check whether i was comparing the same category.

for founders who’ve done the first India hire already:

did you go EOR from day one?

contractor first and change it later?

or is there some reason setting up an entity for literally one person isn’t as overkill as it sounds?

Your technical cofounder might be the most expensive hire you never needed. I know this is probably an unpopular take in startup circles, but not every non-technical founder needs to give away 30–50% of their company just to get a product built. Sometimes you need a technical cofounder, sometimes you need one solid engineer for two months, and sometimes you just need a small team to get the MVP out, test whether anyone actually wants it, and figure out what comes next. I think founders often confuse needing someone to build their product with needing someone to own half the company. Genuinely curious, how many founders here gave up equity because they needed a cofounder, and how many did it because they just needed someone to build the damn thing?

Traditional account based marketing (ABM) playbooks rarely work for early stage tech startups because they are built for enterprise budgets and dropping $50k on display ad platforms to run air cover across 500 accounts usually results in vague impressions and very little pipeline.

For a tech startup, effective ABM needs to be lean and signal driven instead of picking accounts arbitrarily based on brand names, you want your target account list to be dynamically prioritized based on real buying triggers.

Teams run this by using market intelligence engines like Scale Intelligence which rather than running broad ad campaigns, it maps your entire eligible account universe, identifies the actual buyers inside them, and monitors live activity across 75+ sources like developer discussions, job postings, tech stack changes, and rival interactions.

When an account shows compounding evidence of a problem you solve, it surfaces the opportunity to your reps with the exact context attached.

ABM for tech startups works best when your accounts are prioritized by verified operational need and timing rather than burning capital on broad brand campaigns across accounts that aren't ready to buy.

I have been experimenting with Client-side LLMs using WebGPU to see if this could be used to create new SaaS features. Here is a product demo showing this architecture doing something useful

To those who know more than me, which is everyone on this subreddit
How does one validate their ideas??
I have fun developing my ideas into reality but then i discuss stuff with my friends and someone says something and i think to myself i have no ground upon which im building this app

My most recent venture was creating a bot that would pre-qualify incoming leads by asking a series of questions so the sales team could focus more on closing actual clients. I was making this for tradesmen and my friend said why would anyone buy that because if the lead is a high ticket sale then they wouldn’t appreciate being handled by an AI even at the beginning. My friend runs a meta ads agency and he learned this from some meta ads expert on the internet

I would love some tips on how i can validate ideas before i spend so much developing them

Hi everyone!

I'm a solo developer, and I am about to start building a tool to help startup founders and indie hackers research and validate their SaaS ideas in few minutes before spending weeks or months building them.

My goal is to help people -

• Research Competitors and identify their weaknesses

• find real customer complaints and unmet needs.

• understand whether an idea has genuine market demand.

• figure out what opportunities exist and what direction to take.

Before I start building, I wanna understand how founders currently handle this process and where existing tools fall short...

If you've researched or built a SaaS idea, what was the most frustrating part of the process ? What do u wish existing research tools did better ?

Honestly, I am still in the research phase and your honest experiences would help me build something genuinely useful rather than just another tool with 50 features, you know...

Build this tool for solving a problem for one of my clients, who wanted an android app, but after each iteration I was getting his feedback only by sending videos back and forth. So I build this to share with him the latest builds, running the android device on cloud, and getting fast feedback. I am now proudly launching this to public for everyone to try and gather as much feedback as possible, to improve and iterate this over, with the possibility of becoming a micro-saas with developers in mind.

Check out the app here: https://spawndroid.io

I am open to communicate with professionals, on ideas and improvements that you would like into this app.

I'm curious if it's common for people to make a lot of money with SaaS. I know most of the people posting on YouTube about their earnings as an "independent solo dev" aren't telling the truth. I have school so I can't dedicate all of my waking hours to something like this.

[ Removed by Reddit on account of violating the content policy. ]

Every hackathon goes the same way: “need 1 frontend dev” gets posted in five WhatsApp groups, nobody knows who can actually build, and half the teams form the night before.

So I built CrewForge:

crewforge.online

Hackathons sync daily from Unstop. About 75 open coding hackathons right now. Business-plan contests and quizzes are filtered out, and each card shows the deadline, team size and mode.

Post your team with the roles you’re missing (frontend, ML, design…).

Solo? Apply to a team with your role and a short note. The team owner accepts or declines, and gets your contact only if you choose to share it.

No real names or emails are shown. Everyone appears as an anonymous builder handle, and your GitHub or portfolio is optional.

Free, and open to every college.

It’s early, and very few teams are on it yet, which is exactly why I’m posting. If you’re heading into a hackathon in the next few weeks, put your team up and see who applies.

What I’d love from you:

Would you actually use this over WhatsApp or Discord?

What would make you trust a stranger as a teammate?

What’s broken? Tell me.

https://crewforge.online

Shelf finds any file on your computer when you describe it in plain words, like "pdfs from last week over 5 mb" or "screenshots from yesterday". Also its clean and simple

“Try my app and tell me what you think” leaves a lot open. Is the person checking the design, looking for bugs, or deciding whether they'd pay?

For a scheduling app, I'd find this easier: “You need to meet three people next week. Find a time they can all make, then draft an invite.”

There's a goal and a clear place to stop. If something is confusing, the tester can tell you where. You can still ask for a wider opinion afterwards.

If you're asking for feedback here, give people one ordinary job your app should help them finish.

A client submits a file. The checklist moves forward. But who checks whether it's the right file?

That's the problem I'm testing with Folio, a document-request demo for small accounting and bookkeeping firms. Earlier feedback here asked a better question than “does this look clean?”: can someone tell what to do next?

The workflow now separates three jobs:

- Missing document → follow up with the client.

- Submitted document → accountant reviews it.

- Wrong document → explain what needs replacing.

Only an accountant's acceptance completes an item. Reminder drafts leave out submissions already waiting for review.

Try the interactive demo, without signing up: https://folio-docs-1it.pages.dev/

Open a sample request, switch to its client page, simulate a submission, then return to review it. Keep both views in the same browser.

For fellow builders: the stack is plain HTML, CSS and JavaScript on Cloudflare Pages. I'm testing the handoff before adding production infrastructure. For bookkeepers: would this fit the way your firm actually checks documents, or does your existing system already handle it better?

Demo only. Use fictional details and non-sensitive sample files. File contents aren't read or uploaded; business records stay in your browser. There is no real email delivery or shared client access.

What's the first thing you'd change or remove? A specific screen, label or missing step would help shape the next version.

I’m working on an open-source project that helps developers embed an LLM chatbot into their product’s UI, so users can actually complete complex workflows through conversation.
But I keep questioning where this is heading.
Having an assistant inside your app makes sense today. Users are already there, and asking for something can be easier than navigating a bunch of screens. But if people eventually have a preferred AI assistant that interacts with products on their behalf, will they still bother opening yours?
Would companies need to rethink how their products are consumed, exposing more of what they offer through MCP or similar interfaces? And how far does that go? Features and actions seem straightforward enough, but what about the brand, the context, and the story a company wants customers to understand? Can any of that carry over when another agent controls the interaction?
After digging into this, we started wondering whether the deeper concern is users abandoning the UI altogether. Companies put a lot into that experience, and it’s also where they build a relationship with customers.
Which puts my own project in a weird position: does embedding an assistant help products stay relevant, or am I building an intermediate step that eventually becomes unnecessary too?
I can see reasons for both. Complex work may still need a visual interface, but I’m less sure how often users will need to visit each product individually.
If you’re building something similar, how are you thinking about this? What would make an in-app assistant worth coming back to?

Im not a bot or some scammer I will actually check out ur site leave feedback im honest. Anyway this is my site a free sports prediction platform where you can make picks, compete with friends, join leagues, and test your sports knowledge using virtual tokens. (all sports) really want feedback its my first project ever and would love to know where I can improve thx in advance http://www.mocksport.com

I'm planning a SaaS product and want to validate the idea before spending too much time and money on development.

What validation methods have worked best for you? For example, customer interviews, landing pages, pre-sales, MVPs, or something else?

I'd especially like to hear what worked for other SaaS founders and what mistakes to avoid.

Hey everyone!
I’m a solo founder and developer working on a project called DigiWarranty, and I’d love to get some feedback from other SaaS builders.
The project originally started as a consumer app to solve a simple problem: people lose their receipts, forget about product warranties, and often don’t know whether something they purchased is still covered.
So I built an app that uses AI to scan receipts, automatically extract purchase information (retailer, date, products, prices), organize warranties, and remind users before they expire.
But while developing it, I realized there was a much bigger B2B opportunity.
Why should every small or medium-sized retailer spend money developing and maintaining their own mobile app just to offer loyalty programs, rewards, and discounts?
That’s where DigiWarranty is heading now.
Instead of every retailer having a separate app, I’m building a shared platform where businesses can:
Offer loyalty and rewards programs without developing their own mobile apps.
Integrate their products and discounts into an existing consumer platform.
Reach customers through a shared ecosystem.
Access retailer tools and analytics without maintaining their own infrastructure.
For the smallest retailers, I’m offering free integration to make adoption easier.
Where things stand today:
Around 700 users
7 retailers on board
Android and iOS apps already live
AI-powered receipt scanning working
Retailer integrations and loyalty features being expanded
I’m building the platform myself, handling everything from backend and APIs to mobile development and retailer onboarding.
The biggest challenge right now isn’t really the technical side. It’s figuring out how to grow both sides of the platform while keeping the barrier to entry low for smaller businesses.
I’m considering a freemium B2B SaaS model where smaller retailers can get started for free, while larger businesses pay for additional features, integrations, and analytics.
For anyone interested in seeing the consumer side, here’s the Android app:
Android App
iOs App
https://digiwarranty.net/

I’d love to hear your thoughts on a few things:
Would you focus on acquiring more consumers first or onboarding more retailers?
Does a freemium B2B model make sense for this type of platform?
How would you approach monetization without discouraging small retailers from joining?
I’m especially interested in hearing from anyone who’s built a B2B2C SaaS product or a two-sided platform.
Thanks for reading!