Freelance designer tools: build a six-job stack

Freelance designer tools cover six jobs: making the work, presenting it, collecting client inputs, getting decisions, tracking tasks and time, and billing. A workable stack gives each job one owner and leaves no job split across three apps. App roundups rank tools by features. The more useful test is to count how many places client material can land and how long it takes you to find any one file. That count decides which tool to add, which to drop, and which job you are still doing by email.

The six jobs every freelance design stack covers

A stack is not a list of favourite apps. It is a set of jobs that happen on every project, whether or not a tool is assigned to them. When no tool owns a job, your inbox takes it over by default.

The first two jobs dominate most search results for this topic. The launchthedamnthing.com list of apps for designers and freelancers mixes client management (Dubsado), email marketing (ConvertKit), social planning (Planoly), mail (Spark), photo editing (Snapseed), project management (ClickUp) and feedback (Markup.io). Zapier's roundup of social media graphics tools sorts Canva, Adobe Express, Snappa and VistaCreate by use case — template-based design, scaling a side hustle, occasional images. Both are useful for the make job. Neither tells you who owns collect.

For the make and present jobs in detail — editors, prototyping, handoff to developers — see our breakdown of web designer tools for design and prototyping.

Why "collect" is the job most stacks skip

Collecting is unglamorous. Nobody opens a design app hoping to chase a hosting password. But it is the job that decides when a project can actually start, and it depends on someone outside your stack: the client.

That changes the selection criteria. A design editor only has to work for you. A collection tool has to work for a client who logs in once, uploads twelve files and never thinks about it again. If the client needs an account, a plugin or a tutorial, they will send the logo as an email attachment instead — and your carefully chosen tool sits empty.

Make and present can share a tool; collect and decide usually should

Merging jobs is fine when the same person does both. You make and present, so one editor with share links can own both. Collect and decide are both client-facing and both produce records you need later: what the client sent, and what they approved. Keeping those two in one place means one link per client instead of two, and one archive at handoff.

Count the handoffs before adding a tool

Every tool you add creates new paths a file or decision can travel — and get stranded on. With *n* tools, the number of possible pairwise paths is n × (n − 1) ÷ 2. Not every pair actually exchanges data, but each one is a place where "I sent it in the other app" can happen.

Going from five tools to nine more than triples the paths, from 10 to 36. The sixth tool alone adds five.

Decision rule: a new tool earns its place only if it removes at least one existing tool or one existing channel. A portal that replaces "email plus a cloud folder plus a chat thread" for client inputs takes three channels off the board and adds one. A fourth note-taking app that sits beside the other three does the opposite.

A worked example: one freelancer, six projects

The numbers below are an illustrative assumption, not survey data. Replace them with your own.

Mara is a freelance web designer with six active projects. Each project needs a similar input set: logo files, brand colours, copy for five pages, photos, a hosting or CMS login, and an approval on the homepage design. In a typical input round, she sends four follow-up messages per project. Each follow-up costs about 15 minutes — finding the right thread, checking what already arrived, writing the message, then filing the reply.

6 projects × 4 follow-ups × 15 minutes = 360 minutes, or six hours per input round.

None of those six hours are billable in most fixed-fee projects. And they arrive in fragments: fifteen minutes here, fifteen there, each one interrupting a design session.

The ledger that gives you your own number

Before changing any tool, log two weeks of reality. A spreadsheet with six columns is enough:

1. Date 2. Project 3. Item requested (logo, copy, login, approval…) 4. Channel it arrived through (email, chat, cloud link, portal, call) 5. Days waited between request and arrival 6. Minutes you spent chasing or filing it

After two weeks, sort by column 4 and sum column 6. If more than half of your chase minutes sit in one channel — usually email — that channel is the job without an owner. If waiting days (column 5) are high but chase minutes are low, the problem is the client's calendar, not your tools, and a scheduling rule will help more than software. Our guide to project management for freelance designers builds a full board around that waiting time.

Choosing a tool per job: what to check, not what to buy

Feature lists change every release. The checks below stay stable. Run them during a trial on a real project, not a demo file.

Make and present

• File format exit. Can you export source files in a format another editor opens? Lock-in matters most in the make job, because years of client files live there.
• Share links without accounts. Can a client view a prototype or PDF without signing up? If not, you will end up exporting screenshots, and the present job moves back into email.
• Version visibility. Can a client tell which version they are looking at? A visible version label prevents feedback on an outdated file.
• Asset libraries. For template-heavy work such as social graphics, check the licence terms of included templates and stock assets on the vendor's site before using them in client deliverables.

Collect: briefs, files and logins

• Client effort. Count the steps from receiving your link to a finished upload. Each extra step — account creation, email confirmation, app install — is a point where the client gives up and attaches files to an email instead.
• Structure. Does the tool ask for specific items (logo as SVG or PNG, copy per page) or offer one empty upload box? A single box collects files; a structured brief collects answers.
• Validation. Does it reject the wrong file type or flag a missing item before the client leaves the page?
• Credentials. Logins should not travel through chat. Check how the tool stores and shows sensitive fields, and who can see them.
• Export. Can you get everything out in one download at handoff, with the brief in a readable format?

Decide: feedback and approvals

• Pinned comments. Feedback should attach to a spot on the design, not float in a message.
• Explicit approval. A button or status that says "approved", with a date and a name, is a record. A thumbs-up emoji in chat is a mood.
• Round limits. If your contract caps revision rounds, the tool should make the round count visible to both sides.

Track: tasks and hours

Content Snare's list of productivity tools for graphic designers names project management apps like Notion and time tracking like Toggl, plus secure handling of client data. The selection question for a solo freelancer is simpler than for a team: will you open it daily? A board you update once a week is a historical document, not a tracker. If you already run tasks in a notes app and it works, the gap is more likely in time tracking than in task management.

Bill: quotes, invoices and records

Invoicing tools differ by country, currency handling and accounting integrations, so check them against your own tax setup. Ask your tax advisor which records and formats they want at year-end before choosing — that answer narrows the field faster than any comparison table. On pricing and free tiers for any tool in your stack: plans and caps change, so check the vendor's own pricing page on the day you decide and write down what the free tier limits — projects, seats, storage, export formats.

A 30-point audit for the stack you already have

Score each of the six jobs on five yes/no questions. One point per yes, five points per job, 30 in total.

1. Single owner: exactly one tool or channel owns this job. 2. Client-ready: where a client is involved, they can use it without creating an account. (Score yes automatically for jobs only you touch.) 3. Open export: you can get the data out in a format another tool reads. 4. Two-minute retrieval: you can find any artifact from this job, for any active project, in under two minutes. 5. Actually used: you opened it for this job in the last 30 days.

Decision thresholds:

• Below 18: consolidate before you buy anything new. Remove a tool or close a channel first.
• 18 to 24: fix the lowest-scoring job only. One change, then re-score after a month.
• 25 or more: leave the stack alone. Tool shopping at this point costs more attention than it saves.

Mara's stack, scored honestly:

Mara lands at 24 — fix one job. Collect and decide together lose five points, and both point at the same gap: client-facing material has no single home. The make job, where most of her past tool spending went, already scores full marks.

The pattern is common enough to check for first: designers tend to over-invest in the jobs they do alone and under-invest in the jobs that need the client.

What November and December change for a freelance stack

This article goes live heading into the last weeks of the year, and those weeks put specific pressure on each job.

Collect early when clients close for the holidays

Many client businesses slow down or close over the late-December holidays. If a project is meant to start in January, the inputs for it need to arrive before the client's office goes quiet — otherwise the first January week is spent chasing. A practical rule: ask each client for their closing date, then set the input deadline ten working days before it. That leaves one full week for a second request and a few days of buffer.

E-commerce clients add a second pressure. Holiday campaign work runs alongside regular projects, and their own inbox is at its fullest. Requests that need a structured answer — "which of these five banner sizes do you need?" — get answered faster in a form than buried in a long email.

Check renewals and archive before you cancel

Many design and productivity tools bill annually, and renewal dates often cluster around when you first signed up. Before the year ends:

• List every subscription with its renewal date.
• Run the 30-point audit and mark the tools that scored zero on "used in 30 days".
• For any tool you plan to cancel, export the archive first. Finished client projects, approvals and briefs may be needed again when a client returns for a redesign.
• Confirm with each vendor's terms how long data remains accessible after cancellation.

Close the year's records with the bill job

Gather invoices, payment records and expense receipts in one place while December is quieter. Ask your accountant or tax advisor what they need and by when; the answer depends on your country and business form, so verify it rather than relying on a general checklist.

Where a client portal fits — and where it doesn't

A client portal is a single, secure link per client project through which the client sends inputs and gives approvals. It covers the collect and decide jobs. It does not replace a design editor, a time tracker or invoicing software, and a stack that already scores 25 or more does not need one.

cluein.me is built for exactly those two jobs. Each project gets its own portal link. Clients fill in a brief from a structured template — landing page, webshop or rebrand — upload their files with file-type validation, and approve the project. Clients do not need to create an account. At handoff, you export everything in one click as a ZIP with organised assets and the brief as structured JSON and Markdown. No email chains, everything in one place.

Use the ledger as your fit test. If more than half of your chase minutes come from client inputs and approvals, a portal targets the largest cost. If most of your lost time is in task juggling or billing, start there instead. For how portals compare with other handoff approaches, see our overview of design handoff tools for briefs and file delivery.

The failure mode to watch: adding a portal and still accepting files by email "just this once". Within a month, the portal holds half the material and email holds the rest — and the handoff count from earlier goes up by one. Pick a date, tell every client the link is now the only intake channel, and forward stray attachments into it yourself for the first few weeks.

FAQ

Are free freelance designer tools enough to start?

For the make and present jobs, free tiers can cover early client work, but the limits differ by tool and change over time. Check each vendor's pricing page for caps on projects, storage, seats and export formats before you build client work on it. The export cap matters most: a free tier you cannot leave cleanly gets expensive once years of client files sit inside it.

What are the different types of designers?

Common freelance specialisations include graphic designers, brand and identity designers, web designers, UI/UX designers, motion designers and illustrators. The make job differs between them — vector editors, prototyping tools, animation software — but the collect, decide, track and bill jobs look almost identical. That is why the client-facing half of a stack transfers between specialisations more easily than the design half.

How has AI impacted graphic design?

AI features now sit inside many design tools; Toptal's page on freelance graphic designers lists Photoshop, Illustrator, Sketch, After Effects and Figma alongside emerging AI capabilities. For your stack, treat AI as part of the make job rather than a separate tool. Before using generated output in client deliverables, check the vendor's terms on commercial use and tell the client how assets were produced if your contract requires it.

What are the top 5 freelancing platforms?

No ranking holds for every designer, because platforms differ in client type, fee structure and how work is matched. Marketplaces such as Fiverr's graphic design category and vetted networks such as Toptal work differently, and designers compare their own experiences in threads such as this Reddit discussion of freelance sites for designers. Compare platforms on their current fee pages and on who their clients are — then keep briefs, files and approvals in your own stack, so they stay with you if you change platforms.