4.5 Communication Standards and Slack Norms

The 'I intend to' communication standard

RevGravy has a specific internal communication norm that Phil actively reinforces. When committing to an action, say: 'I intend to [action] by [timeline].' Include what you're going to do, when, and any questions or context that affects the plan.

Good examples

I intend to deliver the TeleCloud workflow by EOD today. No blockers.

'I intend to offboard PPJ on Friday. I'll send a confirmation to Juan before taking any action.

'I intend to assign Bluegrass tickets to Juan starting now. Question: should I also reassign the historical ones?

Slack channel structure

Channel	Purpose	What goes here
#architect-success	ASM-architect collaboration hub	Cycle planner announcements, Friday metrics, Flow Session scheduling, automation rollouts, architect feedback requests
#operations	SLA monitoring and ticket management	Daily SLA check-ins, ticket escalations, HubSpot workflow notifications, project alerts
#general	Company-wide channel	WTW recaps, new client announcements, company news, public recognition
[client-name] channels	One channel per active client	Automated outputs from Make.com, manual updates from architects about that client

End-of-day / weekly form

All architects fill out a standing form every Friday covering: time in client meetings, time in internal/admin work, time in cycle work, customer wins this week, and 'Come across something you wish we did differently?'. Manuel monitors completion and sends reminders if missed.

4.5 Communication Standards and Slack Norms

The 'I intend to' standard, channel structure, EOD form, and weekly snapshot emails