Twenty account briefs that refresh themselves
Sourced briefs on a sales team's target accounts and a Flash Report of what changed, rebuilt every 14 days. The public demo uses fictional names.
Livechecked 21/10
- Client
- A US industrial supplier (name withheld)
- Role
- Built the automations, with Tim N.
- Period
- 08/2026 →
- Proof
- 3 claims
- With
- Tim N.
- Stack
- Python · GitHub Actions · Vercel · HTML
- 1ProblemSales needed prioritized, sourced account research that stayed current.
- 2BuildDeterministic Python builders, a relationship graph, scheduled refresh and a login.
- 3Result20 briefs and a Flash Report, refreshed every 14 days.
Problem
The sales team of a US industrial supplier needed sourced research on its target accounts, ranked by priority, and a short report every two weeks on what changed: news, people moves, hiring and filings.
Build
Deterministic Python builders turn sourced research into account briefs with a priority score, manufacturing sites, role-filtered contacts and sales plays, plus a relationship graph. The Flash Report compares each cycle with the last and answers questions from the graph.
GitHub Actions rebuilds everything when the window passes. A signed-session login protects the production site, and an anonymized copy with fictional companies is public.

Result
Limits
The public demo uses fictional companies. Real account names, contacts and the client's relationship data stay behind the login.
My part
Tim N. leads the client relationship. I wrote 95 of the repository's 101 commits P3.
My commits in the briefs repository95 / 101 · 94%
Links
Proof of delivery · NLV-26-RIB
| # | Claim | Evidence | As of | Confidence |
|---|---|---|---|---|
| P1 | Built 20 account briefs and a Flash Report that refresh every 14 days through GitHub Actions. | 21 Oct 2026 | Public | |
| P2 | 147 test cases, 110 in Python and 37 in Node. |
| 21 Oct 2026 | I hold the artifact |
| P3 | 95 of the repository's 101 commits are mine. |
| 21 Oct 2026 | I hold the artifact |