1Project
Eight structural advantages incumbents cannot copy
Every differentiator in 1Project requires a competitor to restructure their pricing, architecture, or business model to match. That's not a feature list — it's a moat.
Single-tier pricing
Every Creator License grants access to every feature in the product. There are no tiers gating advanced features. No premium add-ons. No "Enterprise" tier that mysteriously appears with new features later. One tier, all features, forever.
Hospital CFOs spend significant energy on procurement decisions. Upgrade traps — required features only available at the next tier up, "AI features" added as a separate SKU, reporting gated behind "Premium Analytics" — are a predictable betrayal. We eliminate them by design.
What competitors do instead
- Wrike: Free, Team, Business, Enterprise, Pinnacle — five tiers
- Monday: Free, Basic, Standard, Pro, Enterprise — features gated throughout
- Asana: Personal, Starter, Advanced, Enterprise — feature gating throughout
- MS Project: Tiered with major capabilities locked to higher tiers
"Every feature in every tier. No upgrade traps. No premium AI sold separately. No reporting gated behind Enterprise. You buy a license, you get the whole product."
Per-creator licensing, not per-user
You only pay for people who create and manage projects. Everyone else — every project participant, every contributor, every stakeholder — uses the system fully for free.
A typical 200-bed community hospital has 2,000 employees who might touch project work, but only 15–25 people who actively create or manage projects. Traditional PM software charges for all 2,000. We charge for the 20.
The math, concretely
Per-user PM software
$600,000/year
2,000 users × $25/month
1Project
$23,760/year
20 Creator Licenses × $99/month
96% less for equivalent or better functionality.
Free external participation
Anyone you invite to a project — contractors, vendors, consultants, inspectors, regulators, government officials — participates fully and freely. Not as "guests" with degraded access. Full participants with appropriate role-based permissions.
Most hospitals tell us about 20% of the people working on a major capital project are actually in the PM tool. The other 80% — the contractors, vendors, and inspectors doing the actual work — are outside the system because licensing them is too expensive or the guest experience is too limited. We fix that.
Hospital project stakeholders who participate free
- General contractors and subcontractors (often 15–50 per project)
- Equipment vendors and installation teams
- Architects, engineers, designers
- Regulatory inspectors (state DOH, CMS, Joint Commission)
- Compliance consultants and audit firms
- Legal counsel
- Government officials
- Patient advocacy representatives
"The plan in our system is the actual plan, because everyone updating it is the actual team."
Person-centric identity across organizations
Your identity in 1Project is a person, not an email address. As you accumulate emails over your career — personal email, employer emails, hospital-assigned contractor emails — they all link to one identity. Your project history follows you across employers. Your professional portfolio is yours, not your current employer's.
This creates a network effect competitors cannot build: consultants accumulate verifiable career credentials in 1Project, become advocates, and bring the tool to every new client engagement — arriving with a built-in internal champion already inside.
How the network effect works
- 1. Hospital A invites Jane (consultant) to their project
- 2. Jane participates free; work attaches to her durable person identity
- 3. She finishes; her 1Project history persists and grows with each engagement
- 4. Hospital B hires Jane; she recommends the tool she has deep expertise in
- 5. 1Project arrives at Hospital B with a credible internal advocate already inside
Healthcare-native PHI handling
PHI handling in 1Project is infrastructure, not a feature. Every major PM competitor — Wrike, Monday, Asana, MS Project — has nothing. They don't even claim to be HIPAA-compliant. 1Project is the only PM platform built to be HIPAA-compliant from the foundation up.
The pointed question:
"Your project teams handle PHI through your PM tool whether you've formally acknowledged it or not. Clinical pathway examples, quality improvement cases, patient flow analyses — these projects touch PHI constantly. Why are you managing HIPAA-sensitive projects with non-HIPAA-compliant software?"
Infrastructure-level PHI, not feature-level
- ✓ Document classification at upload (PHI vs standard)
- ✓ Patient registry integration (HL7, FHIR, direct EHR, custom)
- ✓ Patient linking and minimum-necessary documentation
- ✓ Two-tier storage with customer-managed encryption keys
- ✓ Immutable audit trail for every PHI access
- ✓ Per-project and per-document PHI access controls
- ✓ Mandatory access prompts with purpose capture
- ✓ Retention, disposition, and legal hold
- ✓ Compliance officer role with elevated audit access
- ✓ Breach analysis and subject access request reporting
- ✓ Customer SIEM integration for your own security infrastructure
Hierarchical multi-tenancy for real organizations
Healthcare organizational structures are genuinely complex. HCA's corporate→region→ division→hospital hierarchy. Canadian government's ministry→authority→hospital structure. UK NHS trusts and integrated care systems. 1Project models them natively.
Traditional PM software forces flat tenant structures. You're forced to pick between licensing every facility separately (massive cost) or running one big tenant that doesn't reflect how you actually operate. We don't make you choose.
What this enables
- HCA corporate admins see projects across all 180 hospitals
- Regional managers see their region's strategic initiatives
- Hospital administrators see their facility's projects
- Acquired hospitals onboard gradually with license expansion
- Licensing scope is separable from organizational ownership
- Government oversight access (Canada, UK) works naturally
Same product, role-based visibility, no separate "enterprise" deployment.
On-premises and hybrid deployment
1Project runs in your environment when you need it to. Hosted SaaS in our cloud, dedicated SaaS in your cloud, or fully on-premises in your datacenter. Same codebase, same features, same experience. Windows Server-native for hospital IT environments.
No major modern PM platform has a serious on-prem story. Wrike, Monday, Asana, and cloud-era MS Project are SaaS only. Microsoft is actively deprecating the legacy Project Server. Buyers who can't use cloud PM software — for data sovereignty, IT policy, or regulatory reasons — are a market incumbents have written off.
Deployment options, same product
Hosted SaaS
Our cloud, we manage it. Fastest to get started.
Dedicated cloud
Your Azure or AWS subscription. Your infrastructure team controls it.
On-premises
Your datacenter, your Windows Server. Air-gapped if required. Data never leaves your network.
Disaster-resilient operation
When the internet is down, your hospital's project work doesn't stop. An on-premises 1Project installation continues operating during extended connectivity outages — hours, days, or weeks. Authentication works. Project access works. PHI access works. Your disaster response plan can rely on it.
Hospitals lose connectivity in scenarios other industries don't fully appreciate: hurricanes taking out regional telecom, ransomware quarantine forcing network isolation for weeks, rural ISP failures with no backup path. Every other modern PM platform falls back to paper. 1Project on-prem does not.
The "hurricane rule" — designed in, not bolted on
- ✓ Local OpenIddict instance issues tokens when cloud is unreachable
- ✓ SAML federation to your on-prem Active Directory continues
- ✓ All project work and PHI access operates locally
- ✓ 60-day offline grace period before any enforcement changes
- ✓ License enforcement defaults to warn-only — hospitals are never locked out
- ✓ Bidirectional sync reconciles when connectivity returns
"We're not asking you to trust our disaster recovery — we're providing yours."
See it for your organization
Tell us about your hospital, health system, or consulting practice. We'll show you where 1Project fits and what the cost difference actually looks like for your situation.