Many small businesses and brokers have to reference a variety of documents to execute core tasks. Often a helpful staff member summarizes it all into another PDF-as-index. Recently, I explored changing a search and hope activity into asking plain language questions of a trained LLM. Working with a mortgage broker, we created a personal research assistant available via a private Discord chatbot. "Morty" references a private vector database about regulations and turns a desktop filesystem task into a personal chatbot available from nearly any networked device.
(Image rights: LHD, LLC 2025)
Being a mortgage broker requires mastering regulations to identify the most appropriate package for a particular client. I'm not a mortgage SME, but here was a clear information retrieval improvement opportunity:
- Regulations were dense and difficult to master. Staff "down" time was used to create indices in order to improve turnaround time on core tasks.
- Regulations are public, making efficient retrieval an advantage
An LLM is a great tool to solve this issue. However, the target users are services professionals desiring an uncomplicated interface. Implementation and usage posed technical hurdles for them so far. Additionally there are requirements regarding information privacy.
This is where Limitless Horizons Development came in. Our purpose is to help specialists in non-AI domains leverage the new technology, allowing them to focus on their core business. The goal is to bring in new tools for tasks that are friction on the value human staff bring. In this case, staff needed information as quickly as possible to make decisions and the act of information retrieval itself is friction.
The following technical pieces provide a solution:
- Make.com: Used to create a quick prototype with the client, to verify certain choices
- Live stack: Heroku, Python, Postgres, Open AI, Discord: Discord talked to a headless Django app on Heroku, providing a Postgres vector DB as a tool to Open AI, which received and processed the query.
The result was a new capability within a messaging app the staff already had.
Staff are constantly encouraged in the UI to not include personally identifiable information and the full database is on an owned server. But a production environment this would require a more detailed look and also the business’ documented security requirements.
Editor's note, April 2026: Morty is a working reference implementation exploring this pattern with a mortgage broker's use case in mind, not a currently deployed production engagement. The underlying stack, methodology, and approach are all working and demonstrable. Interested in seeing it applied to your specialist domain? Let's talk.