Solution · Proposals
The proposal went out two weeks ago. The nudge is already drafted.
You send a proposal, go back to delivery, and the deal slides. Nobody decided to drop it. Nobody remembered to ask.
Proposals do not fail loudly. They go quiet.
A client who has not opened the document needs a different message than one who opened it twice and said nothing. dpaperwork tracks whether each document was opened, how long the deal has sat in its stage, and what you last said to the client. Then it drafts the message that fits.
It does the legwork. You make the call.
Nothing reaches a client without your yes, and every draft shows what it changed.
Northwind proposal: sent 12 days ago, never opened
Drafted a short follow-up from your last email thread with them. Waiting for your approval.
Approve, edit, or skip
Sent from your own address
Sent, opened, quiet. Each gets its own nudge.
The Pipeline shows every open deal across every client, with how long it has sat in a stage. Documents sent from dpaperwork record when they are opened. The agent combines the two with your recent email and drafts the follow-up. You approve it before it goes.
Knows what was opened
Sent and never opened is a different problem from opened and quiet, so the draft differs.
Written from the history
Drafts use your recent thread with the client, not a generic template.
Sent from your address
Once you accept it, it goes from your own Gmail, so replies land where you already read them.
Same week, different ending
You remember a proposal three weeks late, in the shower.
A quiet proposal is flagged and the nudge is drafted on day seven or whenever you set.
You send the same “just checking in” to everyone.
The message reflects whether they opened it and what you last said.
A reply sits in your inbox and the deal stage never moves.
The reply is logged on the deal and you are asked about the stage.
What’s doing the work
Questions
Leave the call with your first follow-up drafted.
Every quiet proposal, with the nudge drafted and waiting for your yes.