Key Takeaways
- B2B ecommerce is an integration project, not a website project. Budget 60% for ERP/integration work, 40% for frontend.
- Ask agencies which ERPs they’ve integrated with. Vague answers (“we use middleware”) signal inexperience.
- Demand a paid discovery phase. Fixed pricing without ERP assessment guarantees scope explosion.
- The trap question: “Can you name the developer who will build our NetSuite integration?”
Your ERP defines the risk profile of this project. Not your design preferences. Not your feature wishlist. Your ERP.
If you’re running NetSuite, SAP, Microsoft Dynamics, or Sage, the agency you hire needs direct experience with that system. Customer-specific pricing lives there. Inventory lives there. Order processing lives there. The ecommerce platform is a presentation layer on top of your ERP. An agency that doesn’t understand this will build a beautiful storefront that can’t connect to your business.
Most agencies learned ecommerce on D2C brands. They know Shopify themes and Klaviyo flows. They don’t know how to display contract pricing from an ERP or sync inventory from a WMS. When they take B2B projects, they apply D2C playbooks. The project runs 14 months instead of 6. The budget doubles. The integration never quite works.
The 60/40 Rule
Here’s the ratio that predicts B2B project success: 60% of effort on integration and data, 40% on frontend.
D2C agencies invert this. They spend weeks on homepage design while the ERP integration sits unstarted. Then they discover the hard part at month four, with no budget left to do it properly.
A properly scoped B2B project front-loads the integration work:
| Phase | D2C Agency Approach | B2B Agency Approach |
|---|---|---|
| Weeks 1-4 | Design exploration, wireframes | ERP assessment, data mapping, integration architecture |
| Weeks 5-12 | Build frontend, add integrations “later” | Build integration first, prove data flows |
| Weeks 13+ | Scramble on integration, blow timeline | Polish frontend on stable foundation |
[Diagram: D2C vs B2B Project Timeline Comparison – see visual spec below]
If an agency’s proposal leads with design and treats integration as a line item, they’re applying D2C thinking to your B2B problem.
Red Flags in the Sales Process
They don’t ask about your ERP first
The first substantive question from a B2B agency should be about your operational systems. What ERP are you running? How is it configured? What’s exposed through the API? Who administers it?
An agency that leads with “tell us about your brand” or “what’s your competitive landscape” is running a D2C discovery process. Design matters, but it comes after the operational foundation is understood.
They claim to integrate with “any” ERP
This sounds flexible. It means they haven’t done enough integrations to have real expertise. An experienced agency names specific systems: “We’ve done twelve NetSuite integrations and three SAP Business One projects.” They have opinions about which ERPs are easier to work with. They know the quirks.
“We use middleware that handles everything” is a red flag. Middleware doesn’t handle business logic. Middleware doesn’t know your pricing rules. Someone has to configure it, and that someone needs ERP expertise.
Technical gut-check: Ask if they prefer RESTlets or SOAP for NetSuite integrations. If they don’t know the difference, they aren’t NetSuite developers. A real integration team will explain when each approach makes sense and why they’d recommend one over the other for your use case.
They quote fixed price without ERP assessment
B2B projects have too many variables for confident fixed pricing after a single meeting. Either the agency is padding heavily, planning to deliver change orders, or underestimating the work.
Experienced B2B agencies structure engagements around uncertainty:
| Pricing Model | What It Signals |
|---|---|
| Paid discovery before build quote | They understand B2B complexity |
| T&M with budget range and checkpoints | Honest about unknowns |
| Firm fixed after one meeting | Setting up a painful conversation later |
They’ve never lost a project
Every agency that’s done real B2B work has had projects go wrong. Integration scope that exploded. ERP limitations that weren’t discovered until month three. Data quality issues that derailed timelines.
Ask them: “Tell me about a B2B project that went wrong and how you handled it.”
Listen for ownership. Did they blame the client’s ERP? Or did they explain what they learned and how they run projects differently now?
The Questions That Expose Depth
Use these questions to separate agencies that talk about B2B from agencies that do B2B.
“What percentage of your projects involve ERP integration?”
Below 50%: They’re a D2C shop taking occasional B2B work. Your project will be an exception to their normal practice.
Above 70%: B2B is their core business. Their processes, staffing, and instincts are tuned for this work.
“Which ERPs have you integrated with?”
Good answer: Names specific systems with project counts. “We’ve done NetSuite integrations for eight clients, mostly distributors running Advanced Inventory.”
Bad answer: “We can work with any system.” This means they’ll learn on your project.
“Can you name the developer who will build our integration?”
This is the trap question. It exposes whether they have dedicated integration expertise or whether they’re planning to figure it out.
A real B2B agency has integration specialists on staff. They can name them. They can describe their background. They might even bring them to a sales call.
An agency that hesitates or says “we’ll assign the right resource” is telling you they don’t have dedicated integration capability.
“Walk me through discovery for a B2B project”
D2C answer: Stakeholder interviews, competitive analysis, customer journey mapping, design exploration.
B2B answer: ERP assessment first. What system? What configuration? What APIs? Where does pricing come from? How do orders flow after placement? What’s documented and what’s tribal knowledge?
The focus on operational systems is the signature of genuine B2B experience.
Evaluating References
Ask for references with these characteristics:
- Projects with significant integration complexity (not just a product catalog)
- Businesses similar to yours (distribution, manufacturing, wholesale)
- Projects that had problems and got resolved
The reference who had a flawless experience is less useful than the reference who hit problems and came out satisfied.
Questions to ask:
- How did the agency handle the hard parts of your project?
- Were there scope surprises around integration? How did they respond?
- Would you hire them for a similar project again?
The Business Impact of Getting This Wrong
Choosing the wrong agency costs more than the failed project fee.
Timeline cost: A 14-month project instead of 6 months means 8 months of delayed revenue and continued manual order processing.
Opportunity cost: Your team spends a year managing a struggling project instead of running the business.
Trust cost: After a failed implementation, internal stakeholders become skeptical of the next attempt. Getting buy-in for round two is harder.
Technical debt: A half-working integration that “sort of” connects to your ERP becomes a maintenance burden for years.
The agency selection process deserves serious time. The questions in this article take maybe two hours across three agency conversations. That investment prevents a year of pain.
Making the Decision
The right B2B agency will do things that feel less accommodating during the sales process:
- They’ll push back on your timeline assumptions
- They’ll insist on paid discovery before committing to scope
- They’ll tell you uncomfortable things about your ERP’s limitations
- They’ll ask hard questions about your internal readiness
This pushback is the signal that they know what they’re doing. An agency that says yes to everything is either desperate for work or doesn’t understand what they’re agreeing to.
Find a partner who’s already learned the hard lessons on someone else’s projects.
The B2B Agency Red Flag Scorecard
Use this checklist during agency evaluations. Two or more red flags means keep looking.
| # | Red Flag | Check |
|---|---|---|
| 1 | They discuss design before asking about your ERP | ☐ |
| 2 | They claim to integrate with “any” system but can’t name specific ERPs they’ve worked with | ☐ |
| 3 | They offer firm fixed pricing without a paid discovery phase | ☐ |
| 4 | They can’t name the developer who will handle your integration | ☐ |
| 5 | They have no project failure stories (or blame clients for every failure) | ☐ |
Score:
- 0 red flags: Strong candidate
- 1 red flag: Proceed with caution, dig deeper
- 2+ red flags: Keep looking
Evaluating agencies for a B2B ecommerce project? Happy to be a sounding board on what you’re hearing.
B2B Ecommerce Agency Selection: Frequently Asked Questions
The primary differentiator is the “Ratio of Effort.” B2C agencies are storefront-first, focusing on conversion UI and aesthetic design. True B2B agencies are integration-first, prioritizing back-of-house operational logic like ERP data mapping, customer-specific contract pricing, and complex account hierarchies that reflect real-world business rules.
Projects fail when agencies treat integration as a “bolt-on” task at the end of the build. Because the ERP is the Source of Truth for pricing and inventory, any mismatch in data parity results in operational failure. High-performing B2B projects front-load this risk by defining integration architecture before a single design mockup is created.
An enterprise-grade B2B build typically takes 6 to 12 months. While the frontend can be built quickly, the majority of this timeline is dedicated to technical discovery, API rate-limit testing, and ensuring that order workflows (like PO numbers and manager approvals) sync perfectly with your specific ERP or WMS.
A genuine B2B discovery should feel more like a technical audit than a branding exercise. If an agency doesn’t ask for your API documentation, order flow diagrams, or a meeting with your ERP administrator within the first week, they likely lack the engineering depth required to handle B2B complexity.
The 60/40 Rule states that 60% of the project effort and budget should be allocated to integration, data architecture, and backend logic, while 40% goes to the frontend storefront. Agencies that invert this ratio often produce beautiful websites that fail to function as a viable business tool once they are connected to live data.