How it works

Three parties. Three agreements. One clean structure.

This is the page to forward. It sets out who contracts with whom, who does what, and how money moves. Everything else on this site points back here.

Enterprise clientOwns its data and perimeterDelivery teamWorks inside client systemsYour consultancyOwns deliverySolerWorksOwns complianceClient agreementData agreementPartner agreement

The three agreements

Three parties. Three agreements. No overlap.

Each party owns exactly one thing: the client owns its data, you own delivery, SolerWorks owns compliance. Select an agreement to see how it fits.

Tripartite delivery architectureThree contracts connect the enterprise client, the partner and SolerWorks. The delivery team works inside the client environment.Enterprise clientController. Pays the partner.PartnerSources, hires and directs the teamSolerWorksDPA signatory and processorDelivery teamWorks inside the client environmentCONTRACT 1Client agreementPartner and clientCONTRACT 2Data Processing AgreementSolerWorks and clientMaster Services AgreementCONTRACT 3 · Partner and SolerWorks

Swipe sideways to see the full diagram.

Your team works inside the client’s environment. SolerWorks is the in-country DPA signatory and data processor.

SolerWorks ↔ European enterprise

Data processing agreement

The document the enterprise privacy team signs. SolerWorks signs it with your client directly, as data processor, at no cost to them.

What it delivers

  • A named, accountable data processor in Brazil.
  • The client-contained perimeter, written into the contract.
  • A live register of every engineer with access.
  • A structured incident notification protocol, audit support and certified offboarding.

What it leaves alone

  • Your scope, your pricing and your delivery.

Every engineer also completes a security and privacy onboarding before the client issues access.

Who does what

You run delivery. We run the compliance rails.

SolerWorks is infrastructure. It holds the DPA and the compliance record in Brazil. The team, the process and the margins stay yours.

SolerWorks

Compliance and data governance

  • Signs the data agreement with the enterprise.
  • Binds every engineer to a security and privacy undertaking before access, and keeps the personnel register.
  • Onboards every engineer to the security perimeter.
  • Maintains registers, records and audit evidence.
  • Answers security questionnaires and audit requests.
  • Runs incident notification and certified offboarding.

Your consultancy

Engineering and delivery

  • Contracts and pays every engineer directly.
  • Chooses the engineers and leads the team day to day.
  • Owns sprints, backlog and delivery quality.
  • Keeps the client relationship and the commercials.
  • Scales the team up or down as the account grows.

No markup on talent

The gateway fee is all SolerWorks earns. No commission or margin is added to your engineers’ pay.

No sprint direction

Your delivery leads run the work. SolerWorks never touches scope or schedule.

No pooled payroll

Funds move directly between the parties who earned them. Nothing is held in between.

Money flow

Follow the money

Your client pays you. You pay your engineers. You pay SolerWorks a gateway fee. Three clean, direct flows, and none of them passes through a pooled account.

Money flowThe client pays the partner. The partner pays its contractors directly and pays SolerWorks a service fee.Enterprise clientController. Pays the partner.PartnerSources, hires and directs the teamSolerWorksDPA signatory and processorDelivery teamWorks inside the client environmentPays for servicesClient to partnerNo paymentsService feePartner to SolerWorksPays contractors directlyPayroll never passes through SolerWorks.

Swipe sideways to see the full diagram.

Money flow. Payroll never passes through SolerWorks.
  • Your client never receives a SolerWorks invoice.
  • Finance teams on both sides see a structure they can explain in one sentence.
  • No escrow, no float and no pooled account inside SolerWorks.

Document

Loading document.