Micro.Ai Founder Dossier
Micro.Ai
Founder dossier

The team building what stays.

Micro exists because people do not need another place to consume more. They need a clear way into a topic, proof of what stayed, and a reason to come back.

Meet the founders Why imec
01 Content is everywhere.
02 Direction is missing.
03 Retention is everything.
The split

Two founders. Clear ownership.

Luigi owns the technical engine. Jonas owns the commercial engine. Product direction is shared, because Micro only works when the product, story, and validation loop stay connected.

Luigi Dalan, Co-founder and Technical Lead at Micro
Product and engineering lead
Full time Antwerp Engineering

Luigi Dalan

Co-founder and Technical Lead

Luigi owns Micro’s technical implementation: mobile app development, backend flows, AI path features, audio and lesson systems, infrastructure, App Store releases, data tracking, product testing, and live demos.

Strength Connects product thinking, technical execution, and design sense to ship product people can actually use.
Growth focus Holding steady under pressure and changing course faster when a path is blocked.
Background Computer science background from HTL Villach, web development, technical support, systems work, Unity, AI application development, and full stack implementation.
Built Major parts of Micro’s mobile product, AI flows, roadmap logic, audio implementation, quiz and progress systems, infrastructure, and release work.
Jonas Knoll, Co-founder and Business Strategy Lead at Micro
Growth and fundraising lead
Full time Antwerp Business

Jonas Knoll

Co-founder and Business/Strategy Lead

Jonas owns Micro’s business side: strategy, growth, fundraising, investor relations, legal and compliance coordination, operations, finance, business development, partnerships, positioning, and customer discovery.

Strength Turns loose business work into structured workflows, clear positioning, and external communication.
Growth focus Testing demand earlier and getting in front of customers before building.
Background Emergency medical service, TEDxBrunneck co-organization, AI workflow training, business execution, and organic content growth.
Built A structured AI workflow setup with 12 specialist agents and 49 custom skills for marketing, fundraising, legal, operations, and strategy.
Luigi owns

The product engine.

Luigi is accountable for turning Micro’s concept into something people can actually use. He owns engineering, infrastructure, app releases, technical demos, product behavior, and validation metrics.

  • ✓Mobile and full stack implementation
  • ✓Backend flows, roadmap logic, audio and lesson systems
  • ✓AI feature implementation and product testing
  • ✓Data tracking and live demo readiness
Jonas owns

The commercial engine.

Jonas is accountable for making Micro understandable, testable, and fundable. He owns growth, fundraising, imec communication, positioning, operations, business development, and partnerships.

  • ✓Growth, marketing, and user acquisition
  • ✓Fundraising, investor relations, and imec communication
  • ✓Customer discovery and feedback collection
  • ✓Legal, compliance coordination, operations, and partnerships
How it got sharper

We sharpened what Micro really is.

Early on, the easy way to describe Micro was AI audio lessons. True, but too small. The real problem is bigger, and the product follows from it.

1
First framing AI audio was the headline. Easy to say, easy to confuse with everything else.
2
The insight People do not need more content first. They need a way in, and a reason it stays.
3
Where we landed One topic becomes a path, then checks, weak spot practice, review, and visible progress.
Why we care

Micro is built for the person buried in useful content.

Videos, podcasts, saved posts, notes, and AI answers create the feeling of progress. Then most of it disappears. The user starts again from zero.

Micro should feel like relief. One topic. One starting point. One route through the chaos. Then a check to see what stayed, practice for what broke, and review for what matters.

That is the company Luigi and Jonas are building. Not more content. More that stays.

Current proof

Live, in real hands, and ready for the test that matters.

Micro is live, with a web demo and early user behavior to learn from. The next step is structured validation: return behavior, delayed recall, weak spot recovery, and paid conversion.

Snapshot today

Micro is live on iOS. The web demo is available for testing. Android is in progress. The company is pre-revenue and currently focused on activation, feedback, and product learning.

iOS live on the App Store
Web demo available for testing
76 web demo users
6 full app users

Validation path

1
First session activation Measure topic submit, path opened, Lesson 1 start, Lesson 1 completion, check completion, weak spot triggered, and feedback submitted.
2
Repeat behavior Measure D1 return, D7 return, review return, weak spot practice return, repeat topic creation, and later path completion.
3
Retention and business signal Measure delayed recall, second attempt improvement, weak spot recovery, paid conversion, and B2B pilot readiness.
Mentor and sparring partner

Patric P. Kutscher helps us sharpen the message under pressure.

Kutscher is named as a mentor and sparring partner for communication, pitch clarity, and founder presence. His role is not to validate the product. His role is to make sure the message lands when it matters.

People do not buy features. They buy the hope of change.
What changed

Less feature talk. More transformation.

His feedback helped sharpen one important point: Micro should not lead with features. It should lead with the change the user wants to feel.

  • ✓Clearer pitch structure
  • ✓Sharper founder communication
  • ✓Less technical fog
  • ✓More focus on orientation, progress, and change
Why imec.istart

We are past the build. Now we prove it works.

Micro needs validation pressure, GTM discipline, investor readiness, and access to the right pilot conversations. That is exactly where imec can make the biggest difference.

What imec would help us prove

We do not need support to discover that AI can generate explanations. That is already obvious. We need to prove whether a path and retention loop creates repeated behavior.

D1 and D7 return Do users come back after the first path?
Delayed recall What stays after 48 hours and 7 days?
Weak spot recovery Do misses become stronger after practice?
Review return Do users come back to what matters?
Paid conversion Will users pay when the value is clear?
B2B readiness Can this become company knowledge retention later?

Why this team can use the program well

The team has clear ownership, full-time commitment, a working product, and early users. That is the stage where imec adds the most: disciplined validation on a product that already exists.

  • ✓Luigi can demo the product live and owns the technical path forward.
  • ✓Jonas owns the external story, customer discovery, fundraising, and growth path.
  • ✓Both founders talk to users and share product direction.
  • ✓The company is currently operated through Luigi’s Belgian single-person company structure, with a signed founder agreement between Luigi and Jonas.
  • ✓The team plans to formalize a scalable company setup as part of the next financing step.
Final note

We are clear on what we have built, and what we will prove next.

We are here because Micro has a real product, a clear founder split, and the right next question: can a guided path and retention loop turn curiosity into retained understanding?

Open demo View iOS app