A two-person studio running five client projects does not need a workspace with fourteen tabs. It needs the revision notes, approval records, and deliverable lists to live somewhere both people can find in ten seconds. That is the whole argument behind these toolkits.
Most of the library is reusable files: project templates, intake forms, invoicing checklists, asset organizers, revision trackers. A file is easy to adopt on a Monday and easy to abandon if it does not fit. A small app only appears where a shared file genuinely breaks down, not because software looks more serious.
The modules assume one person handles client contact while the other handles production, and that roles shift mid-project. Intake forms capture who approves, what counts as a revision, and what the final deliverable format is, so scope does not quietly drift while both people are heads-down on the work.
Each resource is a practical file or lightweight app, checked against how designers, illustrators, video editors, and copywriters actually hand work back and forth across Argentina and Latin America. Setup notes are written in plain language, not a manual that assumes a dedicated operations person.
You start with the free starter kit and add only the module that matches your studio size and the way you already work. Nothing forces you to adopt the full set at once, and nothing locks the workflow into a single vendor's idea of how a project should run.
New packs are released monthly, and buyers get lifetime updates plus a private community board for swapping workflow ideas with other small studios. That board is where the awkward edge cases get discussed, the ones no template can anticipate on its own.
Curious how the modules line up against a full platform? Compare the services overview, or see how the pieces fit together on the plans page.
Five screens from the toolkit, each one solving a specific moment where small studios usually lose the thread: intake, revisions, asset handoff, billing, and the weekly check-in.
One page, filled in by the client before the kickoff call. It records who approves, what counts as a revision, and which file formats are expected at delivery. When a two-person studio runs five projects at once, this is the document that keeps the fourth project from quietly borrowing time from the second.
Item, round, requester, status, date. That is the whole structure. Feedback arrives in fragments across email, chat, and call notes, and the tracker exists so a decision made on Tuesday is still visible the following week. Rounds close explicitly instead of fading out.
Approved files sit apart from working files, and every name carries a version and a date. The point is not tidiness. It is that a client handoff does not require opening six folders to work out which logo is current, and that an illustrator joining mid-project can find the right file without asking.
Confirm the deliverable list, check the agreed rate, note any extra rounds, send. The checklist runs the same way every time so billing does not depend on remembering what happened three weeks ago. A short record of what was billed and when keeps follow-ups from turning into archaeology.
A single view that answers the only question that matters on a Monday: which project is waiting on someone else. Deliverables, open approvals, and pending client replies sit in the same place, so the studio does not need to open five separate documents to plan the week.
Each screen ships as a practical file or a lightweight app with plain-language setup notes. Start with the free starter kit, then add the module that matches how your studio already works. See the modules or send a question.
You do not need to adopt the whole library at once. Start with the free starter kit, see how it sits with your current files, then add a single module when a specific bottleneck shows up: intake, revisions, assets, or billing. Two people can hold five active projects that way, without a platform to maintain.
Tell us your studio type and team size, and we will point you to the module that matches. You can also compare what each module covers on the services page, or read how the library started on the mission page.
We use cookies to keep the site working and to understand how it is used. You can accept or reject them. See our privacy policy for details.