Real leads. Clear next steps.
A focused workspace for serious enquiries, qualified opportunities and paid wins.
Every stage is supported by buyer evidence.
Lead register
0 records| Company / contact | Stage / health | Value | Next step | Owner |
|---|
Your next sale starts with a real conversation.
Register a named contact, a reachable phone number and evidence of the enquiry. Stronger stages unlock as the buyer commits.
Qualification policy & research basis
Designed for ImageFirm · researched 16 October 2026. The thresholds below are proposed operating rules, not universal benchmarks. ImageFirm wordmark and navy/teal palette are a proposed identity because no official brand assets were supplied.
| Approach | Benefit / limitation | Applied here |
|---|---|---|
| BANT | Simple budget, authority, need and timing checks. Can oversimplify complex buying. | Four concrete qualification fields; unknown answers remain in earlier stages. |
| MEDDIC | Deeper buyer, pain and decision-process context; heavier administration. | Buyer-stated need, named authority and decision process. Full MEDDIC is intentionally unnecessary for this compact tool. |
| Pipeline rules | Required stage properties improve consistency. Populated fields alone do not establish truth. | Stage gates, duplicate checks, dated buyer evidence, action ownership and visible change history. |
Counting rules. Only stage 03 counts in qualified pipeline, and only while the next action and expected buying date have not passed and meaningful buyer contact is no more than 14 days old. Earlier stages can have an indicative value but contribute zero. Stage 04 contributes its deposit only to deposits recorded, not to open pipeline. All money uses one workspace currency; changing it relabels amounts without conversion.
Working discipline. Review high-stage evidence and deposits against original records weekly. Archive lost or unqualified leads with a reason. The 14-day threshold is an ImageFirm design recommendation. Local history, agent names and backups are editable by someone controlling this device; independent approval, verified payments and tamper-resistant auditing require an authenticated shared system.
Primary sources: Salesforce: BANT vs. MEDDIC · Salesforce: BANT · HubSpot: conditional stage properties · HubSpot: pipeline rules