Emily Denis | Product Manager

I love solving customer problems end to end.

I'm Emily. My favorite part of product work is staying close to one problem from the first conversation to the shipped fix. I've built three small consumer apps that way: FitScript, an AI training coach; HangEasy, a tool for making plans with friends; and NapMap, a nap scheduler for tired parents. Each one started as a real problem in my own life, and all three are live and in use today.

Work

Each case study walks through the problem, the decisions I made along the way, and how I judge whether it's working. All three link to the live product so you can try it yourself.

An AI coach that fits training to real life

FitScript

FitScript reads your sleep, recovery, and race calendar, asks how you're actually feeling, and suggests one workout for the day with the reasoning spelled out in your own numbers. You can adjust the plan just by telling the coach what's going on. Every change to the coach has to pass an eval suite before it ships, and a rules engine steps in whenever the AI is unavailable.

Personalized guidanceConversational coachingEvalsOura + Strava + Apple HealthClaude

Read the case study → Live demo ↗ App ↗

Make plans that actually happen

HangEasy

Group threads fizzle and another month goes by. HangEasy gives the organizer a two minute flow and lets guests RSVP in one tap, with no app and no account. The whole product exists to get a plan from 'we should hang' to a confirmed date.

Social planningOne-tap RSVPSMSWeb app

Read the case study → hangeasy.app ↗

Nap schedules without the math

NapMap

Log a nap as it happens and the rest of the baby's day recalculates, using wake windows that adjust to your baby's age and actual rhythm. I built it for my own daughter and kept it free on purpose. It currently holds a 5.0 rating on the App Store.

iOS + PWAAdaptive schedulingCaregiver sharingFree forever

Read the case study → App Store ↗ napmap.app ↗

How I work

Start with someone's real day

Each of these apps came from watching a problem up close: a training plan that fell apart after a newborn's bad night, a group chat that never picked a date, wake-window math at 3am. I try to understand the whole problem before deciding what to build.

Hold AI to a measurable bar

FitScript's coach only changes when its eval suite passes. Writing those scenarios taught me more about the product than any single feature did, and the suite caught a real safety gap before a user ever hit it.

Meet people where they are

A rough night with a newborn is real training load. A guest who won't download an app is a design constraint. I'd rather adapt the product to the person than ask the person to adapt to the product.

I'm an individual contributor and I like it that way: talking to users, deciding what to build, designing, writing the code, and fixing what breaks in production. If any of this resonates with what you're working on, I'd love to hear from you at emilydenis43@gmail.com.