How to choose your growth tools

Select the right tools for your business model, budget, and growth stage without overspending or under-delivering

The wrong tools waste money and create friction. The right tools compound productivity. Avoid vendor promises and feature bloat. Choose what actually fits your workflow, integrates cleanly, and grows with you.

How to choose your growth tools

Chapters

Chapter
1

How to choose your CRM

Match your CRM to your sales process, team size, and integration needs. Choose the platform that fits your workflow, not the one with most features.

Read

Chapter coming soon

Chapter
2

How to choose marketing automation

Select automation that handles your lead volume and integrates with your CRM. Avoid overcomplicating simple workflows with enterprise tools.

Read

Chapter coming soon

Chapter
3

How to choose project management tools

Pick the right system for your team size and workflow style. Focus on adoption and collaboration, not feature bloat nobody will use.

Read

Chapter coming soon

Chapter
4

How to choose collaboration tools

Set up async communication that keeps teams aligned without constant meetings. Reduce notification overload whilst maintaining clarity.

Read

Chapter coming soon

Chapter
5

How to choose documentation tools

Build a knowledge base that captures processes and decisions. Prevent institutional knowledge from living only in people's heads.

Read

Chapter coming soon

Chapter
6

How to choose automation tools

Connect your growth tools with automation platforms. Handle data flow, trigger workflows, and eliminate repetitive manual busywork.

Read

Chapter coming soon

Chapter
7

How to choose dashboard tools

Build dashboards that show what's working and what's broken. Focus attention on problems without overwhelming people with data.

Read

Chapter coming soon

Chapter
8

How to choose your AI tools

Use AI to amplify productivity in writing and research. Avoid overspending on capabilities you won't use or falling for empty hype.

Read

Chapter coming soon

Chapter
9

How to choose sales enablement tools

Equip sales with proposal software and call recording. Close deals faster without creating admin burden that slows reps down.

Read

Chapter coming soon

Tools

How to choose your growth tools

tools

Notion
Tool

Notion

Flexible workspace for docs, wikis, and lightweight databases ideal when you need custom systems without heavy project management overhead.

Figma
Tool

Figma

Collaborative design for interfaces and assets excellent for landing pages, ads, and prototypes when marketing and design need alignment.

Webflow
Tool

Webflow

Webflow builds custom websites visually without code, offering designer control, CMS capabilities, and hosting for professional web projects.

HubSpot
Tool

HubSpot

All in one CRM with marketing, sales and service, strong when you want one system that teams adopt.

Claude
Tool

Claude

AI assistant for long-form writing and analysis better than ChatGPT for research, strategic docs, and working with uploaded files.

Zapier
Tool

Zapier

No-code automation connecting 5,000+ apps to move data and trigger actions excellent for quick wins when you need integrations that just work.

Books

How to choose your growth tools

books

SYSTEMology
Book summary & review

SYSTEMology

David Jenyns

A step by step way to document and improve processes so the team delivers consistent results without heroics.

Work The System
Book summary & review

Work The System

Sam Carpenter

A plain approach to system thinking. Write procedures, make small fixes and keep operations tidy as you scale.

E-Myth Revisited
Book summary & review

E-Myth Revisited

Michael Gerber

A practical case for SOPs in growth teams. Design roles, write checklists and build a rhythm for continuous improvement.

Checklist Manifesto
Book summary & review

Checklist Manifesto

Atul Gawande

Why checklists work, where to use them, and examples for launches, experiments and migrations. Keep quality high and stress low.

Wiki

How to choose your growth tools

concepts

Wiki

API

Enable tools to exchange data programmatically so you can build custom integrations and automate processes that vendor-built integrations don't support.

Wiki

Customer data platform

Unify customer data from every touchpoint to create complete profiles that power personalised experiences across marketing, sales, and product.

Wiki

Data warehouse

Store raw data from all business systems in one place to run analyses and build reports that combine information across marketing, sales, and product.

Wiki

Integration

Connect tools so data flows automatically between systems to eliminate manual entry, keep records current, and enable sophisticated workflows across platforms.

Wiki

Marketing stack

Organise the tools that capture leads, nurture prospects, and measure performance to automate repetitive work and connect customer data across systems.

Wiki

Sales tech stack

Assemble tools that manage pipeline, automate outreach, and track performance to help reps sell more efficiently and managers forecast accurately.

Wiki

Stakeholder Management

Navigate competing priorities and secure buy-in by systematically understanding, influencing, and aligning internal decision-makers toward shared goals.

Wiki

Standard Operating Procedure (SOP)

Document your repeatable processes in clear, step-by-step instructions that ensure consistency, enable delegation, and capture institutional knowledge.

Playbooks

Other playbooks

Playbook

How to implement tracking

Broken tracking means flying blind. Proper implementation shows exactly which traffic converts, which campaigns deliver ROI, and where to double down. Measurement makes optimisation possible.

See playbook
How to implement tracking
Playbook

Outreach automation

Create an outreach strategy that defines who to target. Configure domains and infrastructure properly. Build targeted lead lists. Write emails that sound human. Design multi-touch sequences.

See playbook
Outreach automation
Playbook

How to design your sales process

Most sales processes are cobbled together inconsistent stages, unclear handoffs, and no visibility into what's working. A proper process turns chaos into predictability. Define stages that match how buyers actually decide, automate the busywork, and track metrics that reveal bottlenecks before deals stall.

See playbook
How to design your sales process
Playbook

How to choose your growth tools

The wrong tools waste money and create friction. The right tools compound productivity. Avoid vendor promises and feature bloat. Choose what actually fits your workflow, integrates cleanly, and grows with you.

See playbook
How to choose your growth tools
Playbook

Strategic planning

Without clear strategy, every tactic feels like a guess. Define who you're for, what problem you solve, and how each touchpoint moves them closer to buying. Turn scattered efforts into a coherent system where marketing, sales, and product pull in the same direction.

See playbook
Strategic planning
Playbook

How to expand revenue per customer

Acquiring new customers is expensive. Growing existing ones is profitable. Identify expansion opportunities from usage patterns and needs. Design clear upsell paths that feel natural, not pushy. Time offers to renewal cycles and milestones. Structure pricing that enables growth.

See playbook
How to expand revenue per customer
Further reading

More about

How to choose your growth tools

Async video and screen recording

Teams spread across continents rarely share the same calendar slots. A recorder that turns your screen and voice into a link saves the ritual of booking a call. Look for instant cloud upload, viewer analytics, and password-protected links so clients can watch updates when it suits them.

Real-time visual collaboration

Design reviews, journey maps, and rough wireframes all benefit from live cursors and shared canvases. A tool that supports vector editing, comments, and quick prototype links avoids the “final-final-v3” file spiral. Check how well it handles heavy images and whether guests can comment without a paid seat.

Secure credential sharing

Growth stacks balloon to dozens of logins ad platforms, analytics, landing-page builders. A password manager that stores and autofills credentials, enforces two-factor authentication, and revokes access when a freelancer rolls off the project is non-negotiable. Make sure it logs who accessed what and supports shared folders tied to role, not person.

Version history and file recovery

When five people edit the same asset, mistakes will happen. Automatic versioning lets you rewind a Figma frame or restore yesterday’s Loom clip without raising a support ticket. Confirm the retention limits on the plan you choose; cheaper tiers sometimes trim history after thirty days.

Integrations and notifications

Status updates should flow into Slack or e-mail by default. Loom comments, Figma design approvals, and LastPass shared-folder invites need to push alerts where the team already lives. Native integrations beat webhooks here, as they preserve context and cut setup time.

Guest access and permissions

Agencies and in-house teams often bring in contractors for a sprint. A clean permission model lets you invite guests to specific files or folders without exposing the whole workspace. Check whether the platform charges for viewers, how temporary access works, and whether you can transfer file ownership when someone leaves.

Cross-platform performance

Mobile, tablet, and low-power laptops must still load boards and videos quickly. Test large Figma files on a mid-range machine, or a Loom recording on limited bandwidth, to ensure friction stays low for every stakeholder.

These features keep collaboration smooth, secure, and quick exactly what a growth team needs when juggling campaigns across time-zones and tools.

Why do hybrid teams need dedicated collaboration tools?

When half the team sits in the office and half dials in, outdated habits surface fast screens get aimed at laptops, meeting notes vanish, and nobody remembers who owns the next step. A shared whiteboard such as Miro keeps every diagram in one place and lets remote colleagues sketch in real time. Paired with Loom recordings for quick context, decisions stay visible and new joiners catch up without booking another status call.

How does asynchronous video improve remote work?

Time-zone gaps turn short questions into 24-hour delays. I record a two-minute Loom, walk through the screen, and drop the link in chat. Teammates watch when they wake, respond with timestamped comments, and we avoid scheduling yet another call. The thread stays linked to the project, so future reviewers see exactly what was agreed and why.

What solves design feedback across locations?

Figma’s multiplayer editing means everyone from product to marketing can point at the same pixel without version-control headaches. Comments sit on the frame, replies resolve them, and the history panel shows who changed what. No more “final_v7” files or screenshots pasted in chat. The design team iterates faster, and reviewers see progress without pinging designers for new links.

How do we keep passwords secure in a distributed setup?

Shared logins multiply when contractors and agencies join a project. LastPass stores credentials in encrypted folders, autofills them, and lets me revoke access with one click when someone rolls off. It also enforces two-factor authentication, which stops the common “shared spreadsheet of passwords” risk dead in its tracks.

What is the minimum viable stack for async collaboration?

I start with four pieces: a real-time whiteboard (Miro) for brainstorming, a design hub (Figma) for assets, an async video tool (Loom) for quick walkthroughs, and a password manager (LastPass) for secure login sharing. Anything beyond that must replace one of these or automate a clear pain point; otherwise it adds more log-ins than value.

Hybrid, remote, or fully async each arrangement benefits from the same principle: keep context attached to the work and make updates available on demand. When diagrams, demos, and credentials live where everyone can find them, distance stops being a blocker and the pace of execution stays high.