The case against performance management software for companies under 100
Read more Performance Reviews
When you’re choosing employee feedback software for a 30-person team, the listicles are the wrong place to start. They compare features. The decisions that actually determine whether the tool works for you happen one level up, at the criteria you use to read those feature lists in the first place. That’s where I’d want a founder in my shoes to spend the first hour.
I’ll get this out of the way up front: I run a company that sells one of these tools. So discount everything below accordingly. The reason I’m writing this anyway is that the post I needed when I was doing this evaluation didn’t exist, and writing it now from inside the category is the most useful thing I can offer. Here’s what I looked for, what I wish I’d weighted more heavily, and what made each decision easier in retrospect.
Key Takeaways
- Listicles compare features; the question that determines fit is which criteria you use to read those feature lists. The criteria are upstream of every comparison.
- For a 30-person team, the five criteria that mattered most for me were time to first review, per-seat pricing math, the reviewer experience, the synthesis output, and exit costs.
- Enterprise tools (Lattice, Culture Amp) and SMB-targeted tools (15Five, Small Improvements) fail differently at this size. The failure mode is the diagnostic, not the brand.
- “Anonymous” feedback in a 30-person team is often a polite fiction. The tool’s anonymity model has to be credible to direct reports or upward feedback collapses.
- In retrospect, the criterion I’d weight more heavily is module breadth: every module nobody opens becomes a process somebody quietly has to run.
The first thing I noticed when I started looking was that the search results all looked the same. Ten-tool roundups, in roughly the same order, with the same feature columns: pulse surveys, 360 reviews, eNPS, integrations, mobile, pricing tier. They tell you what’s in the box. They don’t tell you which boxes you should open at your size.
The reason the listicles feel useless at a small company isn’t that they’re poorly written. It’s that they’re written for someone two or three sizes up from you. A 200-person company really does need eNPS dashboards and HRIS integrations and analytics that can slice across departments. A 30-person company has none of those problems yet, and a tool optimized for them is a tool optimized for somebody else’s headaches.
What I read instead were the demo videos, where you can see how a real reviewer experiences the tool, and the pricing pages, which (when you read them honestly) tell you who the product was actually built to sell to. For a deeper version of that lens applied to 360 software specifically, the what to look for in 360 feedback software for small teams breakdown covers the criteria angle in more detail.
Five criteria did almost all of the work for me. They’re listed below in the order of how often they ended up being the decisive thing on a given tool, which isn’t the order I started with.
The single fastest filter I applied: how long would it take, from creating an account, to have my first 360 review actually running? If the answer involved a sales call before I could see the product, the tool wasn’t built for someone at my size. Enterprise vendors openly advertise multi-week implementations; that’s accurate for the buyer they want, and a deal-breaker for the buyer I was.
A founder running their own evaluation can usually test this in under ninety minutes. Sign up, create a review, write three questions, invite a friend, complete the form yourself, and look at what comes out the other end. If you hit a wall configuring permissions before you’ve even sent the invitation, that’s the answer. The friction you encounter testing is the friction your team will hit in production, and your team will be less patient than you.
The per-employee pricing model that looks reasonable on the page compounds in two directions you don’t notice until later. First, you’re paying for every seat whether they use the tool monthly or once a year, and most of your 30 employees will be in the “once a year” bucket. Second, the entry tier rarely includes the features the demo sold you on; the modules that mattered live a price plan or two up.
The honest math is to take the highest plan that includes what you actually need, multiply by your full headcount, multiply by twelve, and ask whether that number buys you something a shared document and an afternoon doesn’t. For larger platforms targeting growing companies, that math gets uncomfortable before you cross 50 people. Check the vendor’s pricing page for the current numbers; they change.
This is the criterion I almost skipped, and it would have been the costly one. The buyer is the founder or People Ops lead. The user is the engineer or designer who has to fill out feedback for four colleagues after a long day, and whose grumbling is what determines whether the round ever finishes.
The test is to actually open the reviewer-side form for a tool and complete it for one person. Time yourself. Notice what made you hesitate, what made you re-read, what felt like busywork. A pulse survey designed for engagement benchmarking and a 360 form designed for real development questions look almost identical on the buyer’s spec sheet and behave completely differently to the person filling them out. The form your team actually completes wins; the more comprehensive form your team abandons mid-round is worse than nothing.
Every vendor demo ends with a beautiful screenshot of a results page. Mine did too, before I knew what to look for. A radar chart is not a development conversation. The output a manager actually needs is something short enough to read in five minutes and specific enough to use in the meeting that afternoon.
The right question to ask in a demo: “Show me the artifact a manager hands the employee, or reads from in a one-on-one.” If the answer is a dashboard, you’re going to be doing the interpretation work yourself, which was the part you were hoping to outsource. If the answer is a themed written summary with example quotes, that’s the version that earns its keep at this size. The interpretive work is the expensive part, and a tool that doesn’t help with it is mostly a survey distribution platform.
Here’s the one I missed. I was thinking about modules I’d use, not about modules I wouldn’t. The platforms that bundle goals, engagement surveys, comp planning, and 1:1 templates alongside reviews look like value on the pricing page. In practice, every module you don’t open shows up on the dashboard as a configuration option that somebody on your team will quietly start running because it looks like negligence not to.
For a fuller version of this argument, the case against performance management software for companies under 100 covers what platforms install along with the thing you came for. The short version: at 30 people, pick the tool whose breadth is closest to what you actually need, and resist the bigger one even if the price difference is small. The price difference is not where the cost lives.
Three names came up in nearly every evaluation conversation, and looking at each one taught me something different about the criteria above. None of this is a ranking; the diagnostic value was in the failure mode.
Lattice is the one I spent the most time inside. It’s well built and clearly designed for a buyer who already has a People function. The implementation reality, the module breadth, and the contract structure are all calibrated for that buyer. None of those are flaws in absolute terms; they’re answers to a different question than the one a 30-person team is asking. For a more direct take on the trade-offs at small scale, see Lynxify vs Lattice.
Culture Amp taught me about per-seat math. The product is genuinely excellent at engagement measurement, which is the use case that justifies the headcount-scaled pricing. If engagement benchmarking is the job you’re hiring the tool for, the numbers add up. If you’re hiring it primarily to run a 360 once or twice a year, you’re paying for an engagement dashboard you’ll glance at quarterly.
15Five taught me about the reviewer experience side. It’s clearly designed for ongoing lightweight feedback, which is its strength and its frame. Whether that frame fits depends on whether you want feedback to be a steady rhythm or a structured round; both are valid answers, and the tools optimized for each behave differently in the hands of a tired reviewer at 6pm on a Friday.
If you want the ranked-comparison version of this view, the best 360 feedback software for small companies covers four tools head to head with the same criteria lens.
I’ll keep this short, because of all the paragraphs in this post, this is the one to discount most heavily.
What I wanted was a focused 360 review tool that did one thing the way a small team would actually use it: fast setup, no annual contract, anonymity that holds at small scale, and a written synthesis a manager can read like a person rather than a dashboard. I couldn’t find it in the form I wanted, so I built it. That’s Lynxify, and you should evaluate it with the same skepticism you’d apply to any tool whose founder is also writing the buyer’s guide.
If you want to try it instead of just reading about it, start your first 360 in Lynxify, no annual contract, no credit card required. Or run the next round in a shared document and prove you don’t need a tool yet. Either way, you’ll know more than you did before you started.
Features fit a checklist. Criteria fit a story. The checklists on the listicle pages are accurate, and they are not the level the decision actually gets made at. The decision gets made at the level of which criteria you read those checklists with, which is determined by the size of the team that will actually use the tool, not by the size of the team in the demo video.
Pick the criteria you’d weight on day one of running the tool, not day one of evaluating it. Then read the pricing page honestly. The rest of the evaluation gets a lot shorter.
How do I choose employee feedback software for a small team?
Start with criteria, not features. The five that determine fit at small scale are time to first review (can you launch in hours, not weeks), per-seat pricing math at your actual headcount, the reviewer experience from a tired employee’s side, the synthesis output a manager can actually use, and module breadth (every module you won’t use is a process that quietly starts running). Test each criterion by signing up and running a real review with a few colleagues before any buying decision.
Is a low-cost or no-cost tool enough for a 30-person team?
For your first one or two review rounds, a shared form and a written summary is usually enough. The limits show up with scale: no access control on sensitive feedback, manual chasing of responses, and synthesis time that grows with every person reviewed. The point to evaluate a dedicated tool is when those limits are taking real hours every quarter, not when the form looks unprofessional.
What does employee feedback software actually cost for a small company?
Pricing in this category typically runs per employee per month, with the features most small teams want often living on a mid or top tier rather than the entry plan. Multiply the relevant plan by your full headcount and twelve months and judge whether that buys you something a manual process doesn’t. Check each vendor’s pricing page directly; the published numbers move, and SMB-targeted vendors price differently from enterprise platforms.
When should a small company switch from spreadsheets to dedicated feedback software?
The switch point is synthesis time, not headcount. Running a review for one or two people on a shared form is an afternoon. Running it for eight or more people, twice a year, while collecting, theming, and writing summaries by hand becomes days of work per round. When the synthesis hours start cutting into the work you’re actually supposed to be doing, a focused tool starts paying for itself.
Dmytro Shtapauk
Practical tips and experience from top-notch experts
