Muhammad Bilal · applied AI consultant · Germany

I build AI
that holds up
in production.

The hub for client engagements, agentic tooling, and research residue. Most of what gets shipped here started as somebody else’s deadline. The personal half lives at bilalm.me.

Current
LaMechKy GmbH · advisory engagement
Cited in
SSRN 4763140 · TRR 266
Reply
Within 48 hours
Now · February 2026 onward

A marketing agency in North Rhine-Westphalia, with the lights on.

Phase II of an advisory engagement at LaMechKy GmbH — the Power BI stack and the Node middleware that makes Toggl, Absence.io, and their internal CRM tell one story. The numbers below are from the close of Phase I.

Power BI · Node · Express · Toggl · Absence.io · LaTool · Render

Selected · Three of sixteen

Work that shipped.

Chosen because the receipts are countable, recent, and attributable. The remainder live at /projects.

  1. 01Research pipeline · TRR 266 / TUM × LMU × Bocconi × IESE

    STOXX Europe 600 extraction

    Six reporting years of European annual reports rendered into a machine-readable corpus. The downstream paper, on climate disclosure in financial statements, runs the dataset through ClimateBERT. Acknowledged in SSRN 4763140.

    Python · Claude · PyMuPDF · ClimateBERT (downstream)

    Read the paper
  2. 02Advisory engagement · LaMechKy GmbH, NRW

    BI stack on Toggl, Absence.io, internal CRM

    Ten weeks scoped as an unpaid PoC, converted to a paid retainer when the numbers held. Eight Power BI pages and a Node middleware bridging the auth protocols product teams pretend aren’t there. 23 KPIs live by the close of Phase I.

    Power BI · Node · Express · Toggl · Absence.io · LaTool · Render

    Read the engagement note
  3. 03Open source · Operations automation

    Jira ticket generator

    Planning meetings produce transcripts. Jira expects epics, stories, acceptance criteria, and estimates. Between the two lies a tedious hour. This tool collapses it to about five minutes — parse, draft, file against the Atlassian REST API in a way any team lead can audit.

    Python · Claude · Pydantic · Atlassian REST · MIT

    See the repository
Practice · How I engage

Small teams. Fixed scopes. Production targets.

  1. i.

    Small teams.

    I work directly with the person who can decide. No account managers. No project triangles. The shortest line between a problem and a working system.

  2. ii.

    Fixed scopes.

    Six to fourteen weeks, written down before we begin. No retainers. No scope drift. No surprise invoices. The deliverable is on the page from day one.

  3. iii.

    Production targets.

    Every engagement closes on a measurable outcome — a number on a dashboard, a paper that cites the work, a system someone else now runs without me.

  4. iv.

    Honest no.

    If the project is wrong for me, or the model is wrong for the project, you’ll hear it in the first call. The reply is part of the work.

Contact · Reply within 48 hours

Bring me a problem.

Send the constraint, the deadline, the shape of the data. I’ll tell you in the first call whether I’m the right person for it.

mbilal.workmail@gmail.com
mbilal.works · one of a pair · personal hub at bilalm.meBuilt to a DESIGN.md spec · Bricolage Grotesque + JetBrains Mono · MMXXVI · North Rhine-Westphalia