Body composition is noise until you read it as a trend.

Hume Health's Body Pod measures body composition — fat, muscle, water — via bioelectrical impedance. Any single reading is half signal, half hydration. A small AI stack is how you turn a scatter of weekly numbers into a trend that actually means something.

The raw signal under the score

  • Body fat percentage and fat mass
  • Muscle mass and skeletal muscle
  • Body water and hydration markers
  • Weight and derived ratios over time

Export your readings from the Hume app. The value isn't any single measurement — it's the series. Hand the AI a few months and let it do the smoothing.

One method, not one more app

Hume Health Body Pod is the data source. The method is what turns that data into something you can read, question and act on — the same three layers, whatever app or device you happen to use.

  1. 01

    Research

    Sourced search that ranks real evidence above influencer claims — so you start from what the studies actually say.

  2. 02

    Ledger

    One long-context record of your own data and notes, re-read together week after week, so patterns surface instead of scrolling past.

  3. 03

    Protocol

    A single, constraint-aligned plan that fits your real schedule — one thing to change, not a textbook to obey.

“But it already has AI built in.”

More wellness apps and wearables are doing exactly that — building a capable assistant straight into the app. It is genuinely useful, and it changes nothing about why this method exists.

A built-in assistant can only see one app’s data, and it answers inside the frame of the company that built it. Your sleep, your labs, your training, your cycle and your notes still live in separate silos — and the questions that matter most sit in the gaps between them.

The method works the other way around. You bring the data out, into tools you own, and read it across every source at once. When an app gets a smarter assistant, that’s one more good input to your stack — not a new dashboard to be governed by.

Four tools, one workflow

  1. 01

    Hume Health Body Pod

    The sensor. It records the raw signal — your job is to get the export out of it.

  2. 02

    Your chat assistant (ChatGPT / Claude / Gemini, free tier)

    The analyst. Reads the export, finds correlations, explains them in plain English.

  3. 03

    Your notebook tool (NotebookLM)

    The memory. Holds weeks of exports plus your own notes for long-context, cross-week synthesis.

  4. 04

    A scheduled action / custom agent

    The ritual. Sends the weekly nudge, drafts the read-out, keeps the loop running without you.

Why one reading lies

BIA sends a tiny current through you and infers composition from resistance — which means hydration, time of day, food and exercise all move the number before any real change does. People take one reading, panic or celebrate, and learn nothing. The fix isn't a better scale; it's a better reading. Measure consistently and let an AI separate the trend from the daily noise.

Compose the full picture

Body composition only makes sense next to what you're doing — training, protein, sleep, a cut or a bulk. The app shows the number; an AI reading the export alongside your training and nutrition log can tell you whether muscle is actually trending up or whether you're just better hydrated this Tuesday. That context is the difference between data and a story.

The method on a scale

Research how BIA behaves so you stop over-reading it. Build a ledger of consistent weekly readings plus context. Run a protocol — e.g. a protein change over eight weeks — and let the AI read the smoothed trend. The pod measures; you decide what moved.

Three prompts you can use today

Paste each into the chat assistant you already use, along with this week’s Hume Health Body Pod export.

Smooth my body composition

I'm pasting weekly Body Pod readings for 12 weeks: date, body fat %, muscle mass, body water, weight, all taken at the same time of day. Give me a smoothed trend for each, and tell me what's genuinely changing versus measurement noise. No medical advice.

Read composition against training

Here are my Body Pod readings plus my training and protein log. Tell me whether muscle is trending up and fat down in line with my effort, or whether the changes are within noise. Be honest if it's too early to tell.

Design a composition test

Design an 8-week single-variable test (e.g. raising protein to a target) using my Body Pod data. Hypothesis, the change, what to hold constant, the metric, the success rule.

A cadence you can actually keep

  1. 01Weekly: one reading, same time of day, same conditions.
  2. 02Monthly: export and ask the AI for the smoothed trend.
  3. 03Log training and protein alongside it.
  4. 04Run one 8-week change at a time.
  5. 05Keep the full series in your notebook tool.

What this won’t do

  • BIA is an estimate, not a DEXA scan — read trends, never single readings.
  • Hydration, food and exercise swing the number; consistency of conditions is everything.
  • Healthy change is slow; give any protocol weeks, not days.

Before you paste anything

  • Never ask AI for a diagnosis. It reads patterns; it does not practise medicine.
  • Strip names, emails and any clinical ID before you paste an export.
  • Don't paste other people's data — only your own.
  • Treat the output as a hypothesis to test, not an instruction to follow.
  • If a pattern worries you, take the written summary to a clinician — don't act on it alone.

Common questions

Is BIA accurate?+

For absolute numbers, roughly. For tracking your own change under consistent conditions, useful — which is what the AI reads.

How often should I measure?+

Weekly, same time and conditions. Let the trend, not the reading, guide you.

Can AI smooth the noise?+

Yes — separating trend from variation is exactly what it's good at.

Does this replace a coach?+

No. It gives a coach a clean trend to program against.

Want the method behind this stack?

The free 10-day email challenge teaches the same Research → Ledger → Protocol method on whatever data you already collect.

Keep building your stack

Based on what you've been reading — always learning.

See all →