JONAS STAMM
β€” FIELD NOTES
ai-engineeringβ€” April 19, 2026Β· 4 min read

How RAG Beats Fine-Tuning for Most Startups

How RAG Beats Fine-Tuning for Most Startups When we first started building BauGPT, I was convinced we needed to fine-tune our own model. I mean, it sounds so c...

JS
Jonas Stamm
Founder, BauGPT

How RAG Beats Fine-Tuning for Most Startups

When we first started building BauGPT, I was convinced we needed to fine-tune our own model.

I mean, it sounds so cool, right? "We have our own proprietary model trained on German construction law." It's a great line for VCs. It feels like you're building a real moat. 🏰

I thought RAG (Retrieval-Augmented Generation) was just a temporary hack. A band-aid until we got enough data to do "real" AI work.

I was wrong. 🫠

After a year in the trenches, I can tell you: for 95% of startups, RAG isn't just a starting point. It's the destination.

Here’s why we ditched the fine-tuning dream and went all-in on RAG.

The Fine-Tuning Fantasy

The dream is simple: you take a base model (like Llama or GPT-4), feed it thousands of your specific documents, and suddenly it "knows" everything about your niche.

No more long prompts. No more searching through databases. Just pure, distilled intelligence.

Sounds amazing. But in practice? It’s a nightmare. 🀣

First, fine-tuning is static. If a building code changes tomorrow (and in Germany, they change all the time), your fine-tuned model is instantly out of date. You have to re-train.

Second, fine-tuning is a black box. When the model hallucinates a DIN standard, you have no idea why. You can't just fix a typo in a text file. You have to tweak hyperparameters and hope for the best.

And the biggest killer? The "New Model" problem.

The Maintenance Trap

Imagine you spend three months and €20k fine-tuning a model based on GPT-4. You finally get it working perfectly.

Then OpenAI releases GPT-4o. Or Anthropic drops Claude 3.5.

Suddenly, your specialized model is worse than the new base models from the big players. 🫒

If you're fine-tuning, you're now stuck. You either stick with your old, expensive, specialized model, or you start the three-month training process all over again for the new version.

With RAG, switching models takes ten minutes.

We switched from GPT-4 to Claude 3.5 Sonnet in an afternoon. We just pointed our RAG pipeline at a different API endpoint. Our data (the vector database) didn't have to change at all. πŸš€

RAG Is Just "Finding the Right Page"

I like to explain RAG like this:

Fine-tuning is trying to make a student memorize every book in a library before an exam.

RAG is giving that student an open-book test and a really fast librarian. πŸ“š

When a user asks BauGPT about minimum concrete cover for a foundation, we don't expect the model to "know" it. Instead, our system:

  1. Finds the exact paragraph in the 1,000-page DIN 1045.
  2. Pastes that paragraph into the prompt.
  3. Asks the model to explain it to the user.

It’s more accurate. It’s verifiable (we can show the user the source). And it’s much cheaper. ✌️

When Should You Actually Fine-Tune?

I'm not saying fine-tuning is useless. It has its place.

If you're trying to change the style of the output (like making it sound exactly like a specific person) or if you're working with a very niche format that standard models just can't parse, fine-tuning can be great.

But for knowledge? RAG wins every time.

Unless you have millions of rows of data and a team of PhDs, don't try to teach the model new facts. Just give it the facts when it needs them. πŸ€“

The BauGPT Way

Our stack is simple now:

We spend our time improving our search and our document parsing, not waiting for training jobs to finish. πŸ› οΈ

The Takeaway

If you're a founder and your CTO says you need to fine-tune a model for "proprietary knowledge," ask them if they've tried a better RAG setup first.

Most of the time, the problem isn't the model's brain. It's the model's library.

Keep your intelligence liquid. Keep your data separate from your weights.

The models are getting smarter every week. Don't weigh yourself down with a specialized version that will be obsolete by next Tuesday. 😎

LG Jonas


Building BauGPT β€” making construction sites smarter with AI. If you're building AI in the real world, reach out!

Keep reading

All writing β†’
build-in-public Β· Jun 1, 2026
β–Έ$ we run ai agents inside baugpt.
# build-in-public
read-time: 7min

We run AI agents inside BauGPT. Here's what it taught us about building them.

We build AI for the construction industry. We also run AI agents inside our own company to handle scheduling, ticket routing, code review, and content ops. That...

7 MIN READ
β†—
product Β· May 21, 2026
NΒΊ 02

Our enterprise onboarding takes 90 minutes. The procurement took 11 weeks.

A construction company with a four-billion-euro annual turnover signed up for BauGPT last quarter. Their procurement process took eleven weeks. The actual onboa...

4 MIN READ
β†—
product Β· May 21, 2026
NΒΊ 03

We process 40,000 WhatsApp messages a week. Here's why we built there.

BauGPT processes 40,000 WhatsApp messages a week. About 40% of them are voice notes. I mention this not to flex on a number. I mention it because it explains ev...

4 MIN READ
β†—
β€” THE NEWSLETTER

One note a week.
No fluff, just what works.

AI engineering, growth hacks, and messy lessons from shipping BauGPT. Unsubscribe anytime. I'll even miss you.

FIELD NOTES Β· NEXT ISSUE DROPS MONDAY
↳ No spam. One note weekly.