G2

Julian C.

Sales Operations & CRM Manager

Industrial Automation

Mid-Market (51-1000 emp.)

10/22/2026

Business partner of the seller or seller's competitor, not included in G2 scores.

"Flexible Workflow Builder That Streamlines Complex RFQ Bids and Sales Ops"

4/5

What do you like best about Worksection?

The standout feature for our sales ops team in Worksection is its flexible workflow builder paired with custom fields, which fits really well alongside our core CRM eSalesTrack. We don’t run lead scoring or opportunity forecasting inside it, but it’s where we orchestrate all the action items that sit outside our CRM pipeline. We build dedicated workspaces for large industrial RFQ bids, and the custom fields let us lock in critical details like part numbers, customer territory code, quote expiration date, and TCPA opt-in status right on every task. The drag-and-drop workflow canvas saves me roughly three hours each week, because I don’t have to rebuild approval sequences from scratch every time we kick off a new complex equipment bid.

Our sales cycle runs long, often stretching 90 to 180 days, with lots of handoffs between inside sales, field reps, engineering, and our estimating team. Before Worksection, reps relied on scattered calendar reminders and long email chains to track quote revisions and customer follow-ups. Now every quote task links directly to assigned stakeholders, with built-in due dates and automatic escalation alerts. If our estimator delays turning around a bill of materials for a heavy machinery quote, Worksection flags the overdue task and notifies me automatically. That visibility keeps our bid timelines from slipping without me having to ping every team member individually.

I also rely heavily on its granular member permission controls. We regularly invite outside manufacturer vendor reps into our bid workspaces to validate component lead times. I can set their role so they only view and comment on tasks relevant to their product line; they can’t peek at other active customer opportunities or our internal pricing notes. This keeps us aligned with CCPA and TCPA best practices, limiting exposure of our customer contact data only to parties that genuinely need it.

One unexpected benefit I stumbled on is the built-in time & cost tracking module. Our leadership wanted better visibility into how much labor we sink into each RFQ, not just the final deal value. Our field sales reps log their time spent on site surveys and discovery calls directly against bid tasks. The aggregated time data feeds our sales ops reports, so we can flag low-margin bids that soak up too much team time before we invest more resources. This was not what I originally set the tool up for, but it’s become a core part of our quarterly sales efficiency reviews.

The native API is another plus. We set up lightweight syncs to push completed task notes back into eSalesTrack, so our CRM opportunity records get updated with meeting summaries and revision logs without manual copy-paste work from our reps.

Suggestions: I’d love deeper native CRM connectors built specifically for platforms like eSalesTrack, instead of relying on custom API scripts. Right now our sync needs occasional maintenance when either platform pushes an update. Adding pre-built TCPA compliance field templates for opt-out tracking would also help us standardize our marketing consent records across all sales tasks. Mobile task editing can also feel clunky for our field sales team; improving offline mode would be a big win for reps working out at customer plant sites with spotty cell service. Review collected by and hosted on G2.com.

What do you dislike about Worksection?

My biggest frustration with Worksection is the narrow set of native CRM integrations, and it does not ship with a pre-built connector for our eSalesTrack platform. It only supports a small handful of mainstream CRM tools out of the box, so everything we sync has to run through custom API scripts I built myself. Every time either platform rolls out an update, the sync breaks unexpectedly. Last month, a backend API change wiped out three weeks of quote follow-up notes that should have pushed back into our CRM opportunity records. That forced our sales team to manually cross-check hundreds of tasks, costing us close to six hours of sales ops labor and creating gaps in our TCPA consent logging. It adds ongoing maintenance overhead that I didn’t anticipate when we rolled the platform out.

The guest permission model is another major gap for our workflow. We frequently bring in vendor contacts to review component lead times for our industrial equipment bids. Even when a guest is limited to one workspace, they can view every custom field value on every task inside that project. We store sensitive customer data like phone numbers, opt-in status, and territory assignment in those custom fields to stay compliant with CCPA and TCPA rules, and there is no toggle to hide individual custom fields from external guests. I cannot lock down pricing or consent metadata separately. Our workaround is creating completely isolated workspaces for every single vendor, which bloats our workspace list, makes reporting messy, and slows down my quarterly sales efficiency reviews. There is no task-level access restriction at all, so exposure risk for customer PII is always top of mind.

The reporting engine also falls short for sales operations analytics. We rely heavily on filtering bid tasks by territory, TCPA opt status, quote expiration date, and estimated deal value. The built-in report filters are rigid, and exported spreadsheets do not preserve my saved filter sets. I have to rebuild the filter criteria from scratch every time I pull a bid pipeline snapshot for leadership. There is also no scheduled report delivery; I cannot set it to auto-send our weekly RFQ status summary to sales managers. Every week I manually generate, format, and distribute that report, which eats into time I could spend refining our lead routing and nurture workflows.

The mobile experience is another consistent pain point for our field sales reps who visit manufacturing plant sites. There is no true offline mode. If they step into a facility with poor cellular coverage, they cannot pull up task details, log a site note, or update a follow-up status. Reps have to jot everything down in a separate notes app and circle back later once they get service, which often means delayed updates or missed follow-up deadlines.

Suggestions: First, add a pre-built native connector for niche sales CRM platforms such as eSalesTrack, with automatic webhook retry logic when syncs fail. Second, add granular custom-field visibility rules for guest users, so I can hide TCPA consent data, pricing, and PII from outside vendors while still letting them see their assigned task instructions. Third, expand the report builder with saved filter presets and scheduled email delivery for sales leadership. Finally, implement offline mobile support so our field reps can log updates without reliable cell service at customer sites. Review collected by and hosted on G2.com.

What problems is Worksection solving and how is that benefiting you?

Before rolling out Worksection, our sales coordination was messy and disjointed. Our core CRM eSalesTrack held lead and opportunity data, but all the supporting bid work, estimator handoffs, vendor component checks and follow-up notes lived in a mix of email threads, shared spreadsheets and personal calendar reminders. We struggled with disconnected bid workflows where sales, estimating and vendor stakeholders worked in silos, but now we can build dedicated workspaces for every RFQ and tie all quote tasks, approvals and supporting documentation together in one place, which has resulted in a roughly 50% drop in missed quote deadlines for our long-cycle industrial bids.

For our line of industrial equipment sales, a single RFQ can take months to close. We need input from inside sales, field reps, our estimating team, and multiple component suppliers. Before Worksection, if a field rep visited a factory site and collected new customer requirements, they would email notes to the estimator, copy the sales manager, and hope everyone saw it. It was common for revisions to get overlooked, or for a vendor lead-time update to never make it back into the opportunity record. Now when we open a workspace for a bid, I set up a standardized workflow with sequential tasks: site discovery, bill of materials build, vendor component validation, internal pricing review, and final quote release. Each task auto-assigns the right person and sets clear due dates. When a vendor updates lead times on a part, they comment directly on their assigned task, and every stakeholder gets notified instantly.

We also struggled to keep consistent track of TCPA and CCPA consent status alongside bid activities. Reps would store opt-in notes randomly in CRM free-text fields, making it hard to prove we followed compliance rules if we needed to pause outreach. Now we added mandatory custom fields inside every workspace task to log consent status, source of contact, and opt-out flags. Every time we schedule a follow-up call or SMS touch, the rep has to confirm the consent tag before moving the task forward. This standardization cut down the time I spend auditing our customer consent records for compliance reviews by about four hours each month.

One more pain point we fixed was our lack of visibility into how much labor each bid consumes. We struggled to measure the operational cost of our RFQs beyond the final deal value, but now our team logs time against each task in Worksection’s built-in time tracking, which has resulted in us identifying low-value bids that drain our estimating and sales bandwidth. Last quarter, we used that data to adjust our bid qualification rules, and we stopped chasing small, labor-heavy RFQs that rarely converted. That freed our estimating team to focus on larger, higher-margin opportunities.

We still keep our core pipeline, lead routing and forecasting inside eSalesTrack, using a custom API sync to push task notes back to opportunities. It’s not perfect, but it bridges the gap between our CRM and execution workflows.

Suggestions: I’d like native, out-of-the-box integration support for niche CRMs like eSalesTrack so I don’t need to maintain custom API scripts. Saved report templates with scheduled delivery would cut down my weekly admin work even more, and offline mobile access would be a huge upgrade for our field reps working at remote manufacturing sites with spotty cellular connectivity. Review collected by and hosted on G2.com.