Your Daily Rhythm
2026-07-13 · How your day runs: the daily meeting, Slack, the scoreboard, the numbers you own, and how you close out each day. You start Jul 14.
What this isYour daily flow with Akash.
Why it mattersSame rhythm every day. No guessing.
What you doFollow it. Close out clean.
Read time4 minutes.
Confirm at kickoff: whose 1 PM? You work Philippine time. Akash works Eastern time. The daily meeting is "1 PM" — but not yet fixed to one clock. 1 PM in one zone is the middle of the night in the other. First thing at kickoff, pick the exact time that works for both.
A day in your life
Your workday has a simple shape. One meeting, one build block, one report.
Daily meeting · 1–2 PM
Meet Akash live. Read the scoreboard together. Go over yesterday. Pick your one priority for today. In the ramp, this is every day.
Build time · 2–4 PM
Make the day's content and ads. This is your main block. Stay in it.
End-of-day report · 4 PM
The system fills in the numbers. You add 5 short notes and check one list. Then you post it in Slack (#daily-reports).
Log off clean
Four quick steps and you are done. No loose ends for tomorrow.
The daily meeting
Live, every day 1–2 PM
You meet Akash live during the part-time ramp. This is where your judgment gets calibrated. As things settle, it can drop to a few days a week.
Your 4 PM report feeds it daily
Your end-of-day report in Slack is the input for the next meeting. Akash reads it, and answers come back at the meeting or in Slack.
The meeting agenda (same order each day)
1Read the scoreboard
2Yesterday
3Today
4Decisions
5Taste-pass
If a topic runs long, it becomes a task or a parked decision. The meeting never runs over.
Slack — our team chat
Slack is the main place the team talks. You join on day 1. WhatsApp is only for quick pings until you are set up in Slack.
Where things go
- #daily-reports — your 4 PM report + daily numbers
- #client-onboarding — your first build
- #call-ins — booked calls and call notes
- #notes — quick thoughts and small questions
- #documents — links to docs and finished work
Rule of thumb
Reports and numbers go to #daily-reports. Client setup goes to #client-onboarding. Call activity goes to #call-ins. Loose notes go to #notes. File links go to #documents.
The scoreboard
The scoreboard is one page that shows each lane's target and actual for the day. You read it, you don't rebuild it from memory.
live Already built
The Loop Engine (our automatic scoreboard) is running today. It tracks 8 department lanes. Weekly targets are set. Daily numbers flow in on their own.
week 2 Being dialed in
Your daily lanes get added as tracked numbers. From week 2 you own keeping them fed and correct.
The numbers you own vs. the numbers Akash keeps
Collins owns
- Daily slate: all 5 formats shipped
- Ads staged and ready
- Speed to a new lead
- Follow-up coverage
- No-show recovery
Akash keeps
- Cash collected
- Qualified calls held
- Spend and budget
- Finance
Your work feeds Akash's numbers. You never own those numbers yourself.
End of day: who does what
The AI does
- Slate scorecard, with links
- Ads staged: count + previews
- Every change you made, with undo links
- Board changes + tomorrow's queue
You never type these.
Collins does
- What you built that the log can't explain
- What you checked, and the proof
- What's blocked, and the decision you need
- What you need from Akash
- Tomorrow's first move
5 short notes.
Collins verifies
- The "for Akash" list is complete, with links
- Every outside change has an undo entry
- Nothing client-facing is set to auto-send
Check before it posts.
Log off: your checklist
- Save your work. One command to push your branch (git push). That is the whole save.
- Board current. Your 3 cards show true status. Move what's done.
- Tomorrow staged. Content queue loaded. Ad inputs picked. No morning scavenger hunt.
- Run
builder-eod. One command writes your report, files your tasks, and posts to Slack #daily-reports.
What you do NOT do: no drive uploads, no backup rituals, no hand-updated task lists.
Git saves your work. The brain (our shared memory) holds your tasks. The report files itself.
What you do next
- Learn this flow so it feels automatic by day 1.
- At kickoff, confirm the 1 PM meeting time in both zones.
- Close every day with the log-off checklist above.
Extra detail — the tables behind your scoreboard (skip on day one)
All of this already runs in Postgres (our shared database). You do not build it.
- LIVE — 8 lanes in
sp_department_registry: Content Strategy, Repurposing, Demand, Sales, CRM+Systems, Client Success, Finance, Onboarding. Each has a lead and a lag metric.
- LIVE — Weekly targets set (46 rows in
sp_department_targets, week 07-13). The Sunday projections rite ran 07-12.
- LIVE — Daily actuals flowing: 12 metric keys in
sp_daily_actuals, fresh today. Metric definitions live in scorecard_metrics (25 metrics).
- PARTIAL — About 1 week of history. Client Success and Finance lanes are thin (correct — no clients yet).
Still to dial in before day 1 (built by Claude/agents)
| Gap | Fix |
|---|
| No single rendered scoreboard page yet | Build the dashboard (CF Pages, live mode): 8 lanes × target/actual/Δ, red-lane-first, plus Collins' production row. |
| Collins' production lanes not registered yet | Add to scorecard_metrics: production.daily_slate_completion, production.ads_staged, sales_automation.speed_to_lead_min, followup_coverage_pct, noshow_recovery_rate. |
| Feeds for those lanes | Wire from sp_organic_queue/sp_content (slate), sp_ads_pipeline_items (staged ads), sp_auto_followup_queue/sp_ghl_* (sales automation). Collins owns keeping these fed from week 2. |
| Targets are starter guesses | Run 2 clean weeks of locked targets + logged actuals before stretch/tightening kicks in. |
Starter targets
- Daily slate: 5/5 formats every workday (newsletter + organic + AI-UGC video + carousel + statics).
- Content: 20 scripts/week · 40 statics/week (already set).
- Repurposing: ≥7 assets per recording (already set).
- Ads staged: daily batch, number set at kickoff.
- Sales automation: baseline in week 3, then targets.
End-of-day report — the exact fields and checks (mechanics)
The AI compiles (from the brain, at your logoff)
- Slate scorecard: which of the 5 formats shipped, with links (from
sp_organic_queue/sp_content).
- Ads staged today: count + previews + hooks (from
sp_ads_pipeline_items); autopilot's verdicts (from sp_test_decisions).
- Every ledgered change with a rollback link.
- Board deltas + tomorrow's queue depth.
The builder-eod script
One command runs steps 4–5 of log-off: it reads the brain, renders the report, prompts your 5 fields, writes the handoff row, and posts. Week-1 fallback if it isn't ready: fill daily-update-template.txt by hand; the AI half is compiled for you next morning. The checklist holds either way.
The one list Akash trusts
The "for Akash" list holds every item waiting on his flip — spend, sends, approvals — each with a link. A miss here breaks the system. Verify it before the report posts.
For Akash — open items to confirm (not Collins' to-do)
- Daily meeting time: 1–2 PM, live daily during the ramp. Open sub-item: confirm whose zone the 1 PM is on (Collins is PH time).
- Confirm Collins' starter targets: 5/5 slate daily; ads-staged/day number; sales-automation baselines in week 3.
- Report surface is set: it writes to the brain and posts in Slack #daily-reports at 4 PM.
Verified against the brain 2026-07-13. Companion docs:
Builder Vision ·
Start Plan ·
the board.