The Operations Tech Stack We Deploy for Every New Small-Business Client

Most small businesses do not have a tech stack. They have a tool pile. Someone bought QuickBooks in 2019, someone else opened a Trello board during the pandemic, a seasonal hire introduced Airtable, the marketing agency set up HubSpot for one campaign, and now nothing talks to anything and the founder pays for eleven subscriptions to keep it all partially alive. When we start work with a new small-business client, the first thing we do is not add software. It is decide what the seven systems of record will be and then move every workflow onto those rails.

This article is the standard stack we deploy. Seven tools that cover every operational need a small business has until it hits the scale where custom software genuinely pays back. The stack holds up because each tool is chosen for a specific semantic role, not a feature list, and because we are extremely clear about which tool owns which kind of truth.

Why Seven, And The Three Sources Of Truth

The count matters. You could build a comparable setup with fifteen tools that each do one thing well, and for enterprises with dedicated operations staff that might be the right move. For a small business it is the wrong move. Every tool you add is a login for every new hire, a billing line to monitor, a policy to write, a potential source of silent data drift, and an onboarding surface for whoever has to hand work off. The cost of a tool is not its subscription fee. It is the cognitive load it imposes on the people who use the business.

Seven is the number where we can still say, on a whiteboard in front of a non-technical founder, exactly where every piece of information lives and how it moves. Below seven you force tools to do jobs they are bad at, such as running an ecommerce storefront inside Notion, and the duct tape eats the savings. Above seven you lose the mental model, which is the most valuable thing a small business operator can have. The seven we deploy are n8n, Claude, Notion, Google Workspace, Slack, Stripe, and Shopify or WooCommerce. Each one has a precise role that does not overlap with the others. If you cannot say in one sentence why a tool is in the stack, it should not be in the stack.

Before talking about any of the seven tools, we decide on sources of truth. A source of truth is the system that, if two systems disagree, wins the argument. Every small business needs three of them. Google Workspace is the source of truth for people. Who works here, what their email address is, what calendar they hold, what documents they have access to, when they are out of office. Every other system inherits identity from Workspace through single sign-on, which means when someone leaves you revoke one account and they lose access to everything. We have watched small businesses spend entire weekends hunting down orphan logins after a departure because they never made this decision. Notion is the source of truth for knowledge. Process documents, meeting notes, client briefs, internal wikis, project plans, decision logs. When someone asks how do we do this, the answer is always a Notion link. Knowledge that is not in Notion does not exist, and treating that rule as absolute is what keeps Notion useful. Stripe is the source of truth for money. Every dollar that enters the business does so through Stripe, whether as a subscription charge, an invoice payment, a marketplace payout, or a Shopify settlement reconciled back to Stripe. The accounting system reads from Stripe, not the other way around. These three choices are the load-bearing walls of the stack. The remaining four tools are the rooms you build between them.

n8n For Glue, Claude For Judgment

Between every pair of systems there is a conversation that used to happen in a human brain. The new signup happens in Stripe. The kickoff document needs to appear in Notion. The project channel needs to spin up in Slack. The welcome email needs to go out from Workspace. None of those tools know about the others, and you do not want to pay any of them to know, because the pricing gets ugly fast once you start buying their integration tiers.

n8n carries messages between systems on your behalf. We self-host it on a small server, which means the cost of running thousands of workflows is a coffee per month, and the data never leaves infrastructure you control. The alternative is Zapier or Make, which are fine for tiny use cases but price aggressively once you start automating the way a real business automates, and which put your customer data on someone else's audit scope. Vendor integrations break on the vendor's schedule. Workflows that live in n8n break on your schedule, which is the only schedule you can do anything about. More importantly, workflows in n8n can be read. You can open the canvas and see exactly what happens when a customer pays, whereas a bundle of native integrations across five vendor settings pages is functionally invisible to anyone who did not set it up.

Automation without judgment is just a louder version of whatever mistakes your process already makes. The interesting work in any small business is the judgment work. Is this email angry or confused. Is this invoice a real chargeback risk. Does this support ticket deserve a refund. Is this lead worth a founder call. For decades these questions were the reason you could not fully automate a small business. Claude is in the stack for the thinking. Every n8n workflow that touches customer behavior has at least one step where Claude reads something, forms a judgment, and returns a structured answer the rest of the workflow can act on. Support triage, invoice dunning tone, content moderation on customer reviews, the daily summary that lands in the founder's inbox with the three things that actually mattered in the last twenty-four hours. Without this layer, your automations degrade into the most literal possible interpretation of every edge case. With it, they behave like a competent assistant who read every message and knew what to escalate. We use Claude rather than bolting several model APIs into the stack because consistency of tone across all touchpoints matters more than squeezing a cent per call. The customer who reads the dunning email is the same person who reads the support reply, and small businesses can only afford to project one brain.

Notion For Memory, Workspace And Slack For Communication

Every process your business runs has a prose description that no software can replace. How you price custom work. How you handle a client who keeps missing payments but is a good long-term relationship. Which exceptions to the refund policy are acceptable and which are not. This is the memory of the company, and if it lives only in the founder's head it is a liability the day the founder takes a vacation. Notion holds that memory. We structure it with a clients database that links to projects, a people database that links to roles, a process library that links to the n8n workflows that implement those processes, and a decisions log that captures why things are the way they are. Six months after you made a call about annual billing, nobody remembers why you decided what you decided, and a decision log is the cheapest possible insurance against repeating the same argument. We pair Notion with Claude deliberately. Any new hire can ask Claude to read the relevant Notion page and answer their question, which means the cost of documenting a process drops to near zero as long as the documentation lives where Claude can reach it.

Workspace handles communication with the outside world. Email is still how serious business gets done with customers, vendors, and partners. Calendar is still how meetings happen. Drive is still where the legal team expects to find the signed PDF. We use Workspace rather than Microsoft 365 because Workspace APIs are easier for n8n to talk to, the identity model is cleaner for non-technical founders to administer, and the calendar integrations with every other tool in the modern stack are first-class. If you are already on 365, we do not migrate you. The pain of migration is rarely worth the marginal simplification. Workspace also plays a quiet second role as the shared drive for document artifacts that should not live in Notion. Signed contracts, tax forms, bank statements, legal filings. These belong in Drive because that is where your accountant and your lawyer expect to find them, and because Drive's permissioning is better than Notion's for documents that external advisors occasionally need read access to.

If Workspace is how you talk to the outside world, Slack is how the inside of the company talks to itself. Slack is in the stack because the automations need a place to show up. The daily summary Claude writes lands in a channel. The alerts from n8n when a workflow breaks land in a channel. The Stripe failed-payment notifications and Shopify low-inventory warnings land in channels. You could route all of these to email, but email buries them, and nothing worse can happen to an operational alert than to be buried. We configure Slack with a small number of standard channels across every client, specifically an alerts channel for machine-generated notifications, an operations channel for human coordination, a clients channel for client-adjacent discussion, and a leadership channel. We resist letting clients add channels until they have a reason that clearly maps to a team or a function. Channel sprawl is to Slack what tool sprawl is to the overall stack.

Stripe For Money, Shopify Or WooCommerce For Commerce

We covered the source-of-truth role already. The mechanical role Stripe plays is simpler. Every payment the business takes runs through it, whether that is a direct subscription billed through Stripe Billing, an invoice sent through Stripe Invoicing, a Shopify order that settles through Shopify Payments which is Stripe underneath, or a marketplace payout routed through Stripe Connect. The unified ledger is the gift. You can ask one system what the business earned this month, from whom, in what mix of currencies, with what refund and chargeback rate, and get a clean answer. n8n listens to Stripe events for almost every automation that matters. New customer kicks off the onboarding flow. Failed payment kicks off the dunning sequence. Subscription cancellation kicks off the offboarding and win-back sequence. Refund issued kicks off the reconciliation update in the accounting system. Every one of these is a workflow that used to be a coordinator's job description, and every one of these runs better as code because it runs identically every time.

The last slot in the seven is conditional. If the business sells physical or digital goods through a storefront, that storefront is Shopify for clients who want speed and do not mind the platform cost, or WooCommerce for clients with a WordPress investment they want to preserve and a tolerance for more operational work in exchange for more control. Founders who want to focus on the business choose Shopify. Founders who want to focus on the website choose WooCommerce. Both slot cleanly into the rest of the stack through n8n and Stripe. For clients who do not sell through a storefront, this slot is empty. You do not fill slots that do not need filling.

The Vertical Swaps We Actually Make

No standard stack survives contact with a real business unchanged, and pretending otherwise is how consultants lose credibility. There are three recurring swaps we make often enough to codify. For pure services businesses such as agencies, consultancies, law firms, and accounting practices, we drop Shopify or WooCommerce entirely. There is no storefront to run, and adding one creates a category of problems the client does not have. We keep the other six tools and sometimes add a proposal-and-contract tool that integrates with Stripe, though increasingly we build that workflow inside n8n with Claude generating the proposal text and Stripe Invoicing handling the payment, which keeps the stack at seven.

For SaaS companies, we drop both Shopify and WooCommerce for the same reason and we add two tools. Supabase replaces the role that would otherwise need Airtable or a custom backend, because a SaaS company has its own product database that is fundamentally different from a storefront database. Clerk handles authentication so that the founder does not spend their first year writing password reset flows. Notion remains the knowledge source of truth for the company's internal operations, even though the product itself has a separate documentation site that is often built in Mintlify or GitBook. SaaS companies are the most likely to stretch the stack to eight or nine tools, which is acceptable because the complexity of the product justifies it.

For ecommerce-only businesses with very simple internal operations, especially single-founder brands, we sometimes drop Notion and use Google Workspace as the shared drive for process documents as well as external documents. This is not ideal, and we tell the founder so, but for businesses where there are never more than three people in the room at once, Notion can feel like overhead. The moment the team grows past three or the operational complexity grows past about ten running processes, we reintroduce Notion. It is the easiest tool in the stack to add later because everything else was already set up to link to it.

How The Stack Composes, And When You Outgrow It

The reason this specific configuration works is not that any single tool is best in class, though most of them are close. The reason is that the composition forms a coherent loop. Money comes in through Stripe. Customers enter through Shopify or WooCommerce or Stripe directly. n8n routes them to Notion where records get created, to Workspace where welcome emails get sent, to Slack where the team gets notified, and to Claude whenever a judgment has to happen in the middle of any of that. Knowledge flows the other way. The team writes processes in Notion, which n8n reads and executes, which Claude refines in flight, which Slack alerts the humans about when something steps outside the pattern. The loop is small enough that a founder can hold it in their head. That is the deliverable. Not the individual tools but the mental model of how the business runs. Once the founder can narrate their own operations in a paragraph, every future decision about whether to add a tool, hire a person, or change a process becomes dramatically easier because there is a clear system to measure the change against.

This stack is designed to carry a business from roughly zero to somewhere between ten and twenty million in revenue depending on the category, with teams of ten to forty people. Past that point, specific seams strain. Claude as a single judgment layer gets supplemented with domain-specific models. Notion gets joined by a dedicated customer-facing documentation platform. n8n gets supplemented with proper event streaming infrastructure as the volume of messages between systems crosses a threshold where observability matters more than flexibility. Stripe stays. Workspace stays. Slack usually stays. The point of the stack is not to run your company forever. It is to run your company competently for the years in which competence is the scarce resource.

If you are a small business founder reading this and recognizing that your current setup looks nothing like this, you are not unusual. Almost every business we deploy for starts further from this configuration than they realize. The path from a tool pile to an operating stack is a project we run as a four to six week engagement, which begins with an audit of what you have and ends with the seven tools configured, the n8n workflows running, the Notion pages written, and your team trained to operate without us in the room. If that sounds like the project your business needs next, the way to start is the short form linked below. We read every submission and reply within a business day with whether this is a fit and what the first step would look like.

Book a stack-deploy discovery call with WitsCode >