https://www.producthunt.com/prod...
It's the end of the month. Your client needs a performance report, so you open five tools, screenshot the numbers, paste them into Google Slides, and spend two hours making it look like you didn't just paste screenshots into Google Slides.
We just made that whole process unnecessary.
Databox
@etiennegarcia That's the split we kept coming back to as well, getting the answer is only step one, turning it into something you can actually hand off is the part that eats the time. Thanks for the kind words, glad it landed.
Hey all! Weighing in here. From a technical standpoint, what makes this reliable is where the data comes from. The artifact isn't summarizing a pasted export, it's pulling from your live connected sources across 130+ integrations. That's the difference between a document that reads well and one I can actually stand behind in a meeting 💪🏻
Databox
@emil_korpar Nailed the technical distinction here. Summarizing a pasted export is the easy version, standing behind the number when someone asks "where did this come from" in a meeting is the bar we actually held ourselves to. Thanks for breaking that down for the thread.
I really like that the reports stay connected to live data instead of becoming outdated static documents or PDFs.
Databox
@divya_kothari1 Good catch to flag, though worth being precise on what "live" means here. An artifact itself is a snapshot, once it's generated, the data inside it is frozen and won't auto-update. But you can re-trigger the same report anytime, and it'll pull fresh, live data from your source with no extra setup, no reconnecting, no rebuilding the prompt. So each generation reflects your current numbers, it's just that a single artifact doesn't refresh in place. Appreciate you digging into the details.
Loomal
This would save client-facing teams hours every month rebuilding the same presentation for recurring client meetings. Solid update.
Databox
@krutiparekh16 That's exactly the use case we had agencies in mind for. Recurring client decks are the most repetitive part of the job, and also the easiest to get wrong when you're doing it by hand every month. Appreciate you checking it out.
congrats on the launch! is there a limit to how large the data sets can be/upfront usage? for example if I'm migrating from another tool could I upload my larve pre-existing data sets?
the edit-mode-vs-prompt-mode split is a smart way to avoid the "AI overwrote my wording" problem. question on that: once I've hand-edited a few sections and then ask Genie for a structural change later, is there version history I can roll back to if the new prompt mangles something near my edits, or is the artifact a single mutable document with no undo path back to an earlier state
Databox
Every team I talk to has some version of the same Friday afternoon task: turn the week's numbers into something presentable and pass it around. Artifacts replaces that with a prompt. You ask Genie for the report, get back a finished document, and either share the link or download the PDF. You skip the whole assemble-and-format slog in the middle.
Databox
@thomas_bossee1 Exactly the moment we built this for. That Friday afternoon "turn the numbers into something presentable" task shouldn't take longer than the analysis itself. Ask Genie, get the doc, share the link. That's the whole workflow now.