01Product reach
30,000 downloads
The niche application reached thirty thousand downloads.
Founder product evidence
Grimoire
A private digital magical journal turned automatic astrology, weather, music, and tarot metadata into sigil-like stamps for later pattern discovery.
The app reached 30,000 downloads and dozens of paying customers within two months of monetization.
Situation and responsibility
What was at stake
Spiritual practitioners wanted to digitize a practice traditionally kept in physical journals, which were not always nearby and did little to resurface patterns over time.
The product had to merge several inconsistent data sources while protecting private practice and feeling ritualistic rather than like a reskinned productivity tool.
- Evidence
- Founder-owned product
- Audience
- Witches and spiritual practitioners
- Stack
- Node.js, MySQL, and multiple external data sources
- Responsibility
- Research, product, UX, visual design, architecture, and implementation
Diana’s responsibility
- Validated the niche through an adjacent course
- Designed the automatic tagging model
- Integrated astrology, weather, music, tarot, and numerology data
- Pivoted the visual system in response to community feedback
Important decisions
Judgment made visible
Each response follows from an observed condition. The last column marks the tempting shortcut the work needed to avoid.
| What you notice | What it may mean | A useful response | What to resist |
|---|---|---|---|
| Manual metadata would interrupt a ritual. | The system should feel aware without demanding form work. | Automatically stamp entries with sigil-like contextual tags. | Do not expose integration mechanics during reflection. |
| Early visuals read as 'love and light.' | The interface missed the community's identity. | Pivot to dark mode, arcane type, and slower, softer transitions. | Do not use generic wellness aesthetics. |
| Entries could contain intellectual property and private practice. | Privacy was part of respectful UX. | Keep the product private and make deeper data progressively discoverable. | Do not turn sensitive practice into a social feed. |
Decisions and delivery
How the work moved
- 01
Validate the intersection
Use response to a Tech Witchcraft course as evidence that spirituality and technology could meet productively.
- 02
Turn metadata into ritual
Map external data into poetic sigil-like stamps rather than technical fields.
- 03
Listen and pivot
Replace the early light theme with a dark, layered system aligned with community feedback.
Working through a similar constraint?
Describe the problem →Visual evidence
The product in view
A sequence of available project views shows how the system behaves across moments, not only as a single polished frame.
Supported outcomes
What the evidence supports
Quantitative claims appear only where the repository provides them. The remaining outcomes are explicitly qualitative, operational, or statements of responsibility.
02Commercial validation
Dozens of customers
Dozens paid within the first two months of monetization.
03User behavior
Pattern discovery
Automatic tags helped users find recurring contextual relationships in their entries.
Bring me the version that is hard to explain.
If your niche audience needs to feel understood before they will trust the product, tell me what mainstream tools miss.
Describe a similar problem →