Build Plan: FileDeck
● Live prototype This tool has a working CLI/web build you can try right now →Concept FileDeck — File Command Center cluster, Team variant.
Summary
A spreadsheet says what happens to each file. FileDeck does all of it, or none.
Power-user file tools are fragmented and often visually dated; one coherent workflow can replace 3–4 utilities.
Primary persona
The IT / SMB Admin — an IT lead or small-business owner who needs to deploy, license, and manage the tool across many machines with minimal per-seat friction.
Target customer (from research): SMB / IT.
Competitive inspiration
We’re combining the strongest parts of tools people already pay for:
| Source app | Modeled annual revenue | Current stack |
|---|---|---|
| Directory Opus | $4.5M | Native C++ |
| Listary Pro | $2.5M | C++/native + modern UI |
| Duplicate Cleaner Pro | $2.5M | C#/.NET likely |
| Advanced Renamer Commercial | $1.5M | Delphi/native Windows |
Combined addressable revenue pool (modeled): $11.1M. Target capture rate: 8.1%.
Feature scope
v1 (MVP — ship this, nothing more):
- Dual-pane file management
- Instant launcher/search
- Duplicate detection
- Bulk rename
v2 (after v1 has real usage data):
- Previews
- Rules
Architecture sketch
- Application shell: C#/.NET 10 WinUI 3
- Supporting component: Rust filesystem/indexing core
The split matters more than the exact tech: keep the engine (file I/O, hashing, scanning, capture — whatever is CPU/IO heavy) decoupled from the UI shell, so the engine can be tested headless and reused across variants in this cluster.
Roadmap
| Phase | Focus | What happens |
|---|---|---|
| Weeks 1–3 | Core engine spike | Stand up the riskiest part of the tech stack first (the engine, not the UI) against real sample data and confirm the approach holds up. |
| Weeks 4–10 | v1 feature build-out | Build the full v1 feature scope below on top of the proven engine, wiring up the UI shell as features land. |
| Weeks 11–14 | Polish, packaging & soft launch | Crash/usage instrumentation, code signing, pricing/licensing wiring, and a soft launch to a small user group plus a silent-install/deployment test pass. |
- MVP timeline: 9–14 weeks
- Build simplicity: 6/10 (higher = simpler)
- Opportunity score: 7.3/10
Go-to-market
- Outbound to SMB IT admins and managed-service providers (MSPs)
- Volume licensing with a simple per-seat or site-license price
- Deployment docs / silent-install support for RMM and Group Policy rollout
- Case studies from 2-3 early pilot customers before wider SMB outreach
Success metrics
- Activation: % of installs that complete the core action (the thing in “Feature scope v1”) within the first session
- Retention: 30-day active rate among installs that activated
- Monetization: trial-to-paid conversion rate, tracking toward the $902K/yr mid revenue scenario within 12 months of launch
- Quality: crash-free session rate ≥ 99.5% before removing the “beta” label
Risks & mitigations
| Risk | Why it matters | Mitigation |
|---|---|---|
| Naming risk | The working name has a flagged trademark/domain collision and cannot be used as the shipping brand as-is. | Run a formal name-clearance pass (trademark + domain + store-listing search) before any public landing page, build, or store listing goes live. |
| Market risk | Users already pay for the incumbent tools this concept borrows from and may see little reason to switch. | Lead marketing with the specific market gap this product closes, not a feature checklist — differentiation is the pitch, not parity. |
| Distribution risk | New, unsigned Windows apps routinely get flagged by SmartScreen or Store review, which kills first-run trust. | Budget for a code-signing certificate and Microsoft Store review lead time before any public launch date is promised. |
| Technical risk | Deeper OS/hardware integration (drivers, SMART data, low-level file APIs) adds real platform risk beyond typical CRUD app work. | Spike the riskiest OS integration point in week 1, before committing to the rest of the UI — kill or de-scope early if it doesn’t check out. |
Revenue scenario (modeled, not a forecast)
| Scenario | Estimated annual revenue |
|---|---|
| Low | $406K |
| Mid | $902K |
| High | $1.7M |
Pricing
$59–$149/user/yr + site license
Naming status
Working name only — brand verdict CAUTION (Medium). Collision: FileDeck. Possible only after formal clearance.
This is a working title for planning purposes. Clear the name (trademark + domain + marketplace search) before any public build, landing page, or store listing.
Build checklist
- Validate demand (forum/Reddit/community signal check for the file command center job-to-be-done)
- Clear the working name (trademark, domain, store listing collisions)
- Spike the core engine described in the architecture sketch above
- Ship a thin end-to-end MVP covering the v1 feature scope only
- Instrument usage + crash reporting before wider release
- Set up licensing/payment (one-time key or subscription per pricing direction)
- Soft-launch to a small user group and gather pricing/feature feedback
- Revisit the v2 feature list using real usage data, not guesses
Notes
Working product name only; validate trademarks/domains and user demand before build.