Product build
AgentsThatEmail
Forward the thread, get the summary back
There was nothing to install and no account to set up. You forwarded the long email thread to a bot, and a minute later everyone on it got a short summary back, with the decisions and the to-dos pulled out. The inbox was the whole interface.
The problem
Every team has the forty-message thread nobody rereads, and the person who got CC'd at message forty-one with no idea what was decided. Most tools that fix this ask you to leave your inbox, sign up for theirs, and paste your email into a box. So nobody does, and the thread stays a wall.
The build
The bot had an email address, and that was the entire front door. AWS SES caught whatever landed there and dropped the raw message in S3. A Lambda function parsed the mail, handed the text to GPT with one instruction, summarize this and surface the action items, and then replied through SES to everyone on the thread except the bot itself.
Every reply ended with a plain line saying it was written with AI, because the honest thing was to say so. The whole service deployed from a single template. There was no box to keep running, and nothing new for anyone to learn.
The outcome
You forwarded the thread and a minute later you were reading three lines instead of thirty. It worked because it lived where the conversation already was. That is the same reason letmecheckbot answers inside the group chat today, rather than asking anyone to open an app.