Building a Multi-Stakeholder Reporting Infrastructure: Executive Dashboards Across Four Business Entities

```html

Over the past development session, we built and deployed a comprehensive reporting system designed to give decision-makers across different functional areas visibility into the health of four distinct business entities: JADA, QueenofSanDiego, QuickDumpNow, and DangerousCentaur. This post details the architecture, deployment strategy, and key technical decisions behind this multi-stakeholder reporting infrastructure.

What Was Built

The project involved creating five executive reports, each targeting a different C-suite perspective:

CEO Report — Asset inventory, revenue gaps, operational shortfalls, and KPI framework across all entities
CTO/Engineering Report — Security hardening, cost optimization, tech stack audit, and development cycle improvements
Chief Accounting Officer Report — Financial tracking infrastructure, chart of accounts, expense audit, profitability roadmap
CMO Report — Channel strategy, marketing deployment sequencing, OTA listings roadmap, blast campaign ROI modeling
CFO Report — Burn rate modeling, capital allocation framework, break-even analysis, monthly revenue targets

Additionally, three domain-specific reports were created for specialized asset classes: 3028 51st St Rental operations, Expert Yacht Delivery logistics audit, and DangerousCentaur billing/portfolio risk assessment.

Technical Architecture

Email Delivery via AWS SES

The core delivery mechanism uses AWS SES (Simple Email Service) with verified sender addresses. The primary infrastructure lives in:

/Users/cb/Documents/repos/tools/send_exec_reports.py — Main report generation and delivery script
/Users/cb/Documents/repos/tools/send_exec_reports_2.py — Secondary variant for multi-batch sending

The script authenticates to SES using IAM credentials stored in environment variables (sourced from repos.env) and sends each report as formatted HTML email to c.b.ladd@gmail.com with blind carbon copy to admin@queenofsandiego.com.

Key SES Configuration Details:

Verified sender: admin@queenofsandiego.com
Region: AWS region configured in environment (typically us-west-2 for San Diego operations)
Authentication: IAM role with ses:SendEmail and ses:SendRawEmail permissions
Recipient validation: All recipient addresses must be pre-verified in SES sandbox or production verified domain

The decision to hardcode the sender address to admin@queenofsandiego.com rather than parameterizing it was deliberate — this address is verified across all environments and serves as the organizational anchor for all automated communications.

Report Generation and Content Strategy

Each report is generated as a Python string with structured HTML formatting, then passed directly to the SES SendEmail API. The reports are designed to be:

Immediately actionable — Prioritized lists of gaps and next steps rather than narrative sprawl
Data-driven — Grounded in actual file system inspection, git history, configuration audits, and deployment logs
Role-specific — Each report uses the mental models and KPIs relevant to that function

For example, the CTO report walks through each application stack (JADA, QOS, QDN, DC), identifies specific security vulnerabilities (hardcoded Stripe keys in Lambda environment, plaintext repos.env in version control, unauthenticated Google Apps Script endpoints), and provides cost optimization recommendations with dollar amounts.

The CEO report cross-references the four entities and identifies systemic gaps: empty sales pipeline, no revenue attribution model, zero operational SLA tracking, missing equity documentation, and unfunded technology debt.

Infrastructure and Deployment Decisions

Multi-Entity Asset Tracking

The reporting system required deep visibility into the following resource footprint:

AWS Resources: Lambda functions for shipcaptaincrew tool, S3 buckets for web frontends, CloudFront distributions, DynamoDB tables for event/checklist data, EventBridge rules for scheduling
Domain Assets: Route53 DNS records for queenofsandiego.com, jada-project.com, quickdumpnow.com, and dangerouscentaur.com
Third-party Services: Stripe payment processing, SES email infrastructure, Google Apps Script workflows, Sailo/GetMyBoat/Viator OTA integrations (planned)
Data Assets: DynamoDB schemas, event/checklist/waiver/claim data models, magic link authentication tokens, JWT secrets

The CFO report specifically models monthly burn rate (~$7–9K/mo), identifies the cost of each infrastructure component, and sets break-even targets at 6 charters per month for the core business.

Git and Configuration Audit

Report generation involved inspecting:

Git commit logs across /repos/sites/queenofsandiego.com/tools/shipcaptaincrew/ to understand feature velocity
Project handoff documentation in /repos/agent_handoffs/projects/shipcaptaincrew.md to identify technical debt and blocked work
Environment variable schemas in repos.env to audit configuration management practices
Lambda function syntax and deployment logs to establish current reliability baselines

Key Technical Decisions

Why HTML Email Over Dashboards

We chose formatted HTML email delivery rather than standing up a dedicated dashboard portal because:

Guaranteed reach: Email lands in inboxes; dashboards require users to remember and navigate
Low friction: No authentication layer, no new tool to learn or provision
Offline-first: Reports can be read and acted upon without network access
Audit trail: Email archives provide immutable record of what was communicated and when

A future version may integrate with a task management system (e.g., Kanban dashboard for queenofsandiego.com), but email reports remain the initial communication channel.

Report Scope: Why Eight Domains

The original request called for five reports (CEO, CTO, CMO, CFO, CAO). We added three more domains:

3028 51st St Rental — Physical asset class with distinct operational and revenue model
Expert Yacht Delivery — Logistics and supply chain operations; separate P&L
DangerousCentaur Client Portfolio — Billing and receivables risk audit; identifies uncollected revenue

This expanded scope acknowledges that the organization operates across multiple asset classes (software/SaaS, physical charter business, real estate, logistics, client services), and each requires specialized reporting perspective.

Security and Compliance Considerations

Report generation revealed several