Your 100-person company has no HR department. So why are you the one comparing performance review software at 9 p.m., trying to find a tool that won't become another login managers ignore? Your managers aren't the problem. A lot of review tools just feel built for companies with an HR ops team, a rollout plan, and a calendar full of training sessions. You have none of that. You have work to ship, people to support, and a review cycle that needs to happen without eating a week of everyone's time.
Below: three criteria for picking a tool (can you run a full cycle in a week, does it live where managers already are, does it collect feedback all year), the demo questions that expose how much admin you're buying, and the red flags to watch for when nobody owns HR ops.
Why a 100-Person Company With No HR Keeps Buying the Wrong Review Tool
At 100 people, reviews usually live in a spreadsheet, a shared doc, or a form nobody opens until the week they're due. The person nominally running them is a COO, an office manager, or a founder who already has a full-time job.
Then the cycle starts. Managers get a blank field and are asked to summarize six months of work they can't remember. What comes back is generic praise, vague concerns, and ratings that reflect the last six weeks, not the last six months. Writing performance reviews from memory is the problem, not lazy managers.
The comparison articles you find first are written for companies with someone whose whole job is running reviews. At 100 people with no HR function, that person doesn't exist. Their criteria aren't yours.
So ask which tool this team can actually run next quarter without hiring or training anyone, not which one has the most features.
Get it wrong and nobody logs in. The cycle gets cancelled or quietly slides back into a doc, and the second attempt is much harder to sell internally than the first.
Start With How Your Team Already Works, Not a Feature Checklist
Before you open a comparison table, write down three facts. Where do managers already talk all day? Who would actually run the review cycle? How many hours a week can that person give it? Be honest about what's realistic, most people in this role have a few hours a week at most, not a dedicated block.
Turn each fact into a constraint. No admin? Heavy setup is out. Managers never leave Slack or Teams? A new login is out. Nobody keeps notes? Tools that rely on memory are out.
Translate features into effort. Every extra feature has an owner, a setup cost, and a real chance of being ignored. If no one will own it, it is a liability you pay for.
Set your order of operations: can you run a real cycle fast, does it fit where people work, and does the draft come from feedback you already collected? Everything else is a tiebreaker.
Keep the shortlist to two or three tools. Score them against your constraints, not a generic table built for a bigger company. Start with review software your managers won't avoid using and that fit test.
Criterion 1: Can You Run a Full Review Cycle Within a Week?
Setup speed is the first thing to test.
Before you sit through a demo that opens on a polished dashboard, ask what has to happen before that dashboard is real. Importing people, mapping reporting lines, deciding who reviews whom, writing the questions: all of it is your job, and all of it takes time.
Get the timeline in writing
Ask how many days from purchase to the first review request going out, and which tasks sit with your team versus the vendor. From Setup to First Review Cycle in Days is a useful reference for what a realistic rollout looks like. If the answer is vague, treat that as the answer.
Test the admin load live, not on a slide
Count the clicks to launch a cycle, send reminders, and chase the last three managers who haven't submitted. Then ask about the messy reality: a manager change mid-cycle, a new hire starting two weeks before reviews are due. A tool that needs a clean org chart will fail at 100 people.
Ask whether the first cycle runs from an editable template or a blank question builder you design while doing your day job.
Set the target: first request out within a week of signing up. No project plan, no kickoff meeting, no consultant.
Criterion 2: Does It Live Where Managers Already Are?
Setup speed means nothing if nobody opens the thing. Count the tools your managers open every day. A platform that adds a login competes with their actual job, and the job wins.
Ask where a feedback request lands: an email inbox, Slack, Microsoft Teams, or a dashboard nobody visits. The right answer is the place managers already type all day. Interruption research shows context switching carries a real cost, and tools that pull people out of their flow get skipped.
Be straight about adoption. If a manager has to remember to log in, most won't, because nothing in their day reminds them the tool exists. A request that arrives inside Slack or Teams doesn't need remembering.
Check mobile. Managers here travel, sit between meetings, or work a shop floor; a desktop-only flow slides to the deadline.
Think about employees too. Peer feedback dies fast when it needs an account, a password reset, and a link buried in an old thread. Look for integrations that put the request where people already work.
That's why WorkStory runs feedback and review cycles natively inside Slack and Microsoft Teams instead of its own app. Worth testing in your trial, since it's positioning rather than proof. Apply the same test to every tool on your shortlist.
Criterion 3: Does It Collect Feedback All Year Instead of Testing Memory in December?
Because memory is short, the tool needs to collect input during the year, not just at review time. In practice, a review written in one sitting tends to reflect whatever's freshest, not the full year.
So ask how the tool gathers input during the year: short prompts after a project ships, quick peer notes, 1:1 takeaways, recognition messages. Small and frequent beats one long form every twelve months.
Then ask what the draft is built from. The best answer: it assembles feedback people already gave and hands the manager something to edit, not a blank page and a thesaurus.
Confirm that feedback is visible where it's useful. If it only surfaces at review time, managers can't see what was said about someone before they rate them, and the whole thing still feels like guesswork.
Verify you can run a cycle without launching a separate feedback collection project in November. If you have to chase input yourself, the tool hasn't solved the problem you bought it for.
WorkStory's stated approach is that AI turns feedback collected through the year into review drafts. That's positioning, so test it with your own team: does the first draft read like your team, or like a template?
The Demo Questions That Show How Much Admin You Are Buying
Your shortlist is set. The demo is where you find out what running this actually costs you, in hours and in names. Ask them in order, and see each answer live.
- Show me the first review cycle, start to finish, in a live account. No slides, no pre-recorded walkthrough, no account stuffed with fake feedback.
- Who on our side does work before the first request goes out, and how many hours is that? Names and numbers, not roles. "The admin" is not a name.
- How do reminders work when three managers have not submitted? Automatic, or does someone on your team send them by hand, one at a time?
- Where does a feedback request appear for a manager who never opens your app? Show me, in the product, on a phone.
- What does a review look like before the manager edits it, and where did that text come from? This is the most useful screen in any demo.
- What happens if we sign for a year and want out in month three? What do we keep, in what format, and what happens to the feedback people gave?
- How do you handle a manager change and a new hire who starts mid-cycle? At 100 people, that is every quarter.
- Which parts do we configure, and which arrive ready to use? The ratio tells you more about setup cost than any pricing page.
Setup cost is the real price. The tool that arrives mostly ready is the one your team can run next quarter.
Red Flags to Watch When Nobody Owns HR Ops
You just asked a vendor to walk you through a full cycle live. Now watch for the traps that show up after you sign.
The longest feature list wins, at 100 people, unused features are pure cost.
It tops the comparison articles. Those rankings are written for companies with a dedicated people team and someone who owns the process. You have neither.
No named admin. If the answer to "who runs this?" is "we'll figure it out later," the cycle stalls at the first reminder email.
No explanation for managers. One short, honest message about why reviews are changing and what's expected keeps cycle one from feeling like homework handed down from nowhere.
A year-long contract before a single cycle. You would be buying a process you have not tested with the people who actually have to use it.
Treating the template as the hard part. Editable questions matter far less than whether feedback flows in during the year.
A process built on memory. If the tool only works when people can recall six months of work, you bought a nicer version of the problem you started with.
Where WorkStory Fits in This Shortlist
If your shortlist survived those red flags, here is where WorkStory fits. It targets SMBs with 50 to 300 employees, meaning companies with no dedicated HR ops function and no spare headcount for setup. It runs natively in Slack and Teams (covered in Criterion 2), and the AI-draft approach described in Criterion 3 means managers edit rather than write from scratch.
Treat those as positioning claims, not proof. If the goal is to give team members faster, clearer feedback on their actual work, the only honest test is a trial with your own team and your own feedback, not a sales deck.
Practical move: run one cycle with a handful of willing managers before rolling it out to all 100 people.
What to Do This Week
Set a decision date and work backward. Five things, in order:
- Write down three constraints: who administers reviews (name the person, not the role), where managers already work, and whether feedback gets collected between cycles.
- Shortlist two or three tools and score them against those constraints only. Ignore the feature grid. A tool that wins on features nobody will configure loses on the one metric that matters: whether the cycle actually ships.
- In every demo, ask to see a full cycle run live, not a slide, not a pre-loaded account.
- Name the admin before you sign, and get the setup timeline in writing with names attached to each task.
- Run one cycle with a small group of managers, then decide. The tool worth paying for needs no new app, launches fast, and drafts reviews from real feedback.
Conclusion
A 100-person company with no HR needs a review cycle that ships in under a week, lives where managers already work, and collects feedback all year instead of testing memory in December. Name those constraints first; the tool matters less.
Keep going: the seven requirements to write down before you demo turn this into a one-page brief, and Slack feedback or a separate HR app shows where chat-native cycles stop being enough. For the tool side, see performance review software and how to choose performance management software your team will actually use. Already shortlisting? Compare WorkStory vs Lattice and WorkStory vs 15Five.
Want to see a full review cycle run inside Slack or Teams with your own team? Book a demo.
FAQ
How do you choose performance review software with no HR team?
Judge it on how little admin it asks for: can it run a full cycle in about a week, does it live in the tools managers already use, and does it collect feedback all year. A tool that needs a dedicated owner will stall without HR ops.
What should a 100-person company look for in review software?
Fast setup, no second login for managers or employees, automatic reminders, and a review draft built from feedback collected during the year instead of a blank form.
Can you run performance reviews without an HR department?
Yes, if the software handles scheduling, reminders and drafting so a founder or ops lead is not chasing people by hand. WorkStory runs feedback and review cycles inside Slack and Microsoft Teams for this reason.
