The problem surfaces in a specific organizational context: a company or institution has standardized on Premiere Pro because it's what their professional editors use, but now non-specialist staff — communications coordinators, teachers, HR video producers — are also expected to make simple edits. Trim a clip, add a title, adjust audio. These users don't need 80% of Premiere's features. They need the 20% that covers their entire job. But Premiere presents all of it at once, and users reported that 'the amount of screens that must be kept open to actually edit a video are too many and make everything very confusing.'

The reason this stays broken is structural: Adobe's Premiere Rush was supposed to be this product, but it's a separate app with a separate subscription, a different file format, and no ability to hand off to a Premiere Pro editor for finishing work. The organizational workflow breaks. IT doesn't want to manage two apps. Non-specialists end up forced into full Premiere anyway, where they're immediately overwhelmed.

What these users need isn't a dumbed-down app — they need a constrained workspace that hides what they don't need and surfaces only the actions relevant to their specific task type. A communications coordinator making an interview clip needs: cut, titles, audio levels, export. That's it. The 'steep learning curve requiring many hours of video tutorials' complaint comes almost entirely from users who are being shown tools they will never use.

This is a business because the demand is organizational and recurring. Every company that runs video production in-house has this two-tier editor problem: the pro editor and the occasional contributor. The occasional contributor's inefficiency has a real cost — delayed social posts, bottlenecked communications teams waiting for the pro editor to do a 10-minute job. An IT or operations buyer will pay a per-seat fee to eliminate that bottleneck, and the need recurs as headcount grows.

What to build

Build a Windows and Mac desktop app that connects to a shared Premiere Pro project library via Creative Cloud, presents a stripped-down editing workspace with only cut, titles, audio, and export visible, and outputs a sequence that a Premiere Pro editor can open natively for finishing — with no file format conversion required.

Where to start

Start with higher-education communications departments that already have Creative Cloud institutional licenses — they have a clear two-tier problem (faculty/student vs. professional AV staff), a procurement process that moves faster than enterprise, and a measurable pain point in video turnaround time for admissions and marketing content.

The hard part

Deep integration with Premiere Pro's project file format requires either reverse-engineering undocumented Adobe internals or negotiating an API partnership with Adobe — neither is fast, and Adobe has a history of breaking third-party integrations through updates.

How it makes money

Per-seat annual license sold to the IT or communications department administrator — priced below the full Premiere Pro seat cost to make the ROI obvious when replacing a Premiere license for occasional users.

See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Video Editing.

More ideas in Video Editing