191 lines
5.6 KiB
Markdown
191 lines
5.6 KiB
Markdown
# Landing Page Redesign — Draft
|
|
*Iaso, March 15, 2026. For review by Johan → implementation by James.*
|
|
|
|
---
|
|
|
|
## Design Principles
|
|
|
|
- **Lead with the specific, not the general.** "Your thyroid is in range" lands harder than "your health data."
|
|
- **The carousel shows. The copy explains. Don't double up.** If the carousel demonstrates something, the hero doesn't need to say it again.
|
|
- **Three audiences, one page.** (1) Someone with an active health mystery. (2) Someone proactively managing their health. (3) A caregiver managing someone else's data. All three should feel seen.
|
|
- **inou is infrastructure. Never say "inou's AI."** The AI is theirs.
|
|
|
|
---
|
|
|
|
## HERO SECTION
|
|
|
|
### Headline (three-line)
|
|
```
|
|
Your thyroid is "in range."
|
|
Nobody connected it to your fatigue,
|
|
your weight, always being cold.
|
|
```
|
|
|
|
### Sub-headline
|
|
```
|
|
inou gives your AI the full picture.
|
|
Your labs. Your scans. Your genome. Your symptoms. One place.
|
|
```
|
|
|
|
### CTA
|
|
```
|
|
[Get started — free until July 2026]
|
|
```
|
|
|
|
### Carousel captions (revised)
|
|
1. `Track your labs over time — and see exactly what your AI sees when a value moves.`
|
|
2. `Log anything. "Took ibuprofen, headache again." Your AI follows up tomorrow.`
|
|
3. `Your own MRI — zoom into the same slices your AI analyzed.`
|
|
4. `Navigate every plane. Verify every finding your AI flagged.`
|
|
5. `Your AI connects the dots across labs, genome, and symptoms — and explains what it found.`
|
|
6. `[New: gym/fitness context image] Your body composition, vitals, and training data — not just when something's wrong.`
|
|
|
|
---
|
|
|
|
## PITCH SECTION (below hero)
|
|
|
|
### Block 1: The problem
|
|
|
|
```
|
|
AI can already reason about your health.
|
|
|
|
It just doesn't have your data.
|
|
|
|
Your cardiologist has your echo.
|
|
Your rheumatologist has your labs.
|
|
Your GP has your vitals.
|
|
Your genome is in a file you downloaded once and never opened.
|
|
Your symptoms are in your head.
|
|
|
|
Nobody has all of it.
|
|
Your AI can — if you give it the infrastructure.
|
|
```
|
|
|
|
### Block 2: What inou is
|
|
|
|
```
|
|
inou is a personal health vault.
|
|
|
|
Upload your scans. Import your labs. Connect your genome.
|
|
Log your vitals, medications, symptoms, anything.
|
|
|
|
Then connect Claude or Grok.
|
|
Ask what nobody in a 15-minute appointment had time to ask.
|
|
|
|
inou doesn't analyze your data.
|
|
Your AI does.
|
|
inou just makes sure it has everything it needs.
|
|
```
|
|
|
|
### Block 3: The tracker (for the masses)
|
|
|
|
```
|
|
You don't need an MRI to start.
|
|
|
|
"Had a headache. Took ibuprofen."
|
|
|
|
inou logs both. Tomorrow morning it asks: did you take it again?
|
|
|
|
Over time, your AI sees patterns your doctor never had the data to find.
|
|
Fatigue on days after poor sleep. Headaches before your period. Energy dips
|
|
that correlate with your iron levels.
|
|
|
|
The daily picture is what makes everything else make sense.
|
|
```
|
|
|
|
### Block 4: The connection (the real pitch)
|
|
|
|
```
|
|
A single lab value is a number.
|
|
A single scan is an image.
|
|
A single symptom is a complaint.
|
|
|
|
Put them together — connected to the same person,
|
|
accessible to the same AI, in one conversation —
|
|
and they become a story.
|
|
|
|
Stories lead to decisions.
|
|
Decisions change outcomes.
|
|
|
|
That's what inou is for.
|
|
```
|
|
|
|
---
|
|
|
|
## TRUST SECTION (keep existing, minor edits)
|
|
|
|
```
|
|
Your data stays yours.
|
|
|
|
Never used for training.
|
|
Your data is never used to train AI models — not ours, not anyone's.
|
|
|
|
Never shared.
|
|
We don't sell, share, or provide access to your data. Period.
|
|
|
|
Encrypted end-to-end.
|
|
At rest and in transit. Military-grade. Your data never travels unprotected.
|
|
|
|
Delete anytime.
|
|
Your account, your decision. Request deletion and it's gone — permanently.
|
|
```
|
|
|
|
---
|
|
|
|
## WHY WE BUILT THIS (keep, minor tightening)
|
|
|
|
```
|
|
You've collected years of health data.
|
|
|
|
Scans from the hospital. Blood work from the lab. Results from your
|
|
doctor's portal. Data from your watch. Maybe even your DNA.
|
|
|
|
And then there's everything only you know — your weight, your blood
|
|
pressure, your training schedule, the supplements you take, the
|
|
symptoms you've been meaning to mention.
|
|
|
|
It's all there. But scattered across systems that don't talk to each
|
|
other, held by specialists who only see their piece, or locked in your
|
|
own head.
|
|
|
|
Your cardiologist doesn't know what your neurologist found.
|
|
Your trainer hasn't seen your blood work.
|
|
Your doctor has no idea what supplements you're taking.
|
|
And none of them have time to connect the dots.
|
|
|
|
Your AI can. But it needs the full picture.
|
|
|
|
inou is the full picture.
|
|
```
|
|
|
|
---
|
|
|
|
## FOOTER CTA
|
|
|
|
```
|
|
Your health. Your AI. Your answers.
|
|
|
|
[Get started — free until July 2026]
|
|
```
|
|
|
|
---
|
|
|
|
## Notes for James
|
|
|
|
### Carousel image 6 (X-ray replacement)
|
|
Replace the `dev.inou.com` X-ray screenshot with either:
|
|
- A real lifestyle photo: woman checking her phone after a workout, with a subtle inou tracker overlay — communicates "proactive health, not just crisis health"
|
|
- OR: a screenshot of the tracker daily check-in UI (the prompt card system) — shows the daily engagement layer
|
|
|
|
### Carousel image 2 (new tracker slide)
|
|
Need a screenshot of the tracker interface — the prompt card view. Shows:
|
|
- A completed card ("Took ibuprofen — 400mg") with a pending card above ("Did you take ibuprofen today?")
|
|
- The freeform input box at top
|
|
- Clean, warm design
|
|
|
|
### Structural note
|
|
The current landing page puts "Why we built this" near the top, which means the first thing a new visitor reads is a long explanation of the problem. Consider moving it below the trust section — let the pitch land first, explain the origin later for people who are already interested.
|
|
|
|
### Tone note
|
|
The current copy says "AI finally can" — this implies inou provides the AI. It doesn't. The revised copy makes clear that inou is the infrastructure and the user brings their own AI (Claude, Grok). This distinction matters legally and strategically.
|