← → to navigate · F fullscreen · P to print/PDF
Platform rebuild · Proposal

Own your data.
Sell it with confidence.

A ground-up rebuild of the Motology fitment platform — the database, the API, and the admin — engineered for the German deal and everything after it.

Prepared for Duncan · Motology ·by CallCore Ltd
Where things stand

Your database is
held hostage.

The current platform works — but it’s controlled by TekFirst, it’s slow, it lets bad data in, and it can’t do what the German deal needs. Here’s the honest picture.

The situation today

Eight problems standing between you and the deal

🔒
Held hostage by TekFirst
You can’t change your own system without going through them — and you’re not a priority.
⚠️
Dirty, loosely-validated data
A tyre pressure sits in a speed-rating field. Loose validation lets bad values in that directly undermine your “perfect fit” USP.
🐌
Slow under reasonable load
Queries load thousands of rows to return twenty, hogging memory and bandwidth. A few simultaneous “small” requests can take it down.
🧨
Risky, manual upgrades
Strong evidence of hand-edited database changes — 82% of tables are dead noise left behind by risky manual tinkering.
🇪🇺
Not Europe-compatible
The API can’t be queried the way European customers work — no K-Type, HSN/TSN or VIN lookups.
💳
No real metering or billing
“Per-click” usage is inferred from log lines and silently under-counts under load — you may be under-billing.
📄
No API documentation
New customers can’t self-serve an integration — every one is a bespoke, hand-held effort.
🖥️
Dated admin experience
Poor visual and information hierarchy makes day-to-day editing a chore for your team.
The evidence, in numbers

This isn’t a hunch — it’s in the data

Pulled directly from your live database and application code.

82%
of tables are dead backups & scratch — ~185 of 226, holding ~13 million stale rows
1,354
columns typed NVARCHAR(255) — enums, numbers & dates all stored as loose text
6×
the same tyre rating written six different ways — data no customer can trust as-is
0
durable usage records, API docs, or automated schema migrations
The proposal

A platform you own,
built to sell.

Eight problems, eight answers. Modern engineering, your brand, your infrastructure — and no more TekFirst.

What we’ll build

Every problem, answered

✦
Brand-new, compact database
Clean, correctly-typed, ~40 real tables instead of 226. Yours, in your cloud.
✦
Strict validation, end to end
From the UI to the database, bad values are impossible to enter. Clean once — stays clean forever.
✦
System-managed upgrades
Controlled, tested, versioned migrations. No more risky manual tinkering with production.
✦
Repeatable Load / Clean / Insert
Extensively tested migration from the old database — no information loss, replayable on demand.
✦
High-performance API
Purpose-built and lean — a million requests an hour won’t even touch the sides. Real metering & billing built in.
✦
Europe-compatible & documented
K-Type, HSN/TSN & VIN lookups, backwards-compatible, with no-brainer docs customers integrate in minutes.
✦
Data Health screen
Surfaces every invalid value for one-click, one-time fixing — the mess made manageable.
✦
Admin that “just makes sense”
A slick, modern workspace with real information hierarchy your team will actually enjoy.
Concept
The new admin

Built around the screen your team lives in

At a glance

Front and rear fitments in banded columns — staggered setups read instantly, no legend needed.

Engineer-friendly

Sizes, offsets and codes set in monospace, lined up so anything out of place jumps out.

One clear action

Edit a fitment right beside the grid — front and rear laid out like the car itself.

New fitment workspace concept
Concept
The new admin

Find any vehicle in a keystroke

Jump

Know the FTID or model? Type it and you’re there — search is a Ctrl+K command, not a permanent sidebar.

Discover

Just browsing? Narrow down by Year → Make → Model.

Resume

Recent vehicles are one click away, so you pick up exactly where you left off.

Vehicle lookup command palette concept
Concept
Data Health

20 years’ worth of issues — fixed in an afternoon

Why

Your data is the product. Its accuracy is the sale. Bad values quietly erode both.

What it is

A screen listing every value the new system rejected, grouped so one decision fixes every affected row.

The end result

1,122 bad rows → ~45 decisions. Fixed once, remembered forever, and structurally impossible to reintroduce.

Data Health cleanup screen concept
Performance

“A million requests an hour won’t even touch the sides”

✘
Today
Loads thousands of rows to return twenty. A handful of concurrent requests exhausts memory and falls over — swallowed errors show as empty results.
✔
Rebuilt
Returns exactly what’s asked for. Purpose-built metering & rate-limiting so no single consumer can ever take the platform down.
1M/hr
target throughput, comfortably
Metered
durable, auditable per-customer usage — real billing
Guarded
rate limits protect uptime for everyone
Backwards compatibility

buywheels keeps working — TekFirst need do nothing

How it works today

Your fitment data is exported as CSV files and dropped onto an FTP folder on a schedule. The widget imports them on its side.

What we do

Reproduce that export exactly — same files, same format, same drop — scheduled reliably by Hangfire.

The result

The widget keeps running through cutover with zero changes on TekFirst’s side. One less thing they control.

Hangfire dashboard showing scheduled buywheels CSV export jobs
The new API

Documentation customers integrate against in minutes

Europe-compatible

Look up by K-Type, HSN/TSN or Year-Make-Model — and extensible to VRM/VIN via a lookup provider — the way European customers actually work.

Self-documenting

Rendered live in Scalar with full names, descriptions, field & model docs and enum values — no PDF, no guesswork.

Ready first

Stub endpoints hosted early so the Germans build and steer against it while the rest is built underneath.

Scalar API reference for the Pro-Fit vehicle fitment API
Monitoring & peace of mind

You’ll know before your customers do

Modern observability baked in from day one — not bolted on after something breaks.

◎
Error logging & alerting
Every exception captured in Sentry with full context — caught and understood, not silently swallowed.
◎
Performance metrics
Response times, throughput and slow-query visibility, continuously.
◎
Uptime monitoring
The API and site watched around the clock, with alerts if anything drops.
◎
Scheduled-job monitoring
Cron/Hangfire jobs — like the buywheels export — verified to actually run, every time.
How it unfolds

Six milestones — a live demo at each, roughly every fortnight

M1New database, Official FitmentTree Schema V1 & nightly feed to LipKoWeeks 1–3
Demo: LipKo pulling your live nightly export into their system — proving the HSN/TSN mapping against real chassis. Repeatable ETL, mess surfaced in Data Health.
M2Consumer query API — hosted & documentedWeeks 4–6
Demo: a live, documented API — a real K-Type lookup returning real fitment.
M3Write-back, metering & buywheels kept aliveWeeks 7–8
Demo: LipKo writing K-Type/HSN-TSN back with a full audit trail; usage metered; the buywheels export running untouched.
M4FitmentTree Pro — read-only for customersWeeks 9–11
Demo: a customer browsing the whole catalogue — search by K-Type, make or model.
M5FitmentTree Admin — editing & validationWeeks 12–14
Demo: your team editing, with bad data blocked at the door.
M6Harden, monitor & cut over → liveWeeks 15–16
Demo: live in production, monitored — a clean break from TekFirst.
Investment

Fixed price. Paid as it’s built.

£40,000
fixed — six milestones, a live demo at each.
  • ✓ A clean data feed LipKo can build against in ~3 weeks
  • ✓ Fully live and off TekFirst in 3–4 months
  • ✓ You own the code; it runs in your cloud; full handover
  • ✓ A rock-solid platform, forged by 26 years of hands-on experience
Payment schedule · you pay for what you’ve seen delivered
On signing deposit—£4,000
M1 · New DB, Official FT Schema V1 & LipKo feedwk 3£4,000
M2 · Consumer query APIwk 6£7,000
M3 · Write-back, metering + buywheelswk 8£5,500
M4 · FitmentTree Prowk 11£6,500
M5 · FitmentTree Adminwk 14£7,500
M6 · Harden + cutoverwk 16£5,500
You’re financing a build, not gambling on it — a demonstrable step, and a payment, roughly every fortnight.

Independence.
Then profit.

A platform that’s yours, fast enough for any customer, accurate enough to stake your name on, and ready for the Germans.

CallCore Ltd × Motology·Let’s build it.
1 / 16