The questions partners ask first.
Mostly about conflict, contracts, and what the client sees. Reasonable questions to ask before handing anyone access to your best account.
Will you ever compete with us for Salesforce work?
No. We never compete for your Salesforce business. We do not run a Salesforce implementation practice, we do not bid on platform implementation work, and we sign a mutual non-solicit covering Salesforce engagements. The same principle applies to whatever platform practice a partner runs — ERP, commerce, or managed services.
The reason is commercial rather than sentimental: partner referrals are how we grow, so competing with a partner would cost us more than any single engagement could return.
What if my client approaches you directly afterwards?
We route them back to you. If a client we met through your engagement asks us to work on something, our answer is to involve the partner who introduced us. Where you have engaged us white-label, the client typically has no route to us at all, which is the cleanest version of this.
Do you work with our competitors?
We work with multiple firms in the same category, in the same way a specialist engineering supplier does. What we never do is carry information between them. Engagement details, client identities, architectures, and commercial terms stay inside the engagement, under your NDA. If a specific conflict concerns you, raise it before we start and we will address it in writing.
Will you try to expand into the rest of the account?
No. We introduce nothing you have not asked us to introduce. If we notice an opportunity while working, we tell you — not your client. Whether it becomes anything is your decision and your revenue.
Whose paper do we work under?
Yours. We sign your NDA, MSA, and subcontract agreements. Partners rarely want a second contractual framework inside a client programme, so we do not insist on ours.
Who owns the code and the IP?
Whatever your agreement with your client specifies — normally you or the client. We claim no ownership of engagement deliverables. Where we use pre-existing internal libraries, we identify them up front and license them so nothing we leave behind creates a dependency on us.
Are you insured, and will you accept our liability terms?
We carry commercial insurance and will provide current certificates on request. Liability, indemnity, and limitation terms are negotiated inside your subcontract like any other provision — send the paper and we will respond with any exceptions, which are usually few.
How do you handle client data and security review?
Access is scoped to what the work requires and provisioned in your systems rather than ours, so your access controls and logging apply. We work within your data-handling and residency requirements, and we can complete client security questionnaires and attend security reviews as part of your team.
What exactly does the client see?
Your firm. We work under your email domain and project tools, deliver in your templates with no eProxim branding, and appear as your team in client-facing meetings. We never contact your client directly unless you put us in the conversation.
If you would rather introduce us as a named integration specialist — some clients find a dedicated firm on the hard part reassuring — we do that instead. It is your call, per engagement.
Can we say the work is ours?
Yes. Under a white-label engagement the work is delivered as yours, and we do not publish, reference, or claim it. We ask before using anything as a reference, and a no requires no explanation.
How quickly can your engineers be inside our tools?
Usually days. You provision accounts on your domain and in your tools, we name the engineers who will hold them, and we complete your onboarding requirements. The constraint is normally your provisioning process rather than our availability.
How do you price engagements?
Scoped work packages are quoted as fixed-scope engagements with defined outcomes. Embedded bench and fractional architecture engagements run on a monthly commitment. Managed integration support runs on a separate agreement with agreed response targets.
Rates depend on the mix of roles and the delivery locations involved, and we give partners a rate card rather than quoting engagement by engagement.
Where do your engineers sit?
Alpharetta, Georgia, plus delivery centres in Iași and Gurgaon. Most engagements are blended, with senior architecture and partner-facing roles onshore. If a client requires specific locations or residency, tell us early and we will staff accordingly or decline.
What does “fast response” actually mean?
On difficult and at-risk projects, we respond the same business day. A rescue then begins with a one-day deep dive followed by written recommendations, rather than a multi-week discovery phase.
How small an engagement will you take?
Small enough to be worth starting. Partners often begin with one integration or a single deep dive, because that is a sensible way to test whether a firm behaves the way its website says it does.
What happens after go-live?
Handover is part of delivery: documentation, runbooks, and a walkthrough with whoever maintains it next. If you want continuing monitoring, alerting, and support, that becomes a managed integration agreement — still under your brand, still with you owning the client. If you would rather your own team runs it, we make sure they can.
Do you take fixed-price work?
Where scope can genuinely be fixed, yes — a defined integration with clear acceptance criteria is a reasonable fixed-price engagement. Where the work is discovery-heavy, as most rescues are, we start with the bounded deep dive and price the rescue once the situation is understood. Fixed-pricing an unknown mostly transfers risk into contingency.