Skip to main content

Software & Platforms

This page provides guidance on the categories of platforms we work with and how platform decisions are made.

Platform Categories​

We provide consulting and advisory services for these categories of open-source business software:

Enterprise Resource Planning (ERP)​

Systems that integrate core business processes including finance, inventory, manufacturing, and operations.

Typical use cases:

  • Manufacturing operations
  • Distribution and logistics
  • Financial management
  • Multi-department integration

Key considerations:

  • Significant implementation investment
  • Requires strong internal commitment
  • Long-term operational responsibility
  • Process alignment critical

Customer Relationship Management (CRM)​

Systems that manage customer interactions, sales processes, and relationship data.

Typical use cases:

  • Sales pipeline management
  • Customer service operations
  • Marketing automation
  • Contact and account management

Key considerations:

  • User adoption is critical to success
  • Data quality determines value
  • Integration with other systems often needed
  • Process discipline required

Content Management Systems (CMS)​

Systems that manage digital content, websites, and documentation.

Typical use cases:

  • Public websites
  • Internal documentation
  • Digital asset management
  • Multi-channel publishing

Key considerations:

  • Technical capability for customization varies
  • Security and maintenance critical
  • Content governance often overlooked
  • Scalability needs vary significantly

Business Intelligence (BI)​

Systems that analyze data and provide reporting and visualization capabilities.

Typical use cases:

  • Operational reporting
  • Executive dashboards
  • Data analysis
  • Performance monitoring

Key considerations:

  • Data quality is fundamental
  • Source system integration required
  • Interpretation skills matter more than tools
  • Ongoing maintenance of reports needed

Automation and Workflow​

Systems that automate processes and manage workflows across applications.

Typical use cases:

  • Process automation
  • Integration orchestration
  • Approval workflows
  • Scheduled operations

Key considerations:

  • Requires clear process documentation
  • Error handling critical
  • Monitoring and alerting needed
  • Dependency on connected systems

Platform Selection Approach​

We do not sell or recommend specific products by default. Platform selection is based on:

1. Requirements Alignment​

Does the platform address the documented requirements? Every platform has strengths and weaknesses — the question is fit, not quality.

2. Client Capability​

Can the client realistically operate this platform? Powerful platforms require capable teams. We recommend within the client's reach.

3. Ecosystem Maturity​

Is the platform actively maintained? Is there a healthy community? Will it exist in five years? We avoid platforms with uncertain futures.

4. Sustainability​

Can this platform be maintained long-term? Some platforms require specialized skills; others can be maintained by general IT staff.

5. Total Cost​

What is the true cost over time? License fees (even zero) are only part of the picture. Hosting, maintenance, customization, and training all contribute.

Example Platforms​

The following are examples of platforms within our scope. This is illustrative, not exhaustive or prescriptive:

CategoryExample Platforms
ERPERPNext, Odoo (open-source edition)
CRMSuiteCRM, Odoo CRM, Mautic
CMSWordPress, Drupal, Strapi, Directus
BIMetabase, Apache Superset
Automationn8n, Apache Airflow

We evaluate platforms on a case-by-case basis. Inclusion here does not imply endorsement; exclusion does not imply rejection.

Trade-offs to Communicate​

When discussing platforms with clients, ensure they understand:

Open-Source Reality​

  • "Free" software has costs in hosting, maintenance, and internal effort
  • Community support varies in quality and responsiveness
  • Commercial support options exist but cost money
  • Updates are the client's responsibility

Customization Trade-offs​

  • Customization increases maintenance burden
  • Heavily customized systems are harder to upgrade
  • Standard configurations are safer long-term
  • Every customization is technical debt

Implementation Complexity​

  • Enterprise platforms require significant implementation effort
  • Success depends on process alignment, not just software
  • User adoption is often the hardest part
  • Ongoing investment is required

No Perfect Platform​

  • Every platform involves trade-offs
  • "Best" is contextual to requirements and constraints
  • Waiting for perfection means waiting forever
  • Switching costs are real and significant

What We Do Not Do​

  • We do not sell software licenses (there are none for open-source)
  • We do not receive referral fees or commissions from vendors
  • We do not have exclusive partnerships with specific platforms
  • We do not guarantee platform behavior or reliability
  • We do not provide platform support or maintenance