PRODUCT ENGINEERING

Build an add-on or plugin

Extensions designed to remain updateable, testable and operable — from a focused connector to a standalone product module.

Typical fit

  • WordPress or WooCommerce extension
  • Browser extension or internal add-on
  • CRM/ERP extension
  • API connector or MCP server

What we handle

  • Architecture and stable interfaces
  • Licensing/entitlements where needed
  • Update and migration paths
  • Testing, security and release flow
  • Backend/API components where required

Process

Build an add-on or plugin

  1. Assess target and host system

  2. Define interfaces and lifecycle

  3. Build and test the core function

  4. Secure release, updates and handover

What we watch closely

  • Host-version dependencies
  • Update compatibility and data migrations
  • Permissions, secrets and API limits
  • Licensing and distribution model

What we need for an assessment

  • Target platform and function
  • Existing system/repository if available
  • External APIs/dependencies
  • Preferred release/distribution path

Frequently asked questions

Can you take over an existing plugin?

Yes. We assess code, dependencies and update path before choosing targeted modernization or a rebuild.

Do you build MCP connectors?

Yes, where MCP is useful for the integration case; conventional APIs remain an option.

PRODUCT ENGINEERING

Describe the current situation and target

No meeting required. We check whether we can take it on, what information is missing and what a sensible first step looks like.

info@general-informatics.com