Should B2B Software Serve Users or Their Managers? Pipedrive's Salesperson-First Bet
Short answer: Prioritise the daily user when their repeated use creates the data, outcome or compliance evidence the manager buys. Win the user's core workflow first, then give the manager enough visibility to approve, pay and renew. Start with management instead when adoption can be mandated, the buyer receives value without frequent user input, or regulation requires central control. Measure both user success and buyer success separately.
Many B2B products have at least three customers hiding inside one account: the person using the product, the manager assessing performance and the buyer controlling budget. Their incentives overlap less than a feature list suggests.
A manager may want complete reporting. A salesperson may see every required field as time taken away from selling. Software that pleases the buyer during a demonstration can therefore fail after purchase because the people creating its data avoid it.
Pipedrive built from the salesperson's point of view
Pipedrive says its story began in an Estonian garage in 2010. Its company history describes the founders as salespeople who wanted a CRM built by and for salespeople, centred on an accessible visual sales process.
Co-founder Timo Rein stated the contrast more sharply in a 2017 interview: most CRM software was designed to control salespeople, while Pipedrive was intended to help them. The product's visual pipeline put the seller's next actions and deal movement near the centre.
That choice did not make managers irrelevant. If salespeople maintain a useful pipeline, managers receive better visibility. The strategic bet was about sequence: create daily value for the person whose behaviour generates the management information.
Pipedrive's eventual scale does not prove a user-first strategy is always superior. Security software, payroll controls and statutory reporting may create value centrally even when employees would not voluntarily adopt them. The case is most useful when manager value depends on accurate, repeated user activity.
My view is that early B2B software should default to the daily user's success, even when the manager signs the contract. A buyer can force a login. They cannot force honest, timely use indefinitely without creating another management problem.
Use the User-Buyer Value Bridge
The User-Buyer Value Bridge traces one recurring user action through to the result the economic buyer funds.
| Bridge point | User evidence | Buyer evidence | Failure signal | |---|---|---|---| | Trigger | A frequent task already occurs | The task matters to a funded objective | Rare or optional workflow | | User gain | Less effort, better outcome or fewer errors | Staff capacity or quality improves | Data entry with no immediate return | | Repeated action | Suitable users return without chasing | Coverage becomes representative | Mandated logins, missing records | | Organisational signal | Activity creates reliable shared data | Manager can decide or forecast better | Attractive dashboard built on stale input | | Economic result | User completes more valuable work | Revenue, cost, risk or time improves | Usage rises without business effect | | Renewal | Users resist losing the workflow | Buyer can defend the spend | One side wants cancellation |
Your product needs both sides of the bridge. User delight with no organisational value creates a difficult expense. Executive reporting with no credible input creates a dashboard theatre business.
Identify the person who creates the product's value
Ask whose repeated behaviour makes the promised outcome possible. For a CRM, sellers update opportunities. For expense software, employees submit records. For security monitoring, automated systems may create most of the data while administrators act only on exceptions.
Observe the current workflow. Do not begin by asking managers which dashboard they want. Watch five to ten users complete the job without your product, time the steps and identify the cost they personally experience.
Then ask managers which downstream decision depends on that work. A forecast, allocation, audit or coaching conversation should change when the underlying activity improves. If the manager cannot name a decision, reporting may be a sales feature rather than a valuable outcome.
Test the user promise before adding reporting depth
Give a small team a complete user workflow and the minimum buyer control required for a safe pilot. Define activation as a completed job, not an account created.
For sales software, activation might require adding a real opportunity, assigning a next action and moving it after customer contact. Track how many suitable users complete that sequence without founder help, how long it takes and whether they repeat it the next week.
Only then assess reporting. Does the manager receive information that is more current or accurate than their spreadsheet, meeting or existing system? More charts are not more value.
Avoid letting one executive customer turn the product into a bespoke command centre. Label every requested feature by who benefits, how often it is used and which user behaviour supplies it. If a report requires five extra fields per deal, calculate the adoption cost.
Worked example: RouteRep chooses its first CRM buyer
RouteRep is a hypothetical UK CRM for small field-sales teams. A regional distributor has 30 representatives and two managers. The managers request 18 reports and are prepared to buy 30 seats at £30 a month. In user interviews, representatives care about logging a visit from a phone in under 45 seconds and seeing the next action.
RouteRep tests two comparable teams for eight weeks.
| Measure | Manager-first version | User-first version | |---|---:|---:| | Contracted seats | 30 | 30 | | Weekly active representatives | 12 | 26 | | Complete opportunities after eight weeks | 34% | 82% | | Monthly seat revenue | 30 x £30 = £900 | 30 x £24 = £720 | | Direct service cost | 30 x £5 = £150 | 30 x £5 = £150 | | Monthly onboarding and support | 18 hours x £30 = £540 | 6 hours x £30 = £180 | | Monthly contribution during pilot | £900 - £150 - £540 = £210 | £720 - £150 - £180 = £390 |
The manager-first contract has 25% more revenue but 46% less contribution during the pilot. More importantly, two-thirds of opportunities lack enough activity for the reports to be trusted. The user-first version produces a smaller dashboard with much better coverage.
RouteRep should not ignore managers. It should show the three decisions supported by reliable data: opportunities with no next action, stage ageing and forecast range. The other 15 reports wait until repeated buyer evidence justifies their effect on user work.
Suppose user-first adoption remains 26 representatives and the distributor renews for 12 months. Annual contribution before shared overhead is £390 x 12, or £4,680. If adding eight requested fields reduces weekly active use to 18 and raises support to £360 a month, contribution falls to £210, while report credibility also weakens. Feature volume has destroyed both sides of the bridge.
Sell to the buyer without misrepresenting the user
A user-first product still needs a commercial sale. Explain the causal chain: representatives complete a faster workflow, records become current, and managers make a specific decision with better coverage. Demonstrate the user action before the dashboard.
Include users in pilot selection and review. A manager's claim that the team “will use it” is not evidence. Neither is one enthusiastic champion. Track suitable users invited, activated, repeating and completing the critical records.
Define administrative rights, data ownership, monitoring and privacy plainly. Employee monitoring and data protection requirements vary by country and use. Obtain qualified local legal advice where the product affects employment decisions, sensitive data or regulated records.
Know when manager-first is correct
Start from the manager or central operator when the value does not depend on voluntary repeated use by many employees. Examples include automated infrastructure monitoring, central purchasing controls and payroll administration.
Manager-first can also be appropriate when the buyer carries a material compliance duty and must set the workflow. Even then, reduce user burden. Mandates create initial use but poor design still produces errors, workarounds and support cost.
Compare the two routes directly:
| Condition | User-first | Manager-first | |---|---|---| | Value source | Frequent frontline action | Central decision or automation | | Adoption | Must be earned repeatedly | Can be configured or mandated | | Early proof | Time saved and outcome completed | Risk, cost or control improved | | Main danger | Popular tool with no budget | Paid shelfware and bad data |
The choice is not ideological. It follows the mechanism of value creation.
Reach a decision in ten weeks
Weeks one and two: map the user action, manager decision and budget owner. Observe real work and identify where value crosses between them.
Weeks three to eight: run one narrow team pilot. Hold the product scope stable and track activation, repeated workflow completion, data coverage, support, buyer decisions and contribution.
Weeks nine and ten: interview users who adopted, avoided and abandoned the workflow, then review the buyer's actual decisions. Prioritise the side whose success causes the other side's value. If no bridge appears, change the segment or problem before adding more features.
Related guides
Frequently asked questions
Is the user always the customer in B2B software?
No. The user operates the product, while an economic buyer may approve the spend and an administrator may control access. Treat each as a customer of a different outcome. Map who experiences the problem, who creates the data, who receives the organisational result and who can stop renewal. The product must connect them. Calling only the buyer “the customer” hides adoption risk; calling only the user “the customer” hides budget and governance. Interview all material roles and keep their evidence separate.
What if managers love the demo but employees avoid the product?
Treat it as a failed value bridge, not a training problem by default. Observe employees completing the workflow and identify whether the product adds time, duplicates another system or exposes them without helping them. Remove fields and steps that do not support a named decision. Then retest voluntary repeated use within the authorised pilot. Management can require compliance, but persistent avoidance produces incomplete data and costly enforcement. Do not use executive enthusiasm to report adoption until suitable users repeatedly complete the core job.
Should users be involved in the buying process?
Yes, when their repeated behaviour determines success. Include representative users in workflow observation, pilot design and the renewal review, while keeping commercial authority clear. Avoid selecting only the most enthusiastic employee. Include sceptical and average users who face the normal workload. Their role is not to vote on every feature. It is to show whether the product makes the required job easier or more successful. If buyer confidentiality prevents user involvement before purchase, make a time-boxed adoption pilot a condition of expansion.
How much reporting should the first version include?
Include only the reporting needed to prove the buyer's primary decision and to operate the pilot safely. For a sales product, that may be stage value, ageing and missing next actions rather than a library of 40 dashboards. Each report should name its source fields, user effort and action taken by the manager. If a report is admired but never changes a decision, remove it. Expand after data coverage is reliable and repeated buyer behaviour shows a real need, not because competitors list more charts.
Can a top-down sale still produce bottom-up adoption?
Yes, if the contract funds access while the product earns repeated user value. Start with a limited team, define the user outcome and let expansion depend on activation and retention rather than seats purchased. Give managers honest adoption reporting without turning every interaction into surveillance. A named internal champion can remove process barriers, but cannot substitute for useful software. Price the support required to cross from signed contract to live workflow, because a large top-down sale can be unprofitable during an extended rollout.
When should I target managers first?
Target managers first when they directly operate the product, when automation creates value without broad employee behaviour, or when central risk and compliance control is the primary paid outcome. Validate that they use the output for a repeated decision and that deployment does not impose hidden work on others. Examples may include infrastructure alerts, purchasing approval and statutory administration. Employment, privacy and sector rules can affect monitoring and control, so obtain qualified local advice. Manager authority helps adoption, but it does not prove continuing value.
Comments (0)