Blog Tools guide

The right tool for every job.

375 tools for design, websites, automation and AI, sorted by the work they do. Pick a job or search, and our pick comes first.

New this season 14

The agents and assistants that arrived in the last few months, and what each one does.

Every tool, by the work it does 375

15 kinds of work. Each opens with our pick and why we’d start there.

Thinking and writing 24

Where we start Claude for writing and long documents, with Perplexity alongside it for research that needs sources.

Agents that do the work 13

Where we start Claude Cowork or ChatGPT Work for finished documents and research. For anything that touches money or customers, a person still approves the last step.

Browsers that browse for you 6

Where we start Claude in Chrome or Gemini in Chrome when a team already lives in Chrome; Comet for people who want AI at the centre of their browsing.

Design and brand 34

Where we start Figma for identity, interface and design-system work, and Canva for the templates a team edits day to day.

Images, video and sound 41

Where we start Adobe Firefly where commercial safety matters most, Midjourney for art direction, and Descript for editing anything with speech in it.

Motion and 3D 17

Where we start Rive for interactive animation, Spline for 3D, and GSAP when the motion lives in code.

Assets and inspiration 15

Where we start Unsplash and Envato for everyday assets, Getty Images when only premium editorial will do, and Cosmos for shared moodboards.

Websites and content 32

Where we start Webflow or Framer for marketing sites a team edits visually, Shopify for stores, and a headless CMS such as Sanity when content has to feed more than one place.

Building with AI and code 30

Where we start Claude Code and Cursor for production work, and v0 or Lovable when an idea needs trying before it is built properly.

Automation 17

Where we start n8n for automations we host and monitor, and Zapier when a client’s team will look after it themselves.

AI that knows your business 40

Where we start Claude or OpenAI models, documents searched with pgvector in Supabase, systems connected through MCP, and every answer logged in Langfuse.

The systems you already run 39

Where we start No single pick here. The right system is the one your team already uses well; our job is to make it work with the others.

Research and planning 13

Where we start Miro for mapping, Dovetail for making sense of interviews, and Microsoft Clarity for seeing how a current site is really used.

Measuring and maintaining 32

Where we start Search Console and Lighthouse on every site, axe for accessibility, and an uptime monitor on anything a business depends on.

How we run projects 22

Where we start Notion for shared project pages, Linear for tasks, and a password manager for every login.

Updated October 2026. Tools change quickly, so we revise this guide as the landscape moves. Product names and logos are trademarks of their owners and appear here only to identify them.

How we choose a tool.

There is rarely one best tool, only the best fit for a team, a budget and a goal. Three questions decide it.

The job comes first

We start from what the business needs to happen, then find the tool. Never the other way round.

Your team can run it

A tool only earns its place if the people using it every day are comfortable with it after we leave.

Your data stays yours

We check where information goes, who can see it, and how you would take it with you if you moved on.

What it is
Best for
Where we start in

Have a project in mind?

Let’s shape your next step.

Tell us where your business is today and what you want to achieve. We’ll help define the right approach.