Assembling your own stack: the method

From a catalog of tools to a coherent system

You now know the tools across the seven territories. The risk at this stage is wanting to install everything at once. Assembling a stack isn't accumulating: it's selecting, step by step, the tools that match your stage and making them work together. This chapter gives you the selection method and ready-to-use sample stacks.

Five criteria for choosing a tool

Before adopting a tool, run it through the filter of five questions:

1. Is the need real and recurring? If the task is one-off or rare, a dedicated tool isn't justified.
2. Does the tool integrate with my stack? A tool that connects to Zapier, has an API, or offers a native integration beats an isolated silo.
3. Is the free or entry plan enough at this stage? Don't pay for features you won't use for months.
4. Is my data portable? Check the export (CSV, API). A tool you can't get out of is a trap.
5. Is the learning effort proportionate to the gain? A powerful tool that takes two weeks to learn for a marginal gain isn't a priority.

If a tool fails several of these questions, postpone adopting it.

The "one territory, one tool" rule

When starting out, limit yourself to a single tool per territory. Seven to ten well-chosen, well-connected tools beat thirty overlapping ones. You'll add sophistication only when a real bottleneck demands it — not before.

"Zero budget" sample stack (validation and launch)

To start without spending, leaning on free plans:

• Validate: Google Trends + Tally + Carrd
• Build: Airtable + Softr + Canva + Claude/ChatGPT
• Acquire: Search Console + Metricool (free) + MailerLite (free)
• Sell: free HubSpot CRM + Cal.com + Stripe
• Automate: Zapier (free) + Notion
• Manage: Qonto/Shine + Indy
• Steer: Plausible (or GA4) + Microsoft Clarity

Monthly cost: close to zero, excluding the business bank account. Enough to validate and make your first sales.

"In traction" sample stack (first regular revenue)

When the business takes off and the time saved justifies the spend, you upgrade on the sensitive points:

• Build: Framer or Webflow for a professional website
• Acquire: ConvertKit/Kit for advanced email + paid Buffer + a bit of measured Meta/Google Ads
• Sell: Pipedrive or paid HubSpot + Loom + PandaDoc
• Automate: Make for complex scenarios + integrated AI assistants
• Manage: Pennylane or Tiime + an accountant
• Steer: Looker Studio + Stripe/ChartMogul

Indicative budget: a few hundred euros per month, to be measured against the time saved and the revenue generated.

Migrating without breaking everything

Changing tools is inevitable as you grow. To avoid the pain:

• Export before migrating: retrieve all your data (contacts, content, transactions) in CSV format or via the API.
• Run them in parallel for a few days before cutting off the old tool.
• Document your automations: a simple note listing "what is connected to what" will save you during a migration or an outage.
• Avoid simultaneous changes: migrate only one territory at a time.

Mapping your stack

Keep a living map of your stack, in a simple Notion page or a spreadsheet, with for each tool: its role, its cost, its connections, and the person/account managing it. This map is invaluable for spotting duplicates, anticipating costs, and regaining control when the stack grows.

The anti-patterns to avoid

• The tool collector: testing every new release without ever integrating any durably. The hidden cost is scattered focus.
• The weekend tinkerer: spending more time configuring tools than serving customers. Tooling is a means, not an end.
• The tool prisoner: choosing a platform without checking portability, then ending up held hostage. Always know your way out.
• The over-payer: stacking up premium subscriptions "just in case." Every euro of subscription must be justified by a gain in time or revenue.

Key takeaways

A good stack is built by selection, not accumulation: one tool per territory, chosen with five clear criteria (real need, integration, cost, portability, learning effort), and connected to the rest. Start with a "zero budget" stack, upgrade only on real bottlenecks, map your tools, and prepare your migrations. Tooling is a means in service of your business — never an end in itself.