# Trusteed: your first client project

For ecommerce integrators and technology partners. Choose one client and an operation. Use this kit to prepare the technical review and estimate the work your team would need to quote before the client commits to an integration pilot.

The project still needs a compatibility review.

## Describe the client's project

Record the platform and version, store website and technical contact. Which action would you test? Explain who uses the assistant and the data it needs to read or the operation it needs permission to request in the client's store.

Still choosing a client? List the platforms your team maintains.

## Check the integration

Review [integrations](https://trusteed.xyz/en/integrations) and [protocol coverage](https://trusteed.xyz/en/protocol-coverage). Check specific actions, requirements and availability. Demo steps are examples whose applicability needs to be checked against the selected store's platform and the scope you agree on with the teams involved in the pilot.

Use the [free audit](https://trusteed.xyz/en/audit) to review public pages. It measures what can be observed on the website. It doesn't establish that a production checkout is available.

## Define an acceptance test

Choose a supported action. Document inputs and the expected result. For purchase approval, agree on a spending limit and test a request that can proceed as well as one that needs review by the person responsible for the operation.

Name the person who approves it.

Where receipt issuance supports the operation, check the TrustReceipt and its contents. Its signature establishes the record's integrity and issuer. Evidentiary use depends on the contents and the process in which the receipt is presented, including any requirements set by the recipient of the evidence.

## Assign the work

| Work | Owner to agree on |
| --- | --- |
| Client contract and support | Partner / client / Trusteed |
| Connector setup and permissions | Assigned technical team |
| Rules and human approval | Merchant and pilot teams |
| Acceptance test | Client's project owner |
| Infrastructure incidents | Trusteed owner under the agreement |
| Maintenance and configuration changes | Contracted owner |
| Billing, data access and exit | Parties to the agreement |

Payments use the merchant's account and credentials. Trusteed is neither a payment processor nor merchant of record. Keep credentials out of evaluation forms and emails.

## Quote the first project

Separate assessment, configuration and any development work. Include the acceptance test. Add Trusteed licensing or usage and recurring support costs so the parties can agree on who charges for each part before work starts on the client's store.

Referral fees and white-label terms need a separate agreement.

## Before adding a second store

Keep the scope and acceptance test. Review incidents and support hours from the first project so your team can identify repeatable tasks and check which requirements differ for the next store you plan to integrate.

## Next step

[Request a project review](https://trusteed.xyz/en/partners#partner-form). You can explore the partnership before choosing a client. Share the platform and proposed operation when you have them.