Clients·Fraud Investigations & Finance

Doug Loud.

Built a one-click web dashboard that hides Claude, n8n and Qdrant from non-technical users

Industry
Fraud Investigations & Finance
Role
Attorney, Fraud Investigations
Filmed
May 2026
Engagement
Mentorship
You can read about it and learn about it, but you can't fly a plane, you can't ride a horse without somebody teaching you. It is not the same thing as reading about it.
Doug Loud

The before.

Doug is an attorney by training, working in fraud investigations, security analysis and finance. He has been around long enough to remember Fortran and punch cards, has written HTML by hand before CSS existed, and still has a senior developer friend from AWS and Microsoft on speed dial. So he is not afraid of the tooling. The problem was the same one every operator runs into eventually.

Half of his users cannot reliably copy and paste. Find and replace is a major event. A regular database exposes too much information at once for the kind of sensitive fraud work he handles, so he needed controlled, button-driven access for people who were never going to learn the underlying system.

The YouTube halfway problem.

Before joining, Doug had done what every self-taught operator does. A vast pile of YouTube videos and articles. Each one got him about halfway to where he needed to be. Then the tutorial would end, the use case would not match, and he would be stuck. He had also lost the kind of weekend you do not want to lose to LLM hallucinations, including the famous incident a year ago where Claude wrote him beautiful documentation for a command that did not exist.

His rule, from a long career in serious work: you can read all the books you want, but you cannot fly a plane or ride a horse from a manual. At some point you need someone next to you who has been there before and knows the one keystroke the book has not gotten to yet.

What we built.

The build is a clean white web page called the ISI Web Assistant. From the user's side, it is a list of buttons. Behind the buttons is a routing layer Doug built with Claude Code, n8n workflows and a Qdrant vector database, all wired together so the user never has to know any of it is there.

The button layer.

Claude Code wrote the front end through the interview workflow Doug picked up in the course. Each button maps to a specific job. One says hello world by running a Claude skill. Another says hello from n8n by triggering an n8n workflow. A third pulls today's appointments out of Google Calendar.

The most useful one is the financial information button. It is built for stock traders who need to see the cost basis of their positions after writing options against them, with the rest of the table locked down. Two buttons run from Claude into n8n, pull the right slice of the portfolio, and display only what the user is allowed to see.

The RAG layer.

Doug also wired the Andrej Karpathy wiki into the dashboard as a question-answer interface. Ask a question, the workflow reads the wiki, the answer comes back inside the same simple page. He has the same content sitting in Qdrant for the heavier lifting. His framing on which to use: sometimes you need a Ford F-150 to take three bales of hay to the barn, and sometimes you need a sand truck for all of New York City. Qdrant is the sand truck.

The orchestration.

Underneath the page is a router workflow that decides which downstream workflow handles each request. Calendar questions go one way. Financial queries go another. Business card scans get parsed and loaded into Coda, where they feed a corporate information system tracking every company the firm deals with. The user never sees any of it. They click. Something appears.

The shift.

Doug is doing things now he could not even conceive of on day one of the course. The same web page he was sketching on a napkin in week one is live, cranking away, and serving users who were never going to learn n8n if their day depended on it.

Because of this course and the Claude course together, I'm able to do things I couldn't even conceive of before the beginning of the course.

The deeper shift is the second person in the room. Doug is the kind of operator who can lose fourteen or fifteen hours to a problem before he gives up. That stubbornness is a strength when there is someone he can finally call. The course turned those fourteen-hour solo sessions into one good question on a group call, where someone else had already hit the same wall the week before.

Run, do not walk to sign up for the course. You may not know it yet, but you need it.
The numbers

What Doug walked away with.

Outcome 01
One button, no Claude, no n8n
End-user experience
Outcome 02
Claude skills + n8n + Qdrant RAG
Backend orchestration
Outcome 03
14-15 hour debug sessions, gone
Time previously lost solo

More stories.

All stories →
“I just needed someone to tell me what to build first.”

Be the next
architect.