Scoring model
Configurable qualification inputs and score rules that turn form context into an explicit decision.
Lead Engine
A configurable operating pack for qualifying inbound demand and routing the right lead to the right owner with explicit rules, executable reference logic and implementation evidence.
STORE ELIGIBLESOURCE INCLUDED12-MONTH UPDATES
WHERE ARE YOU BUYING FROM?
RF checkout uses its own regional RUB price and RF payment rail.
P0 / loading checkout configurationFORMATCODE / CONFIG / DOCS
RUNTIMENODE 20+ / BROWSER
LICENSESTANDARD COMMERCIAL V1
ARTIFACTSHA-256 LOCKED
WHAT IT CHANGES
Turn an inbound form into an operating system.
Lead Engine is not a CRM and it is not a hosted lead platform. It is the logic layer between inbound context and an operational handoff: score what arrived, disqualify what should stop, route what should move and leave a testable record of why.
Because the reference logic is delivered as source, the implementation can be adapted to the project rather than forcing the project into a SaaS workflow.
Disqualification
Hard-stop rules keep non-fit leads out of the routing path before ownership is assigned.
Territory routing
Reference routing logic maps qualified demand to owner and operational handoff.
Regression tests
Executable cases protect scoring and routing behavior while the implementation evolves.
Schema + CRM map
Normalized lead shape and field mapping reduce ambiguity between form, router and CRM.
Scoring playground
A browser-facing playground makes configuration behavior visible before integration.
IMPLEMENTATION PATH
Configure. Prove. Connect.
The pack is designed to move from local configuration into a project integration without changing the core decision model.
01Model
Define qualification inputs, weights, hard stops and routing conditions.
02Exercise
Use tests and the playground to validate expected scoring and route outcomes.
03Integrate
Map normalized lead fields into the form/CRM boundary and connect the handoff.
04Operate
Keep routing behavior under regression coverage as the business rules evolve.
Payment is not entitlement.
The browser starts checkout. Only a verified server-side provider event creates the canonical Order, active Entitlement and immutable license snapshot.
RF-first regional railrefund → revokedprivate delivery
Source modification is allowed.
One production/internal deployment or one client deployment. The resulting project can be handed to one end client. Source resale, redistribution and sublicensing are prohibited.
Read the licensing model12 months of eligible releases.
The purchased version remains licensed perpetually. Later releases become downloadable only after a Store eligibility decision and only inside the entitlement window.
View release decisionsRELEASE LINEAGE
The version number is not the authority.
The Store tracks released, held and audit-pending artifacts separately from the current selling version.
VERSIONSTORE DECISIONARTIFACTDELIVERY
v1.0.0
HOLD
eec520d4d240…
Blocked
v1.0.1CURRENT SELLING
STORE ELIGIBLE
c388766141e1…
Entitled
v1.0.2
AUDIT PENDING
2372237297f4…
Blocked
c388766141e1cce0e474a2d3fa3069de18a44952104781602fa556edf2eaf8ff25,301 bytes / private server storage only. Paid product bytes are never shipped from the public static Store tree.