Technical modernisation proposal

Global Vans.
Built for what comes next.

A new independent vehicle-data, pricing and enquiry platform that completely decouples the Global Vans website from iComplete.

Prepared byDigital Impact
Created byWill Craig
ProjectPhase One
StatusDraft for discussion

01 / Project overview

A permanent foundation,
not another temporary fix.

Global Vans currently relies on an ageing iComplete CRM and page-generation system to manage vehicle pricing and produce the HTML pages that form its website.

The arrangement has become increasingly difficult to maintain, creates recurring technical and SEO issues, and makes routine frontend improvements disproportionately complex. The internally owned legacy system no longer receives supplier product updates.

Digital Impact's original recommendation was for the Global Vans IT team to create a structured feed from iComplete for a new website to consume. This was the lower-cost route for the initial frontend scope, but it would require Global Vans to design, build and maintain a new integration within an unsupported legacy platform.

The IT team has confirmed that it does not wish to pursue this route, particularly as iComplete is intended to be retired. The recommended direction is therefore to build the permanent vehicle-data, pricing and enquiry capabilities now rather than invest time and cost in an interim feed that would later need to be replaced.

Standalone Global Vans application
Automated CAP data updates
Car and van pricing manager
IDS-to-CAP pricing migration
X Range product management
Vehicle imagery integration
Enquiry storage and delivery
Controlled API and test frontend

What technical debt means

Modernising 10–15 years of inherited constraints.

Technical debt is the ongoing maintenance burden created by older technology, historical system decisions and outdated integrations. Over time, it makes routine updates slower, increases the risk of errors and restricts the organisation's ability to introduce improvements.

The current IDS update process demonstrates this problem. Updates can disrupt pricing or website output and reportedly lead to approximately two weeks of corrective work. The new CAP-based system replaces this with a controlled update process designed to preserve existing pricing relationships.

02 / How the project evolved

From an interim feed
to an independent platform.

Original recommendation

An iComplete JSON feed

Global Vans IT would create and maintain a structured feed from the existing platform for a new frontend to consume.

  • Lower initial frontend cost
  • Requires client-side feed development
  • Preserves iComplete and IDS dependencies
  • Would need replacing when iComplete retires
Recommended direction

A CAP-based Global Vans application

The IT team does not wish to create the interim feed. Phase One therefore brings forward the permanent data, pricing and enquiry capabilities.

  • Removes reliance on iComplete
  • Replaces the IDS foundation with CAP
  • Creates one controlled source of truth
  • Supports any approved future frontend
Why the feed was not pursued

The proposed feed would have allowed the existing system to continue performing much of the underlying data management, reducing Digital Impact's initial frontend scope. It would also have placed the development, testing and ongoing maintenance of that feed with the Global Vans IT team inside a platform that no longer receives supplier updates.

Why CAP belongs in the new foundation

The current website relies primarily on IDS vehicle data while Global Vans is moving to CAP. A feed from the present system would preserve both the iComplete and IDS dependencies. Building a native CAP database removes both legacy foundations and avoids creating an integration that would need replacing when iComplete is withdrawn.

03 / Proposed solution

One application.
One source of truth.

Phase One will deliver one standalone Global Vans application containing the vehicle data and operational functionality required by the website. One properly structured relational database will contain separate tables and modules for CAP data, pricing, custom vehicles, imagery, enquiries, users and integration logs.

The application will expose a controlled API. WordPress will use that API to obtain vehicle and pricing information, while future websites, brand sites or applications can use the same governed source. External systems will not access the underlying database directly.

Designed for change

This separation is a deliberate future-proofing decision. Website technology and AI-enabled services are changing quickly, and the preferred approach is not to bind Global Vans' core operational data to one CMS. Global Vans can change frontend platforms, launch additional websites or internal tools, and supply different approved offer selections from the same governed source without rebuilding the underlying vehicle and pricing system.

04 / Phase One scope

Seven core parts
of the build.

01

Core data

CAP vehicle database

Objective: create a reliable and maintainable source of vehicle information that is independent of the existing IDS and iComplete page-generation process.

Digital Impact will design and build the schema required to hold relevant CAP car and van data, including makes, models, derivatives and technical specifications. Digital Impact has approximately ten years of experience working with CAP data, and the client already holds the required CAP licence and has provided access to the source data.

An automated update process will add new vehicles and apply relevant CAP changes on an agreed schedule or through a manual administrator request. Updates will preserve pricing and other Global Vans records associated with existing CAP vehicles.

Richer vehicle journeysWhere CAP supplies the data, future pages can surface and filter important buying criteria rather than burying them in general specifications. This supports richer vehicle pages comparable with those offered by leading competitors.
Payload1,000 kg
Load length2,510 mm
Electric range205 miles
Illustrative figures only — actual specifications will be supplied by CAP.
  • Initial CAP import
  • Scheduled updates
  • Validation and error reporting
  • Pricing-link protection
02

Commercial control

Vehicle pricing manager

Objective: replace the pricing-management functions currently provided by iComplete with a focused administration interface inside the new Global Vans application.

Administrators will search the CAP database, select a vehicle and create or update the corresponding offer. The interface will display the appropriate pricing fields for cars and vans and support promotional labels such as Special Offer, In Stock and Electric.

Van offersA focused monthly-price workflow using the final fields confirmed from the existing pricing export.
Car offersContract term, payment profile, annual mileage and prices including and excluding VAT, subject to confirmation from the existing export.
New vehicle offerDraft
CAP vehiclePeugeot Partner Standard 1.5 BlueHDi
Monthly price£249.00
Annual mileage8,000
Payment profile9 + 35
Special OfferIn StockDiesel
  • Separate car and van fields
  • Promotional labels
  • Bulk import and update
  • CAP-coded CSV export
  • User-attributed changes
03

Migration

Existing pricing migration

Objective: populate the new application with the vehicle offers currently available on the live Global Vans website, reducing the need for manual re-entry.

Global Vans currently associates pricing with IDS vehicle codes. The new application will use CAP codes. Using the supplied IDS-to-CAP mapping and the pricing table exported from the live system, Digital Impact will match and bulk-import the existing vehicle offers.

During development, a repeatable bulk-update process will allow the demonstration environment to remain aligned with pricing changes made on the live website.

IDS pricing exportIDS-to-CAP mappingValidated CAP offers

Migration assumption: the fixed scope assumes that the supplied IDS-to-CAP mapping and pricing export are sufficiently complete and internally consistent for automated processing. Records that cannot be matched reliably will be reported for manual review.

  • Mapping preparation
  • Bulk offer import
  • Repeatable refresh
  • Exception report for unmatched records
04

Custom products

X Range vehicles

Objective: give Global Vans a structured way to create and promote X Range products without duplicating and modifying core vehicle records inside the legacy CRM.

An administrator will select a standard CAP vehicle as the base and create a linked X Range product. The product retains the technical specifications of the underlying CAP vehicle while adding a custom name, description, modification details, imagery and pricing.

The initial functionality is intended for custom bodywork, alloy wheels, tyres and internal fit-outs. It will not attempt to model engineering-level changes. Detailed conversions will continue to be handled through the Global Vans consultation and sales process.

Base vehicleCAP derivative
Custom layerX Range product
Sales processConsultation
  • Custom name and description
  • Feature details
  • Image uploads
  • Pricing and status
  • Separated from core CAP data
05

Vehicle presentation

Vehicle imagery

Objective: provide reliable vehicle imagery for standard CAP vehicles while supporting custom photography for the X Range.

IMAGIN.studio will be the primary image source, matching vehicle imagery through CAP codes. Mark Murphy at Fleet Alliance holds the relevant provider subscription, and suitable API access will be made available to the project. Coverage will be assessed during implementation before the final mix of API and owned imagery is confirmed.

The API offers a stronger and more flexible presentation than a static repository, including supported vehicle colours and branded number-plate treatments. Existing Global Vans imagery can complement the service and will be included where image records can be exported and reliably aligned to CAP IDs. Manual uploads will remain available for X Range products and agreed exceptions.

CAP matchingSupported coloursBranded number platesOwned-image fallback
  • API integration
  • Coverage assessment
  • CAP-aligned image import
  • X Range uploads
  • Fallback handling
06

Lead visibility

Enquiry management and delivery

Objective: ensure website enquiries are retained within the new Global Vans application and reliably delivered into iComplete or another nominated destination system.

When a visitor submits an enquiry, the application will validate and store a copy before passing it to the nominated system. Delivery status will be recorded so failed submissions can be identified and retried rather than being silently lost.

Each enquiry will retain the available marketing-source attribution, such as Google Ads, organic search or direct traffic. This will use a suitable cookie and tracking configuration based on the approach already used for Fleet Alliance, subject to the website's consent settings and the source data available at submission.

Phase One provides a lightweight enquiry log rather than a replacement CRM. It gives authorised users operational visibility and creates a module that can later be extended into broader lead-flow management if required as iComplete is retired.

CustomerVehicleSourceStatus
Sarah MorganToday, 10:42Ford Transit CustomGoogle AdsDelivered
David EvansToday, 09:18Peugeot PartnerOrganicDelivered
Amelia JonesYesterday, 16:05VW TransporterDirectDelivered

Critical dependency: the fixed scope assumes that the nominated destination system provides one documented, technically accessible method for receiving enquiries and suitable access for integration testing.

  • Secure enquiry endpoint
  • Stored lead copy
  • One destination integration
  • Marketing-source attribution
  • Delivery and retry logging
07

Proof and access

Administration, API and demonstration frontend

The application will support multiple administrative users at launch. All initial users will have administrator-level access, and additional users can be added when required. More granular roles and permission levels can be introduced later if the operational need emerges.

Changes to pricing and other important records will be associated with the authenticated user and remain technically traceable by Digital Impact if an audit or investigation is required. A client-facing audit-log interface is not included.

Approved API endpoints will support vehicle, offer and website functions. WordPress and future frontends will consume these endpoints rather than accessing the database directly, with appropriate validation, authentication and permissions applied to each function.

A basic wireframe-style frontend will prove the complete system. It will demonstrate that vehicles and pricing can be displayed and that enquiries can be submitted, stored and passed to the nominated destination.

The demonstration frontend proves the technical system. It is not the finished customer-facing website.

  • Multiple admin users
  • Secure authentication
  • Approved API endpoints
  • Vehicle listing and detail proof
  • End-to-end enquiry proof

05 / Clear project boundary

Build the foundation first.
Attach the finished website second.

Separating the application from frontend design prevents technical delivery from becoming delayed by visual-design decisions and approval cycles. It gives Global Vans control of the underlying data before the finished website is attached.

Phase One

Technical application

Data, pricing, X Range, imagery, enquiries, API and proof frontend.

Included in this proposal
Phase Two

Focused frontend recreation

Recreate the existing Global Vans presentation on the new technical platform. Fix the current technical SEO and speed issues, address navigation issues and complete other agreed quick fixes.

Suggested budget: £8,000 + VAT
Ongoing

Marketing-led expansion

New landing pages, new features, new templates and wider site expansion delivered as focused projects over time.

Separately scoped

What the foundation unlocks

Full control over the customer-facing websiteFaster-loading, cacheable vehicle pagesResolution of page-generation and technical SEO restrictionsMake, model, derivative and campaign landing pagesFaster marketing-led improvementsAdditional websites and brands from the same applicationFreedom to replace WordPress without rebuilding the core data

06 / Delivery framework

A clear build sequence.
One completed-build demonstration.

The project will progress through controlled internal stages so the data model, administration workflows, migrations and integrations are built in the right order. These are delivery stages rather than separate client sign-off or payment milestones. The meaningful product demonstration takes place when the completed Phase One build is ready for acceptance, after which the separate Phase Two frontend project can begin.

Estimated Phase One build time8 weeks

From technical commencement, assuming timely access to the required source data, technical contacts and test systems.

Weeks 1–2Technical validation and foundation

Confirm inputs and create the database, administration and API structure.

Weeks 3–5CAP and pricing

Import CAP data, establish controlled updates and build pricing management.

Weeks 6–7Migration and integrations

Migrate offers and implement X Range, imagery and enquiry functions.

Week 8Completion and demonstration

Complete end-to-end integration, testing, agreed defect resolution and handover.

  1. 01

    Technical validation

    Confirm source data, exports, destination integration and operational rules.

  2. 02

    Application foundation

    Create the database, administration framework, users and API structure.

  3. 03

    CAP and pricing

    Import CAP data, build controlled updates and deliver the pricing manager.

  4. 04

    Migration and specialist functions

    Migrate offers and implement X Range and vehicle-imagery workflows.

  5. 05

    Enquiry integration

    Store, attribute, forward and validate website enquiries.

  6. 06

    Demonstration and handover

    Prove the end-to-end workflow, resolve agreed defects and complete handover.

Completion checks

Agreed CAP data can be imported and updatedAdministrators can create car, van and X Range offersExisting pricing is migrated with exceptions reportedImagery is returned through the API or agreed fallbackThe demonstration frontend displays approved dataTest enquiries are stored, attributed and deliveredCAP-coded pricing exports can be generated

Detailed delivery dates and client review points will be confirmed following approval and the initial technical-validation stage.

Key assumptions

  • Global Vans maintains the required CAP licence.
  • Fleet Alliance provides authorised IMAGIN.studio access.
  • The IDS-to-CAP mapping and pricing export are sufficiently complete.
  • The nominated destination offers one documented submission method and test access.
  • CAP-aligned historical image references are supplied where migration is required.
  • Client contacts, data and reviews are provided in a timely manner.

Not included in Phase One

  • Finished website design or substantial UX redesign.
  • New branding, copywriting, content production or SEO campaign delivery.
  • Granular administration roles beyond initial administrator access.
  • A client-facing audit-log interface.
  • Additional websites, brands or integrations not expressly listed.
  • Third-party licence fees, hosting and ongoing support unless expressly agreed.

07 / Commercial proposal

£49,500 plus VAT

This is a fixed investment against the defined Phase One outcomes, reflecting the bespoke application, data migration and integration work required to remove the website's dependency on iComplete.

Payment schedule

The payment structure reflects the nature of the build: an initial commencement payment followed by the balance when the completed Phase One system is demonstrated and ready for acceptance and handover.

35%£17,325Approval and project commencement
65%£32,175On completion of the Phase One build
Future frontend — suggested £8,000 + VAT budget

Once Phase One is complete, we recommend an £8,000 plus VAT working budget to recreate the existing Global Vans website on the new technical platform. We will shape the focused Phase Two scope around this budget while retaining the general appearance and structure of the current website, fixing the current technical SEO and speed issues, addressing navigation issues and completing other agreed quick fixes. It does not include a wider redesign or new brand development.

Ongoing and third-party costs

Hosting, monitoring, ongoing maintenance and support will be confirmed separately before launch. CAP, IMAGIN.studio and other third-party licence costs remain outside the Phase One investment unless expressly agreed otherwise.

Moving forward

Next steps.

  1. Approve the Phase One scope and investment.
  2. Confirm the commercial agreement and payment schedule.
  3. Provide the technical contacts and destination-system test access.
  4. Validate the CAP, pricing and image source files.
  5. Arrange the technical commencement session.
Review from the top