01

The interruption is larger than the arithmetic

A customer asks when the first payment would fall. A manager wants to compare two terms. A salesperson needs to convert weekly income into a monthly figure before continuing a form. None of those questions requires a large system, but each can break the conversation if the answer lives in a spreadsheet, a search result, or a calculator app on another device.

The cost is not typing the numbers twice. It is leaving the CRM record, remembering the assumptions, deciding whether an unfamiliar calculator means what the employee thinks it means, and then returning to the original screen without losing the customer’s question. A thirty-second calculation can create several minutes of tool hunting and reorientation.

02

Four narrow instruments beat one vague calculator

The LotPro Dealership Calculator was built as a standalone Manifest V3 browser extension with four deliberately bounded modes. Ordinary arithmetic handles quick totals. Date tools answer offset and first-payment questions. Payment math exposes the term, rate, amount, and resulting estimate. Income conversion keeps the source frequency visible while producing a comparable figure.

Keeping the modes separate makes the assumptions legible. A date calculation should not look like amortization, and an income conversion should not quietly inherit values from a payment screen. Each tool can explain the inputs it accepts and clear its own state. The panel can dock beside the current page or float above it, and Alt+C provides a consistent way to call it without abandoning the active record.

  • Standard arithmetic for the immediate question
  • Date offsets and illustrative first-payment dates
  • Payment and amortization estimates with visible assumptions
  • Gross-income frequency conversion
03

Why this lives beside the work

A calculator does not need access to the dealership’s customer data to be useful. The extension can remain a local utility while the employee decides which figures to enter. That keeps the scope understandable and avoids turning a convenience tool into another system of record. It also means the panel can support a CRM conversation without claiming a formal integration with every page underneath it.

The commercial idea is modest: show what the broader LotPro product values while solving a real, self-contained problem. The extension uses the same dense, decision-oriented design language and can point interested users toward LotPro, but the calculation must remain useful on its own. If the promotion disappeared, the utility should still earn its place beside the browser.

04

The result: answer, compare, return

The intended loop is short. Open the panel, choose the instrument that matches the question, enter the assumptions, compare a change if needed, and close or dock the tool while the underlying dealership screen remains exactly where it was. The employee spends attention on the decision rather than on finding a place to perform the math.

This is a small example of LotPro’s larger product thesis: useful context should survive the movement between tools. In this case the simplest way to preserve context is not to move it at all. The calculator comes to the active page.

05

The boundary on every result

The calculator is a locally installable pre-alpha utility. It is not presented as a Chrome Web Store release, a lender system, an underwriting engine, or a source of tax, payroll, or financial advice. Payment and date outputs are illustrative and can differ from lender contracts, jurisdiction rules, and dealership policy.

That boundary is part of making the tool trustworthy. The extension should make assumptions easier to see and adjust; it should not make a reference calculation look like an approval. Preview feedback is most useful when it tests whether the modes answer real dealership questions clearly, not whether the interface can imply authority it does not have. A strong result leaves the employee more certain about the assumptions and appropriately uncertain about anything only a lender, contract, or policy can decide.

More LotPro build notesBack to all notes