Total Clinics (Year 10)
--
Year-1 Net Income
--
Break-even Month
--
Final Cash Balance (Year 10)
--
10-Year Summary
| Year | Capital Investment | Clinics | New Opened | Opening Costs | Total Revenue | OpEx | Total Net Income | Cash Balance | Operating Float | Expansion Threshold | Free Cash |
|---|
Cash Balance Over 10 Years
Revenue vs Operating Expenses
All Scenarios
| Name | Description | Start Year | Created | Actions |
|---|
Edit: --
View Projection →Derived from Physician Capacity (not editable — change staffing or schedule to affect these)
Configurable Assumptions
Weekly intake = min(capacity-derived rate, this cap). Leave blank unless demand, not capacity, limits intake.
When a patient leaves the program (churn begins) and the span of the weekly detail view.
Staffing
| Role | Count | Plan | Salary ($) | Benefits (%) | Weekly Cost | Actions |
|---|
Clinic Resources
| Name | Type | Role | Capacity (hrs/wk) | Space (sqft) | Max Patients | Units | Active | Actions |
|---|
Revenue Streams
Configurable revenue items for this scenario. Each item defines what is billed, how often, and who pays.
| Name | Category | Price | Frequency | Patient Weeks | Paid By | Billing Code | Status | Actions |
|---|
Cost Items (COGS)
Variable costs that scale with patients. Fixed costs (staff, rent) are managed in Assumptions and Expansion tabs.
| Name | Category | Cost | Frequency | Patient Weeks | Linked Revenue | Status | Actions |
|---|
Revenue & Cost Summary
Revenue Items
--
Cost Items
--
Revenue by Payment Source
These items define how revenue and costs are calculated in projections. Changes here affect all computed financials.
Startup Costs
Per-scenario startup cost items. Fixed costs and per-physician scaling costs for clinic launch.
| Name | Category | Amount | CapEx? | Per Physician? | Actions |
|---|
Total CapEx
--
Total Working Capital
--
Contingency
--
Launch Cost Per Clinic
--
Capital & Expansion
Applied to positive EBIT each month and year; no loss carry-forward
Straight-line on start-up items flagged as CapEx
Cash must exceed launch cost × (1 + contingency%) to trigger expansion
Operational cap on how many clinics can open in a single year
Working Capital Required
--
Ramp-up months × monthly costs
Launch Cost Per Clinic
--
CapEx + working capital + contingency
Expansion Trigger
--
Cash needed to open next clinic
Capital Available After Clinic 1
--
Operating Costs
Recurring operational costs for this scenario. Supports fixed and per-physician cost types with various frequencies.
| Name | Category | Amount | Frequency | Type | Active | Actions |
|---|
Total Weekly OpEx
--
Total Monthly OpEx
--
Annual OpEx
--
Quick Preview
Year-1 Net Income
--
Year-10 Clinics
--
Year-10 Cash Balance
--
Projections: --
Calculation Breakdown — How These Numbers Are Derived
Physician Utilization Schedule
Show Detailed Utilization Table
| Week | New Patients | Active Patients | Available Min | Follow-Up Min | Initial Min | Used Min | Unused Min | Utilization | Capacity → Patients |
|---|
Single Patient Journey
What a single patient experiences from enrollment through completion.
Cash Flow Schedule — Revenue, COGS & Operating Costs by Week
52-Week Operating Model
| Week | Meal Revenue | App Revenue | Visit Revenue | Total Revenue | COGS | Gross Profit | OpEx | Net Income |
|---|
Monthly P&L Statement
| Month | Total Revenue | COGS | Gross Profit | OpEx | EBITDA | Depreciation | EBIT | Taxes | Net Income |
|---|
10-Year Summary
| Year | Capital Investment | Clinics | New Opened | Opening Costs | Total Revenue | OpEx | Total Net Income | Cash Balance | Operating Float | Expansion Threshold | Free Cash |
|---|
Cash Flow Trajectory
Revenue Ramp (First 24 Months)
Clinic Growth
Patient Flow (52 Weeks)
Global reference data shared across all scenarios. Changes here affect all scenarios that reference these items.
Billing Codes
Defines what each service IS: fee, physician time, group/individual. Revenue items in scenarios reference these.
| Code | Official Name | Fee ($) | Minutes | Group? | Group Size | Max/Day | Category | Notes | Actions |
|---|
Remuneration Plans
Defines compensation structures for staff: salary, commission (% of billing), or hybrid. Assigned to staff in scenario editor.
| Plan Name | Type | Base Salary ($) | Commission (%) | Benefits? | Benefits (%) | Description | Actions |
|---|
Staff Roles
Role definitions for staffing. Compensation is determined by the remuneration plan assigned in each scenario.
| Role | Category | Actions |
|---|
Programs
Program definitions. Revenue items, costs, and scheduling are configured per-scenario in the editor.
| Name | Duration (weeks) | Description | Active? | Actions |
|---|
Access control for people and AI clients. Access tokens let your own AI tools (Claude, ChatGPT, Cursor and others) read and modify scenarios on your behalf; every change they make is recorded in the audit log under your name.
Users
Only listed, active users can sign in (email + one-time code). Optional IP restrictions apply to sign-in and browser sessions.
| Name | Role | Active? | Last Sign-in | Tokens | IP Rules | Actions |
|---|
Local Package
A self-contained copy of the platform with a snapshot of your data, for running on your own machine (see the README inside). Contains program files, so it is offered here rather than by email.
Checking…
Access Tokens
Tokens for AI clients and scripts. Scopes: read (view and compute), write (create and edit), admin. A token is shown once, at creation. Optional IP restrictions apply to that token only.
| Name | Prefix | Scopes | Created | Expires | Last Used | IP Rules | Status | Actions |
|---|
Connect your AI
ThriveAB Plus exposes a Model Context Protocol (MCP) endpoint so any MCP-capable AI can learn the platform and work on scenarios using one of your access tokens.
MCP endpoint:
claude.ai and Claude Desktop (custom connector)
- Open claude.ai → Settings → Connectors → Add custom connector.
- Name: ThriveAB Plus. URL: the MCP endpoint above.
- Authentication: No sign in. Under Request headers add
Authorizationwith valueBearer <your token>. - If the token has IP restrictions, include the Anthropic services preset: claude.ai connects from Anthropic's network, not from your computer.
Claude Code (terminal or IDE)
Or commit a project file .mcp.json that reads the token from an environment variable:
Cursor and other MCP clients
Add to ~/.cursor/mcp.json (most clients accept the same shape):
Anthropic API (your own agents)
The Messages API MCP connector calls this server for you. Calls originate from Anthropic's network (use the Anthropic services IP preset if restricting).
Quick test from a terminal
ChatGPT connectors require OAuth sign-in rather than a fixed token; that option is planned for a later release.