Nordkessel AG (illustrative) · Nordkessel AG, Use Case Identification Workshop
Example report generated via the Lunnoa Reports MCP
Section 01

Executive summary

Across a two-day workshop with Nordkessel AG's operations and finance teams, we mapped nine candidate automation use cases. Four are recommended for a 12-week first wave.

At a glance

Use cases identified
9
Across finance, operations and HR
First-wave candidates
4
Ready to scope within two weeks
Manual hours / month
612
Estimated across the four first-wave flows
Key findingHigh impact

Purchase order approval passes through four inboxes before it reaches the ERP

Every purchase order today is touched by procurement, the requesting department, finance, and procurement again. Each handover is a manual email forward, and the audit trail lives across four separate mailboxes rather than one system of record.

Key findingMedium impact

HR onboarding checklists are tracked in a shared spreadsheet

New joiners are added to a shared Excel tracker that HR updates manually against eleven separate systems (payroll, badge access, laptop provisioning, and others). Missed rows are the most common source of onboarding delay.

Nordkessel automation maturity, current vs. 6-month target

Scores from nine stakeholder interviews using the Lunnoa maturity framework (1 = ad hoc, 5 = optimised).

Current Target
“

We know exactly what the process should look like on paper. The problem is that on paper and in four inboxes are not the same thing.

”
Elena Brunner, Head of Procurement
RecommendationDo nowEffort: MOwner: COO + IT Director

Commit to a 12-week first wave covering purchase order approval, onboarding, and expense triage

The three use cases share a deployment pattern (Lunnoa agent plus ERP API plus ticket fan-out) and together cover the largest concentration of manual hours observed during the workshop.

Section 02

Use cases identified

Nine candidate use cases came out of the workshop, scored on implementation effort and business impact. Four sit in the quick-win zone and are recommended for wave one.

Nine use cases scored on effort and impact

Effort and impact both scored 1 to 5 by the workshop group

FinanceHRProcurementOperationsGovernance

Recommended for wave one

Wave 1 Finance

Purchase order approval

Automate routing and three-way sign-off for purchase orders between the requesting department, procurement, and finance, with a single audit trail instead of four inboxes.
Impact
≈ 240 hrs / month
Effort
M
TTV
6 weeks
Owner: Elena Brunner
Wave 1 HR

Employee onboarding checklist

Replace the shared spreadsheet with an agent that provisions payroll, badge access, and equipment requests automatically as each step completes.
Impact
≈ 140 hrs / month
Effort
S
TTV
4 weeks
Owner: Jonas Weber
Wave 1 Finance

Expense report triage

Auto-categorise expense submissions against policy and flag only genuine exceptions for human review, rather than every line item.
Impact
≈ 90 hrs / month
Effort
S
TTV
3 weeks
Owner: Elena Brunner
Wave 2 Procurement

Supplier contract renewal alerts

Track contract end dates and auto-generate renewal or renegotiation tasks 90 days ahead, replacing an ad hoc calendar reminder system.
Impact
≈ 60 hrs / month
Effort
S
TTV
4 weeks
Owner: Elena Brunner

Manual hours per month, before vs. projected after wave one

BeforeAfter
Today (manual)
  • Purchase order arrives by email, forwarded across four inboxes for sign-off.
  • Finance re-keys header and line data into the ERP once approval finally lands.
  • No single record shows where an order currently sits.
After wave one (Lunnoa-led)
  • Lunnoa agent receives the request, applies the approval matrix, and routes automatically.
  • Approved orders post to the ERP directly; exceptions land in one queue.
  • Procurement sees live status for every order in one view.
Section 03

Roadmap and next steps

Wave one is scoped as a 12-week delivery, deployed on Nordkessel's own infrastructure with no data leaving the client environment.

Wave one, 12-week delivery

Foundation work runs in parallel with the first use case build

  1. Phase 1, Foundation
    Weeks 1 to 3
    • ERP middleware exposed
    • Lunnoa platform deployed on client infrastructure
    • SSO configured
  2. Phase 2, Build expense triage and onboarding
    Weeks 4 to 7
    • Expense triage live week 6
    • Onboarding checklist agent live week 7
  3. Phase 3, Build purchase order approval
    Weeks 8 to 11
    • Approval matrix configured
    • ERP write-back tested with finance
  4. Phase 4, Stabilise and handover
    Week 12
    • Runbook handed to internal IT
    • Wave two backlog agreed
RecommendationDo nextEffort: SOwner: COO

Agree the wave two backlog before wave one delivery completes

Supplier contract renewal alerts and customer ticket routing are the strongest wave two candidates based on the effort and impact scoring. Confirming scope in week ten avoids a gap between waves.

Workshop participants
Elena Brunner
Head of Procurement · Finance
Interviewee
Jonas Weber
HR Operations Lead · People
Interviewee
Markus Steiner
COO · Executive
Sponsor
Sasa Kelebuda
Founder, Lunnoa · Lunnoa
Workshop participant