Indelica 1Project™
Professional project management software. All of it.
1Project is a complete, professional-grade project management platform — the core capabilities called for by PM², the project management methodology developed by the European Commission, and by PMI's PMBOK guidance, in one product with no feature tiers.
It scales both directions: one person organizing their own work, GTD-style, or an enterprise managing a multi-facility hospital. And underneath it all sits an AI and compliance framework built into the foundation, not bolted on.
Everything professional project management requires
Before the differentiators, the fundamentals — the full working toolkit a PM organization expects, with terminology a credentialed practitioner immediately recognizes.
Plan & schedule
Work breakdown structures of any depth, the four classical dependency types (FS, SS, FF, SF) with lag and lead, multiple named baselines with plan-vs-actual variance, resource assignment and booking, and project calendars.
Track every kind of work
Nine work item types — tasks, milestones, risks, issues, decisions, change requests, actions, assumptions, constraints — in one unified model, each with structured attributes and human-readable reference numbers (RISK-001, ISS-042).
Govern & control
Configurable workflows with role-gated transitions and a full transition history, phase gates, change governance, and Kanban boards projected directly from workflow state.
Report like a PMO
Generate the formal artifacts — Risk Register, Issue Log, Decision Log, Project Charter — as versioned documents compiled straight from live project data, plus portfolio dashboards for executives and governance staff.
Manage stakeholders & teams
A first-class stakeholder register with power/interest analysis and engagement history, departments and teams, threaded comments with @-mentions, and notifications that reach the right people without configuration.
Find anything
Unified full-text and semantic search across projects, work items, comments, and documents — plus shared libraries of project templates, workflow definitions, and standards.
For one person
One professional, one license: a consultant or independent contractor gets the entire product — WBS, baselines, formal artifacts, personal task management — with nothing held back. Your identity and project history are yours, traveling with you across employers and engagements.
For an entire enterprise
Hierarchical multi-tenancy models real organizations — corporate, region, division, facility — with portfolio visibility flowing through the hierarchy and licensing at any level. The same product, at multi-facility scale.
Every feature above is in every Creator License — there is only one tier. See pricing →
Nine structural advantages incumbents cannot copy
The foundation above is table stakes done right. What follows is not: 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 projects. Everyone else — every project participant, every contributor, every stakeholder — uses the system fully for free.
A typical 200-bed community hospital has up to 2,000 people who might touch project work — staff, contractors, vendors, inspectors — but only 15–25 who actively create projects. Per-seat software taxes every one of those participants; we charge only for the 20 who create. Everyone else is free.
The math, concretely
Per-seat software, full participation
$600,000/year
2,000 participants × $25/month to include everyone
1Project
$23,760/year
20 Creator Licenses × $99/month
96% less for equivalent or better functionality.
Illustrative, using published mid-tier per-seat list pricing (Wrike Business ~$25/user/mo, MS Project Plan 3 $30, monday.com Pro ~$24) — the tier with the security, portfolio, and external-access features a hospital needs. Per-seat vendors ration seats rather than license every participant; the figure shows the cost of full participation under their model.
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.
Construction teams lose 35% of their time — more than 14 hours a week — chasing information across disconnected tools, and nearly half of all rework comes from exactly that kind of miscommunication. 1Project ends the disconnect: every contractor, vendor, and inspector on your project is a full participant, free — so the plan in the system is the plan on the ground.
See the research behind this →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. Large US health systems operate corporate→region→division→facility hierarchies. Canadian government runs ministry→authority→hospital structures. UK NHS has trusts and integrated care systems. 1Project models all of 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.
Executives and governance staff get org-wide visibility without a Creator License — they're not creating projects, so they shouldn't need one. Two built-in roles handle this: the Executive Viewer for C-level portfolio dashboards, and PMO Director for governance staff who need to track risk, issues, and decisions across the org. Assign the role to any org level — visibility flows from there automatically.
What this enables
- Corporate executives see projects across all facilities in their licensed scope
- 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
Executive and PMO access — no Creator License required
Executive Viewer
Cross-project portfolio dashboard — view all projects, work items, and reports without being added to any project individually. No seat cost.
PMO Director
Broader governance visibility — adds risk, issue, decision tracking, and report generation across the org. Also no Creator License.
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.
Available even when the internet is down
When the internet is down, your hospital's project work doesn't stop. An on-premises 1Project installation continues operating during connectivity outages — hours, days, or weeks. Authentication works. Project access works. PHI access works.
Every other modern PM platform is cloud-only — when the connection drops, the tool is unusable and your team falls back to paper. An on-premises 1Project install keeps working regardless.
How offline operation works
- ✓ A local identity service issues authentication tokens when the 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
AI-native — agents are first-class, not bolted on
AI agents are architectural primitives in 1Project, not a chatbot stapled to the side. An agent holds an identity, works under the same roles and permissions as a person, and every action it takes is audited — with its reasoning recorded on automated runs. There is no separate, weaker "AI mode" with a private backdoor to your data. On the roster, an agent is a named teammate — a name, a bio, a face — with one small AI mark so you always know.
The principle we build to is blunt: an AI agent is governed by the same rules as a person. The same framework — identity, licensing, permissions, audit — applies whether the participant is a person or an agent. An agent can draft a work breakdown, flag a risk, level resources, or move a work item — and every one of those actions runs through the same permission checks and lands in the same audit trail as a person's. In healthcare, where every action near sensitive work has to be accountable, that isn't the unsettling part — it's the responsible one.
We don't just ship AI. We're built by it.
1Project is built by its own fleet of AI software agents working alongside people — both designing, both building. The agents write the overwhelming majority of the code; people review every release before it ships.
And they coordinate inside 1Project itself — planning, sprinting, and reviewing their own work as work items, running a basic Agile Scrum cadence we're building into the product as we use it. The product manages the team that builds it.
"Before a single outside person logged in, the most demanding users 1Project had were the AI agents that build and run inside it every day."
Meet Forge, the agent that leads them →See it for your organization
We're looking for beta testers across industries — healthcare, construction, government, and professional services. If you run complex projects with external stakeholders, we'd like to hear from you.