SunsetLedger, tells buyers which vendor code is abandoned
A weekly intelligence feed for operations managers in UK software firms, showing which third-party libraries and vendors in their stack have quietly stopped shipping security fixes.
The expensive part of a business idea is not having it. It is the time you spend finding out it does not work. This pack is that work, already done, with its sources left open.
UK·30 sources·6/6 checks·Verified today
Sourced from netrisk.io
94.5%
This one came through the filter. 1,444 ideas went through it and the rest died on cited evidence. Read what killed them.
One page of the evidence record0bf4d472ef2b90ad
Certification audits require documented evidence of supplier security controls, and the standard method is a static questionnaire that goes out of date between annual audits.
Set by how big this idea could get and the market it targets, never by the size of the pack. See the ladder.
14-day money back, no questions asked
Survived all 6 checks
Instant download the moment you pay
The pack’s own model puts month one at 8× what the pack costs, and payback at 4 months. The workings are the fourth document, and its arithmetic is computed rather than written.
The numbers are in the pack. Pricing mechanics and unit economics, the assumptions behind them listed in full, and anything the research could not stand up is marked so.
Secure checkout via Stripe. A pack is evidence-backed research, not a promise of business success. See our refund policy.
What’s inside your pack
The moment you pay, you download the whole pack. 8 documents, no drip feed, no login.
your pack/8 documents
├──00_Executive_Summary.md
Executive SummaryThe opportunity on one page: what it is, what checked out, and what we do not claim.
├──01_Blueprint_BuildSpec.md
The Blueprint (Build Spec)What to build, in what order, on what stack. Includes the non-goals for v1 and what would kill this.
├──02_Marketing_Plan_GTM.md
The Go-To-Market PlanWhere your first customers come from. Named channels, the beachhead to start in, and the signals that say stop.
├──03_Operations_Plan.md
The Operations PlanHow it runs once someone pays. Delivery, capacity limits, the compliance you cannot skip, and where the manual work sits.
├──04_Financial_Model.md
The Financial ModelPricing and the numbers behind it. Anything we could not verify is marked missing, never made up.
├──05_First_Week_Checklist.md
First-Week ChecklistSix steps for days one to seven: confirm the buyer, size the smallest paid offer, pick one channel.
├──Marketing_Assets.md
Marketing AssetsLaunch copy you can send today: listing page, outreach, social. Claim-checked like the research.
└──QA_Report.md30 sources
The QA Report, with the receiptsEvery check this pack faced, each verdict, and a clickable source behind every claim.
8 plain-text documents in a zip, 5,000+ words. Yours to keep, edit, or paste anywhere. No login, no subscription.
Instant download
Could you run this?
Behind the research is a business somebody has to actually operate. Here is who they would be selling to, and how soon the first money arrives.
Sells to businesses
Part automated
Full-time
Data intelligence
MarketUKThe opportunity, its evidence and its economics are researched for this market. The pack itself is priced and sold in GBP.
Who paysOperations managers at software firms who own the supplier list, approached around the ISO 27001 audit, which one vendor page (netrisk.io) says requires documented evidence of supplier security controls.
How we tried to kill it
Each check is an attack, not a rubber stamp. An idea dies on the first check where cited evidence goes against it. This one survived all 6. Finding nothing is not the same as finding a green light; see how each check works on /how-it-works.
Exactly what this pack covers, plus a blurred look at the document you receive.
SunsetLedger, tells buyers which vendor code is abandoned
01 · A written method for judging whether an outside software component is still being maintained, built only on public evidence you can point a customer to.
Certification audits require documented evidence of supplier security controls, and the standard method is a static questionnaire that goes out of date between annual audits.
02 · Links to every page quoted in this pack, including Snyk's lesson on unmaintained software and HeroDevs' definition of end of life, each labelled with who published it and what they sell.
Month 1 revenue
£1,300
LTV : CAC
7.1×
Payback
4 months
Unlocks the moment you buy
01A written method for judging whether an outside software component is still being maintained, built only on public evidence you can point a customer to.
02Links to every page quoted in this pack, including Snyk's lesson on unmaintained software and HeroDevs' definition of end of life, each labelled with who published it and what they sell.
A look inside
Real, sourced lines taken straight from the pack. Every source below is a live link: open one and check the claim before you buy.
Extract · evidence record
Certification audits require documented evidence of supplier security controls, and the standard method is a static questionnaire that goes out of date between annual audits.
Set by how big this idea could get and the market it targets, never by the size of the pack. See the ladder.
14-day money back, no questions asked
Survived all 6 checks
Instant download the moment you pay
The pack’s own model puts month one at 8× what the pack costs, and payback at 4 months. The workings are the fourth document, and its arithmetic is computed rather than written.
The numbers are in the pack. Pricing mechanics and unit economics, the assumptions behind them listed in full, and anything the research could not stand up is marked so.
Secure checkout via Stripe. A pack is evidence-backed research, not a promise of business success. See our refund policy.