Every resource in the library starts as a real studio problem, not a feature list. A designer tracking a third round of revisions in a chat thread. An illustrator waiting on an approval that never got written down. A video editor chasing feedback across three apps. A copywriter rebuilding the same client intake questions from memory. Those moments are where a module begins.
Each toolkit is built as a practical file or a small app, then walked through the same workflow it was meant to fix. If a template cannot survive a two-person team running five projects at once, it does not ship. Documentation stays in plain language on purpose: a studio should be able to open a module and start using it the same day, without a training session or a setup call.
The goal is narrow. Reduce the repetitive admin that piles up around revisions, approvals, and deliverables, and leave the actual creative work alone. Nothing here asks a small team to adopt a heavyweight platform or maintain a second system on top of the tools they already use.
Design, illustration, video, and copy each leave different traces: revision rounds, approval notes, asset versions, scope questions. A module starts from one of those traces and gets shaped until it holds up under normal use, not a demo run.
Before release, a toolkit is run against the workflow it targets. If a step adds friction without removing any, it gets cut. The test is simple: does a small team keep using it after the first week, or does it quietly fall out of the routine?
Setup notes are written the way one studio would explain a file to another. Short, specific, no jargon. The point is that a two-person team can adopt a module on their own and adjust it to their own client rhythm.
New packs are released monthly, and buyers keep access to every later version. A private community board is where studios swap the small adjustments they made, so a fix that worked for one team can reach the rest.
The library is shaped by the daily friction of independent studios and freelancers working across Argentina and Latin America. If you want to see how it fits your own setup, the free starter kit is the place to begin, and the module that matches your studio size comes next.
No partner logos live on this page, and that is deliberate. Friendmode does not publish client names, endorsements, or collaboration marks it cannot verify. What we can show is the process: every toolkit in the catalog starts from a workflow that already exists in a working studio, then gets tested against that workflow before it ships.
A designer juggling three revision rounds on one logo. An illustrator waiting on approval that never gets written down. A video editor chasing feedback across four chat threads. A copywriter rebuilding the same intake questions for every new client. Each module begins as one of these specific frictions, not as a feature list.
Depending on the task, a resource becomes a reusable file or a lightweight app. Intake forms and invoicing checklists usually work best as files you can edit and hand off. Revision trackers and asset organizers sometimes earn a small tool when a shared document starts to break. The choice follows the workflow, not the other way around.
Before release, each pack runs through the same scenario it was built for. If a two-person team cannot adopt it without a training session, it goes back. If the setup notes need a glossary, they get rewritten. The test is simple: does this remove repetitive admin, or does it add another platform to manage?
Setup notes stay short and specific. No jargon, no assumed tooling, no dependency on a specific platform. A freelancer in Buenos Aires and a small studio elsewhere in Latin America should be able to open a pack, read the notes once, and start using it the same afternoon.
New packs are released monthly, and buyers get lifetime updates plus a private community board for swapping workflow ideas. The library keeps growing because the friction does not stay still. If a module does not match your studio, the free starter kit is the place to begin before choosing one that does.
See available modulesHow a resource gets made
Nothing in the library begins at a whiteboard. A designer chasing the same revision note across three channels, an illustrator waiting on an approval that never got written down, a video editor rebuilding a feedback list from memory, a copywriter retyping client intake answers into a brief: those are the starting points. We take the friction as it actually shows up, then shape a file or a small app around it.
We write down what happens in order: who receives the request, where scope gets fixed, when a round closes, who signs off. The format comes after. Sometimes the answer is a spreadsheet with five columns. Sometimes it is a lightweight app that only does one thing. We do not decide that in advance.
A draft module runs through a real client job before it ships. That is where weak fields surface: an intake question nobody answers, a tracker column that stays empty, a naming rule that breaks the first time two versions land on the same day. We cut what does not get used.
Setup notes are written the way you would explain the file to a colleague, not the way software manuals read. A two-person team should be able to open a module and start using it without a training session or a support ticket. If a step needs a paragraph of context, the step is wrong.
The point is fewer places to look, not another platform to maintain. A module earns its place when it removes a repetitive task: retyping scope, hunting for the current logo file, reconstructing which revision round was approved. If it adds a habit without removing one, it does not go in.
New packs go out every month, and existing ones get updated when a workflow shifts. Buyers keep lifetime access to those updates, so a module bought for a two-person studio still works when the team grows. Notes on what changed come with each release.
A private community board sits alongside the library, where buyers compare how they run intake, revisions, and handoffs. Most of the useful changes to a module come from someone describing a version that broke in their own studio. That feedback loops back into the next release.
Every module starts from a workflow we have seen in small studios: a designer juggling revisions, an illustrator chasing approvals, a video editor collecting feedback across three channels. The point is not another platform to manage. It is fewer places to look, and fewer things that quietly slip.
Client intake forms in the library capture the few things that cause trouble later: who approves, what counts as a revision, which format is expected, and when the work is considered finished. Filling it in takes a client a few minutes, and it gives you something to point back to when a request drifts.
A feedback tracker records the decision, not just the change: who asked, on which round, and whether it was approved. That single habit stops the same note from reappearing two weeks later, which is where most small studios lose their evenings.
The brand asset organizer keeps approved files apart from working drafts, with a naming rule that carries version and date. Handing files to a client stops being a search exercise, and nobody has to guess which logo is current.
The invoicing checklist is short on purpose: confirm the deliverable list, check the agreed rate, note any extra rounds, send within a fixed window. It also keeps a plain record of what was billed and when, so a follow-up never means digging through old threads.
Some tasks are fine in a shared file. Others break once two people touch them at the same time. Each module says which one it is and why, so a two-person team can adopt it without a training session or a migration plan.
Documentation stays short and specific: what the file does, where to put it, and what to change first. If a step needs a paragraph of explanation, the module gets rebuilt instead. New packs are released monthly, and buyers keep lifetime updates plus access to the community board for swapping workflow ideas.
Not sure where to start? The free starter kit covers intake, revisions, and handoff in one file. You can also see how the modules fit together on the services page, or read more about how each one is built and tested.
Contact usFriendmode builds modular toolkits for independent studios, freelancers, and small teams that need to organize client work without heavyweight platforms. Every resource starts from a real workflow, not from a feature list.
Each toolkit begins as a practical file or a lightweight app, then gets tested against the messy parts of studio life: a designer juggling revisions, an illustrator tracking approvals, a video editor chasing feedback, or a copywriter sorting out client intake. If a step adds friction instead of removing it, it does not ship.
Documentation stays in plain language, so a two-person team can adopt a module without a training session. The point is fewer places to look, not another platform to manage.
Client intake forms, revision trackers, and asset organizers come out of the daily friction of independent studios across Argentina and Latin America. The catalog covers reusable project templates, invoicing checklists, and brand asset organizers for designers, illustrators, video editors, and copywriters.
A module is only finished when it holds up on live projects. We check whether the structure survives a second month of use, whether a handoff stays readable, and whether the notes make sense to someone who did not set it up.
New packs are released monthly, and buyers get lifetime updates plus a private community board for swapping workflow ideas. Start with the free starter kit, then pick the module that matches your studio size.
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.