Projecto

The problem

Every job starts with the same twenty folders.

Rushes, proxies, audio, graphics, exports, deliverables, and the eight subfolders inside each of them. The structure never changes, and you rebuild it by hand at the start of every project, or you duplicate last month's folder and spend the afternoon emptying it.

The copy that was supposed to be empty is never quite empty. A stray render, an old audio file, a client note from another job, and they follow you all the way to delivery.

The answer

Define the tree once.

Projecto takes a ZIP of your ideal project structure, asks where it should go, and rebuilds it. Any depth of hierarchy, exactly as you designed it, in the time it takes to pick a destination.

The structure is previewed before anything is created, and you can exclude folders and files from that preview, so one template covers the small jobs and the big ones.

How it works

A ZIP is the template.

There is nothing to learn and no format to respect. Build the folder tree you want once, however you like, ZIP it, and that archive is now your template. Change your mind about the structure and you change the ZIP.

Names follow a date-first convention, YYMMDD_Project_Client, so the folders sort chronologically on their own for the rest of their life.

What is in it

The rest of the toolbox.