.NET architecture
Minimal API, layer boundaries, MongoDB, gRPC, streaming. Where to simplify and where structure actually pays off.
People often write to me to think through a technical decision. This page explains what I can actually help with and how it usually goes — so you know what to expect before writing.
Minimal API, layer boundaries, MongoDB, gRPC, streaming. Where to simplify and where structure actually pays off.
RAG, hybrid search, MCP, function calling, agent orchestration: model choice, cost, guardrails and fallbacks.
How to set up hooks, skills, quality gates and multi-model review without turning the assistant into a tech-debt generator.
What to learn, what to skip, and how a full-stack profile evolves after twenty years on the job.
A couple of lines on what you're building, where you're stuck and what constraints you have. The more concrete, the better.
Over email or on a call, depending on how involved it is. We look at the real problem, not the simplified version.
We analyze it together and implement it using the technologies that best fit the problem — zero fluff, you walk away with something that works.

A pipeline that reads invoices, contracts and orders from PDFs and scans: layout analysis + LLMs to extract fields, business rules to validate them, and typed APIs to push everything into the CRM or ERP.
.NET · OpenAI · Anthropic · Ollama · MongoDB

A private conversational assistant: it answers over the internal knowledge base with RAG and source citations, runs tools via MCP against CRM and ERP, and generates reports and charts on demand.
.NET · Next.js · MCP · OpenAI · Anthropic · Ollama · Qdrant · MongoDB

An agent with RAG over different sources — records, email, documents, ERP — that unifies data in the context of the customer card: precise answers and records updated directly through APIs.
.NET · MCP · OpenAI · Anthropic · Ollama · Postgres · Qdrant