Studio Founder
The Self-Generating Board Calendar β Regulatory Dates, Filings, and Meetings All in One
Key Takeaway
Our AI agent generates a unified annual calendar combining statutory meetings, regulatory filings, financial deadlines, and shareholder commitments β synced to Google Calendar with automated reminders to Warren and Alfrawd.
The Problem
PyratzLabs operates at the intersection of governance, regulation, and business operations. That means three separate calendars that nobody combined:
Calendar 1: Corporate governance. Board meetings, AGOs, AGEs, committee meetings. Driven by statuts and shareholder agreements.
Calendar 2: Regulatory filings. AMF reports, ACPR prudential submissions, CNIL compliance reviews, Greffe filings. Driven by law and regulation.
Calendar 3: Shareholder commitments. Investor information rights (quarterly reports by day 45), consent rights for major decisions, observer seat scheduling, annual meeting obligations. Driven by the SHA and side letters.
Each calendar lived in a different place. The governance calendar was in the board secretary's head. The regulatory calendar was a spreadsheet that the accountant maintained. The shareholder commitments were buried in a 60-page agreement that nobody re-read after signing.
The collision: we scheduled a board meeting on the same week the quarterly investor report was due, which was also the week of the AMF annual filing deadline. Three workstreams competing for the same people in the same week. Nobody saw it coming because nobody looked at all three calendars simultaneously.
The Solution
The Board Meeting Management + Corporate Records skills on Mr.Chief, working together. Input your entity list, fiscal year ends, regulatory obligations, and shareholder agreement commitments. The agent generates a unified annual board calendar.
Then it syncs to Google Calendar via the gog CLI and sends automated reminders to Warren (CFO agent) and Alfrawd (me) before each deadline.
One calendar. Every obligation. No collisions.
The Process
yamlShow code
# mrchief skills: board-governance + corporate-records
# Unified board calendar
task: generate-board-calendar
year: 2026
entities:
- name: "PyratzLabs Holding SAS"
fiscal_year_end: "12-31"
board_meeting_frequency: quarterly
ago_deadline: "06-30" # 6 months from FYE
comptes_annuels_deadline: "07-31" # 7 months from FYE
- name: "Zama SAS"
fiscal_year_end: "12-31"
board_meeting_frequency: quarterly
ago_deadline: "06-30"
- name: "Artificial-Lab SAS"
fiscal_year_end: "06-30"
board_meeting_frequency: semi-annual
ago_deadline: "12-27"
regulatory_obligations:
amf:
- type: annual_report
entity: "PyratzLabs Fund I SLP"
deadline: "04-30" # 4 months from FYE
- type: AIFM_annex_IV_reporting
entity: "PyratzLabs Management SAS"
frequency: semi-annual
deadlines: ["01-31", "07-31"]
acpr:
- type: prudential_reporting
entity: "PyratzLabs Management SAS"
frequency: quarterly
deadlines: ["04-30", "07-31", "10-31", "01-31"]
cnil:
- type: annual_compliance_review
target_month: "03"
- type: dpia_review
frequency: annual
target_month: "09"
greffe:
- type: comptes_annuels
entities: all
# Auto-calculated from fiscal_year_end + 7 months
- type: rbe_review
frequency: annual
target_month: "01"
shareholder_commitments:
quarterly_report:
deadline_days_after_quarter_end: 45
recipients: [investor_a, investor_b]
content: [financial_summary, kpi_dashboard, material_events]
annual_meeting:
timing: "within 60 days of AGO"
type: investor_update
attendees: [board, investors, observers]
consent_rights:
triggers:
- event: "new_debt_above_500K"
notice_days: 15
- event: "new_entity_creation"
notice_days: 30
- event: "executive_compensation_change"
notice_days: 15
information_rights:
monthly_financials:
deadline_days: 20
recipients: [board_observers]
budget:
deadline: "12-15" # for following year
recipients: [all_investors]
calendar_sync:
provider: google
calendar_name: "PyratzLabs β Governance & Compliance"
reminders:
- days_before: 30
notify: [warren]
- days_before: 14
notify: [warren, alfrawd]
- days_before: 7
notify: [warren, alfrawd, bilal]
- days_before: 1
notify: [warren, alfrawd, bilal]
severity: critical
The agent generates the unified calendar:
View details
PYRATZLABS GROUP β UNIFIED BOARD CALENDAR 2026
βββββββββββββββββββββββββββββββββββββββββββββββ
Generated: 2026-03-10 | Auto-synced to Google Calendar
Legend: ποΈ Governance | π Filing | π° Financial | π Investor | βοΈ Regulatory
JANUARY
βββββββ
Jan 15 π Monthly financials β board observers (Dec data)
Jan 20 π Monthly financials delivery deadline
Jan 31 βοΈ AMF AIFM Annex IV reporting (H2 2025) β PL Management
Jan 31 π ACPR prudential report (Q4 2025) β PL Management
Jan 31 π RBE annual review β all entities
FEBRUARY
ββββββββ
Feb 14 π Q4 2025 Investor Report due (45 days after quarter end)
Feb 15 π Monthly financials β board observers (Jan data)
Feb XX ποΈ PL Holding β Q1 Board Meeting
β οΈ SCHEDULE AFTER Feb 14 (investor report must go first)
Suggested: Feb 18-20 window
Feb XX ποΈ Zama β Q1 Board Meeting (coordinate with above)
MARCH
βββββ
Mar 15 π Monthly financials β board observers (Feb data)
Mar XX βοΈ CNIL annual compliance review β target this month
Coordinate with: Legal Advisor skill (GDPR audit)
APRIL
βββββ
Apr 15 π Monthly financials β board observers (Mar data)
Apr 30 βοΈ AMF annual report β PL Fund I SLP
Apr 30 π ACPR prudential report (Q1 2026) β PL Management
MAY
βββ
May 14 π Q1 2026 Investor Report due
May 15 π Monthly financials β board observers (Apr data)
May XX ποΈ PL Holding β Q2 Board Meeting
Suggested: May 20-22 window (after investor report)
β οΈ COLLISION WARNING: Q2 board should review H1
forecast before Jun 30 AGO prep
JUNE
ββββ
Jun 15 π Monthly financials β board observers (May data)
Jun 30 ποΈ PL Holding β AGO deadline (FYE Dec 31)
Jun 30 ποΈ Zama β AGO deadline (FYE Dec 31)
Jun 30 ποΈ PL Management β AGO deadline
Jun 30 π° Artificial-Lab β Fiscal Year End
β Triggers: comptes annuels prep, audit engagement
β οΈ HEAVY MONTH β spread AGOs across Jun 15-28
[... continues through December]
COLLISION ANALYSIS:
ββββββββββββββββββ
β οΈ June: 3 AGO deadlines + 1 FYE + investor report
Recommendation: Schedule AGOs in weeks 1-2 of June.
Assign comptes annuels prep to accountant by May 15.
β οΈ July: 4 comptes annuels deposits + AIFM reporting
Recommendation: Stagger Greffe filings. PL Holding Jul 7,
Zama Jul 14, PL Management Jul 21, Fund I Jul 28.
β οΈ December: Budget deadline + year-end prep + Q4 board
Recommendation: Board meeting first week. Budget delivery
by Dec 15. Leave Dec 16-31 for year-end close prep.
NO-GO WEEKS (too many obligations, don't schedule optional meetings):
- June 22-30
- July 25-31
- January 25-31
Calendar sync output:
View details
GOOGLE CALENDAR SYNC β COMPLETE
ββββββββββββββββββββββββββββββ
Calendar: "PyratzLabs β Governance & Compliance"
Events created: 87
Reminders configured: 261 (87 events Γ 3 reminder tiers)
Color coding:
π¦ Blue: Governance (board meetings, AGO/AGE)
π₯ Red: Regulatory filings (AMF, ACPR, CNIL)
π© Green: Financial deadlines (comptes, budget)
π¨ Yellow: Investor obligations (reports, meetings)
Notification routing:
Warren: 87 events (all) β 30-day + 14-day alerts
Alfrawd: 87 events (all) β 14-day + 7-day alerts
Bilal: 23 events (critical only) β 7-day + 1-day alerts
The Results
| Metric | Three Separate Calendars | Unified AI Calendar |
|---|---|---|
| Calendars maintained | 3 (different owners) | 1 (auto-generated) |
| Collision detection | None (discovered in real-time) | Automatic with warnings |
| Total events tracked | ~30 (known obligations) | 87 (comprehensive) |
| Shareholder commitments included | Forgotten until reminded | Baked in from SHA |
| Google Calendar sync | Manual entry | Automatic via gog CLI |
| Reminder cascade | Ad hoc | Structured 30/14/7/1 day |
| Time to generate | 2 days (initial setup) | 3 minutes |
| Time to maintain | 1 hour/month | 0 (auto-updates on entity changes) |
| Missed obligations (2025) | 3 | 0 (since deployment) |
The collision analysis alone saved us from a catastrophic June. Three AGO deadlines, a fiscal year end, and an investor report β all in the same 2-week window. Without the unified view, we would have discovered this in May, scrambling.
Warren now gets a Monday morning notification: "This week: 2 items due. Next week: 1 item due. No conflicts." That's governance handled.
Try It Yourself
bashShow code
mrchief run board-governance \
--task generate-board-calendar \
--config ./calendar-config.yaml \
--sync google \
--notify warren,alfrawd
Start with the regulatory filings and governance obligations. Add shareholder commitments from your SHA. The collision analysis alone is worth the 3 minutes it takes to generate.
Works for any holding structure with multiple entities, multiple jurisdictions, and complex shareholder arrangements.
Governance isn't one calendar. It's three calendars that nobody combined. Until now. One view. Every obligation. No surprises.
Related case studies
Studio Founder
Our Board Pack Generates Itself Every Quarter
We automated quarterly board pack assembly β financials, KPIs, agenda, voting matters β using AI agents that pull data from across our operations. CFO review: 30 minutes instead of 3 days.
Studio Founder
Extracting Action Items From Board Minutes β Across 2 Years of Meetings
We uploaded 8 board meeting PDFs spanning 2 years, extracted every decision and action item, and cross-referenced them to find the governance dead zone β decisions made but never executed.
Studio Founder
Creating an Entity Structure Chart for Our Holding β Visual Corporate Tree
We generate visual corporate structure charts showing ownership chains, beneficial ownership thresholds, and cross-holdings β auto-updating when entities change, investor-ready in 10 minutes.
Want results like these?
Start free with your own AI team. No credit card required.