Talk to CGH.
Five inquiry paths, one email, operator-staffed. Pick the path that fits — the subject line routes the message internally.
Pick the path that fits.
Every inquiry reaches the same inbox — the subject line tags it for the right kind of response.
Evaluating a product.
For operating teams looking at WorkforceForge, ShopPilot, RoutePilot, PulsePilot, or ServiceLead.
Include in your emailInclude which product, the workflows you are solving for, and brief operational context.
Email with subject: Product inquiryPiloting an in-development product.
For service operations interested in piloting alongside us. Mutual selection — we work with teams whose operational reality teaches us as much as our software helps them.
Include in your emailInclude business shape, current operational stack, and the workflows that hurt most.
Email with subject: Design partnerPartnering on workflows.
For partnerships involving shared operational workflows, integration discussions, or co-development.
Include in your emailInclude the shape of the collaboration being proposed and what success looks like for your team.
Email with subject: Operational collaborationWriting about CGH.
For journalists, analysts, or operators covering service-business software, supervised automation, or operator-led companies.
Include in your emailInclude publication, deadline, and the angle you are working on.
Email with subject: PressAnything else.
Feedback, questions, introductions, or anything that doesn’t fit the categories above.
Include in your emailA few sentences of context helps the response be useful.
Email with subject: GeneralOne channel, operator-staffed.
CGH is a small operator-led team. Email is reviewed regularly during business hours, and we respond personally rather than through ticketing software. There is no scheduling tool, no chat widget, and no automated routing — just a person reading the message and deciding how to engage.
Early operational products are still evolving. The most useful inquiries include context about your workflows or operational challenges. If we can't help directly, we'll usually say so quickly rather than route you in a circle.
Background before reaching out.
The ecosystem overview and the writing surface answer many of the common questions ahead of a first conversation.