What I Can and Can't Show You

Three of the systems on this site are publicly live today: a legal research copilot, an AI travel planner, and an AI publishing platform. I engineered them, and each page states which role I held.

They were built for a previous employer's clients, before VelvoAI existed. The client relationships were the employer's, not mine. I am not free to name either party, and I have no permission to publish their results — so you will not find outcome numbers on those pages, and I am not going to estimate any.

• The problem each system was built to solve
• The architecture, and the decisions that could have gone another way
• Exactly which parts were mine, and which were not
• The public interface of products you can go and look at yourself
• What I would instrument and measure if I built the same thing for you

It is listed differently on purpose. I built it myself, to see how far the pattern could be pushed. It has never been deployed for a client and has no production users, so nothing on its page is a client result.

I cannot ask a previous employer's clients for a quote about work they hired the employer to do. Rather than publish something vague or anonymous that you have no way to check, I have published nothing.

If you want to speak to someone who has worked with me before committing to anything, ask, and I will tell you what I can arrange.

Judge me on the engineering, not the logos: how the systems are put together, whether the reasoning holds up, and how the conversation goes when you describe your own problem. Those you can evaluate directly.