I like the concept of the EU’s health data space; I don’t like where it could lead.
The EU announced the European Health Data Space (EHDS) last year to break down the silos between healthcare providers across the EU.
The problem for me is that the government ultimately controls the data and how it can be used. The better option is a solution where your health data stays yours.
I’m zeroing in on where most health data spaces fail: privacy.
That's why I'm building @HealifyApp so it
→ exists only in a decentralized, secure space, with a hospital’s level of data security.
→ isn’t shared with anyone unless you specifically request it.
→ isn’t used to iterate or train AI models. It remains only visible to you.
I want to know your thoughts: do you like where the EU is going or would you prefer to have that data in your own hands?
February, on stage at EDC Mexico. Last week, my first live voice call with Anna, the health coach I'm building.
Same habit in both: make something, put it in front of people, see what lands.
I toured for years and my body paid for it. Bad sleep, bad food, a new time zone every few days.
Now I'm building Anna, a health coach you can actually talk to.
If you've toured or worked nights: what would you ask a coach at 3am after a show?
Anna is the health coach I've been building. I talked to her today. For a moment it felt like a real person who knew me.
An exported audio file can contain the wrong mix. You only find out if you listen.
I want the same check when an AI agent says it's finished: open the page it changed, or read the draft it saved. What actually happened?
Am I retiring Sam Feldt?
People know me as a DJ. So when I said I was building an AI business, the same question kept coming:
"Why are you leaving music for AI?"
I'm not.
I'm building Healify so I have more freedom to make music, not so I can stop.
I spent over a decade getting to 7.6 million monthly listeners. I didn't do that to walk away from it. But I also didn't become a musician because I wanted to be only a musician.
If you've toured, you know it isn't a sustainable way to build a life. You outlive it.
So I'm building something that might outlive me.
The goal with Sam Feldt was always to bring more happiness into people's lives.
Same goal with Healify, different platform.
If you've followed my music this far, thank you. Hope you stay for this part too.
Here's a demo of what I've been building.
You get a full picture of your health in a few minutes, wherever you are. That's the part I care about most.
Since the last update: web version is live, we got cleared for Google Play, hired my first full-time developer, and started working with the team at AWS to bring this thing to life.
Check it out so far: web.healify.ai
Creative professionals: AI is not going to replace you.
If you spent ten years making music, writing screenplays or designing brands, you built something a model can't be given. You know the difference between technically correct and actually good.
It's what's left after years of making calls under pressure with your name on the result.
So keep making things.
You can use AI to make drafts. You can't hire it to have taste.
I’ve spent 10+ years mastering the art of melody and flow as Sam Feldt.
When I’m Sam Renders, I use the same skills to help businesses optimize their teams and workflows.
I get asked all the time how I split my time between music and tech. Short answer: I don’t.
Music is melody.
Coding is melody.
If you've spent years training taste in one domain, you already have the hardest part of building a product. It’s not a new language, just a new syntax.
Your creative-to-builder path isn't a career switch. It’s a simple skill transfer.
Master the translation, and you’re unstoppable.
A couple years ago I watched someone close to me walk out of a doctor's office with a stack of blood test results. They nodded, said thanks, and left with no idea what any of it meant.
If that happens in my own family, it happens to a lot of other people too.
So I started building an app. Mostly by myself, mostly while on tour.
The idea was simple: scan your results on your phone, get a plain-language explanation for every number, see the actual studies behind the recommendations, and walk into the next appointment with the right questions.
Our phones already track 170+ health metrics without us doing anything. But only about half of us can read a basic blood panel.
Over the next few months I'll be writing about how I'm building @HealifyApp. Follow along if you want to see how it all pans out.
My neighbours are hearing this non-stop right now😂 Click the link to stream KEEP ON RISING🎶 link.to/_KeepOnRising
Goal for July: Make more obscure things nobody asked for.
Watching my son grow up, I’ve realized just how much kids build things 'just because'. And how little we do it as adults.
Most times, if there’s no clear ROI for a project, we don’t bother. But experimentation is how we’ve gotten some of the world's biggest solutions.
Google Street View. Twitch. Gmail. The list goes on.
The real question isn’t "why waste time building projects without a clear path forward?"
It's "why did we ever stop?"
Played 200+ shows before I wrote a single line of production code. Everyone assumed the DJ couldn't build the AI. But reading a crowd and reading a user are the same muscle — sensing what lands a half-second before the data confirms it. The stage was my training set.
the reason teams ship orchestrators isn't accuracy.
it's that orchestrators let you build *judgment* into the system — escalation paths, tone branches, "i'm not sure, let me check" responses.
these are the moments that make or break trust.
a single-call LLM can't do them.
example from healify:
scared user asks about an abnormal bloodwork result.
single LLM call: technically correct answer, clinically flat tone, user leaves forever.
orchestrated agent: "this is unusual, here's what i can say with confidence, here's where to take this next, want me to flag it for a clinician." user stays.
same model. different system. different product.
everyone's debating model benchmarks.
operators are asking one question: does it ship faster than the last version?
i've been building with claude code daily. the thing that changes the game isn't the evals — it's the edit loop. how fast can you go from "this is broken" to "this is working" without leaving the conversation.
that feedback loop is where AI actually compounds. not the benchmark number.






