# Owned demand: your own customer base as a demand pool > Most dealers treat their own customer base as an archive and the portals as the demand engine. Owned demand flips the order: when a car is bought, returned or about to become available, it is matched against live customer wishes first, and the first action is a booked meeting inside your own base. **Source:** https://carruslink.com/en/hub/owned-demand **Last updated:** 2026-08-19 ## Short answer Owned demand means the dealership's own customer wishes form a demand pool that is activated before — or alongside — external listings. The model needs three things: structured and dated customer wishes, automatic matching the moment a car is registered, and an agreed deadline for releasing the car to the portals. ## What owned demand is — and what it is not Owned demand is the demand the business already owns: customers in the base with a registered wish for a specific car, a leasing contract about to expire, or a service history that points to a replacement purchase. The demand is known, consent exists, and the contact route is already there. It does not replace the portals. Bilbasen, DBA and the other platforms create new demand the dealership cannot reach on its own. Owned demand is about sequence: what happens during the hours or days when the car is only known internally. The difference between the two channels is not price alone. A match inside your own base starts with known history, a known budget and a named salesperson. A portal lead starts from zero. - Owned demand = known customer, registered wish, existing consent. - Portal distribution = new demand, unknown customer, cold lead. - Both are needed. The sequence is what can be optimised. ## The four prerequisites the model rests on Without all four, owned demand becomes a statement of intent rather than a flow that runs on its own. The first is structured wishes. A wish needs purchase or lease, model and trim, year and mileage limits, budget or monthly payment, must-haves, what the customer is flexible on, and when the car has to be ready. Free-text notes cannot be matched by a machine. The second is freshness. A wish has a creation date, a last confirmation and an expiry date. A wish from last year that nobody has confirmed is not demand — it is noise that destroys trust in the matches. The third is automatic matching. The match must be triggered when the car is registered — at purchase, at return, at expected availability — not when a salesperson remembers to search. The fourth is an agreed release deadline. The dealership decides how long a car works internally before it goes out externally, and the deadline has to be measurable so it can be adjusted instead of guessed. ## The flow from new car to booked meeting The car is registered with VIN, trim, mileage and expected preparation date. That registration is the event that starts everything else. The system matches the car against active wishes and ranks the candidates. The ranking has to be explainable: which criteria are met, which are close, and what deviates. A salesperson who cannot see why will not call. The salesperson receives the match as a task containing customer history, the registered wish and a suggested message. The goal of the call is a booked meeting, not an update. After the agreed deadline the car is released to the portals — automatically, not from memory. If the car already has a confirmed meeting, release can be postponed with a visible reason. - Car registered → match triggered the same moment. - The salesperson gets context, wish and suggested message in one task. - The first success criterion is a confirmed meeting, not a sent email. - Portal release happens on a fixed deadline, not ad hoc. ## Leasing: returned cars and re-leasing are owned demand For leasing the model is especially concrete, because the expiry date is known in advance. A car returning in 60 days is both future stock and a customer who needs a new contract. The same flow covers both sides: the expiring contract is matched against incoming cars, and the returned car is matched against active wishes before it goes to external distribution or auction. The split of roles between leasing company and dealer has to be agreed before the flow goes live: who owns the customer contact, who may reach out when, and which data may be exchanged. ## KPIs that show whether the model works The number of registered wishes is not a result. The metrics below are the numbers the dealership can pull itself and track over time. Define each metric in writing before measuring, and keep the definition fixed. Otherwise quarter-to-quarter comparisons mean nothing. All five numbers can be pulled by the dealership itself. We do not publish industry averages without a documented method and a described data basis. - Wish coverage: share of active customers with at least one valid, confirmed wish. - Match latency: time from car registration to the first match reaching a salesperson. - Owned-demand meeting rate: share of matches that become a confirmed meeting. - Pre-distribution conversion: share of cars sold before external release. - Owned-demand transaction share: share of all deals that start in your own customer base. ## Pitfalls The most common mistake is treating the wish register as a newsletter list. Owned demand works when the customer gets the one relevant car — not a weekly list of the whole stock. The second is skipping cleanup. Without expiry dates and confirmations the register fills with wishes nobody believes in, and salespeople stop acting on matches. The third is consent. Contacting existing customers with marketing content requires a valid legal basis, and that basis must be documentable per customer and channel. ## Frequently asked questions ### Does owned demand mean dropping Bilbasen? No. The portals create demand you cannot reach yourself. Owned demand is about sequence: matching the car against known customer wishes first, and releasing it to the portals on an agreed deadline rather than at random. ### How long should a car work internally before being listed? There is no industry answer we can document. Set a deadline you can keep — typically from a few hours to a few days depending on preparation time — measure conversion before release, and adjust the deadline on data instead of instinct. ### How do we keep the wish register current without spamming customers? Every wish gets an expiry date and a confirmation date. Confirmation happens during a relevant contact — a match, a workshop visit or a contract expiry — not as a standalone reminder campaign. ### Does this require replacing our DMS? No. CARRUSLiNK sits on top of existing DMS, workshop and accounting systems and reads stock and customer data from them instead of replacing them. ### What if several customers match the same car? Matches are ranked and the ranking is visible: criteria met, criteria close, and deviations. The salesperson decides the order — the system suggests, it does not decide. ## See the flow on your own data 30 minutes walking through customer wishes, automatic matching and meeting booking in CARRUSLiNK with your stock and customer types. — CARRUSLiNK · https://carruslink.com/en/hub/owned-demand