Platform rebuild · Build progress & roadmap
From a live feed
to the full platform.
Where the Motology rebuild stands today — one milestone delivered, the editor in your hands within the week — and how the rest builds up from there.
Prepared for Duncan · Motology·
by CallCore Ltd·August 2026
How it's built
One platform you own — a suite of sub-apps around a shared core
Not one big program. A shared foundation — the clean database, the import, security, reference data — with focused apps built on top, each delivered and signed off on its own.
◆
Shared platform
Clean, correctly-typed database · re-runnable import + corrections · staff sign-in · curated reference data (makes, K-Type, HSN/TSN).
→
Consumer delivery
The versioned Schema V1 contract and the export that puts the catalogue in a partner's hands. LipKo, live.
✎
FitmentTree editor
The tool your team uses day-to-day to create, curate and publish vehicles and fitments.
⇄
CAM alignment
Its own sub-app: align your fitments to the CAM/UVC catalogue and feed Standard/Optional back to CAM Systems.
⚙
Operations console
Staff-facing config: users, the manufacturer master list, delivery profiles, consumer scoping.
★
Motology Pro
The commercial product — a credit-gated catalogue app + a metered API. Bought via Paddle. Post go-live.
The build, milestone by milestone
Parity first, then the commercial product — delivered in signed-off steps
M1
Foundation & the LipKo feed
Model · database · import · Schema V1 · export
Delivered
M2
FitmentTree editor
The testable core — your team's daily tool
~1 week
M3
CAM / UVC alignment
Its own sub-app + export to CAM Systems
Next up
M4
Operations & config console
Users · master list · delivery · consumer scoping
Planned
M5
Parity, hardening & go-live
Replicate the API · cut over in your tenant
Planned
M6
Motology Pro
Credit-gated app + metered API — post go-live
To confirm
Milestone 1 · Delivered
The data is modelled, migrated — and already in LipKo's hands
The whole legacy catalogue, re-modelled clean and published to the Schema V1 contract. LipKo has the full export today (sent by hand for the first run).
8,591
vehicles migrated from legacy Pro-Fit into the clean model
8,554
published to the versioned Schema V1 consumer contract
1
partner receiving the feed — LipKo, delivered & verified
Scheduled delivery · the remaining 5%
lipko-export 0 6 * * * Trigger now ▸ lands in the FTP drop
Concept / mock-up
Milestone 2 · In progress — 60%
The editor your team will be testing within the week
At a glance
Front & rear fitments in banded columns — staggered setups read instantly, sizes and offsets in monospace so anything odd jumps out.
Fast & keyboard-driven
Move by row, edit in place, insert and delete without leaving the keyboard. Built for hours of curation.
Clean data, enforced
Invalid vehicles & fitments are flagged in red and worked off from the dashboard; publish/quarantine keeps bad data out of the feed.
Testable ~1 week from now
You start using it on the test instance to shake out the data model.
Invoiced on sign-off
M2 is invoiced once you've confirmed the functionality works.
Concept / mock-up
Milestone 3 · CAM / UVC alignment
CAM alignment becomes a sub-app of its own
A live worklist
New and changed CAM vehicles surface as a worklist — the team confirms or re-maps the deltas, instead of re-checking the whole catalogue.
Map & classify
Align a CAM vehicle to an FT vehicle and mark each fitment N/A, Standard or Optional — the same fast, keyboard-driven feel as the editor.
Export back to CAM
The Standard/Optional mapping exports to CAM Systems on schedule, once the format's agreed.
Milestones 4 & 5
Then: operate it, and go live at parity
M4
Operations & config console
- › Staff users & roles — the invite/manage screen.
- › Manufacturer master-list maintenance (Admin-only).
- › Per-consumer delivery profiles — scope, region, redaction, schedule, transport.
- › Consumer & API-access scoping (regions, makes).
M5
Parity, hardening & go-live
- › The existing API surface replicated — today's consumers keep working.
- › buywheels, CAM & LipKo exports running to schedule.
- › Hosted in your tenant — monitoring, backups, CI/CD.
- › Cut-over: parallel-run, reconcile, retire the legacy system.
Milestone 6 · provisional — to confirm
The commercial engine
Motology Pro — the product the legacy system never had
Once you're live at parity, the paid product goes on top: one credit wallet, two ways in — bought via Paddle.
- ✦ Read-only Pro app — search a vehicle (incl. by number plate) and view its fitments. Published data only.
- ✦ Pay-per-view credits — fitments blurred until unlocked; credit packs bought via Paddle.
- ✦ Decoy under the blur — fake data until paid, so it can't be scraped from the browser.
- ✦ Organisation accounts — a firm buys credits into one shared wallet its users draw from.
- ✦ Metered Pro API — same catalogue, keys, metering & rate-limits — one wallet across both.
- ✦ Reverse lookup — a tyre/wheel spec → every vehicle it fits. A premium capability.
▷ Paddle checkout · Motology Pro Sandbox
100 creditsstarter
500 creditspopular
2,000 creditsteam
Organisation wallet — shared across the firm's users
Paddle is merchant of record — it handles EU/UK VAT. Sandbox already stood up; pricing to confirm.
Where this goes next
The near term — and how you'll know each step is done
M1 delivered — LipKo has the Schema V1 feed
Sign-off = automate the FTP delivery (demo, then done).
Now
M2 editor testable on the test instance
You start testing the model. Invoice issued once you sign off the functionality.
~1 week
M3 CAM alignment — its own sub-app
Built on the same core; worklist, mapping, export to CAM.
Then
M4–M5 — console, parity & go-live in your tenant
Replicate the live surfaces, cut over, retire legacy.
Then
M6 — Motology Pro
The credit-gated app + metered API, on the running platform.
After go-live
The through-line
Own it. Prove it
at every step. Sell it.
A platform you own, delivered in signed-off pieces you can see working — a feed already live, the editor within the week, and a commercial product waiting at the end.
CallCore Ltd·for Motology
