Case study · Enterprise technology
Demonstration prototypeAspect Management Services Pvt. Ltd. is the technology and transformation partner to Autoworld Japan — Autoworld International Ltd (autoworldjapan.com), an exporter of vehicles from Japan since 2000, based in Yokohama. This case study walks through the ERP + CRM platform Aspect developed for Autoworld Japan.
01 · Context
On autoworldjapan.com, buying a vehicle is a five-step journey. Everything that journey depends on sits behind it.
The buyer’s journey — five steps
What the buyer seesAspect connects what happens behind the front door.
And to be clear about roles: Autoworld Japan is the client and the business; Aspect is the technology and transformation partner.
The client and the business
Autoworld International Ltd (autoworldjapan.com) — an exporter of vehicles from Japan since 2000, based in Yokohama.
The technology and transformation partner
Aspect Management Services Pvt. Ltd. — which developed the ERP + CRM platform this case study describes.
02 · Business challenge
A single vehicle passes through enquiry, sourcing, procurement, inventory, sales, documentation, export, logistics, delivery, finance and management — and when each of those steps lives in its own tool, information fragments and the whole picture disappears.
One vehicle, eleven stages
The cost compounds quietly. Each new hire inherits the workarounds, each new market multiplies them, and decisions are taken on partial pictures because the full one takes too long to assemble.
03 · Approach
The platform is the output. The method is the asset — and it is repeatable.
How the business actually runs — people, decisions and money.
Design the operating model as one connected system.
Make the platform visible and testable, screen by screen.
Connect the flows so records are captured once and shared.
Embed the intelligence layer where decisions are made.
Extend what works across entities, markets and operations.
04 · Solution
Not a set of modules bought separately — one platform, in which the same records move from first enquiry to management reporting.
All platform figures describe the demonstration prototype, which runs on seeded demo data. No production deployment, financial return or operational improvement is claimed.
Two of the platform’s workflows exist because of how this exporter actually trades. Neither is a generic module; both are business-specific by design.
Takes a buyer requirement step by step through an authorised purchase.
Publishes selected vehicles to selected buyers under controlled reservations.
04.1 · Inside the platform
Each mechanism below is demonstrated in the prototype, running on seeded demo data. The rules are built into the screens, not written in a manual.
Requirement lifecycle
Every buyer requirement moves through nine visible stages, from Submitted to Vehicle purchased, each derived from the records. Capture is three-tiered — mandatory and recommended fields — and the buyer’s own words are kept on version one. A Buyer 360 sits alongside: agent, customer status and contact channels on the same screen.
IllustrativeA visualisation of the mechanism as demonstrated in the prototype on seeded demo data — not a screenshot.
Direct procurement
Route A runs as an authorised, step-by-step route from requirement to vehicle in stock, each step with its owner and rule. The procurement authorisation waits at a 30% deposit gate until Accounts verifies the buyer’s deposit — and approval is separated by design, so the requester can never approve their own request.
The requester can never approve their own request.
Each step on the route has its owner and rule.
IllustrativeA visualisation of the mechanism as demonstrated in the prototype on seeded demo data — not a screenshot.
Virtual Stock
In the buyer portal, buyers see only the vehicles made visible to them, each labelled In stock or Sourced to order. A reservation holds a vehicle for seven days, with a payment alert every 24 hours; after the seventh alert without a verified deposit, the reservation releases automatically and the vehicle returns to available.
IllustrativeA visualisation of the mechanism as demonstrated in the prototype on seeded demo data — not a screenshot.
One vehicle record
Every vehicle carries a single record — stock number, chassis, journey stage, buyer and location in one place. Fields are role-aware: a senior buyer sees the procurement price, while the selling price stays restricted.
IllustrativeA visualisation of the mechanism as demonstrated in the prototype on seeded demo data — not a screenshot.
Shared records across shipping, documents and receivables
When a shipment’s ETA is delayed, the buyer and the agent are notified and the balance due date moves with the ETA. Documents are stored once — classified, linked to the vehicle, versioned and released by rule — and receivables keep each currency on its own: currencies are never combined.
IllustrativeA visualisation of the mechanism as demonstrated in the prototype on seeded demo data — not a screenshot.
Two apps, one platform
The buyer app shows what needs the buyer now — a reservation countdown, a payment receipt to upload, estimates to review. The team app lets staff capture a market candidate at the dealer itself, with the business rules built into the form.
IllustrativeA visualisation of the mechanism as demonstrated in the prototype on seeded demo data — not a screenshot.
Permissions defined once
The permission model holds 13 user types, 121 capabilities, 43 restricted field classes and 20 approval routes — defined once and applied across the platform. The same role rules decide what SEER can answer.
IllustrativeA visualisation of the mechanism as demonstrated in the prototype on seeded demo data — not a screenshot.
All seven mechanisms
04.2 · SEER by Aspect
Demonstrated in the prototypeSEER by Aspect is the intelligence layer embedded in the platform — inside the operating system, not bolted on beside it. Every answer follows the same pattern.
Permission-aware is not a slogan. Ask the same panel for gross margin by month as a Sales user and SEER declines: margin belongs to Owner / Admin and Accounts, so it will not answer the question for Sales. The role rules that govern the screens govern the intelligence.
Prototype noteIn the prototype, SEER’s answers are computed from the seeded demo records rather than a language model. The capabilities shown are those of the Autoworld Japan prototype.
05 · Technology & expertise
Technology selection follows business requirements, security, data governance, integration needs, cost and measurable value — never the other way round.
The connected operating model is designed before anything is built.
The system is made visible and testable early, so choices are made on screens rather than specifications.
Flows are connected across functions until a record entered once serves the whole business.
Reporting and intelligence are embedded where the decisions are actually made.
Tailored, not off the shelfThe platform described on this page is not a commercially packaged product, and another client’s platform would not be a copy of it.
06 · Outcomes
What this case study claims — and what it does notNo production deployment, financial return or operational improvement is claimed. This case documents a demonstration prototype running on seeded demo data. Verified outcomes will be added only when they are substantiated.
Expansion items are roadmap potential, not current features. Features labelled as concepts in the prototype — the 360° vehicle view and “View in your space” — remain concepts.
07 · Lessons
If your operations run across disconnected tools —
The same method applies. Understand how the business actually trades, architect the operating model, prototype it so everyone can see it, then integrate, add intelligence and scale.
What Aspect builds is tailored, not off the shelf. Yours would not be a copy of the platform on this page; it would be shaped around how your business trades, with technology chosen to fit the requirement rather than the other way round.
The starting point is a conversation about how your business runs.
Start here
Tell us how your business trades today — the tools, the handovers and where the picture fragments. Understanding that comes before any platform.
