· Valenx Press · 10 min read
Review: Manager Tools 1on1 Software for Remote Teams – Does It Beat a Simple Template?
TL;DR
Manager Tools 1on1 software automates what a disciplined manager already does with a Notion template and calendar reminders. The platform earns its $15-25/user/month only when leadership culture is already broken enough that managers skip one-on-ones entirely. For remote teams under 50 people, a structured template plus Slackbot nudges outperforms the software on adoption speed, cost, and signal quality. For teams scaling past 150 with layered management, the analytics layer and manager coaching prompts justify the switch. The judgment: buy the tool to fix a system, never to create one.
Who This Is For
You are a Director of Engineering or Head of Product at a Series B-C company with 40-120 remote employees. You have already tried running 1on1s. Some managers on your team do them religiously; others cancel three in a row and claim “nothing was pressing.” You are considering Manager Tools software because you read their podcast or book, or because another VP mentioned it. You are comparing it against building something lightweight in Notion or buying a People Ops platform like Lattice that bundles 1on1s with reviews. You do not have a dedicated People Analytics hire. You need a verdict in one week, not a three-month evaluation.
The problem is not your template. It is whether your managers recognize a 1on1 as a judgment signal, not a status update.
What Does Manager Tools 1on1 Software Actually Do?
Manager Tools 1on1 software enforces a specific cadence (weekly or biweekly), a fixed structure (10-10-10 minutes: their agenda, your agenda, joint problem-solving), and a shared note repository. For remote teams, it adds video integration, async prep prompts, and manager analytics showing completion rates, topic patterns, and employee sentiment trends.
In a Q2 debrief I sat on, a hiring manager for a VP of People role at a $200M ARR SaaS company described her stack. She had piloted Manager Tools for six months, then ripped it out. The reason was not feature deficiency. Her managers were completing 1on1s at 94% on the platform, but her skip-levels revealed employees felt “processed, not heard.” The software had become theater. Managers checked boxes. The 10-10-10 structure became a script they read, not a conversation they shaped.
Counter-intuitive insight one: completion rate is a vanity metric for 1on1 software. The signal you want is whether the employee raises the same topic twice without resolution. Manager Tools does not flag this well. A simple template with a “follow-up tracker” column does.
The platform’s actual value is constraint, not content. It forces the calendar block, the prep notification, the shared doc. For remote teams across time zones, this matters more than you think. A San Francisco manager with Bangalore direct reports cannot rely on hallway check-ins. The software becomes the infrastructure. But infrastructure is different from insight.
The judgment: if your managers already run good 1on1s, the software adds friction. If they do not run them at all, the software enforces a floor. The error is buying it for teams in the middle—those with inconsistent practice who need coaching, not tooling.
📖 Related: Self-Review Examples for Amazon PM Promotion: Forte Writing Tips
How Does It Compare to a Simple Template for Remote Teams?
I have seen the template approach work twice, fail twice. The difference was never the template. It was whether someone with authority reviewed it monthly.
At a 60-person fintech, the CEO used a shared Google Doc with five prompts: wins, blockers, career, feedback for me, next week’s priority. He reviewed all 12 manager-employee pairs monthly, in 30 minutes. Completion was 100% for 14 months. The template worked because the review created accountability. Manager Tools would have cost $1,080/month for equivalent headcount and added no value he did not already extract.
At a 200-person edtech, the People team built a beautiful Notion system with 20 templates. Usage cratered after 60 days. Why? No one believed anyone read the notes. Managers copied last week’s entry. The tool became invisible work.
The “simple template” wins when there is a visible reader. Manager Tools wins when the organization is too large for that visibility and you need automated signals.
Specific comparison for remote context:
- Onboarding speed: Template, 1 day. Manager Tools, 2-3 weeks including SSO setup and manager training.
- Cost at 50 users: Template, $0-15/month (Notion Pro). Manager Tools, $750-1,250/month.
- Employee perception (anecdotal from three debrief sources): Template feels personal if manager writes in their own voice; software feels institutional regardless of manager input.
- Manager time per 1on1 prep: Template, 5 minutes. Manager Tools, 8-12 minutes due to interface navigation and required fields.
- Cross-time-zone reliability: Manager Tools wins. The notification system and async prep function when live overlap is minimal.
Counter-intuitive insight two: remote teams need 1on1 infrastructure more than in-office teams, but they need it to feel less structured, not more. The software’s rigidity signals distance. The template’s blankness signals trust—if the manager fills it with substance.
What Does It Cost and Is the ROI There?
Manager Tools pricing is not public, which is itself a signal. Through three procurement conversations I am aware of, the range landed at $15-25 per user per month for teams under 100, with annual contracts and minimums that effectively require 20+ seats. For comparison, Lattice bundles 1on1s with performance reviews at $11-14 per user per month. BambooHR’s performance add-on runs $4.25-6.90 per user per month but the 1on1 functionality is weaker.
ROI calculation must exclude completion rate. The real return is in retention of high-performers who leave because they feel unmanaged. Conservative estimate: replacing a senior engineer in a remote role costs $75,000-150,000 in recruiting, onboarding, and lost productivity. If the software prevents one departure per year in a 50-person team, it pays for itself 3-6x.
But the same math applies to a template with CEO review. The software does not uniquely earn the ROI. What it does is scale the oversight mechanism without requiring executive time.
Counter-intuitive insight three: the ROI of 1on1 software is highest not for the managers who use it, but for the executives who no longer need to police them. This is an organizational psychology principle called “substitution of surveillance.” The software becomes the watcher, freeing up leadership attention. The question is whether you want that substitution or whether leader attention itself was the valuable ingredient.
📖 Related: Princeton students breaking into Notion PM career path and interview prep
When Should Remote Teams Choose Software Over a Template?
Choose software when three conditions align: (1) you have more than 8 managers, making manual oversight impractical; (2) at least one manager has demonstrated they will game or skip 1on1s without structural enforcement; (3) you have someone who will look at the analytics dashboard weekly and act on it.
I have seen teams hit condition one but not three. They buy the software, celebrate the dashboard, and never open it. The spend becomes organizational virtue signaling: “we invest in manager development” without development occurring.
Scene from a hiring committee debate, 2022: The candidate was a Director of People from a fully remote Series C company. She had implemented Manager Tools with 85% adoption. The HM pushed back hard in debrief: “She described running reports. I asked what she changed based on them. She couldn’t name one intervention.” We passed. The software had become her job’s output, not a means to an end.
The template is sufficient when: you have under 5 managers, all known to you personally; your culture already values 1on1s as sacred time; you can afford to review notes or have skip-level conversations that surface gaps.
The transition moment usually arrives between 80 and 120 employees. Below that, the overhead of software procurement, security review, and change management exceeds the benefits. Above that, the visibility problem becomes acute.
Preparation Checklist
Before evaluating any 1on1 system for your remote team, work through this sequence:
- Audit your current state: randomly sample 10% of manager-employee pairs. Ask employees whether their last 1on1 felt useful, not whether it happened. The gap between occurrence and utility is your real problem.
- Define the single intervention. If you could change one thing about your current 1on1s, what would it be? Software that solves everything solves nothing. Be specific: “managers don’t prepare,” “employees don’t raise real blockers,” “no follow-through on commitments.”
- Run a 30-day template trial with one team. Do not build the perfect system. Build a functional one and add a “what changed from last time” column. The constraint forces substance.
- Assign an owner with teeth. Someone must review outputs and have authority to enforce consequences. Without this, neither software nor template works.
- Work through a structured preparation system (the PM Interview Playbook covers remote team diagnostics with real debrief examples of when tooling decisions succeeded or failed based on org size and manager maturity). Use it to benchmark your team’s readiness against cases where software accelerated or stalled.
Mistakes to Avoid
BAD: Buying 1on1 software because your board asks about “investment in people infrastructure.” The purchase signals activity, not outcomes.
GOOD: Buying only after documenting three specific 1on1 failures in the past quarter that structure would have prevented. Example: “Employee raised compensation concern to peer, not manager, because no 1on1 occurred in 6 weeks.”
BAD: Measuring success by dashboard completion percentage. A manager who checks all boxes while employees feel unheard is worse than no system, because the data masks the dysfunction.
GOOD: Tracking “topic recurrence with resolution.” If an employee raises a blocker in week one and it is still present in week three without escalation, that is the signal. Build manual tracking if the software does not surface it.
BAD: Rolling out to all managers simultaneously without a pilot. Remote teams have enough change fatigue. A failed tooling change damages manager trust in People Ops for 12-18 months.
GOOD: Pilot with 2-3 managers who span the range: your best, your average, and your skeptic. Their honest feedback, not the vendor’s references, predicts your outcome.
FAQ
Why do remote teams specifically struggle with 1on1 consistency?
Remote teams lose the ambient accountability of physical presence. A manager in an office sees an employee, remembers to check in. Remote, the 1on1 is the only touchpoint. When it slips, the relationship hollows out over 4-6 weeks. The struggle is not scheduling. It is that remote managers conflate “we communicate in Slack” with “we have a structured conversation about your work.” They do not. Software cannot fix this confusion. Only manager training can. The tool enforces the habit; it does not create the understanding.
Is Manager Tools software better than bundled platforms like Lattice or 15Five?
Not better, more specialized. Manager Tools enforces a specific methodology derived from their podcast and coaching practice. Lattice is agnostic methodology, stronger on review cycles and goal alignment. 15Five leans toward continuous feedback and pulse surveys. Choose Manager Tools if you want to adopt their specific 1on1 doctrine. Choose a bundle if 1on1s are one of several People processes you are trying to systematize. The judgment is not about feature parity. It is about whether you need a tool or a philosophy.
What is the first sign that a template is no longer enough and software is required?
The first sign is not scale. It is when you, as the leader, stop believing your own data. You have managers who swear 1on1s happen, but skip-level conversations reveal divergent realities. You cannot verify manually anymore. The template relies on trust; the software introduces verification. But introduce it only when the cost of verification—financial, time, political—is less than the cost of continued ambiguity. For most remote teams under 80 people, that threshold has not yet arrived.amazon.com/dp/B0GWWJQ2S3).