Draft for attorney review — not yet in force.
AssemblyWright AI — Design Partner Pilot Agreement
Effective date: [DATE]
This Design Partner Pilot Agreement (the "Pilot Agreement") is between Evadaroo & Company, LLC, a Pennsylvania limited liability company trading as AssemblyWright AI ("AssemblyWright", "we"), and the customer named in the Order Form below ("Partner", "you").
A design-partner pilot is a trade: you get the product at a discount and direct access to the people building it; we get honest feedback and, if you opt in, a case study. This document sets out both halves.
Part A — Order Form
| Field | Value |
|---|---|
| Partner (legal entity) | [PARTNER LEGAL NAME] |
| Partner address | [PARTNER ADDRESS] |
| Partner primary contact | [NAME, TITLE, EMAIL] |
| Partner technical contact | [NAME, TITLE, EMAIL] |
| Pilot start date | [DATE] |
| Initial pilot term | 3 months from the start date, then month-to-month |
| Pilot fee | $[500–1,500] per month, billed monthly in advance |
| Included Builds per month | [NUMBER] |
| Overage | None during the pilot. Builds beyond the included allowance are refused until the next period, or the allowance is raised by written agreement at no charge. No overage is invoiced. |
| Users included | [NUMBER] |
| Features included | [LIST — or "all features generally available during the pilot"] |
| Connected Org environments authorized at signature | Sandbox, Developer Edition, and UAT orgs only (see §B.3) |
| Production access | Not authorized. Requires a signed DPA and the written authorization in §B.3.2 |
| Feedback commitment | One 45-minute session per month, plus written notes on each completed Build (see §B.5) |
| Case study | ☐ Opt in — anonymized ☐ Opt in — named ☐ Decline (default: decline; see §B.6) |
| Post-pilot conversion price | The then-current list price of the [Starter / Team / Business] package, less [NUMBER]% for [NUMBER] months from conversion |
| Notice address — AssemblyWright | legal@evadaroo.com; Evadaroo & Company, LLC, [REGISTERED OFFICE ADDRESS] |
Signatures
| AssemblyWright | Partner |
|---|---|
| By: ____________________ | By: ____________________ |
| Name: | Name: |
| Title: | Title: |
| Date: | Date: |
Part B — Pilot Terms
B.1 What this agreement is, and what it sits on top of
B.1.1 The AssemblyWright AI Terms of Service, Acceptable Use Policy, and Privacy Policy apply in full, and the Data Processing Addendum applies where Partner is a controller of personal data. This Pilot Agreement modifies them only where it says so.
B.1.2 Where this Pilot Agreement conflicts with the Terms of Service, this agreement governs for the pilot term.
B.1.3 The pilot fee replaces the standard subscription price for the pilot term. Everything else in the Terms — ownership, confidentiality, indemnities, the limitation of liability, governing law, and the Pennsylvania venue — applies unchanged.
B.2 Pilot status, honestly stated
B.2.1 The Service is early. Features may change, be added, or be withdrawn during the pilot with little notice. Some features are labelled new or beta and have not been run against a live production org.
B.2.2 There is no service-level agreement and no uptime commitment, during the pilot or after it.
B.2.3 Outputs are generated by AI models and may be wrong. Every Deliverable must be reviewed by a competent person before it is relied on or deployed. The review gates and human checkpoints exist for this purpose.
B.2.4 AssemblyWright holds no SOC 2 report, ISO 27001 certificate, HIPAA attestation, or third-party penetration test, and none is in progress. Isolation between workspaces is logical, not physical. Partner accepts this in choosing to pilot, and should not place data in the Service whose handling requires a certification we do not hold.
B.3 Environment restriction — the core safeguard
B.3.1 Until both conditions below are met, Partner will connect only sandbox, Developer Edition, scratch, or UAT orgs — never a production org. AssemblyWright's connection records are tagged by environment, and the release flow warns on a mismatch, but the restriction is Partner's obligation, not a technical lock.
B.3.2 Production access requires both of:
- a signed Data Processing Addendum between the parties; and
- written authorization from Partner, signed by an officer or an authorized IT/CRM owner, identifying the specific org, the scope of permitted writes, and the named individuals in Partner's Workspace who may approve a deploy.
An email from an authorized signatory naming these things is sufficient. A verbal go-ahead is not.
B.3.3 Least privilege. Partner will grant the narrowest CRM permissions that let the Service do the agreed work, and will review them at the pilot's midpoint.
B.3.4 Data minimization in the pilot. Partner will prefer masked, synthetic, or reduced datasets where the work does not require real records, and will not import org context containing regulated data prohibited by the AUP.
B.3.5 Backups. Partner is responsible for its own CRM backups. The Service captures pre-deploy snapshots and prior record values with a 30-day default retention, and those are a convenience, not a substitute for Partner's own backup regime. Rollback cannot undo downstream automation a change triggered in the Connected Org.
B.4 Fees
B.4.1 The pilot fee is billed monthly in advance, in US dollars, exclusive of taxes.
B.4.2 No overage is invoiced during the pilot. If Partner needs more Builds, we raise the allowance by written agreement at no extra charge, or we agree a new fee for the following month.
B.4.3 Model spend is ours during the pilot. Partner is not billed for AI usage.
B.4.4 Money-back. If Partner is dissatisfied, telling us within 30 days of the first paid month at billing@assemblywright.ai gets that month refunded in full.
B.4.5 Conversion. The post-pilot discount in Part A applies if Partner converts to a paid package within 30 days of the pilot's end. It is a discount on list price, not a price lock beyond its stated duration.
B.5 Feedback — what Partner owes us
B.5.1 Partner will provide, in good faith:
- one 45-minute feedback session per month with a person who actually uses the product;
- written notes on each completed Build — what was usable, what was wrong, what was missing — sent by email or entered in the product;
- prompt notice of defects, with enough detail to reproduce them.
B.5.2 Feedback is not confidential to Partner and carries no compensation. Partner grants AssemblyWright a perpetual, irrevocable, worldwide, royalty-free license to use feedback, suggestions, and defect reports to improve and commercialize the Service, without attribution and without any obligation to implement.
B.5.3 Feedback never includes Partner's data. Partner's content, its org configuration, and anything identifying Partner or its clients remain Partner's confidential information under the Terms, and this license does not reach them. If Partner sends us a screenshot or a document to illustrate a defect, we use it to fix the defect and nothing else, and we will delete it on request.
B.5.4 Missing a feedback session is not a breach we will terminate over. If Partner stops engaging for two consecutive months, we may convert the pilot to standard list pricing on 30 days' notice, or end it under §B.8.
B.6 Case study — opt-in, and revocable
B.6.1 The default is no case study. Nothing is published about Partner unless Partner ticks the box in Part A.
B.6.2 Anonymized opt-in permits AssemblyWright to describe the engagement without naming Partner — for example "a 40-person Salesforce consultancy in the Northeast" — including anonymized, non-identifying metrics Partner has confirmed as accurate.
B.6.3 Named opt-in additionally permits use of Partner's name and logo in the case study and in a customer list.
B.6.4 In both cases: Partner approves the text before publication. AssemblyWright will send the draft and will not publish until Partner confirms in writing. Approval of one piece is not approval of another.
B.6.5 No figure is published without Partner's confirmation of its basis in the same approval. No claim will be made about Partner's outcomes that Partner has not confirmed.
B.6.6 Revocable. Partner may withdraw consent at any time in writing. AssemblyWright will remove the case study from its own properties within 30 days and stop further distribution. Copies already printed or held by third parties cannot be recalled, and this is stated rather than promised away.
B.6.7 Partner's own confidentiality obligations to its clients come first. Partner is responsible for having the rights to whatever it confirms.
B.7 Confidentiality and non-disclosure of the Service
B.7.1 Each party's confidentiality obligations under the Terms apply. In addition, during the pilot Partner will treat unreleased features, pricing discussed but not published, and the product roadmap as AssemblyWright's confidential information.
B.7.2 Partner may say publicly that it is evaluating AssemblyWright and may discuss its own experience with its own staff, advisors, and clients. This section restricts disclosure of our non-public materials, not Partner's opinion of the product.
B.8 Term and termination
B.8.1 Initial term: 3 months, then continuing month to month.
B.8.2 Either party may terminate on 30 days' written notice, at any time, including during the initial term. Fees already paid for a commenced month are not refunded, except under §B.4.4.
B.8.3 Immediate termination by either party for a material breach uncured after 15 days' notice, or immediately for an AUP breach presenting an ongoing risk of harm.
B.8.4 On termination: Partner's Deliverables, Knowledge Base entries, and Build records remain available for export for 30 days, after which they are deleted on our normal cycle. Partner may request erasure inside the window and we will confirm it. Changes already deployed into Partner's Connected Org stay in Partner's system. Partner should disconnect its CRM credentials and revoke the corresponding connected app or private-app token in its own CRM.
B.8.5 Survival: §B.5.2 (feedback license), §B.6.6 (case-study withdrawal), §B.7 (confidentiality), and every surviving section of the Terms.
B.9 Liability during the pilot
B.9.1 The limitation of liability in the Terms applies unchanged — the greater of the fees paid in the preceding 12 months or US $100, with the same carve-outs for indemnification, confidentiality breach, unpaid fees, gross negligence, willful misconduct, fraud, and anything that cannot be limited by law.
B.9.2 Partner acknowledges that the pilot fee is discounted precisely because the product is early, and that this allocation of risk is part of the trade.
B.9.3 Nothing here limits AssemblyWright's obligation to notify Partner of a personal data breach within 72 hours, or Partner's remedies for our breach of confidentiality.
B.10 General
Governing law: Pennsylvania. Venue: the state and federal courts located in Pennsylvania, exclusively. Before filing, the complaining party sends written notice and the parties attempt resolution in good faith for 30 days. No arbitration clause. Notices as in Part A. Neither party may assign without consent except to a successor in a merger or sale of substantially all assets. This Pilot Agreement, with the Terms, AUP, Privacy Policy, and DPA where applicable, is the entire agreement for the pilot.
Evadaroo & Company, LLC · [REGISTERED OFFICE ADDRESS] · Pennsylvania, USA · legal@evadaroo.com