Working together
Communication cadence
How often we talk, in what channels, and what each meeting actually accomplishes.
Last updated 2026-04-27
The default Solagon communication cadence is light meetings, frequent async updates, and a real human reachable when something needs a quick decision. We optimize for not wasting your time.
During an active build
A typical build phase looks like this in your calendar:
- One 30–45 minute sprint demo every two weeks. Working software, not slides. End-of-sprint, your time of choice within a one-day window.
- One 15-minute mid-sprint async check-in — usually a written status note or a Loom, no meeting required. Skim it on your own schedule.
- Decisions as they come up — usually 1–2 a week during active builds, mostly via written messages with options laid out.
That's roughly 1.5 hours of meetings per month plus 30–60 minutes a week of async correspondence. Your team can plan around that without it eating their week.
During a retainer
Retainer cadence is lighter:
- One monthly check-in — 30 minutes, what shipped, what's queued, anything to flag.
- Weekly written status note if we're actively shipping that week, otherwise nothing.
- Direct channel for ad-hoc questions — Slack, Teams, or email, your pick.
If you're on a heavier retainer where Solagon is effectively your engineering team, we add weekly working sessions to match the build phase.
Channels — what we use for what
We try to keep channels matched to message type so nothing important slips:
| Channel | Used for |
|---|---|
| Long-form decisions, formal sign-offs, anything you'll want to reference later | |
| Slack / Teams | Quick questions, day-to-day coordination, urgent matters |
| Linear / your tracker | Tickets — the source of truth for what's being worked on |
| Loom / written notes | Status updates, walkthroughs, code reviews |
| Live call | Decisions that genuinely need real-time discussion (rare) |
If you have strong preferences on channels — your team is on Microsoft Teams not Slack, or your security team blocks Loom — we adapt to your environment. We're not religious about tooling.
Response times
During business hours (M–F 9am–6pm ET):
- Routine messages: replied to within 4 hours.
- Decisions blocking the team: 1 hour during build phase, 2 hours otherwise.
- Urgent (production down, etc.): 15 minutes; usually faster.
Outside business hours we monitor for urgent issues but don't respond to non-urgent messages. We'd rather your team have evenings and weekends back than be on a 24/7 chat treadmill.
What we ask for in return
A reasonable cadence cuts both ways. We do best when:
- Decisions come back within a day. Longer than that and the work parks.
- Sprint demo time is treated as actually-attended, not a mute-and-multitask.
- Feedback is surfaced when you think it, not stockpiled for the launch review.
If your team can't hit that for legitimate reasons (busy quarter, key person on leave), tell us up front and we'll plan around it.