MekCar Group · Product and revenue map
Seven businesses.
Seven ways to move
automotive forward.
MekCar is being built as an operating group, not a list of ideas. Each business has a defined customer, product, delivery model and way to earn. The products share a secure foundation, while each can be sold and operated on its own.
PRODUCT DESIGN · COMMERCIAL MODELS · BUILD ORDER
How MekCar earns
Products customers
pay to keep using.
The group combines predictable software subscriptions with implementation work, transaction-based commerce and operational services. A customer can start with one problem—such as missed repair-shop enquiries—and expand into additional products when those products solve a proven need.
Every price, feature and launch date below is a commercial design decision to validate with customers before it is advertised as available. No fictional live customers, inventory or results are represented.
The seven MekCar businesses
A real product and
a real way to earn.
Streams 1–3 are vertical operating products. Stream 4 provides shared automation; stream 5 adds paid insight; stream 6 turns inventory into commerce; stream 7 delivers implementation and ongoing operations.
01
GarageOS
with MekCar Revenue Recovery
What the customer buys
Shop software that organizes customer and vehicle records, appointments, estimates, repair orders, parts, customer follow-up and shop reporting. The first focused module, Revenue Recovery, captures missed enquiries, routes replies, helps turn enquiries into appointments, follows up on unapproved estimates and brings due customers back.
Who pays and how MekCar earns
Independent repair shops pay per location on a recurring software subscription. MekCar can charge separately for onboarding, workflow configuration and approved integrations. Optional messaging or high-volume usage can be metered with clear consent and cost controls.
Buyer: shop owner or service managerOutcome measured: response time, booked appointments, estimate decisions, repeat visitsFirst release: missed enquiry → staff-reviewed response → booking → outcome report
See the first product definition ↗
REVENUE ENGINEPer-location subscription+ setup / integration+ optional usageEXPANSION PATHRevenue Recovery → full GarageOS
02
DealerOS
What the customer buys
A dealership workspace for vehicle stock, sales enquiries, lead ownership, appointments, offers, follow-up and performance reporting. It connects each lead to a vehicle and records the next action, responsible staff member and sales outcome.
Who pays and how MekCar earns
Dealers pay a recurring subscription per rooftop, with the final plan based on stock volume, users and modules. Data migration, inventory feeds and staff onboarding are scoped setup work. Optional advanced automation is an add-on.
Buyer: dealership owner, general manager or sales directorMeasured: lead response, time-to-contact, appointment rate, stock age, close rateOperating loop: stock → enquiry → assigned owner → appointment / offer → sold or closed
REVENUE ENGINEPer-rooftop subscription+ migration / feed setup+ automation modulesEXPANSION PATHSales desk → service → multi-location
03
FleetOS
What the customer buys
A fleet workspace for vehicle records, assignments, service schedules, repair requests, downtime, documents, operating costs and maintenance history. Fleet managers see which vehicles need attention and who is responsible for the next step.
Who pays and how MekCar earns
Fleet operators pay a recurring subscription sized by active vehicles and modules. Onboarding, data cleanup, telematics or maintenance-system connections are priced as implementation work. Partner services can add separately disclosed referral or coordination revenue.
Buyer: fleet owner, operations director or fleet managerMeasured: vehicle availability, overdue maintenance, downtime and cost per vehicleOperating loop: vehicle → assigned operator → maintenance due → repair → back in service
REVENUE ENGINEPer-vehicle subscription+ onboarding / integrations+ optional partner servicesEXPANSION PATHMaintenance control → lifecycle view
04
MekCar Automation
What the customer buys
Configured workflows that move approved work between a customer’s connected systems: route a new enquiry, create a follow-up task, notify the right person, prepare a draft response, flag an exception and keep an auditable record. AI may classify or draft; consequential actions stay under the customer’s permissions and review rules.
Who pays and how MekCar earns
Customers pay an implementation fee for each defined workflow and a recurring automation subscription. Usage-based charges may apply to high-volume runs or external messages. Every workflow has an owner, trigger, permitted action, approval rule, pause control and outcome measure.
Buyer: operations leader, IT lead or product customerMeasured: completion, time saved, exception rate, approval rate and cost per runControls: least privilege, human approval, suppression checks, retries and audit history
REVENUE ENGINEWorkflow setup+ recurring automation plan+ disclosed usage feesEXPANSION PATHOne workflow → monitored workflow library
05
MekCar Intelligence
What the customer buys
Decision tools that explain shop performance, fleet maintenance exposure, dealer stock movement and marketplace supply. Reports show where each signal came from, when it was updated and what data is missing. Early intelligence is based on a customer’s own authorized operational data; broader market benchmarks require reliable, licensed or consented sources.
Who pays and how MekCar earns
Customers pay for higher-tier analytics, scheduled reports or a separate intelligence subscription. Approved business customers may later license data products or API access under explicit terms. MekCar does not sell identifiable customer data as a revenue source.
Buyer: dealer principal, fleet executive, shop group or analystMeasured: adoption, data freshness, decision use and action takenTrust rule: permission, source lineage, aggregation and retention controls
REVENUE ENGINEAnalytics subscription+ scheduled reporting+ approved data/API licensesEXPANSION PATHCustomer reporting → trusted benchmarks
06
MekCar Commerce
MekCar Market + MekCar Sales
What the customer buys
A vehicle marketplace where buyers search and compare real, current listings from MekCar’s own sales operation, approved dealers and authorized private sellers. Seller accounts manage inventory, photos, availability, buyer questions, appointments, offers and sale status. MekCar’s internal stock view separately tracks acquisition, reconditioning, carrying cost and margin.
Who pays and how MekCar earns
Potential revenue includes dealer inventory subscriptions, optional listing upgrades, qualified buyer-lead fees, sourcing or transaction-coordination fees, and gross margin on vehicles MekCar itself owns or is authorized to sell. These are different revenue lines and must be disclosed separately. Buyer-money collection and seller payouts stay off until legal, payments and dispute operations are approved.
Participants: buyers, MekCar sales, dealers and authorized private sellersMeasured: verified active stock, listing quality, qualified leads, appointments and completed salesLaunch rule: only real inventory with seller authority, current photos, price and availability
See the commerce product and transaction design ↗
REVENUE ENGINEDealer listing / lead plans+ coordination fees+ margin on MekCar-owned salesEXPANSION PATHVerified listings → offers → transaction services
07
MekCar Services
What the customer buys
Hands-on help to configure MekCar products, clean and import operational data, connect authorized systems, design team workflows, train staff and run agreed recurring tasks. Each engagement has a written scope, responsible owner, service level and acceptance criteria.
Who pays and how MekCar earns
Customers pay a fixed project fee for defined implementation work or a monthly retainer for managed operations. Third-party costs are itemized. Services can create early cash flow while recurring software products mature, and they reveal repeatable customer needs that should become software.
Buyer: owner or operations leader who wants a delivery partnerMeasured: delivery acceptance, onboarding completion, response SLA and retained accountsBoundary: scoped work, written terms, customer data authorization and documented handover
REVENUE ENGINEFixed-scope projects+ recurring managed retainer+ disclosed partner costsEXPANSION PATHImplementation → managed operations → product adoption
One secure sign-in · separate workspaces
Every person gets
the work they need.
Dealers, mechanics, service advisors, fleet teams, buyers, sellers and MekCar operators use one application shell with different role-based workspaces. A person can belong to more than one approved workspace; access is granted by organization membership and server-side roles.
Private shop, dealer and seller records remain separated. A buyer does not see shop data, one dealer does not see another dealer’s private stock data, and a technician does not receive shop-owner financial permissions.
Production status: the role-based portal is defined here and in the internal architecture specification. The live sign-in, database, APIs and secure role enforcement still need to be implemented and deployed; no preview login is represented as a production account.
Build and sell in an executable order
One group vision.
Sequenced releases.
All seven businesses are defined now. Production delivery is sequenced so the first customer work creates real usage, revenue and evidence for the next build. “Designed” means the product and revenue model are defined; it does not mean the service is already deployed or taking customer data.
Start with one repair-shop workflow, measured outcomes and a signed customer agreement. Deliver onboarding and response operations as a service while the secure product is implemented.
Add shop customer, vehicle, appointment, estimate, repair-order and reporting workflows after the first usage pattern is proven.
Reuse identity, vehicle records, communications, permissions and automation; add the distinct dealership and fleet workflows customers pay for.
Expand approved automation and analytics, then publish the marketplace only when verified sellers and actual inventory can be operated reliably.
Standardize onboarding, support, integration and managed operations into repeatable paid packages with clear service levels.
Operating commitment
Big vision.
Clear ownership.
Measured cash flow.
Each product owner reports on prospects, proposals, paid accounts, recurring revenue, delivery cost, renewal risk and the next release gate. We do not call a product live until the service is deployed, tested with real authorized users and supported operationally.