Why we moved Agreement Sheets from Prints to Quote
The business reason for moving a familiar dealership document—and the screen-to-PDF details the move exposed.
Read the build noteLotPro build notes
The decisions behind the dealership decision layer.
19 public-safe build stories about inventory, chat, templates, tasks, links, accessories, workspaces, calculators, CRM-side tools, Android calls, customer sharing, and controller access.
19 build notes
Specific problems, product decisions, results, and current limits.
Build stories describe implemented work. Pioneer previews explain work still being evaluated. Design notes make future direction explicit.
Share the choice—not the dealership’s private screen
Why remote collaboration needs a separate customer surface instead of a cropped employee workspace.
Read the build noteHow LotPro Companion uses CRM fields without becoming another CRM
Why the extension reads a narrow set of page fields, keeps the lead in place, and varies by supported CRM page.
Read the build noteWhy one dealership context needs more than one screen
How the web workspace, CRM companion, and Android dialer divide the job without discarding the record.
Read the build noteWhat multi-SIM Android phones changed in LP Phone
The line history, call-state, and post-call details that turned a call button into an Android dialer project.
Read the build noteWhy LotPro is being built for keyboard, controller, and TV
The foundation for spatial focus and shared-screen operation—and the difference between direction and finished coverage.
Read the build noteFour dealership calculators, one shortcut
Why ordinary math, date, amortization, and income questions belong beside the conversation that needs them.
Read the build noteTranslate the message without breaking the merge fields
How language support protects placeholders, original text, and cross-tab freshness.
Read the build noteAccessories that fit the vehicle—and the conversation
How trim compatibility, visual choices, dealership pricing, and the customer sheet became one Honda workflow.
Read the build noteA vehicle card should answer the next question
Why inventory actions belong on the selected unit instead of in another utility menu.
Read the build noteCompare the decision—not the spreadsheet
How a dense payment matrix brings terms, cash due, products, and warnings into one live comparison.
Read the build noteChat should bring the context with it
Why a dealership conversation needs the vehicle, document, knowledge, and next task close by.
Read the build noteThe shortlist should follow the salesperson
How pinned inventory moved from one browser moment into a store-scoped employee tool.
Read the build noteBuild the operating board your dealership actually uses
Why Workspaces combine live grids, sources, column access, and inline decisions without pretending every spreadsheet is safe.
Read the build noteA template library is dealership strategy—not canned text
What preserving more than 180 working templates taught us about reusable follow-up decisions.
Read the build noteSync the feed without surrendering local judgment
Why a workspace should show the change before imported data becomes the new truth.
Read the build noteA short link that still knows which vehicle you meant
How dealership scope and the active inventory source make a compact link more useful than a shortened string.
Read the build noteOne inventory view, regardless of where the feed comes from
Why provider differences belong behind a shared inventory boundary instead of inside every product module.
Read the build noteFollow-up should become repeatable work—not another reminder
How task blueprints, recurring instances, and visible ownership turn a decision into execution.
Read the build note