Charter Software

If procurement requires publicly documented enterprise compliance (SOC 2 Type II / ISO 27001) and the vendor cannot provide satisfactory documentation under NDA, this product may not meet that requirement.

If a dealership is very small (single location, low transaction volume) and primarily needs basic inventory, invoicing, and lightweight service tracking, smaller-scope tools may deliver faster time-to-value than a full DMS.

If an organization prefers a standalone accounting plus BI stack and intends to integrate a DMS lightly rather than use the DMS as the system of record, investigate the accounting and reporting capabilities closely.

• An anecdotal accounting-user report indicated continued reliance on spreadsheets for many analytical tasks; procurement should validate reporting and accounting workflows carefully. (https://www.reddit.com/r/Accounting/comments/1dis8rl)

If the organization requires very open third-party integration ecosystems with minimal vendor control, validate the maturity of APIs and the partner ecosystem during procurement.

Current limitations acknowledged by the vendor

• The vendor does not publish a public limitations section; marketing content is primarily positive and feature-focused.

Roadmap / upcoming features

• Not publicly detailed in the accessible sources reviewed.

Scale limitations

• Not publicly documented.

Security/compliance gaps (publicly observable)

• Security certifications (SOC 2/ISO) and enterprise security features (SSO/SCIM/audit logs) are not clearly documented publicly in the sources reviewed.

API limitations / integration constraints

• The vendor states it provides APIs and multiple OEM integrations, but the depth and features of each OEM interface (parts ordering vs. warranty vs. settlement) are typically nuanced.
• Recommended procurement action: request a detailed interface matrix and speak to references for specific OEMs (e.g., John Deere, Kubota, CNH, AGCO).

Vendor-stated differentiators to validate

• Automated OEM price file updates for over 400 OEMs and suppliers (vendor statement). (Primary vendor page)
• Parts locator and OEM portal integrations (e.g., John Deere DTF, CNH Gateway) as stated by the vendor. (Primary vendor page)
• Integrated rental management within the same database as sales inventory and accounting. (Primary vendor page)
• Mobile workflows for technicians (clock on/off jobs, add parts, upload photos). (Primary vendor page)

What is validated by independent/customer evidence?

• Independent validation is limited: review-platform presence exists (G2/Capterra) but with a small sample size. Community evidence is sparse.
• One independent user report indicates ongoing spreadsheet dependency for analytical tasks, which suggests reporting/analysis capability should be validated in demos and reference calls. (https://www.reddit.com/r/Accounting/comments/1dis8rl)

Areas where competitors may have advantages

• DIS: vertical-specific positioning for agriculture equipment dealers.
• Lightspeed: broad adoption and focus in powersports/marine/RV/golf segments; may have stronger ecosystems in those domains depending on dealer needs.
• Newer/niche systems may offer more modern UX and more transparent pricing/free trials in select segments.

Vendor-published case studies (marketing)

• R-Equipment case study (vendor hosted)
  • Vendor-hosted case study page
• Carleton Equipment case study (vendor hosted)
  • Vendor-hosted case study page
• Critical evaluation
  • These pages provide qualitative narratives (for example, references to regained financial control or scaled operations), but any ROI/time-savings metrics should be treated as vendor-published unless independently validated.
  • Methodology is typically not disclosed (sample size, baseline period, attribution), so procurement teams should validate via direct reference calls and request pre/post KPI definitions.

Additional vendor testimonial hub

• CharterSoftware testimonial page includes content around integrated payments and customizable user views, but remains vendor-curated. (Vendor testimonial hub)

• Reddit /r/Accounting: "Anyone else use ASPEN by Charter?" includes a user comment that, after about a year using ASPEN, they still rely heavily on Excel for the work they actually need, and use ASPEN primarily for entering journal entries and other items.
  • Quote: "I’ve been on it about a year in my current position and I still use excel for just about anything that I actually need to work through and just enter the JE’s and other items on ASPEN."
• Interpretation (with caution): this is an anecdotal report that may indicate reporting or usability gaps for accounting workflows (or a training/process mismatch). Single-thread anecdote, not statistically representative.

• Quote: "We rolled it out here in Athens, then to another location about two weeks after, and then another about three weeks or month after. Now we have the five locations up and running." — Brent Gravenhof, Holland Equipment Services. (Official vendor testimonial)

• Vendor case study pages (official testimonials and case studies)

• Likely fit: dealers with a small number to several dozen locations (vendor materials discuss multi-location reporting; testimonial references a small multi-location deployment).
• Employees: typically from several dozen up to many hundreds depending on store count and service operations.

• Possible fit if a dealer wants an integrated system and OEM interfaces, but total cost and implementation complexity may be higher than lighter SaaS alternatives.

What the product does (core value proposition in objective terms)

• ASPEN by Charter is an equipment dealership management system (DMS) designed to support core dealership operations across departments (sales/unit lifecycle, parts, service/work orders, rental, accounting, reporting), with OEM integrations and mobile workflows (ASPEN Mobile, Service Queue). (Primary vendor page and additional product-page corroboration)
• The vendor describes the product's intended business outcomes as operational streamlining and profitability improvement, with an emphasis on reducing manual entry via OEM interfaces and price file automation.

Target market and market positioning

• Target market: equipment dealerships and distributors across rural lifestyle, agriculture, construction, and golf & turf verticals. (Primary vendor page)
• Positioning: a specialized dealership management system (not a general ERP) that emphasizes OEM integrations, mobile support, integrated rental, and integrated accounting/reporting across multiple locations. (Primary vendor page)

Company background (founding year, HQ, key leadership)

• The vendor states a long operating history in dealership systems (marketing references indicate multiple decades of experience). (Primary vendor page)
• Charter Software Inc. announced it was acquired by a larger software group in early 2020; announcement notes Charter is based in Littleton, Colorado, and describes Charter as maker of the "ASPEN Dealer Management System." (Vendor acquisition announcement)
• Leadership: Charter announced a new General Manager (Kanchan) in a company post. (Company announcement)

Funding and growth: investment rounds, acquisitions, estimated customer count/revenue if public

• Acquisition: Charter Software Inc. was acquired by a larger software group (public company) announced in early 2020. (Vendor acquisition announcement)
• Third-party deal commentary: a third-party note described Charter as a provider of "cloud and installed" business management software for small/midsize equipment dealers and distributors, with ASPEN as its flagship. (Third-party commentary)
• Customer count: vendor marketing indicates the product is used by a substantial number of dealerships. (Primary vendor page)
  • A third-party document related to the acquisition likewise characterized ASPEN as used by a substantial number of equipment dealers in North America. (Third-party acquisition-related document)
  • Note: the vendor/third-party usage claim is not independently audited in publicly available sources during this review.

Pricing model with specific tiers and costs where available

• Vendor site: pricing is not publicly posted; the primary CTA is "Book a Demo." (Primary vendor page)
• Market listing: shows pricing as not publicly available (listings typically display "Pricing not provided" for products that require quotes). (Market listing)
• Implication: procurement should expect quote-based pricing (likely per-location/per-module and/or per-user, which is common in DMS/vertical ERP), but exact pricing could not be verified publicly.

Total cost of ownership (TCO) considerations (implementation, training, hidden costs)

• Implementation and migration
  • The vendor states they provide data migration services with a project manager and a documented process to map historical data. Vendor statements about migration effort were not independently validated.
  • TCO risk: migrations in DMS/ERP projects can be time-consuming; procurement should budget for data cleansing, mapping, and validation activities.
• Training and change management
  • The vendor describes blended training: on-site during go-live, virtual training/webinars, online help portal, and phone/email support. (Primary vendor page)
  • Expect internal costs: staff time for training, process redesign, and parallel-run periods—especially for accounting, parts pricing, and service workflows.
• Integrations and payments
  • ASPENPay is offered as an integrated payments option; integrated payments can introduce additional fees and contractual complexity versus using an existing merchant processor. (Vendor product/feature page)
• Hidden/variable costs to validate during procurement
  • Possible OEM integration enablement fees (some OEMs/portals charge activation/integration fees; this is common across DMS contexts, though not specifically documented for ASPEN in the provided sources).
  • Custom reports, custom interfaces, additional sandbox environments, and data exports/BI tooling (Charter mentions a "Query Tool" in its data accessibility content). (Vendor documentation)

Key competitors in the space (4–6 direct alternatives)

• DIS (DIS Quantum / Keystone) — equipment dealer DMS focus. (Vendor product pages / industry listings)
• e-Emphasys — heavy equipment/truck dealer ERP/DMS (commonly cited in heavy equipment dealer ERP discussions). (Industry listings)
• Lightspeed DMS — powersports/marine/RV/golf segments (adjacent, but overlaps for some turf/golf cart dealers). (Vendor product pages)
• Procede (Excede) — heavy-duty dealership DMS (truck/heavy duty). (Vendor comparison resources)
• Dealertrack DMS / CDK / Reynolds — primarily automotive franchise DMS; not always a direct fit for equipment dealers but relevant as large "dealership OS" alternatives for dealer groups that operate mixed businesses. (Industry vendor listings)
• Shop1 (OPE-focused) — relevant if a business is outdoor power equipment service-centric and seeks a smaller-scope, modern system. (Vendor product pages)