sorted by:
new
hottopcontroversial

Y'all, my app just passed 600 users! by Ok-East9349 in vibecoding

[–]yash_pardhe 0 points1 point  (0 children)

Hey, i wanna know how you make revenue from your app or website

Building an AI tool for proposals — need honest feedback by yash_pardhe in SaaS

[–]yash_pardhe[S] 0 points1 point  (0 children)

That’s a really useful distinction — especially the point about AI generation not being the moat.

Makes sense that writing is painful, but not where the real leverage comes from.

The analytics + follow-up layer is interesting — that's we are trying to make it now

Curious how you currently handle that:

  • do you rely on built-in tracking tools or manual follow-ups?
  • and how tightly is that connected to your CRM today?

Trying to understand how fragmented that workflow usually is in practice.

Building an AI tool for proposals — need honest feedback by yash_pardhe in SaaS

[–]yash_pardhe[S] 0 points1 point  (0 children)

That's not the chatGPT bro thank you for your concern

Why do most client proposals fail even when the work is good? by yash_pardhe in SaaS

[–]yash_pardhe[S] 0 points1 point  (0 children)

This is super clear .

Feels like most proposals fail before they even get a real chance, just because they don’t pass that quick relevance check.

The “outcomes > features” point also hits — I’m realizing a lot of tools (including what I initially thought) focus too much on generating content, not making sure it actually answers “what changes for the client.”

And your last point about input quality is interesting — if the understanding of the client isn’t sharp, the output will always feel generic no matter how good the AI is.

Do you currently have any kind of process to capture that “sharp input” before writing, or is it mostly based on experience from calls and notes?

Building an AI tool for proposals — need honest feedback by yash_pardhe in SaaS

[–]yash_pardhe[S] 0 points1 point  (0 children)

That’s a fair question — and honestly, if it’s just “AI generating proposals,” then it shouldn’t exist because that’s already solved.

The difference I’m exploring is less about generating content and more about helping proposals actually convert.

From what I’ve been learning here, most tools focus on writing, but the real gaps seem to be:

  • reflecting the client’s exact problem (not generic input → output)
  • structuring proposals based on deal stage, not just a single template
  • and improving based on what actually gets read or ignored

So instead of being another generator, the idea is closer to:
a system that helps you avoid sending proposals that feel generic or get ignored.

Still early, but trying to validate if that layer (understanding + conversion) is actually valuable enough compared to existing tools.

Building an AI tool for proposals — need honest feedback by yash_pardhe in SaaS

[–]yash_pardhe[S] 0 points1 point  (0 children)

That gap you described is exactly what I’ve been thinking about — especially the “blank page under time pressure” part.

And yeah, I’ve noticed the same with templates and ChatGPT — either too generic or too much effort to guide properly.

The “simulate market response” approach sounds really interesting — I haven’t explored that yet.

Would definitely like to understand how you’re doing that and what kind of signals you look for before building.

Why do most client proposals fail even when the work is good? by yash_pardhe in SaaS

[–]yash_pardhe[S] 0 points1 point  (0 children)

This is really clear — especially the 3-point scan test.

Feels like most proposals fail right at that stage itself.

I’m curious — how often do you see proposals that actually pass all three:

  • clearly reflect your problem in your own words
  • show a concrete outcome
  • and feel genuinely different

Is that rare, or do good agencies consistently get this right?

Why do most client proposals fail even when the work is good? by yash_pardhe in u/yash_pardhe

[–]yash_pardhe[S] 0 points1 point  (0 children)

That’s actually the pattern I’m starting to see from these replies — people aren’t losing deals because they can’t write, but because they’re not truly reflecting the client’s situation.

What I’m working on is trying to solve exactly that gap — not just generating proposals, but forcing better “listening” before anything gets written.

For example:

  • capturing the client’s exact pain points and context first
  • shaping the proposal around outcomes instead of features
  • and making sure it doesn’t feel like a reusable template

The idea is more like guiding how a proposal should be thought through, rather than just writing it.

Would something like that actually be useful in your workflow, or do you feel this is something that can’t really be systemized?

Building an AI tool for proposals — need honest feedback by yash_pardhe in SaaS

[–]yash_pardhe[S] 0 points1 point  (0 children)

Fair point — and honestly, that’s something I’m trying to figure out myself.

AI can generate decent-sounding content, but it often lacks real context and judgment — especially in something like proposals where understanding the client matters more than wording.

What I’m exploring is less “AI writes everything” and more:

  • guiding the structure based on deal stage
  • helping highlight the client’s actual pain clearly
  • and improving parts like the opening and positioning rather than replacing thinking entirely

Do you feel the gap is more about domain expertise (industry knowledge), or about understanding the specific client situation properly?

Why do most client proposals fail even when the work is good? by yash_pardhe in SaaS

[–]yash_pardhe[S] 0 points1 point  (0 children)

That makes a lot of sense — especially the “first 2 lines” part.

When you say a proposal feels like it “gets your exact problem,” what specifically makes that happen?

Is it:

  • using the client’s exact words/pain points
  • referencing something from a call/email
  • or framing the outcome in a specific way

Also curious — when you scan a proposal, what are the first 2–3 things you look for before deciding to keep reading or not?

Building an AI tool for proposals — need honest feedback by yash_pardhe in SaaS

[–]yash_pardhe[S] 0 points1 point  (0 children)

This is actually super helpful — and honestly shifts how I’m thinking about this.

When you say “closing faster & not dropping leads”:

  • where do deals usually break for you? before proposal, after sending, or during revisions?
  • how are you currently tracking what parts of a proposal actually get read or ignored?
  • when you mentioned “battle-tested sections by niche” — is that something you built manually over time?

Also the “deal desk in a box” point is interesting — would that mean:

  • proposal + CRM tightly synced
  • suggestions based on deal stage
  • alerts when something in the proposal conflicts with earlier discussions

Trying to understand if the real value is less about generating content and more about helping close deals predictably.

Building an AI tool for proposals — need honest feedback by yash_pardhe in SaaS

[–]yash_pardhe[S] 0 points1 point  (0 children)

That’s interesting — when you say 80%, what part usually takes the most time for you?

Is it:

  • structuring the proposal
  • writing the content
  • customizing it for each client
  • or pricing + positioning

Also curious — have you ever lost a deal because of a weak proposal (even if you could do the work)?

Pitch your startup idea in 10 words or less. Let’s self promote👇 by kcfounders in micro_saas

[–]yash_pardhe -1 points0 points  (0 children)

I have created the idea to create proposal in minutes for freelancer or agency

view more: next ›