What Makes a Yacht Listing Website Useful?
7 October 2026Before the Yacht Announcement Goes Out
8 October 2026
Marketing presents one enquiry total. Sales presents another. Both reports may be internally correct while answering different questions. Redesigning the dashboard will not resolve that disagreement until the team understands what each number includes.
Imagine a brokerage comparing a campaign export with a CRM dashboard. This is an illustrative investigation, not a client result. The campaign export counts form submissions. The CRM counts unique contacts. A buyer who submits again about another yacht may contribute twice to one report and once to the other.
Write down the question before checking the chart
“How many leads did we get?” leaves several possibilities open. Are we counting submissions, people, enquiries or opportunities? Does a phone call count? Are test entries excluded? Do existing customers belong in the same total?
The right definition depends on the decision. A campaign team may need submission volume; a broker may need the number of active enquiries requiring a response. Give each measure a name that reveals what it counts.
| Measure | Definition to agree | Common source of disagreement |
|---|---|---|
| New enquiries | Enquiry records created during the period | Duplicate submissions or imported historical records |
| Unique contacts | Distinct people under an agreed matching rule | Different email addresses or incomplete identifiers |
| Active opportunities | Records in agreed sales stages at a stated time | A current-state chart compared with a historical snapshot |
| Response time | Elapsed time between specified start and response events | An automated acknowledgement counted as a broker response |
Time is part of the definition
Choose the date that places a record inside a reporting period. Creation date, import date, first contact and stage change describe different events. Also agree on the reporting time zone and the moment a weekly or monthly snapshot is taken.
A report built from today’s status cannot always reconstruct what the pipeline looked like last month. If that historical question matters, plan event records or snapshots before it becomes a reporting requirement. A dashboard cannot recover events that the source system never retained.
Follow a small sample through the systems
Pick a few anonymised records representing ordinary and exceptional cases. Trace their source, identifiers, dates and status changes. Explain where each appears in the reports. This is often easier to review than comparing totals without seeing the underlying rules.
Keep an exception list for missing fields, conflicting identifiers and failed imports. Somebody needs to own the resolution. A chart can display an unknown category, but it cannot decide whether the underlying record is a duplicate or a genuine new enquiry.
Telemetry needs the same discipline
For an app or web portal, define events before comparing activity. A page view, a PDF request and a completed enquiry are different actions. Specify when an event is recorded and whether retries or repeated clicks create additional events. Then connect the analysis to a decision the team can make.
Bilişim Atölyesi develops dashboards, sales reporting and telemetry analysis around agreed data sources. The first deliverable can be a shared definition sheet and a traceable sample, followed by the dashboard. Bring the reports that currently disagree.