How we work

Giving an engineering partner production access is a trust decision before it is a technical one. This page answers what your legal, finance and security reviewers will ask, including the parts where the honest answer is that we don't have something. Anything you don't find here, write to contact@renaiss.io and we'll answer it in writing.

Contracting and commercial

We contract through Renaissance Software LLC, a US entity. It is the party on the MSA and the invoicing entity for the engagement — there is no cross-border contracting arrangement on our side, so this is a standard US-to-US commercial relationship.

• Tax forms. W-8BEN-E does not apply: that form is for foreign entities receiving US-source income. We provide a Form W-9 confirming US taxpayer status and EIN for your vendor onboarding.
• Withholding. None. Payments to a US entity under a W-9 carry no US tax withholding obligation on your side.
• Invoicing and payment. USD invoices drawn on a US bank account, paid by domestic ACH or wire — no international wire mechanics. Payment terms are net 30.
• IP ownership. You own what we build. All intellectual property developed for a project belongs to the client.
• Whose paper. We can work from our standard MSA or yours, whichever your legal team prefers. NDAs and data processing agreements are scoped to the engagement, especially where regulated or sensitive data is involved.

Insurance

Our coverage is underwritten by a carrier rated A++ (Superior) by A.M. Best.

• Commercial General Liability — $1,000,000 per occurrence and $2,000,000 general aggregate.
• Technology Errors & Omissions (Professional Liability) — written specifically for our industry, with limits of $2,000,000 per claim and $2,000,000 in the annual aggregate.
• Contract provisions — our policies include Waiver of Subrogation provisions and the ability to name clients as Additional Insureds where the contract calls for it.

We work under strict corporate compliance requirements regularly and can provide a current Certificate of Insurance immediately for any new engagement.

Security and compliance

We do not hold SOC 2 Type II or ISO 27001, and we have no certification programme in progress. You would find that in diligence anyway, and a vendor who lets you find it has already cost you a week. If an audited certification is a hard requirement for your engagement, tell us early and we will say honestly whether it makes sense to keep talking.

What we do run today:

• Access and credentials are managed by us through Google SSO, granted per engagement and revoked when it ends.
• Everyone on your engagement clears the same hiring process before they start: a background check, a pre-employment psychometric assessment, and the same confidentiality and intellectual-property terms. That last part is what makes “you own what we build” hold all the way down to the person writing the code.
• We do not run MDM on company endpoints. We would rather say so than imply a control we do not have; if your policy requires managed endpoints, raise it early and we will scope it into the engagement.
• Certifications are held by named engineers — AWS Solutions Architect (Associate and Professional), AWS Developer, AWS Security Specialty, AWS Database Specialty, HashiCorp Terraform, GCP and Azure credentials and ITIL Foundation. They are evidence of practice, not a substitute for an audited security programme.

How we staff

Everyone sells nearshore hours. The questions that decide an engagement are about who shows up, whether they stay, and what happens when they don't.

Do I interview the engineers?

Yes. Every engineer clears our internal process before they ever reach a client: a coding challenge, a system design interview, cultural fit, and an English evaluation. On top of that, you are welcome to interview anyone we propose — and if you want that right in writing, we put it in the MSA.

Will the senior engineer I met still be on my account in month four?

Yes. We don't rotate people to a new logo mid-engagement. If a change ever becomes necessary, you hear it from us in advance — not when the commits stop looking familiar.

What is your attrition rate?

Our annual attrition runs under 10%. In an industry where 20–30% is normal, that's the number we'd rather be judged on: the engineer you meet in month one is, in all likelihood, the engineer you still have in month twelve. We are not publishing an average-tenure figure yet, because the number we have is an internal estimate rather than a figure out of People's records.

What happens if someone leaves?

If an engineer leaves your engagement, we replace them within 15 business days with someone at the same level, with a handoff overlap so delivery doesn't dip. That commitment lives in the MSA, not in a sales conversation.

What English level, measured how?

Every engineer is evaluated for English as part of our hiring process — a live interview, not a self-reported score. The floor is B2 or above, and we filter for the English the role actually demands. We don't issue certificates and we don't claim them.

Is the hours overlap contractual?

UTC-3 puts us 4–6 hours of daily overlap with US teams, every day — that's the calendar, not an effort. We commit to it in the MSA.

Who is on call?

On-call and incident response come with Managed Operations, under a defined SLA. In every other model, coverage is Argentina business hours — with 4–6 hours of daily overlap with your team. We'd rather tell you that than sell you a rotation we don't run.

How to start

Most engagements start with a technical assessment: four weeks, a fixed fee from $8,000 USD, and a deliverable precise enough to take to your board. If you move forward with us, the fee is credited against the first phase of work. Write to contact@renaiss.io or use the contact form.