Skip to content
cccskills
FreePublished on GitHub

fundraising-data-room-checklist

Prepare a diligence data-room index with ownership, freshness, access level, conflicts, and counsel review gates.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Fundraising data-room checklist

Use this to index and check records. Do not create missing legal or finance documents and do not grant access.

Build the index

For every file record the section, exact title, covered entity, date or version, owner, approval state, confidentiality class, approved audience, and open issue. Keep superseded files marked as such rather than deleting their history.

Suggested sections:

  • company formation, governance, and board approvals;
  • ownership and security records;
  • financial statements, management reports, budget, and model;
  • banking, debt, grants, and material commitments;
  • customer, supplier, and partner agreements;
  • intellectual property and employment records;
  • privacy, security, insurance, disputes, and compliance;
  • product, market, commercial, and operating metrics.

The company and its counsel decide which sections apply.

Check each section

Flag missing signatures, stale dates, conflicting entity names, inconsistent totals, broken links, duplicate current versions, personal data that is not needed, and records whose audience has not been approved. Compare ownership and finance totals only to identify differences; do not decide which record governs.

Use status values: present and reviewed, present and needs review, requested, not applicable by named owner, or blocked. Never mark not applicable yourself when the item concerns legal, tax, ownership, or compliance.

Produce the diligence queue

Return completion by section, critical conflicts, access concerns, missing owners, and one next action per open item. Keep internal risk notes out of files shared with an investor unless the owner approves them.

Safety rules

Never forge, backdate, amend, or sign a document; interpret a legal term; or share a file. Redact or restrict personal, customer, bank, health, and security data to the least needed. Route legal sufficiency, disclosure, privilege, securities, and ownership questions to counsel and the finance lead.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Write ad variants that each test one idea, within platform limits and supported claims.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

See all skills by Significant-Gravitas

Report a problem with this skill