What a weekly report looks like
Every Monday you get one email per repository. It opens with the calls that matter and links to the full report.
Verdict key
Class: what the market is doing to this part of your product.
Many providers now offer it cheaply. Building your own rarely pays.
The market is moving in. Partial versions exist; watch the gap.
Nothing in the market threatens it. Your own layer is the value.
Something new makes it cheaper or better to build. Consider using it.
Nobody visible is building this. For a niche product, good news.
Recommendation: Build (keep investing), Buy (use a product or service instead), Wrap (build a thin layer on someone else's), Watch (no change yet, keep an eye on it), Delete (only after several independent sources show it is replaced).
Score: defensibility from 0 to 100. High means hard for others to copy or replace; n/a when there is no market signal.
Confidence: how much evidence stands behind the verdict: high, medium or low.
Since last week: verdicts stay put unless new evidence arrives; when one moves, the report names the release that moved it.
This week's calls
Up to three of each, ranked, and always consistent with the verdicts underneath:
- Invest: where your own work is strong and nobody else covers it.
- Stop or buy: where building your own no longer makes sense, with what to use instead.
- Watch closely: where something is moving fast and could change the answer soon.
All verdicts
One row per capability (see the verdict key) in your confirmed list: its class, a recommendation (Build, Buy, Wrap, Delete or Watch), a defensibility score from 0 to 100, a confidence level, and what changed since last week. Each capability then gets a short section with the reasoning and links to every release behind it.
Platform updates
New releases of the libraries and services your project depends on, and news from the platforms you build on, such as app store rule changes.
A full example
A complete public example, based on a well-known open-source project, will appear here once its maintainers have been told about it. Until then, the example on the home page shows the format.