Sales teams on ERPNext hit a wall the moment a Quotation needs to leave the system. Native ERPNext lets you build a Quotation, attach a Print Format, and email a PDF — but there is no branded web proposal, no shareable link that works without a login, no way to know if the buyer even opened it, and certainly no legally-meaningful e-signature. Reps end up exporting PDFs, chasing DocuSign or PandaDoc in a separate tab, then manually re-keying an accepted deal back into a Sales Order. That gap is where deals stall and where your ERPNext data drifts out of sync with what was actually signed.

ECOSIRE builds a proper Frappe app — its own module, installed on your bench with bench get-app and bench install-app — that closes that gap end to end without leaving ERPNext. We add DocTypes such as Proposal, Proposal Template, Proposal View Log, and Signature Request that hang off your existing Quotation. A rep composes a branded proposal from a reusable Proposal Template (Jinja-rendered, using your letterhead, terms, and pricing pulled live from the linked Quotation), then publishes it to a tokenized public URL served by a Frappe website route and a @frappe.whitelist(allow_guest=True) method. Every open, scroll, and download writes a row to Proposal View Log, so the rep sees "viewed 3 times, last opened 2 hours ago" instead of guessing.

Signature capture is embedded in that same page: the signer draws or types their signature, which is stored as a Signature Request child record with the captured image, signer name/email, timestamp, and IP address for an audit trail. On submit, a hooks.py doc_events handler (or a dedicated server script) flips the proposal state and — this is the payoff — programmatically creates or submits the downstream Sales Order from the accepted Quotation, so an accepted proposal becomes a real ERPNext document with zero re-keying. Decline routes back to the owner with the reason logged. Notifications for view/open/accept/decline are delivered through Frappe's email queue and optional real-time toasts, and a scheduler event (scheduler_events in hooks.py) sends follow-up nudges on proposals that have been viewed but not signed after N days.

Because it is a native app, everything respects ERPNext's permission model: DocType permissions and role profiles control who can send and who can see whose proposals, client scripts drive the compose UX inside the Desk, and the whole thing is reachable over the standard Frappe REST API and whitelisted methods for any portal or automation you already run. It is built and tested against Frappe/ERPNext v15 and v16.

This is a build-to-order product, not a marketplace download. After a short scoping call we confirm your exact requirements — branding, template structure, which Quotation fields flow into the proposal, your Sales Order automation rules, and any approval steps — then build your version, run UAT on a staging site, install it on production, and hand over the git repository. Typical delivery is one working week from confirmed scope, and every deployment includes a post-go-live support window.