Design Partner Agreement

The Design Partner Program

Partner joins the Multiflows Design Partner Program: early, discounted access to the Multiflows AI SDR platform in exchange for active use and structured feedback during the platform’s trial phase. Partner’s feedback directly shapes the product roadmap.

What you receive

• Platform access — the full Multiflows AI SDR platform: automated prospect research, ICP scoring, personalized email drafting, reply handling, follow-up sequences, task management, and team dashboards, for the seats defined in Section 7.
• Onboarding — a guided onboarding and AI-calibration session scheduled within 5 business days of the effective date. Go-live target: within 2 weeks of the effective date, provided Partner has supplied the items in Section 6.1.
• Direct support channel — a direct line to the Multiflows engineering team (email and messaging) plus the in-app feedback portal, where every bug report and feature request is tracked with a visible status.
• Monthly review — one 45-minute roadmap and feedback call per month, plus a monthly usage and results summary.

Support and bug-fix commitments

Support hours: Sunday–Thursday, 09:00–18:00 Israel time, excluding Israeli public holidays. All response times are measured in business hours and days within this window.

Resolution times are good-faith targets, with one exception: if a Critical (P0) issue remains unresolved for 5 business days, Partner may terminate this agreement immediately and receive a pro-rated refund of the current month’s fee.

Platform availability: a 99% monthly uptime target, excluding scheduled maintenance announced at least 48 hours in advance and placed outside Partner’s stated business hours where practical.

Feature development commitments

Minor feature — up to 2 development days (e.g. a new filter, table column, template control, or workflow adjustment). Major feature — up to 10 development days (e.g. a new integration, page, or workflow).

Per calendar month, Multiflows commits to delivering up to 2 minor features requested by Partner, and per calendar quarter, 1 major feature. Selection happens jointly at the monthly review call from Partner’s feedback-portal requests.

• Requests must fit the multi-tenant platform (no Partner-exclusive forks); Multiflows retains final say on architecture and security fit.
• Unused allocations do not roll over to the next period.
• Sizing (minor vs. major) is estimated by Multiflows and communicated before work starts.
• Delivery target: minor features within the same calendar month of selection; major features within the quarter.
• Requests that benefit all tenants may be delivered ahead of, and in addition to, these allocations.

Trial-phase acknowledgment

The platform is in active development. Features may change with notice; Partner’s feedback shapes the roadmap but, beyond Section 4, does not obligate inclusion of any specific request. Pre-release features shared with Partner are confidential until publicly released.

What you agree to

6.1 Accounts and third-party costs

Partner maintains the following accounts and pays their costs directly to the vendors. Multiflows never marks these up or bills them on Partner’s behalf.

• Apollo.io — account with API access (prospect data enrichment).
• OpenAI — API account with billing enabled (AI drafting and research). Typical usage at current tuning is roughly $1–2 per day per active seat.
• Gmail or Outlook — mailbox(es) with OAuth access for sending.
• API keys and mailbox connections supplied within 5 business days of the effective date.

6.2 Active participation

• Use the platform actively: at least 1 outbound run per week per active SDR seat, or an equivalent cadence agreed at onboarding.
• Attend the monthly review call.
• Report suspected bugs and requests through the feedback portal so they are tracked and covered by Sections 3–4.
• Respect platform sending limits and warmup schedules, which protect deliverability.

6.3 Compliance and content

Partner is the sender of record for all outreach and is responsible for the legality of its targeting and content under applicable law (for example, CAN-SPAM and GDPR). Multiflows provides suppression, opt-out handling, and deliverability tooling, but does not provide legal advice.

6.4 Case study (optional)

Partner agrees that Multiflows may reference Partner’s name and logo and publish a jointly-approved case study. This is opt-in; leave the box unchecked to decline.

Pricing

• Billed monthly in advance; the first invoice issues on the effective date.
• Excludes the third-party costs in Section 6.1 (Apollo, OpenAI), which Partner pays directly.
• Price lock: this rate is guaranteed for 12 months after Multiflows’ general-availability launch, provided the agreement remains active.

Term, termination, and data

• Initial term: 3 months from the effective date; month-to-month thereafter.
• Notice: either party may terminate after the initial term with 30 days’ written notice. Either party may terminate immediately for a material breach left uncured for 14 days after written notice. The P0 remedy in Section 3 applies at any time.
• On termination: Multiflows provides a full export of Partner’s data (prospects, contacts, emails, tasks; CSV/JSON) within 5 business days, revokes stored API credentials immediately, and deletes Partner data within 30 days, except as required by law.

Data protection

Partner data is isolated per tenant (database row-level security), API credentials are encrypted at rest, and access is limited to the Multiflows team for operation and support. Partner retains all rights to its data. Multiflows retains all rights to the platform, including improvements informed by Partner feedback.

Limitation of liability

Each party’s aggregate liability under this agreement is capped at the fees paid by Partner in the 3 months preceding the claim. Neither party is liable for indirect or consequential damages, except for breaches of confidentiality (Section 5) or Partner’s compliance obligations (Section 6.3). The Terms & Conditions govern all matters not addressed here.