Verified User in Information Services
UI
Mid-Market (51-1000 emp.)
"Focused Sales Execution with Flexible Automation, Reporting, and a Clean Mobile App"
4.5/5
What do you like best about Pipeline CRM?

I value how Pipeline CRM keeps its core experience focused on sales execution instead of overloading users with unrelated modules. I’m Lukas Ogod, a Business Technology Specialist at Big Sky Digital Partners, an information services firm with 51–200 team members. Much of my work revolves around standing up new business tools, tuning permissions, and validating whether a platform fits our internal operational rhythm. Last quarter, we rolled out a bloated, multi-feature CRM that forced sales reps to click through seven separate screens just to log a discovery call. One of our senior reps delayed updating a high-value managed services deal for three days because the workflow was so cumbersome; leadership missed the shift in timeline and shared an inaccurate revenue forecast with our stakeholders. After switching to Pipeline CRM, that same rep can log activity, adjust the deal stage and set a follow-up task within a handful of clicks. The automation builder is straightforward for someone like me to configure, so I can spin up lead routing, follow-up reminders and stage-change notifications without chasing outside support.

I also appreciate how flexible the custom fields and reporting engine are for our information services sales cycles. Our deals often include custom scoping details, SLA notes and technical requirement tags that don’t fit generic CRM templates. I recently imported a batch of 36 inbound leads from our partner referral program and built a custom field set to track infrastructure requirement tiers. I then created a dashboard that groups opportunities by technical complexity, so our pre-sales engineering team can prioritize the resource-heavy deals early. It doesn’t force us into a rigid sales template; I can reshape the pipeline stages, add conditional fields and tweak dashboard views to match how our sales team actually moves opportunities forward. That hands-on configurability matters a lot because we don’t have a dedicated CRM admin team, so all the iterative setup work lands on my plate.

The clean mobile experience is another practical win for our field and remote sales staff. Many of our reps meet with IT stakeholders on-site and need to pull up deal context or log notes right after conversations. Back in spring, one rep finished an on-site assessment and intended to update the opportunity before driving back, but our old CRM’s mobile layout was so broken that he put it off until the next workday. In that window, the prospect sent an email changing their budget, and the update never got tied to the record. Our account manager followed up with the original pricing and created confusion. Pipeline CRM’s mobile app mirrors the core web workflow well, so updates happen in real time. This keeps the pipeline data fresh between my weekly report pulls, and cuts down on the pile of catch-up data entry that used to hit my inbox every Friday. Overall, it strikes a good balance: powerful enough to automate our key sales handoffs, but simple enough to encourage consistent adoption across the team. Review collected by and hosted on G2.com.

What do you dislike about Pipeline CRM?

One major constraint I keep running into with Pipeline CRM is weak native automation logic for layered, conditional triggers that bridge sales deals and our service intake workflow. I’m Lukas Ogod, a Business Technology Specialist at Big Sky Digital Partners, an information services firm with 51–200 team members. Not long ago, I attempted to build a rule meant to notify our pre-sales engineering group only once a deal hit technical review and carried a specific infrastructure scope tag. The platform’s native automation builder could not combine both filters properly. Alerts began firing for every opportunity entering that stage, no matter the service category, and the engineering team grew desensitized to the notifications. I had to build a workaround on an external automation platform, adding extra ongoing upkeep I was hoping to skip entirely.

Linked record handling during CSV imports is another area that creates consistent operational friction. Last month, I processed a curated batch of 41 partner-referred leads that already mapped to existing company accounts. After the upload completed, many of those lookup relationships failed quietly. There was no itemized error log pointing out which leads failed to attach to their parent accounts. A sales rep flagged the issue when they opened a lead and found it orphaned from its company profile, and I spent nearly two hours manually reconnecting the records. This bottleneck slows our lead onboarding cadence whenever we receive large enriched datasets from our partner network.

Forecast audit logging falls short of the traceability our internal planning process requires. Our leadership frequently asks me to trace edits to close dates or deal values and capture the rationale behind those adjustments. Earlier this quarter, two separate sales managers updated the projected close date on the same managed services opportunity. The activity log only noted a generic record update, without specifying which field changed and without a required field for justification. When our finance team audited the pipeline forecast, we could not verify which revision was authoritative, forcing me to follow up with both managers to untangle the conflicting updates. Review collected by and hosted on G2.com.

See what 914 reviewers think of Pipeline CRM

4.3 out of 5 · Verified reviews from real users

Read all reviews