Custom IDE tooling
Best for: Teams with a repetitive workflow that belongs inside VS Code or a JetBrains IDE.
Possible scope: Workflow discovery, technical design, implementation, tests, packaging, and release guidance.
Build a focused developer tool around a real workflow
GMM's public plugins show the kind of work available: IDE integration, language tooling, local file inspection, compatibility testing, and release engineering. Engagements begin with a concrete problem and an explicit boundary—not a generic transformation promise.
HAProxy workflow engineering
Best for: Platform teams that need editor feedback, organization-specific rules, fixtures, or version migration tooling.
Possible scope: A scoped extension to the open-source language tooling or a separate internal integration.
PKI developer tooling
Best for: Teams that handle certificates, CSRs, CRLs, keys, or keystores in development workflows.
Possible scope: Local inspection and parsing UX with explicit input, privacy, and validation boundaries.
Before a proposal
Define success and non-goals
A useful first conversation covers the users, current workflow, supported environments, sensitive inputs, delivery constraints, and how the result will be verified. Security, compliance, performance, or availability claims are included only when the engagement defines a method to test them.