Skip to content

About the author

Claudio Scheer
Claudio Scheer

I'm a software engineer with a master's in Computer Science. I work on technology problems, mostly the kind that don't have obvious answers. This blog is where I write up what I figure out.

At A1 Lab I spend most of my time on AI projects, system integrations, and the prototype phase of things that haven't been built yet. The pattern is usually the same. A client has a process that hurts. We build a small thing in two to four weeks that doesn't hurt. If it holds up, we keep going.

A few areas I keep coming back to:

  • RAG and document AI. How to make an assistant that actually answers from your data instead of guessing, and what to do when the docs themselves are a mess.
  • Integrations between business systems. ERPs, CRMs, spreadsheets nobody wants to touch. This is the work that decides whether an AI feature is useful or just a demo.
  • Prototypes. The honest version, where the goal is to learn fast and throw things away if they don't work.

The blog ends up being where I write about the parts that took me a while to figure out. Things like why a particular RAG architecture was wrong for what we needed, or how an integration project actually played out once it hit production data. If a post saves someone an afternoon they would have spent debugging the same thing, that's a good post.

Outside of A1 Lab I'm at claudioscheer.github.io, on GitHub as @claudioscheer, and on LinkedIn.


Author's posts

Integrations How to Integrate ERP and CRM Without Unnecessary Complexity

How to Integrate ERP and CRM Without Unnecessary Complexity

Companies trying to connect ERP, CRM, and other disconnected systems usually face the same symptom: the data exist, but they do not flow. The team types the same information twice, fixes errors by hand, and wastes time checking whether one system matches the other.

Read more
Rag How to Build an AI Assistant That Answers from Your Company's Documents

How to Build an AI Assistant That Answers from Your Company's Documents

If you want an AI assistant that answers from your company's documents, the main problem is not the chatbot. The real problem is getting the system to fetch the right information from the right document and answer without making things up. That is where most projects look good in a demo and fall apart in real use.

Read more
Rag RAG Architectures: How to Choose for Your Use Case

RAG Architectures: How to Choose for Your Use Case

RAG matters because it is what separates an AI system that sounds confident from one that can answer based on what your company actually knows. Without solid retrieval, the model fills gaps, mixes context, and gets the most important business questions wrong.

Read more