Get in touch
Portfolio & project governance

Standardize your project portfolio — so it's finally comparable.

Klonn.it structures projects around a shared, standardized WBS across every portfolio you run — then applies that same discipline to progress, budget, ownership and workload. An AI assistant helps you keep it all up to date, and only ever proposes.

Get in touch See how it works
Genuine critical path (CPM) RACI at every WBS level Two-tier OPEX/CAPEX budget AI that proposes, never decides
Environment-level multi-tenant isolation Invitation-only onboarding CSRF protection on every request AES-256-GCM encrypted AI keys
The six pillars

Everything is derived from the work breakdown — nothing is guessed at the top.

Progress, budget and risk all roll up bottom-up from the actual WBS. Here's what that looks like in practice.

01 — Structure

One hierarchy, genuinely isolated by entity

Environment → Portfolio → Sub-portfolio → Project. A portfolio maps to a real business unit — Industrial, Marketing, R&D, IT — a sub-portfolio groups its projects by objective. Every request is checked server-side against the current environment, not just hidden in the UI.

  • Multi-tenant isolation enforced on every route, not just in the interface
  • Opaque URLs — project/portfolio volume is never guessable from the address bar
One hierarchy, genuinely isolated by entity — Klonn.it screenshot
02 — Standardization

A shared WBS vocabulary, not a blank page every time

Each portfolio owns a curated catalog of standard workpackages and deliverables. Reusable project templates pre-select which catalog items apply and pre-schedule their Gantt — a new project starts already sequenced, not from scratch.

  • Portfolio-level catalog, individually activated per project
  • Templates pre-schedule offsets, durations and dependencies
A shared WBS vocabulary, not a blank page every time — Klonn.it screenshot
03 — Planning

Real planning rigor — a genuine critical path, not a badge

Gantt at week, month, quarter or year granularity. Four dependency types — Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish — with lag in business days and cycle detection before anything saves.

  • Forward and backward pass, slack computed per task
  • Zero-slack chains correctly flagged as critical
Real planning rigor — a genuine critical path, not a badge — Klonn.it screenshot
04 — Accountability

RACI at every level of the work breakdown

Accountable, Responsible, Consulted, Informed — assignable at workpackage, iteration, and deliverable level, multiple people per role. Ownership isn't a side document; it drives who can edit what.

  • Write access cascades down the WBS from Accountable/Responsible roles
  • Feeds directly into workload boards — no separate bookkeeping
RACI at every level of the work breakdown — Klonn.it screenshot
05 — Budget

Two-tier budget control, not a single guessed number

Budget lines (OPEX or CAPEX) break down into individually-payable commitments. A committed or already-paid line can't be silently deleted — enforced server-side, not just hidden in the interface.

  • Budgeted, committed and paid reconciled side by side
  • Annualized view with an explicit "unplanned" bucket
Two-tier budget control, not a single guessed number — Klonn.it screenshot
06 — Workload

See where your team's time actually goes

Planned time is entered by the project manager; actual time only ever by the person themselves. A dedicated "My team" board gives a manager visibility into their people's load across every project at once.

  • Planned vs. actual kept strictly separate, server-enforced
  • Real visibility across projects — not a single spreadsheet per PM
See where your team's time actually goes — Klonn.it screenshot
The payoff

Because everything is standardized, everything is comparable.

One consolidation matrix per portfolio — one row per project, one column per standard workpackage, showing rolled-up progress and the worst open risk in every cell.

Project Discovery Build Validation Rollout
ERP Migration Done In progress In progress —
Plant Automation Done Late — —
Supplier Onboarding In progress — — —

Illustrative data. Comparison only works because every project draws from the same standardized workpackage catalog.

AI project assistant

An assistant that proposes. A human who decides.

Ask it to update progress, log time, draft budget lines, or turn pasted meeting notes into tracked actions. Every single change waits for your explicit validation before it touches your data.

1. You ask

"Mark the API integration deliverable at 70% and log today's 4 hours."

2. It proposes

Two proposed changes appear, freshness-checked against your live data — nothing is written yet.

3. You validate

Approve, edit, or reject — with your real RACI authorization re-checked at that exact moment.

4. It's logged

Every validated change lands in a permanent, human-readable changelog for the project.

Explore the AI assistant
Trusted by teams running multi-portfolio operations — customer logos coming soon.
Ready when you are

Bring standardized governance to your project portfolio.

Get in touch Why Klonn.it