Home/Who is it for?
Use cases
Four roles, four readings, one single truth.
PMO, CIO, finance, program directors: each has their questions. MARCEL answers them with the same data — no re-entry, no crossed exports, no contradictory versions.
Head of PMO
"I spend my weeks consolidating instead of steering."
- Every committee demands days of collection: PMs' Excel files, diverging versions, stale numbers.
- Methodologies are not homogeneous: each project manager structures their project their own way.
- Impossible to answer "where do we stand?" quickly without another extraction.
- The portfolio is permanently consolidated — tiles, RAG and budgets up to date as soon as the teams work.
- Committees prepare in one click — branded executive PowerPoint and weekly PDF generated from living data.
- Templates enforce your standard — every new project starts structured according to your methodology.
- The AI agent answers everyday questions — drifts, delays, anomalies: flagged before anyone asks you.
CIO
"My teams are saturated, but nobody knows where."
- Project demands come from everywhere, without objectivised prioritisation.
- The real workload of teams is invisible beyond the current month.
- Security constraints (SSO, isolation, hosting) eliminate half the tools on the market.
- The teams × months cross-view projects workload — overloads visible 3 to 12 months ahead, cell by cell.
- Demands follow a qualification workflow — weighted scoring and compared scenarios to prioritise on criteria.
- SSO, fine permissions and hosting choice — Google, Entra ID or SAML; tenant-isolated SaaS or on-premise.
- Open to your IT landscape — Power BI, Excel, MS Project, webhooks: MARCEL fits into your tools.
Finance department
"I discover the budget landing in November."
- Consumption comes up a month late, aggregated by hand.
- CAPEX and OPEX mix in heterogeneous files.
- Overruns are observed, never anticipated.
- EAC and ETC recomputed continuously — the landing reads weekly, not at year-end.
- CAPEX / OPEX separated at every level — project, program, portfolio: the same structure as your accounting.
- Alerts on threshold crossing — an EAC exceeding the envelope triggers a notification, not a surprise.
- Contractual vs invoiced day rates — vendor variance surfaces line by line, contract by contract.
Program director
"Ten interdependent projects, and a per-project view."
- A milestone slipping in one project impacts three others — discovered too late.
- The program's status is crafted by hand for every committee.
- Risks are tracked project by project, never transversally.
- The program consolidates itself — RAG, budget and milestones aggregated continuously from projects.
- Cross-project dependencies are declared — a slippage propagates visibly on the cross-portfolio roadmap.
- Milestones compare baseline and forecast — the gap to commitment is measured, milestone by milestone.
- Risks roll up transversally — probability × impact heatmap consolidated at program level.
Three key moments
Where MARCEL concretely changes the week.
Does this sound like your day-to-day?
Personalised 30-minute demo, built on your priority use case.