Where add-ons make sense
Industry-specific workflows
Contractor compliance in manufacturing, rostering rules in healthcare, shift-swap policies in retail — process depth that belongs with firms who work in those sectors daily.
Regional and regulatory extensions
State-level or sector-level obligations that matter enormously to some customers and not at all to others, which is exactly the wrong shape for a core module.
Dashboard widgets
The dashboard is composed from widgets rather than fixed reports, so partner-built widgets are a natural extension surface for sector-specific metrics.
Niche system connections
Connections to systems that matter to a specific industry — an ERP, a field-service tool, a compliance registry — where a general integration would not justify the maintenance.
The special case we refuse to hard-code
The usual failure mode in a partner ecosystem is well known. A partner needs something specific for a client, the vendor obliges with a special case, and that special case becomes technical debt everybody pays for. Six months later an upgrade breaks it, and the partner is explaining to their client why the thing they were sold no longer works.
Bhivo avoids that by making the extension points real. Your organisation structure is data, not a hard-coded schema. Approval logic is data too, which is how approval flows differ per customer without branching the codebase. The consequence for partners is the useful part: an add-on can read the organisation model and write into a workflow, and keep working after the platform updates underneath it.
The discipline behind that is a deliberate bias against the sentence "let us just add a special case for this one client." It is not always the comfortable answer. It is the reason an add-on built this year still works next year.