Clients

Lazer's client engagements. Each client has its own subdirectory containing all engagement-specific material — onboarding, architecture, integrations, runbooks, incidents, references — plus a clients/ subdirectory for that client's own clients (the end customers Lazer's client serves).

Active engagements

• Avoca — voice-agent platform for auto-service shops. Currently piloting at EAS Tire & Auto (Ponderosa location). AutoOps CRM integration. Sandy's primary engagement.

Pattern

The /clients/<lazer-client>/ directory holds everything Lazer-client-specific. Inside it:

• onboarding/, architecture/, concepts/, how-to/, reference/, incidents/, solutions/, proposals/ — engagement material at the Lazer-client level.
• crms/<crm>/ — CRM-specific material (e.g., AutoOps, HouseCall Pro).
• integrations/ — non-CRM integrations.
• clients/<their-client>/ — the Lazer-client's own clients (Avoca's clients are auto-service shops like EAS).

Anything that's truly cross-client (patterns, methodologies, Lazer-side practices not tied to a specific engagement) lives at the toolkit root, not under /clients/.