Home Services Work About Blog Pricing Message on Telegram → Get a Free Audit →
← All work Custom business software

FLW [CRM]

We tapped into 25+ years of auto dealership experience to build the CRM that fits small & medium dealers perfectly. No VinSolutions or eLEAD bloat, just a streamlined yet feature-rich CRM and desking tool.

When a business outgrows the software it can buy, we build the software it needs. This one runs a car dealership: every enquiry in one place, and the answer to what would my payment be on screen in a single click.

Year
2025–2026
Role
Product, design, architecture, build, hosting, deploys
Live
Private — dealer login
7
enquiry sources, one inbox
6
live numbers above the fold
1
click from enquiry to deal
6
payment options at a glance

Same team, same standard, one level up. If a spreadsheet and a shared inbox are running something important in your business, this is what replacing them looks like — designed, built, hosted and maintained by the people who made it.

KSR Auto Sales was running enquiries out of a shared inbox and inventory out of a spreadsheet. Enquiries arrived from several places in several formats, so answering one meant retyping it first. Nobody could say which vehicle had been sitting longest without opening two systems and doing the arithmetic by hand.

01

Designed like a product, not an admin panel

Business software is usually ugly because nobody decided it shouldn't be. This has a considered palette, real typographic hierarchy, cards that group what belongs together, and numbers big enough to read across a desk. It is used all day, every day, so it was designed to be pleasant to look at — which is not a luxury when it is the screen someone stares at for eight hours.

02

The screen opens on the decision

Active enquiries, month-to-date sold, close rate, live inventory, pending sales and volume sit above the fold. Underneath: follow-ups due today, and a panel ranking stock by how long it has been on the lot. Nobody has to go looking for the state of the business — it is the first thing on screen.

03

An enquiry arrives and files itself

Enquiries come from seven different places — the website, walk-ins, phone calls, listing sites, referrals, Facebook and repeat customers — in several different formats. They are normalized into one record, tagged with where they came from and what the customer asked about, and are workable the moment they land.

04

One click from enquiry to deal

Every row carries an Open Desking button that takes the customer and the vehicle straight into the deal screen. No re-keying a name, no hunting for a stock number. That one button is the reason these are one system instead of two.

05

The customer's actual question, answered on screen

Desking prices the whole deal in one view — price, add-ons, warranty, trade allowance and payoff, fees and tax — then shows the monthly payment at two terms against three down-payment options at once. The only question the customer really asked, answered without leaving the screen.

06

Built so it can be handed over

Standard Python and Flask, a plain SQL database, version-controlled migrations, and deploys that run from a push. Nothing exotic, nothing that needs us specifically. A client should be able to hire anyone competent and have them find their way around in an afternoon — that is a fairness question, not a technical one.

  • Python
  • Flask
  • SQLite
  • SQLAlchemy
  • Alembic
  • Jinja2
  • PythonAnywhere
  • GitHub Actions
  • Cloudflare

Google PageSpeed Insights, 29 August 2026. Median of five runs, measured at this site's own address. Speed is the desktop figure. Where SEO, accessibility or best practices differ between mobile and desktop, the lower of the two is the one shown.

0
Speed, desktop
0
Speed, mobile
0
Best practices
0
SEO
Largest contentful paint
0.9 s
First contentful paint
0.7 s
Speed Index
1.0 s

Seven sources, one shape

A referral, a Facebook message and a listing-site webhook arrive in three completely different formats. Left alone that becomes three habits, three places to look, and enquiries quietly going cold in whichever one nobody checks. Normalizing them at the door is what makes a single screen possible — and the source stays visible afterwards, because where an enquiry came from is the most useful thing to know when you are deciding who to call first.

When the obvious suspect is innocent

Enquiries from one marketplace stopped arriving, and the software was the obvious suspect. It was innocent. The domain had a stray DNS record sitting alongside its mail records — technically invalid, tolerated by some mail servers and rejected by stricter ones. The strict ones found no mail server, fell back, hit a closed door, and never accepted the mail, so nothing ever reached the application to log. We moved the address to a clean subdomain rather than deleting the record the website depends on. Knowing where to look when the obvious suspect is innocent is most of what you are hiring.

Every business has a version of this. A contractor with estimate requests across email, voicemail and a form. A dental practice with new-patient enquiries in three places. A retailer whose stock lives in a spreadsheet somebody has to remember to update. When the off-the-shelf tools nearly fit but not quite, and the gap is being covered by somebody's memory, that gap is what custom software is for — and it does not have to be a six-figure project to be worth doing.

Want a site that does this for you?

Start with a free audit — a written report on how your site performs today and what it would take to put it in this company. No pitch attached.

Get a free audit →