Send a short note with the symptom, environment, and what has already been tried. I usually start with a focused diagnostic conversation before proposing implementation work.

WhatsApp available for active diagnostics after initial email.

Diagnostic packet

When reaching out, include the smallest useful context.

  • symptom
  • environment
  • what changed
  • what has already been tried
  • logs, versions, network path, or deployment notes if available

Good fit

  • A demo works locally but fails in customer deployment
  • The team has tried the usual checklist and still cannot find root cause
  • The issue crosses code, runtime, network, device, or deployment boundaries
  • A deployment is blocked by environment-specific behavior
  • The team needs a focused diagnostic before committing to a larger rewrite

Not a fit

  • Generic app development
  • Long-term staff augmentation
  • Undefined product ideas without a concrete technical failure
  • Pure feature delivery with no production or reliability concern
  • Requests involving confidential access without proper authorization