# Host a financial model from Claude so your team can use it > Source: > Published: 2026-09-17 12:00:00+00:00 [Blog](https://oncroft.net/blog/) · September 18, 2026 · Rich Chetwynd # Host a financial model from Claude so your team can use it Built a forecast or investment model in Claude? Host it as a private team app with a shared URL and saved numbers, not emailed HTML or chat-only copies. ## Quick answer To **host a financial model from Claude** so your team can use it, deploy the model as a private app on Croft. Your colleagues open a normal link, work against **shared saved numbers**, and you keep iterating in chat. That is the path when search says **share financial model app with team** or **Claude financial model for team**: a lasting URL and one source of truth, not another HTML attachment. ## The model worked. Sharing did not. Finance and accounts people are already building useful tools in Claude: forecasts, investment models, P&L helpers, scenario calculators. The cliff is not the first draft. It is getting the rest of the team onto the same live model. What usually happens: - The model lives in **your** Claude chat. Colleagues cannot open it on their own. - You email an `.html` file. Everyone has a different copy. Nobody shares one set of saved numbers. - You drop it in a shared spreadsheet. The logic that made the Claude model useful gets flattened, and version chaos returns. - You put it on a public host. Internal forecasts and assumptions sit on the open web unless you invent login yourself. So the Claude financial model is good. The team still cannot use it together. ## What hosting should mean for a finance tool For a forecast or investment model, hosting is not “any live URL.” It is: 1. A **link the team can open** in a browser 2. **Shared saved data** so inputs and results persist for everyone 3. **Team sign-in** , so outsiders cannot wander into the numbers 4. **Backups and a way to undo** a bad change 5. A path to **update by chatting** again, without rebuilding from zero If you do not care about coding or deploy, the host should handle HTTPS, deploys, and keeping the server online. This is different from generic [Claude artifact sharing](https://oncroft.net/blog/share-claude-artifact-with-your-team/). Here the job is specifically a **financial model**: forecasts, investment models, P&L tools that need the whole team on one set of numbers. ## Claude chat vs email vs spreadsheet vs Croft | Need | Claude chat | Emailed HTML | Shared spreadsheet | Public host | Croft | |---|---|---|---|---|---| | Team opens their own link | No | Fragile copies | Yes (sheet, not the app) | Yes | Yes | | Shared saved numbers | No | No | Yes, but logic thins out | Extra setup | Included | | Private to your people | Chat-only | File chaos | Usually | You build login | Built in | | Keep the Claude model UX | Yes (for you) | Static file | Lost in cells | Varies | Yes | | No devops required | N/A | N/A | N/A | Sometimes | Yes | Croft is the private place for internal vibe-coded and artifact apps. It is not a public AI-SaaS host, and it is not “keep the Excel file and wrap it.” You bring the Claude model; Croft gives your team a shared app. ## Steps: Claude financial model → team app 1. Get a croft (private server for your workspace). 2. [Connect Claude](https://oncroft.net/connect/claude/) over MCP, or use[Croft Build](https://oncroft.net/build/) in the browser if you prefer not to connect an assistant yet. 3. Ask Claude to **deploy the financial model to your croft** as an app (or rebuild the same logic there from the artifact). 4. Invite colleagues. They open a normal URL, sign in with company login, and work against shared saved numbers. 5. Keep chatting to change assumptions, scenarios, or screens. Deploys and rollbacks stay on the server. More on the product path: [From artifact to app](https://oncroft.net/artifacts/). Prefer Cursor for the next iteration? See [host a Cursor app](https://oncroft.net/host-cursor-app/) and [connect Cursor](https://oncroft.net/connect/cursor/). Ready-made starting points: [templates](https://oncroft.net/templates/). Need live business data later: [connectors](https://oncroft.net/connectors/). You still do not need to learn nginx, Docker, or “how to deploy.” The point of Croft is that the assistant can ship the model for you. ## FAQ ### How do I share a financial model app with my team? Deploy it to Croft as a private app, then invite the people who should use it. They get a normal link and shared saved numbers. Details on [artifacts to apps](https://oncroft.net/artifacts/) and [connect Claude](https://oncroft.net/connect/claude/). ### Can I just email the HTML from Claude? You can, once. Then someone edits a rate, another person has an old copy, and nobody has one source of truth. That is fine for a demo. It is not fine for a forecast or investment model the team uses every week. ### Is this the same as putting the model on a public host? Public hosts are strong for public products. For an internal financial model you usually want a private server and team sign-in by default, not a public URL you lock down after the fact. See also [Where to host a vibe-coded app so it stays private](https://oncroft.net/blog/where-to-host-a-vibe-coded-app-privately/). ### What if the model started as a spreadsheet? Same destination: a private team app with shared data. Croft is for hosting the app your team opens, not for wrapping Excel forever. If you are still in sheet land, start from the Claude or Cursor rebuild, then deploy. ### Do I need to be technical? No. If you can chat with Claude and build the model, you can ask it to deploy to Croft. The people who get the most from this are finance and accounts experts, not platform engineers. ### How much does Croft cost? Solo from $24/month on annual billing, Team $99/month on annual. 7-day free trial, no card to start. See [pricing](https://oncroft.net/pricing/). ## Stake out your croft. Your team's first app could be live before lunch. [Get your croft](https://app.oncroft.net/signup) 7 days free, no card to start. From $24/month - cancel anytime and take everything with you.