Walk me through what actually happened after you sent your last proposal. The full story not just the outcome.
I have been talking to founders and B2B salespeople lately and I keep hearing the same thing.
You spend hours on a proposal or pitch. You hit send. And then nothing. Just silence.
But what happens in that silence is different for every deal and most people have no visibility into it at all.
So I want to ask a simple question and I genuinely want to hear the full story not just the summary.
Walk me through the last time you sent a proposal to a potential client. What actually happened after you hit send?
Specifically I am curious about:
What did you do while you waited
How long before you followed up and why that timing
Did you ever find out if they actually read it
What did you assume was happening on their end
How did it end and did the outcome surprise you
I am not looking for best practices or what you think you should do. I want to know what actually happened. The awkward parts included.
I will share what I have been learning from these conversations once a few people have shared their stories. Some of the patterns are genuinely surprising.
Last one I sent: two weeks of silence, then a 'we went with someone else' with no reason.
What I changed after: started tracking every proposal in a Notion pipeline - status, last contact, follow-up date, what I said in each touchpoint.
Reviewing the last 8: I was doing exactly one follow-up and giving up. The ones that closed usually took 3-4 touches. That data completely changed my follow-up behavior.
The proposal itself usually isn't the problem. What happens in the 10 days after is. And most solo founders have no system for that window - it just lives in their inbox until they forget it exists.
One follow up and giving up is the single most common pattern and it is almost always too early. The ones that closed taking three to four touches is consistent with what experienced salespeople describe across every industry. The data changing your follow up behaviour is exactly what a system should do. The proposal is not the problem. What happens in the ten days after is exactly right and it is the window DocMetrics focuses on most closely.
The 'full story not just the outcome' framing surfaces the real problem: most solo founders have no record of what happened between 'sent proposal' and 'yes/no.' It lives in memory, email threads, and vibes. You can't learn from a process you can't see.
My last few proposals: sent, radio silence for 4 days, followed up, got 'still reviewing,' followed up again, closed. The learning was about when to follow up and with what - but that only became a pattern I could act on once I started logging it consistently.
What actually helped: a CRM entry per proposal with: date sent, client context, follow-up dates, their response signals (did they open it, ask questions, go quiet), and outcome. Over 10-15 proposals, the pattern of who converts becomes visible. You stop treating each proposal as a one-off event.
Building this into a Solopreneur OS: CRM module cross-referenced with the client portal, so proposals aren't just sent - they're tracked, flagged for follow-up, and tied to the eventual outcome.
What was the awkward part of your story - the waiting, the ambiguous signals, or the follow-up timing?
The proposal as a one off event that lives in memory and email threads and vibes is exactly the problem. The pattern of who converts only becomes visible once you start logging it consistently is true and it is why building the system matters more than any individual follow up. What made the difference in the awkward stories is almost always follow up timing. Not the proposal content. Knowing when to reach out and with what based on something observable rather than gut feel is the gap DocMetrics tries to close from the document engagement side.
Sent a proposal last week for a 3-month retainer. What happened after:
Day 1: nothing. Resisted urge to follow up.
Day 3: sent a 'just confirming you received it' - they'd forwarded it to their ops person.
Day 5: ops person had questions about deliverable timing. 40-min call.
Day 7: revised proposal with a smaller Phase 1 to reduce their commitment risk. Sent.
Day 9: signed.
The thing that made the difference wasn't the proposal itself - it was having a CRM that flagged this contact as 'proposal sent, no response' on day 3 so I actually followed up instead of assuming silence was rejection.
I've been building a Solopreneur OS in Notion where the CRM database surfaces exactly this: contacts by pipeline stage and days-since-last-touch. Without that view I would have let this one go cold after day 5 and assumed they passed.
The proposal was fine. The system around it is what closed it.
Your story is the clearest description of what good follow up looks like that I have seen in this entire thread. The system flagging proposal sent no response on day 3 is what made the difference. Not the proposal. Not the follow up message. The system that told you it was time to follow up and gave you the reason to do it. The 40 minute call happened because you did not assume silence was rejection. DocMetrics tries to give the same signal from the document side. Not just that they have not replied but what their engagement pattern suggests about why.
Sent a proposal in January. Nine days of silence.
On day 3 I nearly sent the usual "just checking in" email. Decided to wait.
Turns out they had been going through it the whole time. Opened it 4 times. Spent 12 minutes total. Went back to the pricing page twice.
When I followed up on day 9, I referenced the pricing section specifically. They said "funny you mention that, we were just discussing it internally." Signed two weeks later.
If I'd sent that generic check-in on day 3, I would have interrupted a conversation I didn't even know was happening.
The thing that changed my whole approach to follow-ups:
I stopped treating silence as one thing.
"They haven't opened it yet" and "they've been through it four times" feel identical from your end. But they need completely different responses.
This story is exactly why I built what I built.
The line that hits hardest is the last one. They have not opened it yet and they have been through it four times feel identical from your end. That is the whole problem in one sentence. The silence looks the same from the outside regardless of what is actually happening on the other side.
What you did on day 9 is what most salespeople never get to do because they do not have the information to do it. You did not follow up about the proposal in general. You followed up about the pricing section specifically because you knew that was where their attention was. That specificity is what made them say funny you mention that. A generic check in on day 3 would have been noise. A targeted reference to what they were actually discussing was signal.
The distinction you drew between the two types of silence is the exact problem I have been trying to solve. Not all silence is disengagement. Some silence is the loudest buying signal you will ever see if you have the right information to read it.
I built DocMetrics specifically for this. To turn that invisible activity into something a salesperson can actually act on. Would love to know if you are still using a tool for this or figuring it out manually.
The proposal that surprised me most was submitting to the Firefox Add-ons store (AMO). I expected a quick automatic review but got a detailed manual review with thoughtful feedback about privacy practices and permission minimization. They asked me to reduce my extension's permissions to only what's strictly necessary, which actually made the product better. The "outcome" was approval, but the process improved the code.
That’s really interesting—the feedback loop ended up being more valuable than the approval itself.
It feels similar to how in proposals, the hidden interactions matter more than the final yes/no. Did that experience change how you think about visibility into user behavior?
The silence after a proposal is the worst. What I've found is that most of the time it's not disinterest—it's that the person you sent it to now has to sell it internally and doesn't know how. They become the bottleneck because you didn't give them the tools.
Sending a 'champion kit' alongside the proposal—a one-pager they can forward, pre-answered objections, a demo video for async walkthroughs—cuts the silence dramatically. The proposal isn't for the buyer, it's for everyone the buyer needs to convince.
That’s a great point. Most deals don’t die at “no”, they die at internal friction we don’t see.
I like the idea of a champion kit—it basically turns the buyer into a guided seller inside their own company.
I’ve seen even a simple “forward-ready summary + ROI bullets” change response speed completely.
The silence after hitting send is a digital black hole where we spend way too much time refreshing our inboxes and doubting the entire pitch. We often imagine a harsh rejection while the client is simply juggling fifty other open tabs and a crowded calendar.
What is the most creative excuse you have heard after a long period of silence?
One of the most creative ones I heard was: “We love it, but our internal approval system is on a seasonal pause.”
In reality, it was just buried in backlog. Silence usually says more about priorities than interest.
The "seasonal suspension" of the approval system sounds like a clever way of saying they forgot their administrator password. This demonstrates that silence is often simply due to organizational delays in processing tasks, rather than an evaluation of your work. Have you ever experienced a potential customer who hadn't been in touch for a few months and then reappeared as if nothing had happened?
Exactly—that’s the tricky part. Silence often gets interpreted as rejection, but in reality it’s usually just internal delays or shifting priorities. And yes, I’ve had cases where people reappear months later as if nothing happened.
It is a relief when you realize that silence is usually just messy internal bureaucracy rather than a direct rejection of your hard work. I am building Bunzee.ai to help founders ground their product logic in real market data before they ever have to deal with the stress of the "sending silence." Since you have navigated these long deal cycles, would you mind giving Bunzee a quick look and sharing your feedback?
The interesting part is not whether they replied.
It is whether silence meant disinterest, internal forwarding, confusion, or quiet intent.
That is the real gap.
Most proposal tools only tell you if someone opened the file.
That helps, but it still leaves the most important layer missing: what actually happened inside the silence.
That is where the product gets stronger.
If DocMetrics becomes the system that explains post-send buyer behavior, not just document opens, it stops being a tracking tool and becomes deal intelligence.
That also means the current name may age smaller than the product.
DocMetrics explains the artifact.
Exirra.com fits much better if this expands into the intelligence layer behind deal movement.
Really appreciate this perspective — you’re thinking at a deeper layer than just tracking, and that’s exactly the direction I want DocMetrics to evolve toward.
Since you’ve clearly thought a lot about “post-send behavior,” I’d love to tap into your experience:
If you could design the perfect proposal/docs tool, what are the top features you wish existed — the ones that would genuinely help you understand buyers better and close deals faster, but no current platform gives you?
Not just nice-to-have analytics, but the features that would actually change how you sell.
Happy to hear even the rough ideas — this kind of insight is extremely valuable at this stage.
The biggest feature is not another metric.
It’s interpretation.
A good proposal tool should answer:
is this deal moving
who is really involved
where did interest drop
what silence probably means
what should I do next
Open rate is weak on its own.
Time spent is weak on its own.
Page views are weak on their own.
The value is turning those signals into deal movement.
That’s why I’d be careful with DocMetrics long term.
If the product becomes “proposal intelligence,” the name should not keep anchoring it to documents and metrics.
That may be fine today.
But it gets small fast once the product starts helping sellers understand buyer behavior after send.
This is one of the most valuable perspectives I have received. You articulated exactly what I have been feeling but could not put into words.
The shift from metrics to interpretation — from showing numbers to answering what those numbers actually mean for the deal — that is the real product. And your five questions are the perfect framework for thinking about it. Is this deal moving. Who is really involved. Where did interest drop. What silence probably means. What should I do next.
The name point is also something I am going to sit with seriously. You are right that anchoring to documents and metrics boxes in the thinking before the product even gets a chance to show what it can do.
Thank you for taking the time to share this honestly. This is exactly the kind of thinking that makes the difference.
Glad it helped.
That “metrics to interpretation” shift is the whole thing.
Once the product answers:
is this moving
who matters
what silence means
what to do next
it is no longer a doc tracking product.
It becomes a deal judgment layer.
That is exactly where DocMetrics starts feeling too small.
Not because it is a bad name, but because it points to the artifact instead of the buyer behavior.
If you do decide to explore stronger directions, Exirra.com is the cleanest fit from my side.
It has the sharper, more serious feel this kind of proposal intelligence product needs.
The deal judgment layer framing is exactly right and that is the direction I am heading.
On the name — I appreciate the suggestion and Exirra is clean. But I have learned that the right name comes from customers not from the outside. When the product has proven itself and the category is clear the name will follow naturally.
Right now the focus is on getting real users and letting them tell me what this product means to them. That answer will be more honest than anything I could choose today.
That makes sense for product direction.
But I’d separate customer language from company naming.
Customers can tell you what the product means to them.
They usually should influence positioning, messaging, and feature priority.
But the name has a different job.
It shapes the frame before customers even experience the product.
That is why waiting too long can be risky.
If users first understand it as doc tracking, they will keep describing it that way until you force the frame to change.
So yes, let customers sharpen the category.
But I would not let the current name keep anchoring the product to the smaller version while you are trying to prove the bigger one.