An AI image company. I spent the summer on growth, building launch pages, campaigns and the tool the Storytelling team ran on.
I was the first intern at Reve, on the growth team. Reve makes an image model you can direct. Every image is built from a layout you can edit region by region. Reve 2.0 launched while I was there and debuted at #2 on Arena.ai.
A note on privacy. The internal tool on this page runs on sample data, and the names and numbers inside it are made up, so nothing internal to Reve is shown.
The team was checking how each launch landed across X, Reddit, Discord and a dozen other places by hand, one tab at a time. I asked what they would open first every morning if it existed, built that, and let the rest follow.
It grew into the team's home base. Social listening, a mention archive with translation, a watch for lookalike sites, the outreach pipeline, drafts, a content calendar, and an assistant wired into all of it. I kept it plain, Python and SQLite with no framework, so it stayed easy to change in an afternoon.
For the Reve 2.0 launch I built a 4K zoom out of real downsampled images, so the comparison was honest instead of flattering. Then a landing page and a short coded film for the API, Show Your Layers, which asked people to share the moment the model fought them, and Keep Creating, a free month for creators who shared their work.
I also co-ran the Campus Leader Program, one student at each school, with a hub to run it from.
A green status badge can lie. An API change quietly broke our data collection for days while everything looked healthy. Now I watch what the data says, not whether the job ran.
The hard part is rarely the interface. Getting a CRM to a place a team actually trusts took longer than any page I built.
Artists are arguing about authorship while some of the best ones quietly fold these tools into their process. Working with Reve's creative partners one on one, I saw that tension up close. I think the tools that win are the ones that keep a person as the director.