Communication Standards
We are fully remote, distributed across the US, MENA and Australia. Clear, documented communication is not optional — it is the foundation of how a distributed partner team functions.
Primary communication tool: Discord
Discord Channel Structure
| Channel | Purpose | Expected Response Time |
|---|---|---|
| #general | Company-wide announcements, non-urgent updates | Read daily |
| #business | Sales pipeline, client updates, BD activity | Within 4 hours |
| #pmo | Project updates, timelines, blockers | Within 4 hours |
| #dev | Technical discussions, build progress | Within 4 hours |
| #finance | Invoices, expenses, financial updates | Within 24 hours |
| #urgent | Time-sensitive issues requiring immediate attention | ASAP |
| #wins | Closed deals, milestones, client praise | No response needed |
Communication Rules
- Write complete messages. Do not open with “hey” and wait. State your full question or context in one message.
- Tag the right person when you need a response. Do not post into the void.
- All decisions made on voice calls must be summarized in Discord within 2 hours. If it is not written, it did not happen.
- Time zone awareness is everyone’s responsibility. Fady is in the US; most others are in MENA. Default: respond within your own business day.
- Urgent means production down or client emergency. Everything else is normal priority.
Weekly Partner Sync
- Cadence: Once per week (partners to agree on day and time)
- Format: Discord voice or video
- Duration: 45–60 minutes maximum
Standing agenda:
- Business update — pipeline, client status (Fady, 10 min)
- Delivery update — active projects, blockers (Daniel + Samir, 15 min)
- Dev update — build progress, technical issues (Dev team, 10 min)
- Decisions needed — anything requiring partner alignment (10 min)
- This week’s priorities (5 min)
Note
Daniel captures and posts a summary to #general after every sync.
Remote Operating Principles
Async first. Before scheduling a call, ask: can this be resolved in a Discord message or a short Loom video? If yes, do that. Calls are for decisions, alignment, and relationship-building — not status updates.
Document everything. If it is not in Discord or the KB, it did not happen. Non-negotiable for a distributed team where not everyone is online at the same time.
Overlap window. Partners should identify and protect the daily window when US and MENA timezones overlap. Any synchronous work requiring both sides should be scheduled here.
Availability. If you are unavailable for more than half a working day, post in #general. Client-facing commitments always take scheduling priority — flag conflicts as early as possible.
Progress visibility. Each domain posts a brief weekly update in their channel (#business, #pmo, #dev) — even if it is just “on track, nothing to flag.” Silence in a remote team reads as inactivity.