Contact Me
Beyond the Portal
Practical Tactics to Build B2B Experiences Your Customers Will Actually Use

RudyAbitbol.com
RudyAbitbol.com
B2B eCommerce Expert · Miami | Montreal
Consulting
B2B eCommerce Leader.
18+ years helping Brands, Manufacturers & Distributors launch and scale.
Speaking
Featured in Forbes
Chicago | Atlanta | Miami | Paris
Master B2B Nexus | B2B eCommerce Association Ambassador
60+ eCommerce + PIM
Sonepar
Goodyear
Kate Spade
Coach
Ruggable

Your customer doesn't gain anything by switching
— unless you give them something the phone, the rep, and EDI can't.
Why Portals Get Bypassed
The five reasons, in the order I see them:
01
Sales team resistance — reps fight the channel
02
EDI is already there — for high-volume accounts, the door is closed
03
Customer doesn't know it exists — no one told them
04
Customer doesn't want to take responsibility — pricing errors, wrong SKUs, returns
05
Site is slow, badly designed, or missing SKUs — the table-stakes failure
If your adoption is stuck, it's one of these five. Not 'we need more AI.'
B2B is not B2C with a pricelist.
B2B self-serve is not just 'wholesale.'
It's hierarchies, permissions, contracts, blanket orders, approvals, credit limits, PunchOut, EDI, projects, payment terms.
If your portal is 'wholesale pricing on a B2C theme,' you've built a B2C site for buyers who weren't asking for one.
  • Personalization is important — you already know what's on their contract
  • Search matters less than catalog completeness
  • The job is removing reasons to not switch
Stop optimizing the homepage. Audit the friction.
The Playbook
9 plays. We'll go fast.
Match the portal to the buying process
Project-level commerce (the deepest version of #1)
Kill the channel switch tax
Sell it internally before externally
Get out of the building
Make search work
Role-based by default
Make the portal smarter than the rep
Get the integration order right
Play 1
Match the Portal to the Buying Process
HuskyBoutique.com example.
  • 4 customer experiences, each tuned to a different buyer segment
  • Checkout: from 3 steps to 1
  • Not because we 'simplified UX' — because we matched what the buyer actually does
Optimization is in the small things.
Audit every field. Each one is either earning its place or costing you adoption.
If your checkout has more steps than the phone call, you've already lost.
Play 2
Project-Level Commerce
The deepest version of 'match the buying process.'
A construction or industrial buyer doesn't order for a company. They order for a job site.
Site address
Project budget
Billing reconciliation
Delivery to the right location
If your portal forces them to order at the company level, they'll call the rep.
Applies to: construction material distributors, electrical and plumbing distributors, industrial supply, rental and equipment suppliers — anyone whose buyers manage multiple active projects.
Play 2 — In Practice
For Distributors
What this looks like inside a Job portal:
  • Buyer selects the job site before adding products to cart
  • Every order tagged to a project — no manual sorting after the fact
  • Order history filtered by job, not just by date
  • Delivery addresses tied to job sites, not company accounts
  • Spend by site, real-time
Can your portal do project-level, or only company-level?
If it can't, your customers will keep calling the rep.
SiteJob - A Private Shopify PlusApp I built for distributors
Play 3
Kill the Channel Switch Tax
Every step the phone doesn't have:
Remove
  • Login walls before pricing
  • Captcha
  • 'Confirm address'
  • Re-typing a PO number
  • Pricing visible only after add-to-cart
Put back — the phone can't do this:
  • Order status without a phone call
  • Expected delivery date in real time
  • Named rep on the account
  • One-click reorder from invoice
  • Blanket order burn-down
The phone gives you 'I'll check and call you back.' The portal should give you the answer in one click.
Play 4
Sell It Internally Before Externally
Two internal teams kill or save portal adoption: sales and customer support.
Sales Team
  • Comp alignment — self-serve orders count toward rep quotas
  • Name the rep in the portal — the customer still belongs to them
  • Train reps to demo the portal cold
Customer Support / Call Center
  • Weekly meeting with the call center. Co-build features with the people answering the calls.
  • 3-email rule for technical support. If it takes more than 3 emails, switch to a live meeting. Always.
Reps and CSRs are the two adoption levers nobody tracks.
Play 5
Get Out of the Building
Adoption is field work, not a UX project.
Branch BBQ + Digital Sessions
Train customers on their turf, with their rep beside them
eCommerce Advisors
Dedicated team that visited branches and job sites
Local ERP Integration
Embedded inside the management platform Quebec electricians already used every day
Meet customers where they already work. The portal comes to them.
You'll learn more in a day at a client than in a week brainstorming with your team.
Play 6
Make Search Work
Zero-result queries are your roadmap.
  • What they searched and didn't find = SKUs to add or rename
  • Top searches on items with no images = your highest-leverage merchandising
  • Failed searches by repeat customers = a phone call you're about to lose
What B2B search actually needs:
Manufacturer part numbers + competitor cross-references
Synonym dictionaries (the way your customers actually talk)
Technical attributes (voltage, gauge, thread, finish)
Application context
Most distributors have this data. Almost no one looks at it weekly.
Everyone's Selling You GEO
There's a cottage industry telling you to optimize for AI. Add FAQs. Add schema. Get cited. All of that is fine. None of it is enough.

If everyone in your category follows the same GEO playbook, AI will describe all of you the same way.
Garbage in, Average out.
That's the GEO trap. You optimize to be found, and you get found — as one of fifteen interchangeable options.
People no longer visits sites.
Scan to run your GEO Audit Free · 90 seconds · See exactly how AI describes your business
Play 7
Role-Based by Default
A buyer, an AP clerk, a branch manager, and an end-user need different views.
Husky's 4-experience setup is the canonical example. Build for the role, not the company.
Play 8
Make the Portal Smarter Than the Rep
This is where the portal beats the phone.
The rep can't tell you in 5 seconds:
  • Your full purchase history across 18 months
  • Your blanket order burn-down
  • Your contract pricing on a SKU you've never bought
  • What you ordered for this job site last quarter
The portal can. And AI makes it scalable:
AI Chat
Fed by product docs + FAQ + resolved support tickets → deflects 30–40% of incoming volume
In-App Nudges
UserPilot-style guides buyers through the first 3 orders
Self-Training System
Every resolved ticket trains the system → next customer gets the answer in 5 seconds
This is your AI moment. Not 'AI everywhere.' Specifically: scalable support and contextual recall.
Play 9
Get the Integration Order Right
What's the ROI when integrating a new customer. Not all integrations drive adoption equally:
ERP integration → drives the biggest accounts (real-time pricing, stock, order status)
  1. Mobile App → drives field and branch buyers (Growth lever)
  1. PunchOut → privileged path for enterprise procurement
  1. EDI → last resort. Offer it when you've lost the fight to keep them in the portal.
EDI is not the sophisticated answer. It's the defensive one.
Play 10
What to Measure
Stop tracking 'portal sessions.' Track:
% of orders self-served
Repeat-buyer login rate
Support tickets deflected
Zero-result search rate
Sales rep portal-promoted orders (yes — track which reps are pushing it)
If you can't show movement on these in 90 days, the playbook isn't being run.
What's Next: Agentic Buyers
The portal itself is changing.
AI Agents
Ordering on behalf of buyers
API for Agents - Is your digital ecosystem ready?
The portal stops being a UI for humans and becomes an API for agents
Catalog Data = Shelf Space
If your PIM is messy and your product data is incomplete, you're invisible to the next generation of B2B buyers
The next adoption fight is GEO/AEO — getting your products surfaced in ChatGPT, Perplexity, and Copilot when buyers ask.
Action
Thursday Morning — Do Three Things
Pull your zero-result search log.
Read it. There's a roadmap in there.
Sit in your call center for an hour.
Listen for 'I just called instead.'
Ask one rep what they tell customers about the portal.
The answer will surprise you.
That's it. Don't buy a new platform. Run the plays.
One caveat: none of this works on a digital ecosystem you can't change. If your roadmap is gated by a partner / vendor's release cycle, the playbook stops here.
Want a copy of this presentation?
I write about this every week. Practical stuff, no hype.
DM me on LinkedIn