CASE FILE 000/ ANALYSIS
CASE FILE 000 / SUBJECT

DAPHNE G.S

Data-Driven Problem Solver — Technical Analysis + Business Insight

I turn messy real-world data into clear strategic insights that founders can actually act on.

0Transactions Analyzed
0Pricing Pages Archived
0SaaS Companies Tracked
0Independent Investigations
Portrait of Daphne G.S
IDENTITY
VERIFIED
SIGNAL
ACTIVE
ANALYST
ON RECORD
OBSERVE
CONTINUOUS
INTERPRET
IN PROGRESS
SCROLL TO BEGIN ANALYSIS
01 / IDENTITY

Curious by nature, I approach problems by looking at patterns hidden in unconventional markets. I believe the best insights come from places nobody notices.

Method

Pattern recognition applied to markets analysts typically overlook.

Belief

The best signal usually sits in the data nobody thought to model.

Output

Two independent investigations, both built from public data.

02 / FUNCTION

I turn messy real-world data into clear strategic insights that founders can actually act on — building frameworks that reveal how markets actually behave versus how we think they behave.

SIGNAL→INSIGHT→ACTION
03 / DESTINATION

Interested in roles at startups solving unconventional problems — especially where rigorous analysis can uncover competitive advantages.

Signal Analysis Startup Advantage
04 / EVIDENCE

CASE FILES

Two independent investigations. Public data, rigorous method, no assumptions filled in.
CASE 001 / OPEN MARKET
Bitcoin Darknet Pricing Analysis
DATASET: 109,098 TX
METHOD: GRANGER CAUSALITY
STATUS: RESOLVED
95%+
STATISTICAL CONFIDENCE
BTC PriceReference signal
Vendor Price1–4 day lag response
n = 109,098 transactions
Open Case File
Question

Do darknet vendors systematically respond to Bitcoin price movements, or is pricing random?

Data

109,098 marketplace transactions analyzed across volatile Bitcoin price cycles.

Method

Python (Pandas, NumPy, Statsmodels) — Granger causality testing across a 1–4 day lag window.

Finding

Vendors respond within 24–48 hours with statistical precision — 95%+ confidence, clean one-way causality. Vendors are price-takers.

Business Implication

Economic rationality persists even in unconventional markets — participants actively monitor external signals and act strategically. The pattern generalizes to any marketplace with volatile input costs.

Key Findings
  • Bitcoin prices predict darknet prices within 1–4 days at 95%+ confidence
  • Vendors are price-takers — prices don't predict Bitcoin, clean one-way causality
  • Price stability varies 6-fold by product category, revealing market structure differences
Technical Stack
PythonPandasNumPy StatsmodelsMatplotlibGitHub
github.com/Dgs-analytics/bitcoin-darknet-pricing-analysis →
CASE 002 / COMPETITIVE INTELLIGENCE
Startup-SaaS Pricing Index
DATASET: 10,000+ PAGES
METHOD: SHA-256 DIFF
STATUS: RESOLVED
6×
VARIANCE IN REPRICING FREQUENCY
Developer Tools TrackGitHub — every 5 days
Marketing Tools TrackConvertKit — every 31 days
13 companies · 10,000+ archived pages
Open Case File
Question

How often do SaaS companies change their pricing pages, and what does that frequency tell us about their monetization strategy?

Data

10,000+ archived pricing pages from 13 leading SaaS companies, sourced via the Internet Archive CDX API.

Method

CDX metadata harvest → deduplicated HTML download → SHA-256 content-change detection → per-company metrics aggregation → multi-dimensional visualization.

Finding

Repricing frequency varies 6× across companies — GitHub every 5 days, ConvertKit every 31. Developer tools reprice every 5–9 days; marketing tools every 31.

Business Implication

Pricing-page revision frequency is a behavioral signal — a proxy for how actively a company experiments with packaging, positioning and features. Useful for competitive intelligence, PMs benchmarking velocity, and investors reading operational maturity.

Key Findings
  • Developer tools reprice every 5–9 days; marketing tools every 31 — a 6× variance
  • Repricing frequency correlates with strategic maturity and monetization approach
  • Historical patterns shift over time, indicating companies mature their pricing strategy
Technical Stack
PythonPandasBeautifulSoup CDX APIPipeline DesignMatplotlibGit
github.com/Dgs-analytics/startup-saas-repricing-index →
05 / METHOD
01 / QUESTION

Question First

I start with a question nobody is asking, not the obvious one everyone already knows the answer to.

02 / DATA

Find the Data

I locate public datasets, clean them, and validate that they actually answer the question.

03 / ANALYSIS

Rigorous Analysis

I test hypotheses statistically. No assumptions — Granger causality, not correlation.

04 / INSIGHT

Extract the Insight

I translate statistical findings into business implications. Why does this matter? Who cares? What changes?

05 / PRESENT

Present Clearly

I build visualizations that tell the story. No chart junk. Just signal.

06 / INSTRUMENTS

AI TOOLS

Kept deliberately separate from each case file's technical stack — this is workflow tooling, not the analysis itself.

Research
Hugging FaceCheck for a free open model before reaching for a paid API
Build / Code
CursorCatch logic errors in analysis scripts before running them
Synthesize
NotebookLMTurn scattered source notes into one document before writing findings
Automate
n8nReduce repetitive steps in a one-person research workflow
Deploy / Run
GroqGet fast responses when testing prompts on a student budget
Daphne G.S, quiet portrait

I look for the questions
hidden behind the numbers.

The interesting problems are rarely the obvious ones.

ANALYSIS COMPLETE↓SIGNAL IDENTIFIED↓NEXT QUESTION?

WHAT ARE YOU
TRYING TO UNDERSTAND?

Signal identified. Let's see what we can uncover next.