02.01 · Product Studio / Start here
The product is where the story becomes true.
The website promises that signals go in, the Engine scores every placement, people make the call, and outcomes come out. The Product Studio designs the tools where clients watch that actually happen: the Impact Engine, Media Analysis, the client dashboard, and media planning. Three products on one data layer, one design language, one honesty standard.
The four tracks
Each track has a canonical document and a current status. Start with the document before proposing new work; the specs already commit to more than most people expect.
Track 01 · scoring
The Impact Engine
The scoring and attribution system: daily MIS per placement, lag-aware attribution, recommendations, anomaly detection. The build brief is contract-grade and the vendor build is in motion.
Status · MVP build underway · spec locked
The build brief →Track 02 · reporting
Media Analysis · the new MediaINSIGHTS
The internal reporting tool that absorbs Jasper: omni-channel reporting and ad hocs on the shared data layer, with the score-why-narrative-send flow built in.
Status · systems map agreed · design not started
The systems map →Track 03 · the client surface
Client dashboard
What clients log into: score, why, attribution, narrative, send, with the internal permission toggle and the honesty baseline on the client surface. Four working concepts exist.
Status · four concepts built · direction undecided
The four concepts →Track 04 · planning
Media plan tooling
The forward-looking surface: plans scored before they run, scenario blocks, and the prediction claim the homepage now makes ("the models predict the outcome before the media runs") given a working UI.
Status · open · next concept to design
Design principles
Set during the dashboard concept round, now the bar for every track.
- The client sees clarity, never the machinery. One score, one reason, one recommendation, one action per screen.
- Score and decision first. The biggest thing on any screen is the read. Charts explain the score, never decorate.
- The narrative is the product. A client who reads only the paragraph knows what happened, why, and what Diray recommends.
- Honesty is a feature with UI. The baseline check gets equal visual rank with the score. When media did not drive the outcome, the product says so.
- One brand system. Ink, Broadcast Red, hairlines, mono labels. The product looks like Diray, not a BI tool with a logo pasted on.
- One vocabulary. Signal, score, call, outcome. The words on the website are the words in the product.
Open decisions
- Dashboard direction. Which concept becomes the working surface, and which become the weekly artifact and the QBR wall. The comparison table on the concepts page frames the call.
- V1 scope. What counts as existing Engine functionality is a group decision; the draft list lives on the build brief and is restamped each release.
- The media plan concept. Track 04 has no design yet. It is the studio's next round.
- Per-client theming, density defaults, mobile behavior. Carried from the concept round; decided with the direction call.