Digital Retailing
High-stakes purchases and complex multi-party buying decisions across consumer and commercial segments.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Outcome & Operations Discovery
Align on revenue goals, showroom-to-online conversion targets, integration constraints, and stakeholder decision criteria.
Discovery Questions
Start with the outcomes you care about
- How many rooftops does your group operate?
- Tell me about your revenue or margin targets for online-originated deals this year, and how they differ from showroom-originated deals
- Name the metrics that will make this pilot a success for you
- Approximately how many digitally-started leads do you expect from a single rooftop in a typical month?
- If the pilot delivered your target conversion and profitability within 60 days, who would have the final authority to approve rollout across other rooftops?
Where the current customer journey breaks and why it matters
- When a shopper starts online and then walks in, which step most often causes the sale to stall?
- Walk me through a recent digitally-started deal that failed, what happened, and why it stuck with you
- How often do price or terms shown online differ from what a customer sees in-store?
- Who on your team currently owns follow up for online shoppers at the rooftop?
- Identify the pricing or process mismatch that would make you stop a pilot immediately
How leadership will decide, and what would make them say yes
- What specific decision criteria will your owner or general manager use to say yes or no after the pilot?
- Who must be involved in the approval chain for budget, legal, and operations?
- Who typically signs pilot statements of work and who approves ongoing budget?
- What budget threshold or internal ROI hurdle would block moving forward?
- If the pilot hits the conversion and margin targets you set, what internal obstacle could still prevent rollout?
Integration realities that will make or break the project
- List the systems that must be connected for the platform to perform core functions for your team
- Do you have API access, a middleware layer, or only file exports for those systems?
- Who in your organization controls credentials and can approve access to test environments?
- How long will IT estimate to provide API credentials and sandbox access once requested?
- Identify a single integration gap that would make the pilot infeasible for your rooftop
Who's going to run this and whether your operation is ready
- When pilots stumble at other rooftops, unclear ownership is usually the cause, who will be the day to day owner at your rooftop for pilot operations and issue triage?
- Do you have a named data owner who can deliver inventory, pricing, and customer feeds on the pilot timeline?
- Walk me through your current inventory feed, how accurate are stock levels day to day, and who fixes exceptions
- How many people from sales, BDC, and F&I can participate in training and the pilot at a single rooftop?
- What resource shortage or single staffing gap would stop the pilot from starting on your timeline
Regulatory, lender, and contractual gates to watch
- Name the compliance checks or lender approvals that must be completed before we can run credit or lender flows
- Have you previously allowed soft credit pulls by third parties and what limits applied?
- Are there state regulations, privacy or consent requirements that would change how we present finance or trade offers to your customers?
- Identify any contract or regulatory issue that would kill the pilot if unresolved
What alternatives are you weighing and what would keep you where you are
- Who else are you actively evaluating to solve online retailing and desking?
- Which option do you view as the incumbent or default approach today?
- Has anyone on your team proposed building this capability internally rather than buying it?
- What would have to be true about your current approach for you to keep it instead of switching to a new platform?
- If we cannot meet your top integration or metric target, which alternative would you choose?
Pilot acceptance criteria that would make the decision obvious
- If you had to name one measurable pilot outcome that would make you sign for rollout that week, what would it be?
- Which pilot length feels reasonable to you, 60 or 90 days?
- List the metrics that must be reviewed daily, weekly, and monthly during the pilot
- Who will chair the weekly performance review and who can authorize changes to pilot scope?
- What exit triggers or remediation steps should we plan for if targets are missed at mid pilot?
Concrete next steps, timeline, and the information we need now
- What is the earliest date your team can commit to providing API credentials and a test environment?
- List the signed documents or approvals required before integration work can begin
- What meeting cadence and attendee list would make governance efficient during the pilot?
- If we provided a deployment plan in three business days, who would be responsible for reviewing it?
- What would make your leadership want to accelerate a decision after the pilot completes
-
Solution Experience
Walk through how the platform shortens showroom visits, structures deals online, and maps to the buyer's sales and F&I workflows using real scenarios.
Solution Experience
- Solution Experience — Shortening Showroom Visits and Structuring Deals Online
- Confirm the current state and cost
- You confirm the demonstrated workflow shortens showroom visits and maintains or improves F&I penetration compared with current walk-in deals.
- Provide API access details, DMS/CRM connector documentation, and a sample of the last 30 digitally-started or comparable deals.
- Run the sample pilot projection using the provided deals and deliver estimated deltas for lead volume, conversion rate, average time-in-store, and F&I penetration before the follow-up session.
- Map your integration constraints
- You agree that the proposed integration approach fits within your stated IT constraints or identify the remaining technical blockers to resolve.
- Run a real deal scenario end-to-end
- You agree on the pilot metrics, success thresholds, and the next steps to run a 60–90 day rooftop pilot on a single store.
- Draft the pilot measurement dashboard and propose a pilot kickoff date within two weeks of validated access.
- Demonstrate showroom visit reduction and F&I outcome
- Validate pilot metrics and acceptance criteria
- Forced validation, confirm this maps to your needs
- Solution Experience — Shortening Showroom Visits and Structuring Deals Online
- Solution Experience Deck
- Solution Brief
- meeting
- slides
- document
-
Solution Scope
Define modules (inventory, DMS/CRM, lender connectors, trade-in and F&I flows), responsibilities, pilot metrics, and measurable acceptance criteria.
Scope Configuration
- Connect DMS and sync inventory
- Integrate CRM and route digital leads
- Integrate lender portals for real-time rates
- Configure real-time payment calculator
- Integrate trade-in valuation engine
- Deploy online credit application (soft-pull)
- Map F&I product menu and presentation
- Enable deal desking and summary generation
- Configure pricing rules and incentives
- Train sales and BDC on digital workflows
- Run 60–90 day rooftop pilot deployment
- Provide monthly performance analytics and A/B testing
Scope Questions
Connect DMS and sync inventory
- Do you have API credentials for your DMS to enable VIN-level inventory sync?
- What acceptance criteria will validate inventory sync accuracy (VIN match rate threshold, image availability, and inventory latency in minutes)?
- Which inventory fields must be synchronized (e.g., VIN, mileage, MSRP, dealer price, vehicle condition, images)?
- Who within your team owns the DMS connection and can provide test accounts or sandbox access?
- How often should the inventory feed update during business hours (e.g., real-time webhook, 5-minute, 15-minute)?
Integrate CRM and route digital leads
- When a digital lead is generated from the platform, which fields from the lead (e.g., shopper contact, VIN, offer, credit pre-qualification) must be pushed to the source CRM?
- Confirm whether your CRM accepts leads via API, SFTP, or email, and provide the preferred endpoint type.
- Provide the routing rules for digital leads (e.g., assign to internet sales manager, BDC pool, store ID based on ZIP) and any lead-scoring thresholds.
- List the lead status values your CRM uses that should map to the platform (e.g., New, Contacted, Appointment Set, Sold).
- Specify SLA expectations for lead handoff (e.g., contact within 15 minutes) and any SLA-based automation you require.
Integrate lender portals for real-time rates
- Identify which lender rate feeds or endpoints you currently use (rate sheet API, XML, portal CSV) and whether credentials are available.
- Estimate the acceptance thresholds that will validate lender rate integration (lookup latency in seconds, APR variance in basis points, success rate).
- Describe how lender decision attributes should be mapped into the platform (APR, term, monthly payment, decision code) and whether any lender-specific flags must appear on the deal summary.
- Indicate which lenders require additional consent or a redirect to their portal before a soft credit inquiry and provide their list.
- Assign who will coordinate lender sandbox access and test credentials during integration.
Configure real-time payment calculator
- Select which inputs your pricing model requires for the payment calculator (MSRP, sale price, taxes, fees, trade value, down payment).
- State the dealer reserves or hold amounts that must be applied to payment calculations (e.g., dealer reserve percentage, flat fee per deal).
- Are there state-level tax or documentation rules we must encode for payment accuracy and which states have special rules?
- Outline how manufacturer incentives and dealer discounts should be applied — stackable, expired dates, VIN-level eligibility source (incentive feed vs manual).
- Measure which payment breakdowns are required on the front-end and the printed deal summary (monthly payment, term, APR, total due at signing).
Integrate trade-in valuation engine
- Name the trade appraisal sources you want to use (your in-house appraiser, third-party valuation API, dealer-provided manual valuation).
- Explain the required data flow for trade payoffs and liens — will you provide payoff amounts, or should the platform call a payoff service?
- Share your acceptable tolerance between valuation estimate and final appraised trade-in amount (dollar amount or percentage).
- Flag any dealer policies that affect trade offers (inspection required, conditional offers, appointment required) that should be enforced in the online flow.
- Note the VIN-level data elements required by the valuation engine (VIN, mileage, condition flags, optional photos) and whether photos will be uploaded by customers.
Deploy online credit application (soft-pull)
- Choose which data fields are required on the online credit application before soft-pull consent (SSN last 4, full SSN, DOB, address).
- Record your preferred consent language for the soft-pull and whether you have an existing consent form that must be used.
- Pinpoint the credit bureau soft-pull endpoint type your dealer compliance requires (full credit report prohibited, soft inquiry only) and any state-specific disclosure requirements.
- Schedule how credit pre-qualification results should be delivered to the BDC or internet sales team (instant push, daily report) and any redaction requirements for sensitive data.
- Upload or indicate the compliance documents (FCRA disclosures, privacy policy) we must reference during application flow and who will provide them.
Map F&I product menu and presentation
- Do you have a machine-readable F&I product catalog (CSV, API) with price, term, and product codes we can map?
- What presentation order and default upsell tiers do you prefer for F&I products on the product menu (e.g., service contract first, GAP second)?
- Which F&I attributes must be shown on the online menu to match your paper menu (monthly price, single-pay, coverage highlights)?
- Who will approve the final F&I menu copy and pricing before go-live, and what is their approval SLA?
- How should F&I opt-in/opt-out choices appear on the deal summary and printed contracts for compliance audits?
Enable deal desking and summary generation
- When generating a deal summary, which documents must be included (deal worksheet, customer offer, credit pre-qual, F&I selections)?
- Confirm the desking rules we should enforce (minimum gross, holdback handling, reserve caps) and provide the calculation examples.
- Provide the required fields to populate the printed buyer summary and retail installment contract (buyer name, VIN, sale price, taxes, APR, term).
- List who on your team signs off on final printed summaries and the signature flow (e-signature, in-person sign).
- Specify the format(s) required for exported deal summaries for your DMS (PDF, XML, CSV) and any field ordering constraints.
Configure pricing rules and incentives
- Identify the pricing inputs we should use for rule calculations (floor price, MSRP, advertised price, market adjustment).
- Estimate the frequency of incentive updates and whether you have an incentives feed we can subscribe to (daily, weekly, manual).
- Describe how dealer-specific repricing should apply (store-level overrides, group-level floors, time-limited discounts).
- Indicate any thresholds for automatic price overrides (e.g., approval required if discount exceeds $1,000 or %).
- Assign who will own pricing rule changes during the pilot and their escalation path for exceptions.
Train sales and BDC on digital workflows
- Select which roles should attend training sessions (internet sales manager, BDC agents, sales consultants, F&I manager).
- State preferred training formats and cadence (live workshop, recorded modules, roleplay sessions).
- Are there existing scripts or BDC templates you want us to incorporate into the online lead handoff?
- Outline KPI targets for trained staff during the pilot (contact rate, show rate, digital-to-sale conversion) and the reporting cadence.
- Measure readiness by listing the criteria that confirm staff can handle digitally-started deals (number of practice deals completed, certification).
Run 60–90 day rooftop pilot deployment
- Name the rooftop store for the pilot and confirm the single-store scope and any multi-dealer exceptions.
- Explain the target pilot population and traffic sources (organic website visitors, paid channels, CRM retargeting).
- Share the pilot timeline milestones you require (integration complete, staff training, soft launch, full pilot start).
- Flag any operational constraints that could pause the pilot (holiday sales events, inventory shortages, vendor audits).
- Note the measurable acceptance criteria for pilot success (unique digital leads generated, digital-to-showroom conversion uplift %, average minutes reduced in-store) and the exact thresholds that define success.
Provide monthly performance analytics and A/B testing
- Choose which KPIs you want in the monthly analytics package (unique leads, conversion rate, average deal gross, F&I penetration).
- Record how you prefer A/B tests to be run (variant percentage split, duration, metric to evaluate).
- Pinpoint the access level for analytics dashboards (store-level, group-level, read-only).
- Schedule the monthly analytics delivery method and meeting cadence (automated report + review call, dashboard access only).
- Upload or identify the financial fields needed to calculate per-deal profitability in reports (adjusted gross, holdback, incentives applied).
-
Mutual Commit
Finalize commercial terms, pilot duration and metrics, responsibilities, and any legal or operational dependencies.
Agreement Modules
- Subscription Agreement (Order Form)
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Pilot Metrics & Acceptance Addendum
- Data Processing Agreement (DPA)
- Integration & Connector Addendum
- Service Level Agreement (SLA)
- Change Order Agreement
-
Deployment
Lock readiness facts and configuration values before execution begins.
-
Pre-Deployment Readiness
Capture concrete readiness facts — API access, test environments, data owners, and scheduling for integrations and training.
Pre-Deployment Questions
Environment and site access
- Which environment(s) will the buyer use for the pilot (select all that apply)?
- Which integration endpoints are currently available to the deployment team right now? Select all that apply (inventory, DMS, CRM, lender portals, trade-in valuation).
- If any endpoint above is not yet available, what target date will access (API keys/test accounts) be provided to the deployment team? Please give a date — we use this to schedule integration and test windows.
Data and configuration
- Which configuration domains are already decided and approved by the buyer (select all that apply)?
- Named owner for data and mapping approvals — provide the person who will sign off on final mappings (name, role, email). This person must attend the mapping session.
- Are any bulk data imports or migrations required before pilot (select all that apply)?
People and ownership
- Integration lead (IT owner) — who will be the deployment team's technical point of contact (name, role, email)?
- Business lead (internet sales / BDC owner) — who owns process change and day-to-day pilot operations (name, role, email)?
- Operations approver (GM / dealer principal) — who approves go/no-go decisions and pilot acceptance criteria (name, role, email)?
Timing and constraints
- Target pilot start date and expected pilot window (we expect a 60–90 day pilot). Provide start date and whether you expect a 60, 75, or 90 day duration.
- Are there any scheduling constraints or compliance gates that will block integrations, test transactions, or training during the pilot? (e.g., blackout sales dates, IT maintenance windows, security review timelines)
- If constraints exist, provide the specific date ranges or owning team(s) so we can build the deployment calendar (e.g., 2026-09-10 to 2026-09-20 — IT change freeze; Security team — contact: name@domain).
-
Configuration Details
Lock exact configuration values the deployment team will use — inventory mappings, pricing rules, lender sources, credit-pull settings, and F&I menu mappings.
Configuration Details
Environments & Endpoints
- Enter the production instance name (exact string used in deployment manifests; e.g., 'dealer-xyz-prod')
- Enter your production API base URL (format: https://your-subdomain.example.com; this exact URL is used by integrations)
DMS & Inventory Integration
- Select the DMS integration type the buyer will connect (consumed by the DMS connector step)
- If you selected 'Other' for DMS integration type, enter the exact integration description the deployment should use (leave blank if not applicable)
- Select the inventory source the platform will consume (this value drives inventory connector selection)
- Enter the exact inventory identifier field name used in your source system (stock number field name or column header; deployment will map this verbatim)
Pricing & Deal Rules
- Select the pricing rule variant the deployment should enable (the build will implement this variant)
- Enter the dealer markup percentage to apply to used-vehicle cost when 'Dealer-cost + markup' is selected (numeric, percent; Default is 5)
Lender & Credit Settings
- Select the lender source(s) the platform will use (choose one or more; consumed by lender connector configuration)
- Choose the credit-pull workflow the deployment should implement (this controls consent language and API flows)
- Enter the maximum number of soft-pull attempts before the platform requires a full application (numeric; Default is 3)
F&I Menu & Mappings
- Select the F&I product source the deployment will import and map (consumed by F&I menu mapper)
- Select the F&I menu mapping mode the deployment should use (how products are matched during import)
Integration Authentication & Sync
- Select the integration authentication method for external connectors (provide non-secret identifiers; secrets exchanged out-of-band at kickoff)
-
Pilot Launch & Integration
Execute technical integrations, staff training, and a 60–90 day pilot with clear owners, milestones, and a performance measurement cadence.
-
-
Success
Review pilot outcomes against agreed metrics, capture issues and enhancement requests, and plan rollout or optimization steps.
Success Reviews
- Go-Live Health Check (weeks 1-4)
- First Measurement Review (weeks 4-10)
- Pilot Acceptance Gate (around day 90)
- Quarterly Success Review (ongoing)
Issues & Enhancements
- Schedule targeted refresher training sessions for roles where adoption or handling of digitally-started deals is weak.
- Secure a documented acceptance decision or a conditional acceptance plan with explicit remediation timelines.
- Capture any defects or enhancement requests discovered during audit for prioritization in the ongoing cadence.
- Publish the acceptance determination and the supporting evidence package to the shared workspace.
- Create remediation tickets for any failed criteria with clear success tests and resolution target dates.
- Compile an enhancement request list surfaced during acceptance for prioritization in the quarterly review.
- Performance trend review
- Confirm whether digital-to-showroom conversion rate and F&I penetration are sustaining at or above Solution Scope targets.
- Ensure all high-priority defects and conditional remediations are progressing toward closure with realistic timelines.
- Agree a prioritized set of operational and configuration changes for the next quarter.
- Publish the quarterly performance summary with metric calculations and any data anomalies noted.
- Create prioritized work items for the top enhancement requests and schedule configuration windows as needed.
- Reconfirm success criteria and owners
- Confirm technical integrations are live and stable enough to collect meaningful pilot data.
- Identify and assign remediation actions for any blockers preventing basic platform use.
- Confirm training gaps and schedule any follow-up sessions required before the first measurement window.
- Document and publish the list of open technical defects with reproduction steps and desired resolution dates.
- Collect and share a baseline export of initial usage logs and incomplete checkout counts for trend analysis.
- Schedule follow-up hands-on training for identified user cohorts and record completion status.
- Present first-window metrics and data sources
- Establish whether unique leads generated and digital-to-showroom conversion rate are moving toward the Solution Scope targets.
- Agree a concrete remediation plan with timelines to close the largest gaps before day 90.
- Confirm the dataset and reporting cadence that will be used at the acceptance gate to avoid disputes.
- Produce a validated metric dashboard export that defines each metric calculation and its source systems for acceptance review.
- Implement prioritized configuration or integration fixes identified in the meeting and record completion dates.
- Prepare a sample set of digitally-started deals to be used as audit evidence at the acceptance gate.
- Restate acceptance criteria and evidence package
- Produce a clear pass or fail determination for each acceptance metric recorded in Solution Scope.
- Deployment and integration validation
- Present outcome data per criterion
- Gap analysis and root-cause diagnosis
- Open issues burn-down
- Agree corrective actions and timelines
- User onboarding and role access check
- Enhancement request prioritization
- Document acceptance decisions
- Operational improvements and training refresh
- Agree remediation and conditional acceptance items
- Confirm readiness criteria for acceptance gate
- Early usage signals and error triage