| Client | Company | Phase | Progress | Updated |
|---|---|---|---|---|
| No deals yet | ||||
| Client | Company | Phase | Progress | Value | Assigned To | Updated |
|---|
Upload a CSV file
No file loaded yet. Choose a CSV export of your deal book. The first row must be the column headers, and every row needs an email in a column you will map to deal_email (the deal's unique key).
Map columns
Match each column in your file to a deal field. Unmapped columns are skipped. One column must map to deal_email. Stage, dates, and gate fields are set by the pipeline and cannot be imported.
Dry-run validation
no rows written yetThis is a dry run: every row is checked and nothing is written yet, so you can fix problems first. Committing writes only the valid rows; re-running the same file later is safe because rows are matched by their email and updated in place, never duplicated (that is what "idempotent" means). A blank or invalid email, or a money value that is not a number, is reported as an error and skipped; errors never block the good rows.
| Row | Deal | Action | Status | Detail |
|---|
Import complete
The valid rows are now in your pipeline. If any rows needed attention, download the error report, fix those rows, and re-import the same file; the rows that already imported are skipped.
| Role | Status | Last sign-in | Actions | |
|---|---|---|---|---|
| Loading… | ||||
| Role | Invited | Expires | Actions |
|---|
Branding
Your firm's name as it appears across the app. Changing it updates the name everyone sees on their next page load, and applies to everyone in your organization instantly.
set it to Cascade Deal Partners.
Terminology
Rename the core words the interface uses. Everyone sees the new labels on their next page load; the underlying data and keys never change, so nothing breaks.
rename "deal" to "engagement", so the pipeline reads Engagements.
Custom fields
Extra fields you define that appear on every deal. Adding or removing one changes the deal form, CSV import and export, and the API for everyone immediately.
add a Franchise? yes/no field, or an Earnout % number.
How custom fields work
Approval gates
Checkpoints a deal must pass before it can move forward, such as a signed checklist. These are set by your deployment configuration and enforced on the server, shown here for reference; they cannot be turned off from Settings.
a deal cannot advance past due diligence until its checklist is approved.
Valuation registry
The market multiples the deal valuation tool uses, by practice type. Each range needs a source and an as-of date; until then it shows as an unsourced placeholder. Saving is live for everyone immediately.
ranges are MULTIPLES (e.g. 5x EBITDA), not dollar amounts.
Documents
Which documents each deal tracks and how each is handled. Handling is firm-provided, routed to your e-signature provider, or handled by external counsel. Saving is live for everyone immediately.
the product tracks status and records receipt; your firm's own documents and counsel govern. External-counsel records receipt only — it never drafts or sends a document for you.
Email (SMTP)
Connect an email account so the app can send invitations and notifications for you. Optional: the product runs fully without it. When set, new-user invites are emailed automatically; the password is stored encrypted and is never shown back.
Microsoft 365 uses host smtp.office365.com, port 587, STARTTLS.
Which provider settings do I use?
Email (SMTP)
Whether the app can send email for you (invitations, notifications). Turning it on emails new-user invites automatically; leave it off and you simply copy invite links by hand. Configure it in Settings → Email.
connect Microsoft 365 so a new agent's invite lands in their inbox.
Automation webhooks
Send a signed message to another system whenever something happens in the app, so it can react automatically. Register a URL and the app posts signed events to it; a registered endpoint keeps receiving future events until you disable or remove it. No specific vendor is required.
point it at a Zapier or Make webhook to log every new deal to a spreadsheet.
Which events, and how do I trust them?
| URL | Status | Last delivery | Actions |
|---|
API access
Issue a token so another program can read or update your data through the REST API. The token is shown once; anyone who holds it acts with the scope you pick. Revoke it any time to cut off that access immediately.
a read-only token for a nightly reporting script.
Scopes and safety
Authorization: Bearer <token> (the same scheme the OpenAPI spec documents). Read-only tokens can list data but never change it; read + write tokens can also create and update. Tokens are stored hashed, never in plain text, and a revoked token stops working at once.Authenticate with the header Authorization: Bearer <token>. Full endpoint reference: OpenAPI spec
| Name | Principal | Scopes | Last used | Actions |
|---|
Website intake (inbound)
Let your website or a form tool create deals automatically by posting to this address. Each request is signed with a shared secret, and re-sending the same submission never creates a duplicate.
a website enquiry form files a new deal the moment it is submitted.
Setting it up
E-signature (inbound callback)
Let your e-signature provider advance a deal when a document is signed, by posting a signed callback to this address. Enable it, rotate a per-install secret shown once, and paste that secret into your provider or automation.
works with DocuSign, Adobe Acrobat Sign, or Dropbox Sign via Zapier, Make, Power Automate, or n8n. The callback only advances a deal one stage and never past an unapproved approval gate. Verification recipe: docs/connections/esign-callback.md.
| Client | Company | Assigned To | NDA Signed | |
|---|---|---|---|---|
| Loading… | ||||
| Time | Actor | Action | Target | Summary |
|---|