Tiếng Việt

Operations Manager Tools and Tech Stack: What to Buy, What to Cut (2026)

You walked into the role and inherited 14 tools. Three of them auto-renewed last quarter and nobody noticed. Two of them have one active user, and that user left in February. Somebody bought a "workflow automation platform" on a sales call and it sits at $480/month doing the job of one Zap. The CFO asks why ops spend is up 22% year over year. You look at the receipts and you can't actually answer.

This is normal. Ops absorbs every "we need a tool for X" request that crosses the org, and nobody is named owner of the cleanup. Marketing wants Asana. Engineering wants Linear. Finance wants Vendr. Customer Success bought Notion forms last August and forgot to tell anyone. The stack grows by accumulation, never by decision.

The job isn't to find more tools. The job is to run fewer of them, deeper, with named owners and reviewed renewals. This guide is the working list I'd hand a new ops manager on day one: the Core 6 categories, real 2026 prices, the honest tradeoffs, and the 30-day audit that pays for itself before it's done.

Why the Core 6 Beats the Long Tail

Most ops orgs don't need 20 tools. They need 6 categories handled well:

  1. Project management. The spine. Where work lives.
  2. Docs and knowledge. The memory. Where decisions are written down.
  3. Automation. The connective tissue. Where the boring work runs without you.
  4. Vendor management. The brake pedal. Where SaaS spend gets reviewed before it renews.
  5. Forms and intake. The front door. Where requests come in.
  6. Customer / CRM ops. The relationship layer. Where the people you serve live.

Everything else (analytics dashboards bolted onto a BI tool, three Slack alternatives, the AI notetaker nobody uses, the second screen-recording tool) is duplicate or vanity. If a tool doesn't fit one of those six buckets and have a named owner, it's a candidate to cut.

Here's the rule I use: every tool needs a named owner, a reviewed renewal date, and a sentence about what dies if you turn it off. If you can't write all three on one line, you don't have a tool. You have a subscription.

Category 1 — Project Management (The Spine)

This is the one you'll fight about. Every team thinks the company should run on the tool they prefer. None of them are wrong. They're just optimizing for different jobs.

Asana. $14.99/user/mo Starter, $24.99 Advanced (annual billing). Strong for marketing and creative ops. Timeline view is genuinely good. Workflows and rules are mature. Weak on engineering work. Devs hate the data model, and Jira integrations are still flaky in 2026. If you're a marketing-led org under 200 people, this is a defensible pick.

Monday. $11/user/mo Standard, $17 Pro (annual). Flexible boards, friendly UI, the "I want to see my work as a colored grid" tool. Great under 50 users. Past 50 users it gets messy fast: too many board variants, automations stepping on each other, permissions that nobody understands. The flexibility that wins you over in month one is the same thing biting you in month nine.

Linear. $10/user/mo Standard. Opinionated, fast, beloved by engineering teams. Don't pick this for cross-functional ops. It's a product/engineering tool that thinks marketing campaigns are bugs. If you're a tech-heavy org and ops mostly serves R&D, fine. If ops is brokering between sales, marketing, CS, and finance, Linear will frustrate four of those five.

Rework Work Ops. $6/user/mo. Cross-functional execution layer. Unifies project, task, and cross-team handoffs without the per-seat tax. Honest framing: the UI isn't as polished as Asana, and it doesn't have Linear's keyboard-driven cult feel. Where it wins is price plus cross-team unification. If you're paying $14.99/user across 80 people, that's $14,400/year. Same headcount on Work Ops is $5,760. The delta funds your forms tool, your automation tool, and a quarterly off-site.

My pick if you're starting fresh: if marketing/creative is the dominant ops customer, Asana. If engineering dominates, Linear plus a lighter tool for the rest of the org. If you're cross-functional and budget-conscious (which most mid-size ops teams are), Rework Work Ops.

My pick if you're auditing an existing stack: whatever already has the most active users with real data in it. Migration costs more than license consolidation. Switch only when the current tool is actively breaking, not because the new one is shinier.

Category 2 — Docs and Knowledge

You need one. You only need one. Running two is ops debt that compounds quietly.

Notion. $10/user/mo Plus, $18 Business. Vibes-driven, flexible, the team will actually use it. Weak on permissions at scale and on real version control. Good default for orgs under 300.

Confluence. $6.40/user/mo Standard, $12.30 Premium. Enterprise-friendly, locked-in if you already run Jira. Less fun to write in. Better at "this is the official record" than "this is where we think out loud."

Coda. $12/user/mo Pro, $36/user/mo Team. Doc-as-app, formulas, the option if you want spreadsheets and docs to live in the same surface. Niche but powerful for small ops teams that build a lot of internal tools.

Pick one. The hidden cost of running Notion for product and Confluence for engineering isn't the license. It's the ten hours a week your team spends asking each other where something lives. Consolidate.

Category 3 — Automation

Automation is where ops earns its keep. It's also where ops bleeds money if nobody's watching.

Zapier. $19.99/mo Starter, scales fast. By the time you have 20 active Zaps with multi-step logic and team seats, you're at $400-700/month. Easy to start, gets expensive in the middle.

Make (formerly Integromat). $10.59/mo Core, cheaper per operation than Zapier at scale. Steeper learning curve. If your ops lead can read a flowchart and isn't afraid of an HTTP module, Make saves real money.

Workato. $1,000+/month, enterprise. Don't even quote it under 200 employees. Where it earns its price is when "the integration" is actually a regulated, audited business process: finance close automations, customer onboarding with SLA contracts, HR systems that touch payroll.

The rule I use: if a single Zap costs more than $200/month to run, that's not an automation. That's a feature request to engineering. Document it, hand it off, and stop renting the duct tape.

Category 4 — Vendor Management

This is the category most ops managers underspend on, then regret.

Vendr. Pricing varies, typically $5K-25K/year plus a percentage of negotiated savings. Buys you a procurement team without hiring one. Best for orgs with $500K+ SaaS spend.

Tropic. Similar model, slightly cheaper at the entry tier. Strong on contract intelligence and renewal calendars.

NachoNacho. Closer to a SaaS marketplace with discounts. Lighter weight, fits smaller orgs.

When DIY beats them: under $200K total SaaS spend, under 30 vendors, and you have an ops person who can run a renewal negotiation. Below that line, the math doesn't work. The savings these platforms generate are real but they're a percentage of spend, and the floor is high.

When they pay for themselves: above 30 vendors, above $200K spend, and renewals are slipping past unreviewed. The first two negotiations they run usually cover the annual fee. After that, it's pure leverage.

If you're DIY: build a renewal calendar in whatever doc tool you picked above. Every vendor, renewal date, owner, and last year's negotiation notes. Review it monthly. That's 80% of what Vendr does. They just do it with leverage you don't have.

Category 5 — Forms and Intake

The category most teams overspend on. Forms aren't hard. You don't need a $89/month plan to collect five fields and route them to Slack.

Typeform. $25/mo Basic, $50/mo Plus, scales by response volume. Polished, conversational UX, the right pick when the form is the experience (lead capture on a landing page, NPS surveys, partner applications). Overkill for internal intake.

Tally. Free tier is genuinely usable, $29/mo Pro for unlimited everything. Built by ex-Typeform folks, leaner, no per-response cap on the paid tier. My default for internal ops forms.

Notion forms. Included in your Notion plan. Lightweight, ugly, but free if you're already there. Good enough for "request a new tool" or "submit a contractor for approval."

Google Forms. Free, ugly, works. If your form is "vacation request" or "expense reimbursement under $200," you don't need to pay anyone.

The pattern I see: teams pay $89/month for Typeform Business because someone wanted nicer logic five years ago, and now 18 forms run on it that could have run on Tally or Notion. Audit your forms once a year. Move the ones that don't need polish off the paid plan.

Category 6 — Customer and CRM Ops

If sales has its own CRM and CS has its own help desk and ops has a spreadsheet stitching them together, you're paying three tools to lose customer context at every handoff.

Salesforce / HubSpot. If you're already locked in, stay. The migration cost outweighs the consolidation benefit until something is genuinely broken. Audit seats, kill unused logins, negotiate renewals hard.

Rework CRM. $12/user/mo for cross-team customer ops. Where it wins: sales, CS, and ops sharing one customer record with native multi-channel chat (WhatsApp, Messenger, IG DM, email, SMS, web chat) tied to the timeline. If you're a mid-size org (20-500 employees) where the customer touches three teams during the lifecycle and context is leaking at the seams, this is the right shape. See Rework's pricing for the current tier breakdown.

When Rework CRM wins: mid-size, cross-team customer ops, marketing-and-sales in one funnel, and the team needs unified chat in the CRM record (not a separate inbox tool).

When it doesn't: you're a Salesforce shop with seven years of customizations. You're a pure-sales org where CS doesn't touch the record. You need the deepest enterprise reporting in the market. Honest answer is: stay where you are.

The point isn't to switch CRMs. The point is to stop paying for sales, CS, and ops tools that don't share a record. If your current stack does, keep it. If it doesn't, this is the conversation.

The 30-Day Stack Audit

Run this in your first month, then once a quarter forever. It's the highest-leverage thing an ops manager does.

Week 1, Inventory. Pull every SaaS invoice from the last 12 months. Finance has them. Card statements have them. Build one sheet: tool name, monthly cost, annual cost, renewal date, who signed up for it, who uses it. Don't analyze yet. Just list.

Week 2, Usage. For each tool, get usage data. Active seats vs paid seats. Last login per user. Most paid plans have an admin export. Where they don't, ask the vendor and they'll send it. You'll find seats paid for ex-employees, plans on the wrong tier, and tools where one person logged in once eight months ago.

Week 3, Kill list. For each tool, decide: keep, downgrade, kill, renegotiate. Killing is rarely controversial when you have the usage data. "Five seats, one active user, $1,800/year" makes the case itself. Renegotiation: every renewal in the next 90 days gets a call. Vendors expect it. The default discount for a multi-year commitment plus a "we're considering alternatives" email is 15-25%.

Week 4, The doc. Write the stack doc. One page per category, owner, renewal date, what it does, what dies if it's gone. This is the artifact your CFO has been asking for and your replacement will thank you for. Put it in whichever doc tool survived Category 2.

The first time you run this you'll find $20K-$80K in annual savings depending on org size. That's the salary delta on your next promotion. Use it.

The Ops Manager's Stack Principle

Fewer tools, deeper usage, owned renewals.

Every tool needs a named owner. Every renewal gets reviewed before the auto-charge. Every category has a default and the default doesn't change because someone read a hot take. The ops manager who runs a clean stack with the Core 6 will outperform the one running 18 tools with three people who half-know each, every quarter, on every metric, forever.

Start with the audit. Pick the Core 6 owner for each category. Build the renewal calendar. Then say no to the next three "we need a tool for X" requests in a row. By month three, finance will stop asking why ops spend is up. They'll start asking how you did it.

Learn More