Skip to content
Management & reportingElectronics & SensorsMachinery & Plant EngineeringMetal & MachiningConstruction & Building Services+2

Project plan straight from the kick-off

From kick-off minutes and e-mails, demi builds your internal project plan with milestones and owners, and flags delays early.

Today

Internal projects such as an ERP change, a new hall or a certification start with a good kick-off. After that, the plan lives in a spreadsheet nobody maintains after two weeks, while the real status sits in e-mails, chats and tickets. Management only notices a milestone is at risk once it has already been missed.

An example

Wallner+Hardt Sensortechnik is moving to a new ERP on July 1 and starts with a kick-off of 14 people. From the minutes and slides, demi builds a plan with 38 work packages and 7 milestones, including master data migration by February 15 and test operation from April 1. In January, demi reports that the cleanup of item masters for the pressure sensors is three weeks behind because, according to a ticket, the variant logic for the IO-Link types has not been approved, which puts the master data migration and test operation at risk. The project lead brings the approval forward to the following week.
Fictional company, typical workflow.

Your data, wherever it lives

The plan of an internal project sits in a spreadsheet and a kick-off slide deck; the real status is in e-mails, Teams chats, tickets and calendars. demi reads, understands and links them, with your rights. In minutes, the AI builds the plan with milestones and dependencies and checks it against reality every week, and the project lead decides what changes.

Where the data lives today

  • E-mails
  • Calendars
  • Office files
  • Tickets
  • Chats
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    Data sources in this case: e-mail, calendar, spreadsheets and slides, tickets and chat. demi replaces nothing and reads the kick-off minutes, the slides and the project spreadsheet, plus the project's ongoing e-mails, chats, tickets and appointments. The result is a plan that stays current with every new message.

  2. 2 · PermitPermission Layer

    The project team sees the plan; management sees all projects. demi reads only mailboxes, channels and folders released for the project; private e-mails stay private. Only the project lead changes milestones and dates, and every change is traceable.

  3. 3 · ActIntelligence Layer

    The agent extracts work packages, milestones, owners and dependencies from the kick-off and proposes the plan. After that, it compares plan and reality every week: moved dates, open tickets, missing commitments. demi calculates the critical path by fixed rules, and the agent explains every delay with its source.

How it runs

  1. 1

    After the kick-off, you hand the minutes, slides and project spreadsheet to demi.

  2. 2

    The agent proposes the plan: work packages, milestones, owners and dependencies.

  3. 3

    The project lead checks it, adjusts it and releases the plan.

  4. 4

    demi follows the project's e-mails, tickets, chats and appointments and keeps comparing them with the plan.

  5. 5

    When a milestone is at risk, a notice arrives with the reason and the consequences, and the project lead decides.

What changes

  • A plan that stays current without manual upkeep

  • Delays show up while there is still time to act

  • Management sees all internal projects at a glance

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+162 hfreed per year

Assumptions and calculation

demi keeps the plan current from e-mails, tickets and appointments and flags delays; the project lead decides.

90 min → 63 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

30 project status updates × 90 min × 30% × 1.0 (manual) × 12 months = 9,720 min = 162 h

Value per year, before demi costs

Freed per year+162 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$10,530

gained per year

162 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Do we need project management software for this?

No. demi builds the plan from what your team writes anyway: minutes, e-mails, spreadsheets, tickets. If you already use a project tool, demi writes milestones and tasks into it after approval.

How does demi know a milestone is at risk?

From the signals in the project: a moved date in the calendar, a ticket open for days, a commitment by e-mail that was not kept, a work package another one is waiting for. demi shows every notice with its source, and the project lead assesses it.

Which projects is this suited to?

Internal projects with many people involved: an ERP or MES rollout, a new hall, moving a line, certification to ISO 9001 or ISO 14001, the launch of a new product family. Customer projects that run in the ERP are tracked by demi in the project status for management.

Does demi read all employees' e-mails?

No. demi reads only mailboxes, folders and channels released for the project, such as a project mailbox, a Teams channel and the project tickets. Whatever is not there does not go in.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases