Your finance model, inside Claude.
Connect Claude to Exigyn and ask about runway, clinical spend and hiring in plain language. Claude answers with your plan's numbers, through the same calculations, permissions and audit trail as the app.
Claude does the reasoning. Exigyn holds the numbers.
Ask in plain language
Runway, burn, clinical spend, hiring and variances. Claude calls Exigyn and answers with your plan's numbers, not a guess.
One set of numbers
Claude, the Exigyn agent and the app all run the same calculations. The answer in Claude ties to the screen your board sees.
Agents propose. Finance approves.
Writes are permission-checked by role, shown before and after, and applied only when approved. Every change lands in the audit log.
Bring Claude-built models
Workbooks your team builds with Claude in Excel import as live models: formulas kept, tied out cell by cell, then linked to your plan.
Every program decision, asked in plain language.
"What does a 12-week supply delay on EXG-201 do to our cash at readout?"
"Gate the 14 Phase 3 and launch hires to the topline readout. Show runway both ways."
"Why is Q3 R&D over budget? Break it down by vendor and program."
"Reforecast the PPD CRO budget for slower enrollment at our EU sites."
"Build a board deck on runway, burn and hiring for Thursday."
"Map this Excel model to our clinical plan and show me what would change."
Connected in two minutes.
Exigyn runs a hosted MCP server. Sign in with your Exigyn account and your role, scopes and plan come with you.
Claude (web and desktop)
Open Settings → Connectors → Add custom connector.
Paste the Exigyn MCP URL below.
Sign in with your Exigyn account to authorize.
https://start.exigyn.com/api/mcpClaude Code
Add the server:
claude mcp add --transport http exigyn https://start.exigyn.com/api/mcpRun /mcp inside Claude Code and complete sign-in in your browser.
Built for regulated finance.
Connecting Claude doesn't open a side door. Every request runs through the same access rules and records as the app.
✓Role-scoped access
Admins, editors and viewers get the same scopes in Claude as in the app. Viewers can't write.
✓Every write audited
Who, what tool, when and the payload, logged to your org's audit trail.
✓Confirmation on destructive actions
Deletes and full replacements require explicit confirmation.
✓Org isolation
Row-level security keeps each organization's data separate, enforced server-side.
✓Versioned records
Budget versions, amendments and accruals are immutable. Old versions stay readable.
✓No training on your data
Your data is never used to train models.
Built it with Claude in Excel? It runs in Exigyn.
Import the workbook as an exact copy: formulas, formats and named ranges kept, and every cell tied out to Excel's values. Then Model Map links it to your clinical, OpEx, revenue and workforce plans. Nothing is retyped.
Questions.
Any Claude app that supports custom MCP connectors, plus Claude Code. Connect once with your Exigyn sign-in; your role and scopes come with you.
Bring your finance model into Claude.
Start in the sandbox, or talk to us about connecting your team.