finta-prod-checklist
Fundraise launch checklist using Finta CRM. Trigger with phrases like "finta checklist", "finta launch", "finta go-live".
What this skill does
# Finta Production Checklist
## Overview
Finta is a fundraising CRM for managing investor pipeline, deal rooms, and round tracking. A production integration syncs investor communications, manages deal room access, and automates pipeline stage transitions. Failures mean lost investor touchpoints, broken deal room links, or pipeline data that drifts from your actual fundraise state.
## Authentication & Secrets
- [ ] `FINTA_API_KEY` stored in secrets manager (not config files)
- [ ] OAuth tokens for email/calendar sync stored securely
- [ ] Key rotation schedule documented (before each fundraise round)
- [ ] Separate credentials for staging/prod environments
- [ ] Deal room access tokens scoped per investor group
## API Integration
- [ ] Production base URL configured (`https://api.finta.com/v1`)
- [ ] Rate limit handling with exponential backoff
- [ ] Pipeline stage sync tested with all custom stages
- [ ] Investor contact import validated (deduplication on email)
- [ ] Deal room link generation tested with expiration settings
- [ ] Email sync webhook configured for reply-to-stage automation
- [ ] Financial data integrations verified (Stripe, Mercury, Brex)
## Error Handling & Resilience
- [ ] Circuit breaker configured for Finta API outages
- [ ] Retry with backoff for 429/5xx responses
- [ ] Email sync failure detection (stale inbox = missed investor replies)
- [ ] Deal room link expiration alerts before investor meetings
- [ ] Duplicate investor detection on bulk import
- [ ] Cap table import validation (share counts, ownership percentages)
## Monitoring & Alerting
- [ ] API latency tracked per endpoint (pipeline, investors, rooms)
- [ ] Error rate alerts set (threshold: any sync failure during active round)
- [ ] Investor reply detection latency monitored (<5 min SLA)
- [ ] Deal room access analytics reviewed weekly
- [ ] Pipeline stage transition audit log enabled
## Validation Script
```typescript
async function checkFintaReadiness(): Promise<void> {
const checks: { name: string; pass: boolean; detail: string }[] = [];
// API connectivity
try {
const res = await fetch('https://api.finta.com/v1/pipeline', {
headers: { Authorization: `Bearer ${process.env.FINTA_API_KEY}` },
});
checks.push({ name: 'Finta API', pass: res.ok, detail: res.ok ? 'Connected' : `HTTP ${res.status}` });
} catch (e: any) { checks.push({ name: 'Finta API', pass: false, detail: e.message }); }
// Credentials present
checks.push({ name: 'API Key Set', pass: !!process.env.FINTA_API_KEY, detail: process.env.FINTA_API_KEY ? 'Present' : 'MISSING' });
// Pipeline stages configured
try {
const res = await fetch('https://api.finta.com/v1/pipeline/stages', {
headers: { Authorization: `Bearer ${process.env.FINTA_API_KEY}` },
});
const data = await res.json();
const count = Array.isArray(data) ? data.length : 0;
checks.push({ name: 'Pipeline Stages', pass: count >= 3, detail: `${count} stages configured` });
} catch (e: any) { checks.push({ name: 'Pipeline Stages', pass: false, detail: e.message }); }
for (const c of checks) console.log(`[${c.pass ? 'PASS' : 'FAIL'}] ${c.name}: ${c.detail}`);
}
checkFintaReadiness();
```
## Error Handling
| Check | Risk if Skipped | Priority |
|-------|----------------|----------|
| API key rotation | Lost access during active fundraise | P1 |
| Email sync monitoring | Missed investor replies for days | P1 |
| Deal room link expiry | Investors hit dead links before meetings | P2 |
| Duplicate investor import | Fragmented communication history | P2 |
| Cap table validation | Incorrect ownership reported to board | P3 |
## Resources
- [Finta Platform](https://www.finta.com)
- [Finta Help Center](https://help.finta.com)
## Next Steps
See `finta-security-basics` for investor data protection and deal room access control.
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.