How to share an AI-built sales tracker with your team

Croft published a September 28, 2026 guide recommending that teams share an AI-built sales tracker by hosting it as a private app on Croft rather than emailing HTML exports or publishing it to a public host. The guide says teammates access one lasting URL, work against shared saved pipeline data, and sign in with company login, with backups and rollbacks handled on the server. It describes connecting Claude or Cursor over MCP, or using Croft Build in the browser, to deploy the tracker as an app on a private croft.

Blog https://oncroft.net/blog/ · September 28, 2026 · Rich Chetwynd How to share an AI-built sales tracker with your team Host a sales tracker built with AI as a private team app on Croft. One URL, shared pipeline data, company login, backups. Not emailed HTML or a public host. Quick answer To share an AI sales tracker with your team , host it as a private app on Croft and give everyone one URL. Teammates open it in the browser, work against shared pipeline data , and sign in with company login. That is the path for a sales tracker built with AI for team use: a lasting private app, not an emailed HTML file or a public host. The tracker works for you. Sharing it is broken. Sales people already build pipeline trackers with Claude, Cursor, or a rebuilt sheet: deals, stages, follow-ups, next actions. The app often works fine for the person who built it. The cliff is handing it to the rest of the team. What usually happens: - You email an HTML export or artifact file. Everyone has a different copy. Updates do not sync. - You drop it on a public host. Pipeline numbers sit on the open web unless you invent login yourself. - You keep it in a sheet or CRM export forever. Two people edit at once, and nobody is sure which version is current. - You demo it once in chat. Later, teammates ask for “that tracker” and you have to recreate the session. So the sales tracker is useful. The team still does not have one live app with one shared pipeline. If your starting point is a stocktake sheet rather than a pipeline, see Replace a spreadsheet stocktake with a private app https://oncroft.net/blog/spreadsheet-stocktake-to-private-app/ . For financial models: Turn a spreadsheet financial model into a private team app https://oncroft.net/blog/spreadsheet-financial-model-to-private-app/ . For hosting AI-built apps in general: Where to host an app I built with AI https://oncroft.net/blog/where-to-host-an-app-i-built-with-ai/ . This post is the sales tracker path. What sharing a sales tracker should mean For a pipeline the team relies on, “share it” is not “any live URL.” It is: 1. A lasting URL teammates can open in a browser 2. Shared saved deals so every update persists for everyone 3. Team sign-in , so outsiders cannot wander into pipeline numbers 4. Backups and a way to undo a bad change 5. A path to iterate in chat , without babysitting servers Related reading when you care about recoverability: App hosting with backups and versioning https://oncroft.net/blog/app-hosting-with-backups-and-versioning/ . Emailed HTML vs public host vs sheet vs Croft | Need | Emailed HTML / artifact | Public AI-app host | Spreadsheet / CRM export | Croft | |---|---|---|---|---| | Team opens their own link | No | Yes | Fragile copies | Yes | | Shared pipeline data | No | Extra setup | File chaos | Included | | Private to your people | File chaos | You build login | File chaos | Built in | | Leave one-off demos behind | No | Possible | No | Yes | | Keep iterating with AI chat | Limited | Varies | Limited | Yes | | No devops required | N/A | Sometimes | N/A | Yes | Croft is the private place for vibe-coded and AI-artifact apps. It is not a public AI-SaaS host, and it is not “keep the sheet forever and wrap it.” You bring the sales tracker; Croft gives your team a shared app on a private server. Steps: AI sales tracker → private team app 1. Get a croft private server for your workspace . 2. Connect Claude https://oncroft.net/connect/claude/ or Cursor https://oncroft.net/connect/cursor/ over MCP, or use Croft Build https://oncroft.net/build/ in the browser if you prefer not to connect an assistant yet. 3. Hand the assistant the tracker: paste the artifact, export key fields, or describe deals, stages, and follow-ups. Ask it to deploy the sales tracker as an app on your croft not to email HTML or publish a public URL . 4. Invite colleagues. They open a normal URL, sign in with company login, and work against the shared pipeline. 5. Keep chatting to change stages, filters, 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/ . 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 app for you. FAQ How do I share an AI-built sales tracker with my team? Host it as a private app on Croft, then invite the people who work the pipeline. They get a normal link and shared deal data. Details on artifacts to apps https://oncroft.net/artifacts/ and connect Claude https://oncroft.net/connect/claude/ . Can I just email the HTML or artifact? You can, once. Then someone updates a deal stage, 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 tracker the sales team uses every day. Is this the same as putting the tracker on a public host? Public hosts are strong for public products. For an internal sales tracker 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 an app I built with AI https://oncroft.net/blog/where-to-host-an-app-i-built-with-ai/ . What if I rebuilt the tracker from a spreadsheet or CRM export? Same destination: a private team app. Rebuild the logic as an app not wrap the sheet forever , deploy to Croft, and invite the people who should update deals. Related path for sheets: How to turn a Google Sheet into an app https://oncroft.net/blog/how-to-turn-a-google-sheet-into-an-app/ . What if I already built the tracker in Claude or Cursor? Same steps. Deploy from chat with connect Claude https://oncroft.net/connect/claude/ or host a Cursor app https://oncroft.net/host-cursor-app/ , then invite teammates so they can sign in and use the shared pipeline. Do I need to be technical? No. If you can maintain a pipeline sheet or describe your deals to an assistant, you can ask it to deploy to Croft. The people who get the most from this are sales and ops 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.