Weekly Erik Update (CQ)¶
Owner: Vi | Updated: 2026-02-05
Purpose¶
This is the once-a-week meeting where Erik dedicates focused time to give direction to the CQ team. This is also the weekly wrap-up—a single report that tracks progress every week.
The problem this solves: - No agenda, people rambling - No demos ready, hiding behind screens - "Giant list of what I want to say" instead of structured update - Erik doesn't get the information he needs
Meeting Details¶
| Attribute | Value |
|---|---|
| When | Every Tuesday, 9:00 PM Vietnam time |
| Duration | 45 minutes max |
| Attendees | Erik, Ryan, Vi, all CQ devs |
| Format | Video call, cameras on |
One meeting per project. CQ and Capitalist have separate meetings.
The Monday 5pm Deadline (STRICT)¶
The report must be READY by Monday 5:00 PM Vietnam time.
This is NOT when people start filling it. This is when the complete report is submitted.
| Timeline | What Happens |
|---|---|
| Monday 11am | Daily standup - all ClickUp tickets updated |
| Monday 11am-4pm | Devs ensure their updates are in ClickUp and demos uploaded |
| Monday 5pm | Report READY and submitted |
| Tuesday morning | Erik reviews report, prepares questions |
| Tuesday 9pm | Meeting |
Miss the deadline → Escalate to Ryan.
Collection Process¶
Vi's Role: Facilitate, Not Babysit¶
Vi facilitates the collection but devs are responsible for their own updates.
| Vi Does | Vi Does NOT |
|---|---|
| Remind team of deadline | Chase individual devs repeatedly |
| Consolidate into report | Write updates for devs |
| Flag missing items | Do devs' work for them |
| Escalate if deadline missed | Accept excuses |
Dev Responsibility¶
By Monday 5pm, each dev must have: - [ ] All ClickUp tickets updated with current status - [ ] Demo video uploaded (if applicable) - [ ] Progress notes ready for their priorities
Source of truth: ClickUp. After the Monday 11am standup, all tickets should be up to date. Vi pulls from ClickUp to build the report.
Weekly Status Report Template (1-2 pages)¶
Copy template each week. Google Doc.
1. REVENUE & TRACTION (Ryan)
| Metric | Last Wk | Prev Wk | Δ | Notes |
|---|---|---|---|---|
| Active Customers | ||||
| MRR | ||||
| ARR |
2. PIPELINE & MARKETING (Ryan)
| Metric | Last Wk | Prev Wk | Δ |
|---|---|---|---|
| Qualified Leads | |||
| Form Submissions | |||
| Traffic (Total / SEO) |
3. PARTNERSHIPS (Ryan) — Current discussions or N/A
4. PRODUCT (Vi)
Feedback Summary: Done: __ | In Progress: __ | Not Started: __
Issues Table:
| Issue | Customer | Days | Status | Priority Score |
|---|---|---|---|---|
Score = Impact (0-2) + Severity (0-2) + Workaround (0-2) + Time Pressure (0-2)
Current Priorities:
| # | Priority | Owner | Progress |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 |
Roadmap NEXT: [1] ___ [2] ___ [3] ___
5. SYSTEM (if applicable) — Releases, cost optimization
6. DEMOS
| Feature | Presenter | Link |
|---|---|---|
Demo Rules¶
Use Real Data¶
No fake data. Use real data or data that represents real use cases.
| Don't | Do |
|---|---|
| "Test User 1, Test User 2" | Actual customer names or realistic names |
| Random placeholder text | Real content that shows the feature working |
| Empty states | Populated states that show value |
Why: Fake data doesn't help anyone understand what's going on. Erik and the team need to see real scenarios.
Demo Storage¶
Store all demo videos in a central folder with naming convention:
Folder: [Google Drive]/CQ/Demos/[Year]/[Week]
File naming: YYYY-MM-DD_feature-name_dev-name.mp4
Example: 2026-02-03_crm-tagging_danny.mp4
Demo Format¶
- Keep under 3 minutes
- Record screen + voice walkthrough
- Use real or realistic data
- Show the complete user flow
- Upload by Monday 4pm (before report deadline)
What Erik Wants to Know¶
Erik only needs to know:
- Big picture - Where are we overall?
- Key priorities - What are the top 2-3 things we're focused on?
- Progress - How far along are we on each priority?
- Next steps - What's happening next?
- Delivery dates - When will things be done?
That's it. The report structure answers these questions.
Who Presents What¶
Move away from "Vi presents everything"
| Section | Who Presents |
|---|---|
| Revenue & Traction | Ryan |
| Pipeline & Marketing | Ryan |
| Product Overview | Vi |
| Feature Demos | Dev who built it |
| System Updates | Relevant dev |
Devs present their own work. This builds ownership.
Meeting Rules¶
| Rule | Why |
|---|---|
| Report ready Monday 5pm | Erik comes prepared |
| Cameras on | Engagement and accountability |
| No rambling | Report already covers details |
| Demos use real data | Everyone understands the feature |
| Devs present demos | Builds ownership |
| Start and end on time | Respect everyone's schedule |
Escalation¶
| Issue | Escalate To |
|---|---|
| Report not ready by 5pm Monday | Ryan |
| Dev didn't submit their updates | Vi → Ryan |
| Demo not uploaded | Vi → Ryan |
| Repeated misses | Ryan → Erik |
This deadline is not negotiable.
After the Meeting¶
Within 2 hours, Vi posts summary:
## CQ Weekly Update - Summary [Date]
### Decisions Made
- [Decision 1]
- [Decision 2]
### Action Items
| Action | Owner | Due |
|--------|-------|-----|
| [Action 1] | @name | [Date] |
### Erik's Direction
- [Key feedback or direction changes]
### Next Week Focus
- [Priority 1]
- [Priority 2]
Template Location¶
Google Doc template: [Share link to template]
Copy the template each week. Don't edit the master.
Integration with Other SOPs¶
| SOP | Connection |
|---|---|
| Weekly Planning Meeting | Wednesday planning incorporates Erik's Tuesday direction |
| Daily Dev Update | Daily updates feed into weekly report |
| Task Creation Standards | ClickUp is source of truth |
FAQ¶
Q: What if I don't have anything to demo? A: Show progress anyway—wireframes, partial flows. "Nothing to show" is not acceptable.
Q: What if my demo has bugs? A: Re-record until it's clean. That's why we do pre-recorded demos.
Q: What if the deadline is too tight? A: Plan ahead. Don't wait until Monday to start preparing.
Q: What if ClickUp isn't updated? A: That's a problem. ClickUp should always be current. Fix it.
Q: What if Erik has questions the report doesn't answer? A: "I'll find out and follow up by [date]." Don't make things up.
Summary¶
| Principle | Why |
|---|---|
| Monday 5pm deadline (STRICT) | Erik reviews before meeting |
| Devs are proactive | Vi facilitates, doesn't babysit |
| Real data in demos | Fake data doesn't help |
| Same report structure weekly | Consistency enables tracking |
| Devs present their work | Builds ownership |
This meeting is Erik's time to give direction. Come prepared so he can.