The score should belong to the analyst, not the vendor.
I'm Wade Wickingson. This page is the honest version of why CredScore exists, what I'm trying to do with it, and why I think it matters.
Where "CredScore" came from
Years ago, during a stretch where I couldn't pay my bills on time, I watched my own credit score drop. It was a number I didn't fully understand, controlled by an agency I'd never spoken to, used by lenders to decide whether I was a risk. I couldn't see the reasoning. I couldn't appeal it. I could only watch.
That experience stuck with me. Not because of the financial hit, but because of the structural one. A third party owned the number that defined my creditworthiness, and I had to live with whatever they produced.
A few years later, when I started looking at the crypto compliance industry, I saw analysts in the same position. They were opening dashboards from Chainalysis, Elliptic, and TRM Labs and receiving an opaque risk score on a wallet they were being paid to defend. The reasoning was vendor-internal. The methodology was proprietary. The analyst was expected to act on the output without being able to argue with it.
CredScore is named for the inversion. The score should belong to the analyst. Every signal should be readable. Every conclusion should be defensible. The decision and its rationale should land in the same view, in under 15 seconds.
Built from outside the industry
I'm not a former Chainalysis or Treasury analyst. I don't come from compliance. I'm a self-taught builder who's been tinkering with computers since I was a kid. Before CredScore, I spent six years running social media for a high-end brand. I learned to communicate clearly, to operate online, and to listen to what audiences actually wanted.
Why I started it
I started CredScore because no one with the right background was shipping the deterministic, explainable engine I wanted to see exist. So I made it myself.
What that means for the product
9,200 lines of deterministic scoring logic. No machine learning. No black boxes. Every output traces back to specific on-chain signals an analyst can see, question, and document. Every score is something they can defend in a review.
That outsider position is, I think, the whole reason CredScore exists. The incumbent tools were built by teams whose business model depends on customers trusting the score. Mine was built by someone who didn't trust opaque scores in his own life and decided to build the opposite.
Never finished. Always revised.
I think about the engine the way a designer thinks about a chair. It's never finished. It's always being revised. The threats change. The chains change. The laundering patterns change. A risk scoring engine that hasn't been updated in six months is one that's already wrong about something.
Small fixes ship weekly. Larger changes ship monthly. Every analyst who tells me where the engine got it wrong shapes the next revision. There's a feedback panel on every briefing in the desk that goes directly to me. I read all of it.
Compliance analysts, investigators, and anyone who has to make a call on a wallet.
For the analyst at a small shop who can't afford a $50,000 Chainalysis contract. For the AML consultant working three clients out of a home office. For the trust and safety team at a five-person crypto startup. For the on-chain investigator chasing a hack. For the lender who needs to look at a borrower's wallet before extending credit. For anyone who needs a fast, explainable read on wallet behavior and can't get one from the tools they currently have access to.
If that's you, the product is free during early access. I want you using it. I want your feedback. Founding users get preferential pricing locked in when paid plans launch.
Talk to me directly.
I'm a single founder. I read every email. The fastest way to influence what gets built next is to send a message about what you actually need.