Marketing teams running ERPNext know the gap well: your campaigns generate inbound interest, but the path from a website visitor to a clean, assigned Lead DocType is broken. The native ERPNext Web Form is a serviceable admin tool, but it lives on your Frappe site's domain, offers no embeddable snippet for an external marketing site, has no built-in spam defense beyond basic guest permission checks, and drops UTM parameters and referrer context on the floor. So teams paper over it with Typeform, HubSpot forms, or Google Sheets, then re-key leads into ERPNext by hand — losing attribution, duplicating records, and delaying follow-up past the window where the lead is still warm.

We build a proper Frappe app that closes that gap end to end. The core is a lightweight embeddable JavaScript widget you drop onto any external site (WordPress, Webflow, a static landing page) with a single <script> tag; it renders your configured form, validates client-side, and posts to a @frappe.whitelist(allow_guest=True) method over the Frappe REST API. On the server, a Lead Capture DocType and controller normalize the payload, enforce a honeypot field plus Google reCAPTCHA v3 verification, de-duplicate against existing Lead/Contact records by email or phone, and write a first-class ERPNext Lead with the full UTM set (utm_source, utm_medium, utm_campaign, utm_term, utm_content), landing-page URL, and HTTP referrer stored as custom fields. A hooks.py doc event on Lead after_insert runs your routing rules — round-robin, territory, product interest, or campaign-based assignment — via a server script so hot leads land in the right salesperson's queue instantly, with an Assignment (ToDo) and notification created automatically.

Landing pages are handled by a drag-and-drop builder implemented as a Landing Page DocType with a block-based layout stored as JSON, rendered through Frappe's Jinja website templating so pages are SEO-crawlable, served on your own domain, and version-controlled. Each landing page binds to a form variant so you can A/B test copy and CTAs while every submission still flows into the same governed Lead pipeline. Permissions are wired through Frappe role profiles — marketing users manage forms and pages, sales users see only their assigned leads — and a scheduler event runs a daily digest and retries any deferred reCAPTCHA or webhook failures.

Because this is build-to-order, nothing is a one-size download. We start with a short scoping call to map your form fields, routing logic, reCAPTCHA keys, and the sites you'll embed on, then build against your Frappe/ERPNext v15 or v16 instance. Typical delivery is 2–4 weeks from confirmed scope. You receive the installable app source, staging UAT, and a git repo handover — ECOSIRE builds it, installs it, and supports it after go-live.