Buyer guide
How to choose a Patchworks Partner Agency.
Patchworks is the iPaaS. The Partner Agency is the team that ships the integration on top of it. Two merchants can buy the same Patchworks licence and get materially different outcomes depending on the agency they hire. This guide covers the decision dimensions that actually correlate with delivery quality, the questions worth asking in a discovery call, the red flags worth walking away from, and a fair note on where we sit in the picture.
Why agency choice matters more than platform choice
The team is the variable.
Patchworks is a mature ecommerce iPaaS. The connector library is deep, the flow editor is workable, monitoring is built in, and the canonical retail patterns are well-trodden. The platform decision is well-understood. The agency decision is where merchants still go wrong.
Two merchants on the same Patchworks subscription, paying the same monthly fee, can end up with very different production estates: one quiet, idempotent, cheap to extend; the other a quarterly fire drill of regression bugs, scope creep and surprise invoices. The platform is identical. The variable that correlates with the outcome is the team shipping the work.
That makes the agency choice the single most consequential decision in the Patchworks buying process, not the platform choice itself. Get the agency right and Patchworks becomes the spine you build a multi-year estate on. Get the agency wrong and the same subscription becomes a sunk cost you spend the second year unwinding.
Decision dimensions
Seven things to compare on.
The dimensions below are the ones that, in practice, correlate with delivery quality across the agencies we've audited as part of customer engagements. None of them are surprising. All of them are verifiable in a discovery call if you ask directly.
-
01
Senior-led delivery versus delegation
Look for
The engineer on the discovery call is the engineer on the keyboard during build, and the engineer on the support call two years later.
Avoid
Senior partner runs sales, junior consultants write the integration, an account manager owns the relationship.
Why it matters
The patterns that quietly age badly in production (idempotency, retry, replay, schema-drift recovery) are senior-judgement calls at design time. Delegated delivery tends to produce flows that work the day they ship and need rework within twelve months.
-
02
Ecommerce specialism, not generalist consultancy
Look for
An agency with retail operational depth: split shipments, marketplace settlement, gift-card tendering, multi-currency rounding, OneWorld subsidiary routing. Pattern exposure across many merchants on similar estates.
Avoid
Horizontal IT or ERP consultancy that lists ecommerce as one practice among several. Patchworks is treated as a vendor in the stack rather than the centre of the integration architecture.
Why it matters
Retail operational patterns are unforgiving. The 1p VAT rounding off-by-one, the gift-card tendering that breaks finance, the marketplace SLA that triggers a chargeback: these are specialist failure modes, not generic integration ones.
-
03
Connector breadth, not just NetSuite or Shopify
Look for
A bench that covers the operational stack beyond the obvious pair: WMS, PIM, returns, marketplaces, helpdesks, marketing automation, search and accounting. An agency that has shipped against at least eighty platforms.
Avoid
A specialist who only ships against the canonical pair you're hiring them for today. Adding a returns platform or a marketplace next year becomes a second integration project rather than an extension.
Why it matters
Estates grow. The agency you hire for Shopify-to-NetSuite today is the agency you'll ask for Returns + 3PL + PIM in eighteen months. Breadth is a future-proofing decision, not a now decision.
-
04
Custom build versus template-led delivery
Look for
An agency that starts from canonical patterns and extends them where the merchant's data shape diverges. Documents the divergences explicitly so finance, operations and the next consultant all know what was done.
Avoid
An agency whose default answer is the off-the-shelf template, with custom logic treated as exception work that pushes complexity into workarounds outside Patchworks (custom SuiteScript, vendor-side hacks, manual processes).
Why it matters
Canonical patterns are starting points, not finish lines. Real estates have edges. The agency's relationship with custom build is the single biggest predictor of whether the integration will fit the business in three years.
-
05
Support model and SLA shape
Look for
Monitored flows with active alerting, on-call cover for incidents, tiered response SLAs in pounds, monthly health checks, runbooks the on-call engineer can act on without phoning the integrator. Retainer pricing published openly.
Avoid
"We'll be there if something breaks" with no defined response window, no monitoring, no runbook handover, and per-ticket pricing that gets renegotiated every quarter.
Why it matters
Every integration becomes a support problem eventually. The support model decides what that looks like: a five-minute alert and a confirmed fix, or a Slack message and a quote for emergency work. The cost of bad support over three years exceeds the cost of the original build.
-
06
Pricing transparency
Look for
Published audit fees, retainer pricing visible on the website, clear posture on scope changes during a project, an explicit credit policy if an audit converts into project work.
Avoid
"Let us scope it and come back to you" with no visible benchmark, no published rates, no fixed-fee entry point that lets you assess fit before committing.
Why it matters
Opaque pricing usually correlates with opaque delivery. An agency that won't publish a starting price is also an agency that won't publish a runbook or a flow inventory. Transparency at the front door is a signal about transparency through the project.
-
07
Published track record
Look for
Named case studies with technical detail, comparison content that names competitors honestly, public reference content the buyer can read before the discovery call. Named clients who can be checked.
Avoid
"Trusted by 100+ brands" with no list. Stat blocks without sources. Case studies that read like brochure copy without flows, timelines or named systems.
Why it matters
Publishing is a discipline. An agency that won't say what it's shipped publicly is harder to verify and harder to compare. The agencies that publish honestly tend to be the ones whose work holds up to honest examination.
Discovery questions
Eight questions for the call.
Bring these to every shortlist call. The answers are usually more revealing than the prepared deck.
- Who specifically will write our integration? Will the engineer on this discovery call be on the keyboard, or will the work be handed down a chain?
- Walk us through a flow you built for a comparable merchant. What did the data model look like, what were the edge cases, what changed after go-live?
- What does your support SLA actually cover? Tiered response windows, on-call cover, monitoring, replay capability, change-request handling.
- How do you handle scope changes after sign-off? Do you re-quote, absorb, or treat as a separate engagement?
- What is your approach when an upstream platform changes its API? Who notices, who acts, what's the merchant's exposure?
- Can you share a runbook the on-call engineer uses on a live integration? Sanitised is fine; we want to see the discipline.
- How long does a typical engagement of our shape run, end to end? What are the phases, what does each one produce, what does done look like?
- What do you say no to? An agency that says yes to everything either hasn't been doing this long or isn't being honest about where the work fits.
Red flags
Reasons to walk.
None of these are individually disqualifying; two or three of them in the same conversation usually are.
- "Trusted by 100+ brands" without a list of names.
- Stat blocks without sources (e.g. "500% increase"; increase in what, from what baseline, when?).
- Discovery handed to a junior consultant; senior partner only appears for the sales pitch.
- Vague support pricing or "we'll cover that under the relationship".
- Generic Patchworks pitch with no specifics on Tapestry vs Core, custom connector development, or the things buyers actually have to decide.
- Reluctance to share a runbook or flow-inventory sample for an anonymised customer.
- Pricing locked behind "let us scope it" with no published audit or retainer floor.
Where eCirql fits
Honest positioning.
Against the seven dimensions above, our positioning is specific. Senior-led: the founder writes the integrations on every engagement; senior associate engineers come in when scope warrants it, never as a layer between the client and the work. Specialism: ecommerce integration is the whole practice, not one chapter of a horizontal IT consultancy. Connector breadth: 114 platforms in the published bench. Build paradigm: canonical patterns where they fit, custom flows where they don't, documented either way. Support: monitored process flows, on-call cover, tiered response SLAs from £750 per month, runbook handover on every shipped integration. Pricing: the £1,500 audit fee and the £750 Tapestry-to-Core variant are published; retainer floors are public. Track record: 45 published integration combos, 11 iPaaS and platform comparisons, named case studies, all on the same domain you're reading.
Where another agency might be the better fit: enterprise estates spanning HR / manufacturing / regulated finance need a horizontal iPaaS like Boomi or MuleSoft and the agency to match. Self-serve install-rather-than-build ecommerce shops with stack that matches the Celigo Integration Apps catalogue may get more value from that model than a partner-agency build. Pure US operations with no UK / EU touch could prefer a US-headquartered partner with a deeper local footprint. We've named where each of these competitors genuinely wins in our published comparisons; none of those comparisons are puff.
If you've worked through the dimensions and we look like the right shape: the fixed-fee Integration Audit is the productised entry point. £1,500 standard, £750 for the Tapestry-to-Core variant, ten working days, PDF report and follow-up call, fee credited against project work commissioned within 30 days. If you'd rather just email, the team reads contact@ecirql.com directly.
Questions
Common questions.
-
01 How many Patchworks Partner Agencies are there?
Patchworks publishes a Partner Network directory; the count moves over time as agencies join and certification levels change. The directory is the authoritative source. The headline number matters less than the shortlist you build for your specific estate, which is usually two to four agencies once you filter for geography, specialism and supported platforms. -
02 What is the difference between a 'Patchworks Partner' and a 'Patchworks Partner Agency'?
Patchworks runs a multi-tier partner programme. A Partner Agency holds the certified delivery status and ships integration work on the platform. Other partner tiers cover referrals, technology integrations and resellers. If you are hiring a team to design, build and support your integrations, the Partner Agency tier is the one to filter on. -
03 How long does choosing a Partner Agency typically take?
Two to four weeks of evaluation is a realistic window for a mid-market merchant: discovery calls with two or three shortlisted agencies, a fixed-fee audit or scoping engagement to surface the real work, and a contract decision after the audit lands. Compressing this to under a fortnight tends to surface poor decisions; stretching beyond six weeks usually means the merchant has not aligned internally on what they are actually buying. -
04 Can we evaluate an agency without committing to a full project?
Yes. The pattern most established agencies offer is a fixed-fee integration audit: a productised piece of work with a defined deliverable (typically a report and a follow-up call) that lets both sides assess fit before either commits to a multi-month project. Our own audit is £1,500 for a standard estate review and £750 for the Patchworks Tapestry-to-Core variant; the audit fee is credited against any follow-on project commissioned within thirty days. -
05 What if we are already on a Patchworks Partner and want a second opinion?
An independent integration audit is the right shape. A platform-agnostic audit looks at the flow inventory, the operational handover quality, the failure modes, the cost posture and the deviations from current best practice, and produces a recommendation on whether to stay, fix specific things, or migrate to another partner. We perform these audits routinely; the framework is the same whether the incumbent is a Patchworks Partner Agency or a Celigo / Boomi / MuleSoft estate. -
06 Does Patchworks recommend specific agencies?
Patchworks operates an introducer programme: their account team routes opportunities to Partner Agencies based on geography, specialism and the merchant's stack. The introduction is a useful signal, but it is not an endorsement of fit for your specific estate. Treat the introduction as the start of evaluation, not the end of it.
Get in touch
Tell us what you’re trying to connect.
And what’s in the way. We will tell you whether we are the right people to do it. Drop us a line below, or open the chat in the corner of the screen.
Direct: contact@ecirql.com
Message sent
Thanks. We’ll be in touch.
Your message is in our inbox. A human will read it and reply within a working day. For anything urgent, drop us a line at contact@ecirql.com or open the chat in the corner of the screen.