Before you pick a module

Most questions we get are not about what a module does. They are about whether it fits the way a studio already works, what has to be in place before it is useful, and where the limits are. Below are the ones that come up most often, answered plainly.

What do I need in place before starting with a module?
Short answer
Not much. A module works from the files and habits you already have. For the project template and intake form, it helps to know who approves work and what counts as a revision. For the brand asset organizer, gather the current approved files first, even if they are messy. For the invoicing checklist, have your agreed rates and deliverable list written down somewhere. If none of that exists yet, the free starter kit is the right place to begin, because it sets up the basics before you commit to a specific pack.
How long does setup usually take?
Short answer
Setup is short by design, but the honest answer depends on your studio. A solo designer or copywriter can usually adopt a template pack in an afternoon. A two-person team needs a short conversation about naming rules and who owns which step, which adds time but prevents confusion later. The modules ship with plain-language setup notes, so you are not reverse-engineering a system. We do not publish fixed hour estimates, because a studio with five active projects and scattered files will always take longer than one starting clean.
Do the modules work for illustrators, video editors, and copywriters, or only for design studios?
Short answer
They are built for all four. The project template, intake form, and feedback tracker share the same structure across disciplines, because the underlying problem is the same: scope, approvals, and revisions get lost between messages. What changes is the detail. Video work tends to have more review rounds on a single deliverable. Illustration often involves format variants. Copywriting moves faster but with more small edits. The modules let you adjust fields and columns to match that, rather than forcing one workflow on every studio.
Can I combine several modules, or should I start with one?
Short answer
Start with one, then add. Each module covers a single part of studio admin, so combining them is the intended path, not an exception. The usual order is intake form first, then project template, then feedback tracker, because each one feeds the next. Invoicing checklists and brand asset organizers tend to come later, once the project flow is stable. Adding everything at once usually means none of it gets adopted properly. A two-person team running five projects at once will feel the benefit of two well-used modules more than five half-used ones.
What are the limits of a template pack compared to a lightweight app?
Short answer
A file is easy to adopt and easy to abandon. An app asks for setup and a habit. Template packs suit studios that want control over their own files and do not mind a manual step. Lightweight apps make more sense when several people touch the same record and you need one shared view of status. Neither is better in general. If your revision notes currently live across three channels and nobody is sure which is current, that is a signal an app earns its place. If your problem is that you have no structure at all, a file is the faster fix.
What happens after a new pack is released?
Short answer
New packs are released monthly, and buyers get lifetime updates on what they already own. That means when a module is revised, you get the revised version rather than a separate purchase. Buyers also get access to a private community board for swapping workflow ideas with other studios. We do not promise a fixed response time on the board or a scheduled support window, because we do not run one. If something in a module is unclear, the setup notes are the first place to look, and the contact page is there for anything they do not cover.

Still deciding which module matches your studio size? The free starter kit is the practical first step, and you can read how we handle your details in our privacy policy or send a specific question through the contact page.

Cookies on this site

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.