Modular Adobe Creative Cloud installer for lean workstations

A freelancer or small agency employee sits down on a new machine — maybe a client-provided laptop with 128GB SSD — and realizes they need Photoshop for one specific task: retouching product photos for e-commerce listings. They don't need 3D tools, neural filters in beta, video support, or the bundled fonts they've never opened. But the only way to get any of it is to install all of it.

This gap persists because Adobe has no structural incentive to offer a leaner path. The full install is a moat: every tool bundled in increases switching friction, and support costs drop when everyone runs the same build. A lighter install option would require Adobe to audit feature interdependencies, version them separately, and maintain multiple install configurations — real engineering cost with no revenue upside for them.

What users describe — 'bloated,' 'takes up significant space,' 'more drive space and memory than I think it should' — is not vagueness. It's a coherent signal that the installed surface area doesn't match their actual workflow. A tool that analyzes a user's existing Creative Cloud usage logs (which features they open, which they've never launched) and generates a custom install manifest strips the footprint to what they actually use. On reinstall or new-machine setup, instead of pulling 4GB+ of features they'll never touch, they pull a 600MB build that covers their real workflow.

This is a business and not a feature because Adobe will not build it — it works against their retention logic. For IT managers provisioning 50 creative workstations with tight storage policies, doing this manually would mean auditing each user's workflow, editing installer configs by hand, and re-testing after every Creative Cloud update. That cost recurs every time Adobe ships a major version or someone onboards. The buyer (IT) is different from the user (designer), which is exactly why Adobe has never heard this complaint loudly enough to act.

What to build

Build a desktop app that reads a user's Creative Cloud usage telemetry and installed feature manifest, identifies unused modules, and outputs a stripped installer configuration that can be reused across a team's machines during provisioning or reinstall.

Where to start

Target boutique e-commerce agencies where every employee does the same narrow retouching workflow on underpowered laptops — the use case is identical across seats, so a single stripped config works for the whole team without per-user customization.

The hard part

Adobe's installer manifest format and feature dependency graph are not publicly documented, so the first version requires reverse-engineering which modules are truly standalone versus silently required — one wrong exclusion breaks the install and kills trust immediately.

How it makes money

Annual subscription per organization, priced per seat provisioned, with a free tier capped at 3 seats to let individual freelancers validate the tool before it spreads to their agency clients.