BMH Forge Console

Client Blueprint

Strategic system design and implementation direction tailored to your business.

Executive Summary

Business Context

Company: Middelburg Auto Group

Project: Dealership Sales System

Primary Objective: Build a centralized dealership sales and lead management system that improves lead tracking, customer follow-up, sales visibility, and operational efficiency

Business Context: We are a vehicle dealership selling new and used vehicles, handling customer enquiries, trade-ins, finance-related processes, stock movement, and sales follow-up across multiple staff roles.

Strategic Recommendation

We recommend a single-platform operational system designed to improve operational efficiency, visibility, and long-term scalability.

Problem Landscape

Priority Business Challenges

  • poor lead tracking: This currently limits efficiency, visibility, or scalability in the business.
  • missed follow-ups: This currently limits efficiency, visibility, or scalability in the business.
  • no central visibility of customer status: This currently limits efficiency, visibility, or scalability in the business.
  • manual reporting: This currently limits efficiency, visibility, or scalability in the business.
  • fragmented communication across staff: This currently limits efficiency, visibility, or scalability in the business.
  • slow response to enquiries: This currently limits efficiency, visibility, or scalability in the business.

Recommended User Experience

  • clarity
  • efficiency
  • control
  • scalability

Recommended Solution Strategy

Solution Direction

Recommended Solution Type: Single-platform operational system

This recommendation is intended to create a stronger operational foundation, improve visibility, and support scalable growth over time.

Intended Users

  • Dealer Principal
  • Sales Manager
  • Sales Executive
  • Finance Admin
  • Reception/Admin

System Design Overview

Platform Recommendation

  • Webapp

Growth Direction

The recommended foundation allows the system to expand over time into deeper automation and analytics.

Delivery Roadmap

Phase 1 — Core Platform

  • Core workflow platform: Create a centralized place to manage daily operational activity.
  • Role-based access: Ensure the right users have the right permissions and visibility.
  • Priority integrations: Connect the system to the most important external services.

Phase 2 — Expansion and Optimization

  • Advanced automation: Reduce manual work and improve consistency across processes.
  • Enhanced analytics: Provide better performance visibility and decision-making support.
  • Scalable expansion modules: Prepare the system for future growth and added capability.

Delivery Timing and Investment

Indicative Timeline

Planning: 2 weeks

Design and Build: 6 to 10 weeks

Testing and Refinement: 2 weeks

Deployment: 1 week

Final delivery timing may adjust depending on integration complexity and approval speed.

Investment Guidance

Estimated Range: R218 270R265 720

This range reflects a premium phased solution built for operational improvement and future scale.

Support, Growth, and Next Steps

Support and Growth Guidance

Support: A structured support model is recommended after launch to ensure stability and performance.

Infrastructure: Managed infrastructure is recommended for reliability, monitoring, and future growth.

Future Growth: The recommended foundation allows the system to expand over time into deeper automation and analytics.

Next Steps

  • Confirm the proposed Phase 1 scope.
  • Validate key integrations and dependencies.
  • Approve commercial direction and delivery planning.
  • Move into solution planning and execution kickoff.