Evaluating a Nearshore Partner: 10 Criteria for Integration-Heavy Projects

If your project touches production, stock or order processing, most of the criteria used to compare web agencies stop being relevant. The quotes still look alike — corporate web design, e-commerce, mobile app — but a manufacturer's or distributor's real need usually starts somewhere else entirely: in the processes, not on the homepage.

This article orders the evaluation criteria around that reality. No price list; a set of checks you can apply to the quotes on your desk.

Why process software comes before the website

For a company that sells to other businesses, the website is a shop window. The actual loss happens somewhere less visible: stock tracked by hand, orders retyped from email, shipping status that nobody can answer without a phone call.

That has three consequences for how you should evaluate a partner.

The first question is not design. It is "which process is currently costing money". An agency that opens with layout rather than workflow has skipped the part where the value is.

The buyer is not a consumer. A purchasing manager wants specifications, certificates, dimensions, downloadable documents and a fast path to a quote. Consumer e-commerce patterns — carousels, urgency banners, a cart — do not fit. The cart is usually replaced by a quote request that has to land somewhere a human works.

Selling abroad forces multi-language. Not "add a translation": a separate URL structure per language, correct search-engine signals, product data managed from one source, and documents served per language. Maintaining the same product in two places is a guaranteed source of contradictions.

Questions that reveal an agency's level

Judge by what they ask, not what they present. A team that knows integration work asks:

• Which ERP or accounting system are you on today?
• Where does product data live, and how many people edit it?
• How do orders arrive — email, phone, a rep, a marketplace?
• Does stock need to be real-time, or is a daily sync enough?
• Which export markets, and in which languages do you quote?
• Who maintains the technical documents and certificates?

An agency that starts with "how many pages" or "which colours do you like" is selling a website. Page count is settled last.

Verifying integration experience: three questions

This is the single criterion that genuinely separates agencies on this kind of work.

1. Which system, and in which direction? "We've done ERP integrations" is not information. Was it read-only, or is there also writing into the ERP? Writing is an order of magnitude riskier — one bad record corrupts accounting, and unwinding it is manual work.

2. Is there a test environment? An integration built by experimenting against your live ERP is not acceptable. If the agency does not ask for a test environment, they are transferring the risk to you without saying so.

3. Who owns the failure cases? What matters is not what happens when the integration works, but what happens when it breaks. Are failed records queued and retried? Is a human notified about the ones that cannot be resolved? If that mechanism is not described in the quote, the integration is half-built.

On our side this means automation, ERP and custom API integration work — see what we have delivered.

What an exporting company needs on the site

Does physical presence matter here

The distinction needs to be precise, because this is both overstated and dismissed in the wrong places.

Physical presence is genuinely required for: anything touching the production floor. Terminal installation, barcode scanners, screens on the line, local servers, cabling. When a line stops, remote access is not enough.

Physical presence is largely irrelevant for: corporate sites, e-commerce, mobile apps, dashboards, API integration. This work runs remotely, as it does across the industry.

Let's be explicit about our own position: AsteroSoft is based in Muğla, Türkiye. We have no office in Germany, Italy, Russia or elsewhere in Europe, and we will not claim one. European work runs remotely, and where a scope genuinely requires someone on the factory floor, we say so plainly and plan visits into the contract rather than pretending distance is irrelevant.

The right question is not "where is your office" but "how many hours until I get a response when something breaks, and is that in the contract". A team in your own city that takes three days is worse than a remote team that answers the same day.

Ownership: what you hold after handover

On integration work this matters even more, because the integrations end up embedded in how your company operates. The quote must state that these are in your name:

• Domain and hosting account. In the agency's account, you cannot move it.
• Integration documentation. Which field maps to which, written down. Without this document, the next agency starts from zero.
• API keys and access credentials. Held in your own accounts, not theirs.

That last item is the most commonly skipped. An integration delivered without documentation is permanent dependency on the supplier who built it — and it is the reason replacing an agency sometimes costs more than the original project.

The 10 items to compare

Compare this list, not the price:

1. What does the scope include — only the site, or integrations too?
2. Which systems, in which direction (read/write)?
3. Is a test environment provided?
4. How will errors and retries be handled?
5. How many languages, and who translates?
6. Who updates product and document data, and from where?
7. Is there a measurable performance target for mobile and for visitors abroad?
8. Is technical SEO in scope?
9. How many revision rounds, and how is out-of-scope work priced?
10. Does handover include maintenance, a response time and documentation?

For how these turn into budget, we broke the cost structure down in what a business website costs.

Red flags

• "ERP integration is no problem, we'll handle it." Given without asking which system, which direction and which fields, this answer is a sign of inexperience.
• An agency that does not ask for a test environment. They are pushing the risk onto you.
• A quote that leaves documentation out of scope. It produces permanent dependency.
• "Guaranteed first page on Google." Nobody can guarantee rankings.
• A promise of unlimited revisions. Not realistic.
• A quote far below the others. Usually means it covers far less.

How to sequence the work

A simple rule: measure first, automate second. Projects that start without knowing which process produces the most manual work and the most errors end up automating the wrong thing well.

The sequence that works in practice: pick the single process generating the most manual work, solve it end to end, measure the result, then move to the next. Most projects that start a site rebuild, a B2B store, an ERP integration and a mobile app simultaneously finish none of them.

If your project is closer to tourism, rentals or seasonal demand, the criteria are different — we cover those in how to choose a development partner.

We work from Muğla, Türkiye, delivering corporate websites, B2B e-commerce, ERP and API integrations, automation and mobile apps for clients across Europe. To define the scope together, get in touch.