How a Friendmode resource moves through a project

Every toolkit in the catalog follows the same working rhythm: agree on scope, check the details, write down each stage, handle corrections, then hand over the result. That rhythm is what keeps a two-person studio steady across five active projects. It also means we do not claim certifications, guarantees, or outcomes we cannot back with the files themselves.

Agreement before files: Scope, decision-makers, and deliverable formats get written down first, usually inside the client intake form. Nothing moves forward until the person who approves is named.
Detail checks on the working file: Before a round is sent, the template asks for a short pass over names, versions, and formats. It is a plain checklist, not an automated review, and it catches most of the small mistakes that cause rework.
Stages recorded as they happen: Each stage gets a line in the tracker: what was delivered, on which date, and who signed off. The record lives with the project template, so it stays readable months later.
Corrections kept in one place: Revision notes go into the feedback tracker with the requester and the round number. When a note reappears, the earlier decision is already there to point back to.
Handover with the current file marked: The asset organizer separates approved files from working drafts, so the client receives the version that was actually signed off, with naming that shows version and date.

These steps describe how the toolkits are meant to be used. They are not a certification, an audit, or a promise of a specific result for any studio.

What a module actually is

Scope, formats, and the edges of a Friendmode resource

Every resource in the catalog is either a practical file or a lightweight app. Nothing here asks you to migrate your studio onto a platform, and nothing replaces the tools you already open every morning. The point is narrower: cut the repetitive admin that piles up between kickoff and final handoff.

What is included

A reusable project template you can open at kickoff, a client intake form that records scope and decision-makers before work starts, an invoicing checklist, a brand asset organizer with a naming rule, and a feedback tracker for revision rounds. Each one ships as a working file or a small app, plus plain-language setup notes so a freelancer or a two-person team can start the same day.

What is not included

No account, no dashboard, no login, and no hosted workspace. Friendmode does not connect to external platforms, does not run automated workflows, and does not generate content or decisions for you. There is no billing service, no client portal, and no storage for your project files. You keep your own tools; the module only gives them a structure.

Limits worth knowing

The library is built for independent studios, freelancers, and small teams working across Argentina and Latin America. It is sized for the kind of load a two-person studio carries, roughly five active projects at once. Larger teams with dedicated producers, or studios that already run a full project management platform, will find the modules thinner than what they need.

Details to confirm first

Before you pick a module, it helps to know your studio type, your team size, and which tools you already use. Those three answers decide whether a file or a lightweight app fits better. If a module depends on a specific file format or a habit your team does not have yet, that is worth raising before you commit, not after.

New packs are released monthly. Buyers get lifetime updates on the modules they hold, plus access to a private community board for swapping workflow ideas with other studios.

Not sure where to start? The free starter kit is the shortest way to see how a module behaves in daily use before choosing one that matches your studio size.

Ask about a module

How a Friendmode resource moves from first request to daily use

Every resource in the library is either a practical file or a lightweight app, and the path from picking one to actually running it inside a studio follows the same short sequence. Nothing here needs a platform migration or a setup call. You open the file, read the notes, and start using it on the next project.

Step 1
Request the free starter kit

Fill in the short form with your studio type, team size, and the tools you already use. That tells us whether you are a solo illustrator, a two-person design studio, or a mixed freelance team, so the starter kit arrives with the right notes attached rather than a generic folder.
Step 2
Read the setup notes before touching the files

Each resource ships with plain-language notes that explain what the file is for, which parts you edit, and which parts you leave alone. For a project template that means the kickoff fields; for a client intake form it means the questions you keep and the ones you cut for your own scope.
Step 3
Run it on one live project first

Take a project already in progress and apply the template, form, or tracker to it. A video editor might log the current revision round in the feedback tracker; a copywriter might send the intake form to a client mid-brief. One real project shows you where the structure fits and where it needs a small edit.
Step 4
Adjust the fields to your own workflow

Rename columns, drop questions you never ask, add the approval step your clients actually use. The resources are built to be edited, not followed to the letter. This is usually the point where a two-person team settles on one shared version instead of each person keeping a private copy.
Step 5
Choose the module that matches your studio size

Once the starter kit is in use, the next step is picking the module built for your scale: solo, two to three people, or a larger mixed team. Each module adds the pieces that tend to break first, such as invoicing checklists, brand asset organizers, or a fuller revision tracker.
Step 6
Keep the updates and swap notes with other studios

Modules come with lifetime updates, so a file you set up today keeps working as the library grows. Buyers also get access to a private community board where studios trade workflow ideas, which is often where the most useful small fixes come from.

If you are still deciding where to start, the free starter kit is the honest first move. It costs nothing and shows you whether the file-based approach fits how your studio already works.

Compare the modules on the plans page, or write to us at team@friendmode.com if you want a recommendation before choosing.

Inside one studio admin case, step by step

This is a composite example, not a named client story. It shows how a small creative team used a Friendmode module to hold five active projects together, and where the limits of a shared file showed up.

Context and constraints

A two-person studio handling design and video work across Buenos Aires and other Latin American cities had five projects running at once. Revisions arrived by email, chat, and voice notes. Approvals were verbal. The team did not want a heavyweight platform, and they could not pause delivery to migrate everything into a new system. The constraint was simple: keep the existing tools, add one place where decisions could be written down.

What the module had to do

The starting point was a reusable project template with a fixed set of fields: deliverable list, approval contact, revision rounds, and a closing date. A short client intake form captured scope before the first file was opened, so the studio stopped discovering extra rounds halfway through. Both pieces are plain files, not a platform, and they ship with setup notes written in everyday language.

Where the workflow held

Revision tracking was the part that changed the most. Each round got a row: item, round number, who asked, status, and date. When a note reappeared two weeks later, the team could point to the row instead of searching old threads. Brand assets moved into a single organizer with approved files separated from working drafts, which made client handoffs faster and less awkward.

Where it stayed manual

The tracker did not send reminders, and it did not sync between tools. Someone still had to open the file and update it. For a two-person team that was acceptable, because the alternative was more software to maintain. The honest trade-off: a shared file stays useful only while both people keep it current, and the studio accepted that as part of the routine.

What carried over

The same structure was reused on the next project without rebuilding it from scratch. Invoicing moved to a short end-of-project checklist, and the intake form was trimmed to the fields that actually prevented scope drift. Nothing here is a guaranteed result, and the numbers depend on the studio. What held up was the habit: one place for decisions, one place for assets, one short routine at the end.

What you actually get, and what it changes day to day

Every Friendmode resource is a practical file or a lightweight app, not a platform you have to migrate onto. Below are the outcomes studios tell us matter most, written the way they show up in a normal working week.

Kickoff without a blank page

A reusable project template gives a designer or illustrator a starting structure the moment a brief lands: deliverable list, revision rounds, approval points, and a place for the client's own notes. You open the file, rename it, and the skeleton is already there instead of being rebuilt from memory each time.

Scope written down before work starts

The client intake form captures the questions that prevent drift later: who approves, what counts as a revision, which formats are expected, and when the job is considered finished. A short structured document an illustrator can send before the first call does more for a project than a long questionnaire nobody reads.

Revisions that stop circling

A feedback tracker records the round, the requester, the decision, and the date, so the same note does not reappear two weeks later. Video editors and copywriters working across several channels get one place to check instead of scrolling through threads to reconstruct what was agreed.

Assets that stay findable

A brand asset organizer sets folder logic and naming rules that survive the first month, when vague filenames usually start piling up. Approved files stay separate from working drafts, which makes client handoff a single link rather than an afternoon of sorting.

Billing that does not slip between projects

An invoicing checklist runs at the end of each job: confirm the deliverable list, check the agreed rate, note extra rounds, and send within your own fixed window. It keeps a small record of what was billed and when, so a follow-up message does not require digging through old threads.

Setup notes you can read in one sitting

Each resource ships with plain-language setup notes, so a freelancer or a two-person team can start using it the same day. The point is not more software to learn. It is fewer places to look, and a two-person studio holding five active projects without losing track of revisions, approvals, or deliverables.

Not sure which format fits your studio size? The free starter kit is the shortest way to find out, and the module list shows what each pack contains.

See the module list Ask about a specific workflow