I'm Bobby. I build custom internal tools, dashboards, automations, and small web apps for CRE teams who need something specific and don't have the in-house dev time to build it themselves. Twenty years working in CRE tech means you won't have to explain what a split is, or why the CRM is like that.
Start a conversation See what I doI've been working in CRE tech for about twenty years. Not enough that I'm a household name, but enough to know how the industry actually runs, which tools your brokers will and won't open, and which parts of your stack are politely held together with tape.
These days I build custom apps and small tools for CRE firms who have a specific problem that off-the-shelf software isn't quite solving. Usually that means a dashboard, a workflow automation, an internal app, or some glue code between systems that should talk but don't.
It's a one-person shop. The person you email is the person writing the code. No bench of juniors, no endless discovery phase, no surprise handoffs halfway through the project.
The llama part of the name is there because it makes people smile. CRE takes itself seriously enough already.
Three flavors of the same idea: build the thing that fits the way you actually work, instead of forcing your team to work around whatever you bought off the shelf.
Dashboards and internal tools built for the way your team actually works. Not a generic BI product, not a rigid template. Something that fits.
If someone on your team is copy-pasting data between systems, or running the same manual export every Monday, that's a job for code. I build the glue between the tools you already own.
Small web apps built for one specific job. The kind of thing where off-the-shelf doesn't quite fit and a full product build is overkill.
Most software engagements go sideways for one of a few common reasons. Here's how I try to avoid them.
One-person shop. The person you email is the person writing the code. When I need extra hands, they come from people I've worked with for years, not a rotating bench of juniors figuring things out on your time.
Twenty years in the industry means I can skip the part where you explain how splits work, why the CRM has three custom fields for the same thing, and which platform you're quietly regretting. Saves us both a month of discovery.
Fixed scope where it makes sense. Clear deliverables. Documentation your team can actually read. When the project ships, you own it, and you're not stuck depending on me to keep it running.
Rough idea, firm scope, or just a "does this even make sense" conversation. All welcome. I read everything myself and usually respond within a business day.
Prefer to talk in person? Mention a good time in your message and I'll send over a calendar link.