GitHub Issue

Repo surface could name the first buyer more clearly

Discovered On Apr 20, 2026

Primary Metric open

My main reaction is that the ambition is obvious, but the first buyer disappears. The homepage language points toward integrated marketing intelligence. The repo language points toward causal digital twin, reference implementation, roadmap, and model-choice justification. Each side makes sense on its own. Together, they make it hard to tell whether the first reader is a growth science team, a researcher, an agency operator, or enterprise marketing leadership. I’d narrow the repo surface to one first buyer and one first use case, something like: "A causal simulation stack for growth teams that want to test campaign scenarios before spending real budget." Then the uncertainty bands, counterfactuals, diffusion model, and training details work better as proof for that buyer instead of trying to define the category in the opening.

View Raw Thread

Developer & User Discourse

OranAi-Ltd • Apr 20, 2026

Thanks for the sharp read. You're right — the old hero (`Causal Digital Twin for Marketing at Scale`) was a category description, not a buyer-outcome line, and it made the "who is this for" question read as three different audiences at once.

Landed the reframe in [`256d11e`](https://github.com/OranAi-Ltd/oransim/commit/256d11e) (plus [`ff5836f`](https://github.com/OranAi-Ltd/oransim/commit/ff5836f) for the team block). Primary changes:

- **Hero tagline**: `Predict your next campaign's ROI before spending a dollar.` — single-buyer-outcome framing, enterprise-CMO first
- **New `Who we are` section** — company context (funding round, Tencent Cloud lab, product lines, named clients) to give the repo a concrete company behind it rather than a floating research drop
- **New `What it solves` · three CMO scenarios** — pre-launch ROI ranking, mid-campaign intervention, post-mortem counterfactual — in the buyer's own words instead of "we do counterfactuals"
- **Replaced the abstract "5 subprob...