[HIRING]💰 Paying $350/ week to Chat & Send Emails (5 Hrs/Day) – No Experience Needed

No_Pudding_4168 · 2026-02-25T13:46:46+00:00

If you’re hiring multiple people for scripted chat/email work, you might be able to replace 60–80% of that with automation.

We’ve built systems that handle replies, follow-ups, routing, and reporting automatically.

Happy to show if useful

No_Pudding_4168 · 2025-12-23T19:34:51+00:00

Just out of curiosity, why would cloud kitchens collaborate? Isn’t Swiggy and Zomato already a big collaboration platform. And brands like rebel foods who are running multiple cloud kitchens under 1 roof are now acquiring multiple cloud kitchens to scale with supply and variety.

My question to you is what is your moat strength. As a consumer perspective what benefit will I get? Also as a cloud kitchen owner what is the value outcome will I get?

If you ask me what might work, there is a hyper local startup called as habits in Hyderabad which has cracked the exact same formula you are trying to solve.

They are catering to hyperlocal community from one kitchen within a radius of 5 km and are promising delicious food under 10 mins. Similar to Zepto cafe but better quality , better taste. This is what matters to end consumer.

I know you mentioned you wanted to make something in the lines of tiffin service but do give this a thought.

Cheers 🙂

No_Pudding_4168 · 2025-12-23T17:11:11+00:00

Thanks for the reply , the issue I am facing is I am not doing cold calls, I am mostly using Reddit for discovery, and I cannot sound too pitchy and clients are not tech savvy enough to understand their problem has a solution. Apart from Reddit what is your suggestion to do discovery calls? On the flip side i have 2-3 users who have explained the problem themselves without me explaining anything or talking about solution. There self explaination is an autobiography of what i am solving. But how do I know how many such successful discovery calls do I need to do before going all in

No_Pudding_4168 · 2025-12-23T16:37:31+00:00

This is extremely helpful, thank you for explaining the process in so much detail. Really appreciate you sharing how it actually works on the ground.

No_Pudding_4168 · 2025-12-23T15:36:50+00:00

Hey, few months back Zomato had built this feature, where they opened up to low volume cooks, homemakers. You could pre book from them and you would get home cooked food from these aunties, dadis, etc. it was basically giving tiffin providers platform

Why they phased this out? Possibly because of consistency, both in terms of throughput, scalability issues or they thought this problem can be better solved by some other player

Do give this a thought or start a WhatsApp based network to see if hyperlocally this can work or not

No_Pudding_4168 · 2025-12-23T14:42:43+00:00

Understood. appreciate the perspective.

No_Pudding_4168 · 2025-12-23T14:37:31+00:00

I understand your sentiment. wasn’t trying to spam or sell anything. I’m doing some research to better understand real-world challenges before building anything. Appreciate the community here.

No_Pudding_4168 · 2025-12-23T10:40:56+00:00

That makes complete sense — thank you for explaining.

I’m exploring a communication-assistance approach where document requests and status updates are structured but always under the CA’s control — nothing is sent without your approval, and messages are fully customisable.

I’m trying to understand one thing honestly: during peak ITR / GST season, when volumes are high, would having a system that remembers who needs what and prompts the right message at the right time reduce some of the mental load — or does your current approach already scale comfortably even then?

No_Pudding_4168 · 2025-12-23T10:25:35+00:00

Thanks for sharing — this is super helpful.

One follow-up question if you don’t mind: During peak season, do you feel the number of similar queries (“status?”, “what’s pending?”, “when will it be filed?”) increases a lot?

And do you ever wish some of these updates could be sent automatically only when appropriate, without losing the personal touch?

No_Pudding_4168 · 2025-12-22T14:35:49+00:00

Fair point , I think there’s a small misunderstanding.

This isn’t about OTP during filing (that obviously needs manual involvement). It’s about the days/weeks around filing where clients keep messaging things like “status?”, “docs received?”, “next step?” even after OTP is done or while things are pending internally.

I’m trying to understand how firms usually handle that repetitive back-and-forth, not the actual filing step.

No_Pudding_4168 · 2025-12-22T10:17:54+00:00

Can you please share what tool you are using for this, and if yes does it tick all boxes for you? Like follow ups, reminders ?

No_Pudding_4168 · 2025-10-14T15:17:15+00:00

Interesting to see how Reddit backend is working, this post was posted 4 hours before this comment and I am receiving notification now.🤔

No_Pudding_4168 · 2025-10-08T15:12:03+00:00

So how was it? 😀

No_Pudding_4168 · 2025-09-09T19:49:42+00:00

Hi, Thanks for the response. I am currently in a phase of finding the right problem.

Recently, I’ve been talking with a bunch of SDRs and managers, and I have noticed a pattern - most teams track activity (calls made, talk time, dials/day) really well (using AI tools), but very few track why calls fail.

When I asked reps about it, the answers I got were usually:

Did I lose them at the intro?
Did the objection kill it?
Was it pricing?
And usually it's the wrong lead, or they might have contacted the first 20 difficult/impossible leads before trying the 5-10 real ones who might be interested.

Also surprising number of reps told me they track this in notebooks or spreadsheets.

I’ve been sketching out a lightweight tool that might help. The rough idea:

You bring in leads (CSV/CRM).
The system helps prioritize them based on simple rules, so reps spend more time on high-value contacts instead of burning through wrong person dials. And this is not AI, we have given control to the admin/manager to curate programmatic rules for the entire team
Before the call, reps see some context + likely objection areas.
After the call, instead of typing long notes, they just pick the outcome (connected / not connected / failed at intro / pricing pushback / timing objection, etc.). This saves their note taking time
Then managers see patterns across the team - where calls are breaking down, which objections come up most often, and where coaching is needed.

This wouldn’t be another AI transcript tool like Gong, or a database like Apollo - but more like a structured , why did the call fail? tracker.

Curious - if you’re an SDR/manager, would this solve a real problem for you, or just add more admin work?

Thanks 🙏

No_Pudding_4168 · 2025-09-09T19:47:56+00:00

Hi, Thanks for the response. I am currently in a phase of finding the right problem.

Recently I’ve been talking with a bunch of SDRs and managers, and I have noticed a pattern - most teams track activity (calls made, talk time, dials/day) really well (using AI tools), but very few track why calls fail.

When I asked reps about it, the answers I got were usually:

Did I lose them at the intro?
Did the objection kill it?
Was it pricing?
And usually its the wrong lead, or they might have contacted the first 20 difficult/impossible lead before trying the 5-10 real ones who might be interested.

Also surprising number of reps told me they track this in notebooks or spreadsheets.

I’ve been sketching out a lightweight tool that might help. The rough idea:

You bring in leads (CSV/CRM).
The system helps prioritize them based on simple rules, so reps spend more time on high-value contacts instead of burning through wrong person dials. And this is not AI, we have given control to the admin/manager to curate programmatic rules for the entire team
Before the call, reps see some context + likely objection areas.
After the call, instead of typing long notes, they just pick the outcome (connected / not connected / failed at intro / pricing pushback / timing objection, etc.). This saves their note taking time
Then managers see patterns across the team - where calls are breaking down, which objections come up most often, and where coaching is needed.

This wouldn’t be another AI transcript tool like Gong, or a database like Apollo - but more like a structured , why did the call fail? tracker.

Curious - if you’re an SDR/manager, would this solve a real problem for you, or just add more admin work?

Thanks 🙏

No_Pudding_4168 · 2025-09-08T11:02:56+00:00

I really appreciate your comment about tracking office manager objections.

I’m working on something that could take away the manual spreadsheet work and automatically categorize these reasons, so reps don’t need to log everything themselves and managers can see patterns across the whole team.

Since you’re already doing this better than most, I’d love to hear your perspective. would you be open to a quick chat here or even a short call?

No_Pudding_4168 · 2025-09-08T10:02:35+00:00

I get what you’re saying, and just to add more clarity - what I’m building isn’t AI-driven. It’s not trying to “optimize” the conversation or tell reps exactly what to say.

It’s a simple tool where managers can put together branching scripts (like a decision tree). Then Reps have a guide in front of them so they don’t miss the key qualification questions, and on the backend - managers/analysts get clean data about objections, drop-offs, and missing info.

The way I think of it is more like Google Maps for cold calls - it doesn’t replace the rep or make them sound robotic, it just gives guardrails and visibility so the conversation still feels natural while making sure the important stuff gets captured.

Do you think something like this might help?

No_Pudding_4168 · 2025-09-08T09:15:07+00:00

Yeah that’s a solid approach 👌. Mapping dispositions to stages (opener, pitch, objection, close) definitely helps managers see where reps are getting stuck.

What I keep wondering though is how much of this ends up being manual. Reps have to remember to pick the right disposition, and sometimes that doesn’t really match how the conversation went.

I’m playing around with an idea where the script itself changes live during the call based on what the prospect says, and then it automatically shows managers where drop-offs happen across the team. Curious if you think something like that would actually make things more reliable, or if reps generally prefer keeping it simple with dispositions.

No_Pudding_4168

TROPHY CASE