[Fewer tokens, more horsepower]

[Michael Immanuel]Portfolio / AI EngineerScroll
[About me]Profile / 01

I'm an AI Engineer working on agent architecture and LLM systems, with a product-focused and practical approach.

I build the systems around language models that help intelligent products move from an idea to something useful.

Off the clockCars. Anything with an engine gets my attention, which might be why I like systems that do more with less fuel.

  • Agent architecture
  • LLM systems
  • Tool calling
  • ReAct loops
  • LangGraph
  • Product-focused
[Selected work]CH 01 / Flow 2.0

LLM-powered conversation infrastructure for customer-facing AI agents.

Same engine, different client
One turn through the graphTools: get_order · start_return · check_stock
CustomerReplyUnderstandDecideActRespond
  1. The trace of each step appears here.
Online store · customer chatSimulated
  1. Hi! I'm the store assistant. Ask me about an order, a return, or whether something is in stock.

A scripted walk-through of how a Flow 2.0 turn is structured. The clients, tools and data are fictional, intents are matched with keywords, and no language model is called. Token counts are illustrative, scaled to the measured 60% reduction.

Problem
An AI conversation engine for customer-engagement platforms, where the previous implementation burned far more tokens per conversation than the job needed.
Approach
One LangGraph graph (Router, Brain, Tools, Output). The Brain runs a native tool-calling ReAct loop, and the architecture stays client-agnostic.
Result
60% lower token consumption compared to the old implementation.
My part
I worked on the agent architecture and the systems that connect language models to useful product actions.
[How the loop works]

From intentto action

I work on the systems that connect language models to useful product actions while keeping the experience practical and product-focused.

  1. Understand

    Conversation context

    The system identifies what a person is trying to accomplish and keeps the interaction grounded in the product.

    output / intent
  2. Decide

    Agent architecture

    The model chooses the next useful action within the capabilities and boundaries of the product.

    output / next action
  3. Act

    Product systems

    The system carries out the action and brings the result back into context for the next decision.

    output / product result
  4. Respond

    Customer experience

    The completed work becomes a clear, useful response for the person on the other side.

    output / useful reply
[Selected work]CH 02 / Finovate

3rd place
Finovate hackathon

Finance news with an AI agent on board: it helps people plan their money, then lets them run the numbers.

Read
A finance news site that keeps people up to date.
Plan
A built-in AI agent that helps users plan their finances.
Calculate
Calculators for loans, savings and more.
Planning agentSimulated demo · runs in your browser
  1. Tell me what you earn each month, what you spend on essentials, and your loans: balance, interest rate and monthly payment. I'll work out a payoff plan.

The plan appears here: a debt-free date, a payoff chart you can scrub, and a monthly budget split.

A scripted recreation of Finovate's planning agent: rule-based parsing and a deterministic simulation, with no language model involved. Nothing you type leaves your browser. Illustrative only. Not financial advice.

Hot Lap

Lap 0:00.00Best -:--.--000 km/h

One lap of Spa, flat out. Steer with ← → or by moving the pointer; brake with Space, a mouse press, or the button. Off the tarmac, the clock runs three times as fast.