Most B2B sites convert 1-3% of traffic, which means the other 97% leaves no trace beyond an anonymous line in your analytics. ERPNext gives you a strong CRM — Lead, Opportunity, Contact, and the sales pipeline — but it has no idea who those anonymous sessions were or which of them are showing real buying signals. Native ERPNext Web Form submissions and the Website module only capture people who already raised their hand. There is no IP-to-company resolution, no bot filtering, no intent scoring, and no way to surface a warm account before it fills in a form. That is exactly the gap this build fills.

We build a proper Frappe app (installable via bench get-app / bench install-app) with its own module and a set of purpose-built DocTypes: a Web Visitor (the resolved company/organization), a Visitor Session, a Page View child log, an Intent Signal, and an Intent Score Rule for configuring weights. A lightweight tracking snippet posts pageview beacons to a @frappe.whitelist(allow_guest=True) REST endpoint. On ingest, a server-side pipeline runs the raw IP through a bot/datacenter filter (reverse-PTR + ASN/datacenter range checks) so crawler and hosting-provider noise never becomes a "lead," then performs IP-to-company resolution against your chosen data provider and writes the enriched Web Visitor record. hooks.py doc events and scheduler events drive scoring: each page carries a weight, and an RFM/time-decay model (recency, frequency, and depth of visit) computes a rolling intent score so a company that reads your pricing page three times this week ranks above one that bounced off a blog post last month.

When a visitor crosses a configurable intent threshold, a server script auto-creates or enriches an ERPNext Lead (deduplicating on company/domain so you never double-create), stamps the source, attaches the full visitor journey timeline, and — optionally — assigns it via ERPNext's native Assignment Rules and fires a notification to the owning sales rep. Because everything lives in standard DocTypes, your team works hot accounts inside the ERPNext desk they already use: list views, filters, reports, dashboards, and the normal Lead -> Opportunity conversion flow. Role-based permissions and permission-level (perm-level) field controls keep raw visitor data scoped to the right role profiles, and every whitelisted method is permission- and rate-checked.

Delivery is build-to-order. After a short scoping call we confirm exact scope — which data provider, your intent weighting, dedup and routing rules, and target Frappe/ERPNext version (v15 or v16) — then build on a staging bench for UAT. Typical delivery is one working week from confirmed scope. You receive the full source, a documented install, a git repo handover, training, and a post-go-live support window. There is no instant download and no per-visitor SaaS tax on top; you own the app and it runs on your bench.