Workflow review

Send us the deliverable your team dreads drafting.

The Monday-morning model commentary. The diligence note at 11 PM. The LP update that takes all of Friday. Tell us which one, who reviews it, which workbook tabs and data sources are allowed, and where the final draft belongs. We will map a four-week path to a source-backed Office draft your team can inspect and own.

What the first review leaves behind

Week 1: workflow map — the deliverable, the reviewer, the allowed workbook tabs, folders, and data vendors
Week 2: context, model, and memory policy — which facts enter each run, which model, what stays out
Week 3: a source-backed draft in Word or PowerPoint on real context from your team
Week 4: measured handoff — review time, source coverage, unsupported claims, and the edits the reviewer still makes

Workflow

Show us the deliverable

A short note is enough: the recurring output (e.g., Monday model commentary, IC deck page, diligence note), who reviews it, the workbook tabs, the SharePoint folders, the Capital IQ or FactSet screens, the templates, and the Microsoft surface where the final draft belongs.

Email

hello@valuwiki.com

Subject

ValuClaw workflow review

Security

Discuss security and data handling

Use this for questions about Microsoft 365 access scope, which SharePoint sites ValuClaw reads, source visibility, approval audit trail, model routing policy, Capital IQ and FactSet entitlement handling, data retention, or customer-data boundaries.

Email

hello@valuwiki.com

Subject

ValuClaw security review

Contact: hello@valuwiki.com

Prefer to read the code first? It's all open source on GitHub.