How Civalent Collaborates
async-first, zero daily standups, automated transparency
0
Daily Standups
1
Weekly Sync (15 min)
6
Team Members
$0
Tool Cost (free tiers)
1 — Core Principles
Two teams, two work patterns. Priceless LLC (Leo + James) ships code 30+ hrs/week. Founding Team (George, Jose, Luis, Vanessa) contributes domain expertise, testing, and sales ~5 hrs/week each. Standups waste time for both groups. Instead:
- Transparency is automated — tools report progress, not people
- Coolify is the CI — every push triggers Nixpacks builds, deploys, and reports. No GitHub Actions.
- Claude generates standups — reads GitHub activity and posts a plain-language digest weekly
- One meeting per week — 15-minute Friday sync, agenda auto-generated
2 — The Stack
Coolify + Nixpacks
Build, Deploy, Preview
- Nixpacks auto-builds Docker images on every
git push - Preview apps per branch for the team to test
- Deploy notifications sent to Slack
- Coolify manages deploys on homelab — replaces GitHub Actions entirely
Automated
Self-Hosted (Free)
Jira
Work Tracking + Task Management
- Kanban boards for tasks, bugs, doc uploads, sales pipeline
- Custom issue types: "Doc Upload", "Sales Intro", "Bug Report"
- GitHub integration: PR with
CT-123auto-transitions tickets - Familiar to founding team from construction PM tools
Both Teams
Existing Access
Slack
Communication Hub
#general— announcements, decisions#product— deploy notifications, feature discussions#bugs— testing feedback, issues from founding team#sales— client intros, pipeline updates
Both Teams
Free
Claude Auto-Standup
AI-Generated Weekly Digest
- System cron runs every Friday at 3pm
- Reads GitHub commits, PRs, Coolify deploys, and Jira tickets
- Claude translates to plain language for non-technical team
- Posts to
#product— zero human effort
Automated
~$0.02/week
Remotion Video Changelog
Auto-Generated Weekly Video
- Claude generates structured changelog from GitHub + Jira
- Remotion renders branded 20-30s video (React components)
- Animated: shipped features, metrics, what's next
- Posted to Slack automatically — replaces manual Loom
Automated
~$0.01/render
Notion
Docs, Wiki, Sales Pipeline
- Meeting notes, regulatory documents
- Sales pipeline tracker for founding team
- Knowledge base for domain expertise
Founding Team
Free
3 — Information Flow
Automated
Manual (minimal)
Engineering (Leo + James)
Write Code
GitHub commits + PRs
auto
Coolify Builds + Deploys
Preview app generated
auto
Claude Digest
Weekly summary posted to Slack
Slack
#product
#product
Founding Team
See Deploy Notification
Click preview URL to test
manual
Report Bugs / Feedback
Post in #bugs or create Jira ticket
manual
Upload Docs / Sales Intros
Complete Jira tickets assigned to them
4 — Weekly Rhythm
Automated (no effort)
Manual (human action)
A
MON — FRI (CONTINUOUS)
Coolify deploy notifications
Every code push triggers a build. Success/failure posts to
#product automatically.M
AS NEEDED
Founding team completes assigned issues
Upload regulatory docs, report bugs, make sales intros. Check Jira board for what's assigned to them.
A
FRIDAY 3:00 PM
Claude auto-standup posts
Cron reads GitHub activity + Coolify deploys. Claude generates plain-language summary. Posts to
#product.A
FRIDAY 3:05 PM
Remotion renders video changelog
Changelog JSON fed to Remotion Lambda. Branded 20-30s video with shipped features, animated metrics, and next-week priorities. Posted to
#product.M
FRIDAY 3:30 PM
15-minute weekly sync
The only meeting. Agenda: Claude digest + Loom recap + quick Q&A + next week priorities. Skip if nothing to discuss.
5 — Who Does What
| Activity | Who | Where | Frequency | Effort |
|---|---|---|---|---|
| Write & ship codeFeatures, fixes, infrastructure | Leo + James | GitHub + Coolify | Daily | 30+ hrs/wk |
| Test new featuresClick through preview URLs, report bugs | Founding Team | Coolify previews + #bugs |
2-3x/week | 1-2 hrs/wk |
| Upload regulatory docsBuilding codes, permits, jurisdiction files | Founding Team | Jira | As available | 1-2 hrs/wk |
| Sales introductionsWarm intros to potential clients | Founding Team | #sales + Notion |
As available | 1 hr/wk |
| Review compliance outputValidate AI-generated regulatory analysis | Founding Team | Coolify previews | Weekly | 1 hr/wk |
| Weekly standup digestGitHub + Coolify activity summary | Claude (automated) | System cron + #product |
Friday 3pm | 0 min |
| Deploy notificationsBuild success/failure alerts | Coolify (automated) | #product |
Every push | 0 min |
| Video changelogAnimated recap of shipped features + metrics | Remotion (automated) | Remotion Lambda + #product |
Friday 3:05pm | 0 min |
| Weekly sync meetingOnly synchronous touchpoint | Everyone | Video call | Friday | 15 min |
6 — Getting Started
Setup Checklist (~2 hours)
1. Slack Workspace
Create workspace + 4 channels
~10 min
~10 min
2. Jira Project
Create board, issue types, GitHub integration
~20 min
~20 min
3. Coolify + Slack
Connect deploy notifications
~5 min
~5 min
4. Claude Standup Cron
System cron + GitHub + Jira APIs
~20 min
~20 min
5. Remotion Video
Composition + Lambda deploy
~45 min
~45 min
6. Invite Team
Add founding team to Jira + Slack
~15 min
~15 min
The key insight: Geekbot only knows what people tell it. Claude knows what people actually did.
If transparency requires human effort, it won't happen. Every notification in this system is automated — progress is visible because the tools report it, not because someone remembered to write an update.