Skip to content
Bernhard Götzendorfer
Bernhard Götzendorfer at a workshop

AI-generated

01 /Champion Pilot

Embed AI permanently, not just introduce it.

Six weeks of structured build: one person learns, documents and trains two colleagues. The workflow stays, even when the tool changes.

Fixed-price engagement · 6 weeks · qualitative range, details in the initial consultation

Practical programme with EU AI Act compliance connection

02 /The 6-Week Path

Six weeks. One person. One documented workflow.

  1. W1Champion selection

    Identify the right person and narrow down the target process. Clarify tool approval.

    • Champion profile: brief note on 4 selection criteria
    • Process scoping document (max. 1 page)
    • Tool whitelist start: 1–2 approved tools
  2. W2First steps

    Champion applies the approved tool to the real target process. First workflows emerge.

    • First prompt draft for the target process
    • Short protocol: what works, what does not
    • Open questions for the next support session
  3. W3Refine the workflow

    Expand the prompt library, write down the step-by-step workflow.

    • Written workflow (version 1): step-by-step for colleagues
    • Prompt library (3–5 reusable building blocks)
  4. W4Stabilise the workflow

    Test workflow on real cases, document error sources, define human-in-the-loop.

    • Workflow version 2 with human-in-the-loop markers
    • Short error and exception list: when does the human step in
  5. W5Train colleagues

    Champion trains two colleagues. We observe what needs explaining.

    • Training protocol: what worked, what was unclear
    • Workflow version 3 with improvements from the training
  6. W6Evaluation

    Measure results, prepare rollout decision or document an honest stop.

    • Pilot evaluation: time saved before/after
    • Rollout proposal or stop finding (for internal use)
03 /Champion Profile

Who is suitable as a champion, and who is not.

Four observable criteria. No job title required, no coding experience. Validation possible in three steps.

Suitable

  • Already uses AI tools like ChatGPT or Claude privately, without being prompted
  • Names concrete, recurring process pain points, not just "AI is interesting"
  • Understands both IT and the business side, can switch between both languages
  • Experiments independently, has already tried something without waiting for permission
  • Has at least 2 hours per month for structured support, plus their own learning time

Not suitable

  • Was nominated by management but shows no personal interest
  • Cannot name concrete process pain points, only abstract "AI interest"
  • Expects external consultants to build everything without becoming active themselves
  • Has no time capacity, insufficient management support for release

3-step validation: 30-minute conversation › have them build a prototype themselves › have them train a colleague.

04 /REFERENCE

1st place BitGN Hackathon Vienna · April 2026 (AI Factory Austria)

79 out of 104 points, solo, 11 April 2026. 2nd place: 65 points. A multi-agent system with Soft-SGR and five-layer injection defence. A repeatable process, built daily since late 2024, not invented on the day. Exactly what I pass on in workshops and the champion pilot.

05 /Quick self-check

5 questions before our first call

Answer these 5 questions in advance - we will start more efficiently.

  1. Who is the decision-maker? (Business unit, IT, CEO, Compliance)

    Why we ask this

    Depending on the stakeholder, we need different language, different output formats, and different escalation paths. A CTO asks different questions than a compliance lead.

  2. What budget range is realistic? (Sparring from 450 EUR / Pilot 3,000-5,000 EUR / Custom Build five figures+)

    Why we ask this

    The budget range determines the format, not the ambition. With this information we can recommend the right format directly, rather than developing options first.

  3. Do I have a concrete use case, or am I still exploring?

    Why we ask this

    Concrete use case: Sparring or Pilot. Open exploration: Audit as a starting point. This distinction saves both of us half an hour in the first call.

  4. EU AI Act / GDPR: must the solution run on-prem, or is EU-hosted cloud sufficient?

    Why we ask this

    The hosting requirement fundamentally affects tool selection and pilot scope. Strict on-prem requirements limit available models - better to discuss this upfront.

  5. Who on my team can continue building after the pilot? (1 developer, 1 PM, nobody)

    Why we ask this

    The Champion Pilot only works if someone can take the baton. If nobody is available today, we plan the programme accordingly - or recommend clarifying team readiness first.

No right or wrong answers. These questions help us suggest the right format without wasting time in the call.

Ready for the first step?

30-minute initial consultation, free of charge. We go through your situation and clarify whether a Champion Pilot fits.

Discuss Champion Pilot