ExSift

Clean and transform data — no more manual cleanup or scripts

Visit Website
April 3, 2026 Stop writing ETL scripts

Hey Indie Hackers 👋

Most data teams shouldn’t be writing ETL scripts.

Not because they can’t — but because they’re wasting time solving the same problem over and over again.

Every company I’ve seen deals with messy external data:
Different column names, inconsistent formats, broken values.

And what happens?
Someone writes scripts.
Then rewrites them when a supplier changes a column name.
Then fixes edge cases.
Again and again.

It works… but it’s fragile, time-consuming, and honestly a bad use of time.

I hit this exact problem while dealing with supplier product catalogs — we were spending days just cleaning data before we could use it.

So I built ExSift (https://exsift.com) around a different idea:
you shouldn’t clean data — you should define what “clean” looks like once.

After that, everything incoming should adapt to your structure. Automatically.

No scripts. No constant fixes. No manual cleanup.

Curious where others stand on this:

  • Are you still relying on custom ETL scripts?

  • Or have you found a better way to handle messy external data?

Would genuinely love to hear how people are solving this today.

Comment

About

I kept seeing teams waste hours cleaning vendor data instead of using it. Different formats, inconsistent fields — same problem everywhere. So I built ExSift to fix it at the source and eliminate manual cleanup.