Sprint Engagement Terms

1. What This Document Covers

These terms govern Sprint engagements between your company ("Client," "you") and NJB Intelligent Automation LLC, doing business as Foundari ("Foundari," "we," "us"). A Sprint is a scoped build engagement with defined deliverables, a timeline, and acceptance criteria. This includes QuickStarts (small, fast-turn builds), Core Builds (larger implementation projects), and Bundles (multi-component packages). The specific scope, deliverables, timeline, and investment for your engagement are defined in your signed proposal.

2. Scope of Work

The scope of your Sprint engagement is defined in your proposal, including what will be built, what is explicitly not included, and the acceptance criteria for completion.

What's included is listed in the proposal's Scope of Work section. We will deliver exactly what is described there.

What's not included is listed in the proposal's "Not Included" section. We are explicit about exclusions because ambiguity about scope is the most common source of frustration in professional services engagements. If something isn't listed in the scope, it isn't included. This isn't adversarial — it's how we protect the quality of what we deliver and keep the engagement focused.

3. What We Need From You

Sprint engagements require your active participation at specific moments:

Access. We'll need access to the tools, systems, and platforms specified in your proposal's "What We Need From You" section. Timely access provisioning keeps the project on track. Delays in providing access may extend the timeline.

Decisions. At certain points during the build, we'll need your input or approval to proceed (field configurations, workflow logic, pipeline structure, etc.). We'll communicate these decision points clearly with the context you need to decide. We ask that decisions be made within 2 business days of the request. Extended decision delays may extend the timeline.

Feedback. During the client review phase, we'll present the build for your review and feedback. Timely, specific feedback helps us refine the delivery efficiently. "This looks good" and "I don't like it" are both less useful than "the pipeline stages need a different order because our process goes X then Y."

A designated point of contact. One person on your team who can answer questions, provide access, and make or escalate decisions. This doesn't have to be the owner — it can be an office manager, operations lead, or whoever knows the day-to-day systems best.

4. Payment

Payment terms are specified in your proposal.

QuickStart engagements: Payment is due in full before work begins.

Core Build engagements: Payment is typically structured in two milestones — a deposit (usually 50%) due upon signing, and a final payment (the remaining balance) due upon completion of the client validation milestone. Specific milestone amounts are in your proposal.

Bundle engagements: Payment is typically structured by component, with each component invoiced at its start. The specific structure is in your proposal.

We accept ACH transfer, credit card, and check. Net 15 terms apply to milestone payments unless otherwise specified.

5. Delivery Process

Sprint engagements follow a structured delivery process:

Kickoff. We schedule a kickoff call to confirm scope, collect access credentials, align on timeline, and identify your point of contact.

Build. We execute the scope of work. During this phase, we may reach out with questions or decision requests. We'll keep you informed of progress at agreed intervals (typically weekly for Core Builds, as-needed for QuickStarts).

Quality assurance. Before presenting the build to you, we conduct an internal review against the scope and acceptance criteria.

Client review. We present the completed build in a live walkthrough. You review the deliverables against the scope defined in the proposal. This is your opportunity to flag issues, request adjustments within scope, or confirm acceptance.

Refinement. Based on your review feedback, we make adjustments that fall within the defined scope. One round of refinement is included. Additional rounds may be scoped separately if the feedback represents scope expansion rather than scope refinement.

Launch and handoff. The build goes live (or is handed off for your team's use). We provide documentation covering what was built, how it works, and how to manage it. A training session is included for Core Builds and Bundles.

6. Acceptance

A Sprint is considered complete when the deliverables described in the proposal have been built, reviewed, and accepted by you. Acceptance occurs when:

• You confirm in writing (email is sufficient) that the deliverables meet the scope defined in the proposal, OR
• 10 business days pass after the client review walkthrough without specific, actionable feedback indicating the deliverables do not meet the defined scope

If you believe the deliverables do not meet the defined scope, provide specific, written feedback identifying which scope items are not met and how. We'll address legitimate scope gaps. Requests for work beyond the defined scope are handled as scope changes (see below).

7. Scope Changes

If additional needs are identified during the engagement that fall outside the defined scope, we'll document them and propose one of the following:

• Add-on to the current engagement: If the additional work is small and clearly defined, we may propose adding it to the current Sprint with adjusted pricing and timeline.
• Separate follow-on engagement: If the additional work is substantial, we'll propose it as a separate Sprint or recommend incorporating it into a FUSE program.

No out-of-scope work is performed without written agreement and adjusted pricing. This protects both sides — you don't receive surprise invoices, and we don't absorb work that wasn't priced.

8. Diagnostic Investment Credit

If your Sprint engagement was preceded by a Foundari diagnostic completed within the prior 90 days, the applicable Diagnostic Investment Credit is shown as a line item on your proposal. The credit reduces the Sprint investment by the amount specified. The terms of the credit program are described in your diagnostic proposal and in Foundari's Diagnostic Investment Credit terms.

9. What Happens After the Sprint

When the Sprint is complete, you have several options:

FUSE (ongoing evolution). If your systems need continuous improvement, we can transition into a FUSE program — an outcomes-driven partnership with quarterly goals and monthly deliverables. Your Sprint experience informs the initial FUSE Outcome Backlog.

PSP (stability support). If you need ongoing support for the system we built — break-fix, minor adjustments, reactive maintenance — a Platform Stability Program provides a governed support wrapper.

Additional Sprint. If another build project makes sense, we can scope a follow-on Sprint.

Stand on your own. If the Sprint delivered everything you need, the system is yours, fully documented, and ready for your team to operate.

We'll discuss these options during the Sprint handoff. There is no pressure to continue — the Sprint deliverables are yours regardless.

10. Intellectual Property

All work product delivered during the Sprint — configurations, automations, templates, workflows, documentation, dashboards, and any custom-built components — becomes your property upon receipt of final payment. You own it. You can modify it, extend it, or have another provider work on it.

We do not retain proprietary claims to delivered work product. We retain ownership of our methodologies, frameworks, and reusable tools that existed before your engagement.

We will not use your name, logo, or business details in any marketing or case study without your explicit written permission.

11. Confidentiality

Same confidentiality provisions as the Diagnostic terms. We treat everything we learn about your business as confidential. This obligation survives the engagement. You agree to treat our methodologies as confidential.

12. Limitation of Liability

Our liability for any claim arising from the Sprint engagement is limited to the total amount you paid for the engagement. We are not liable for indirect, incidental, consequential, or punitive damages.

We build systems to the specifications agreed upon in the proposal. The business results those systems produce depend on how they are used, adopted by your team, and maintained after handoff. We do not guarantee specific business outcomes.

Third-party dependencies. Our work may involve third-party platforms (Zoho, Google Workspace, etc.) that we do not control. We are not responsible for changes, outages, or pricing modifications made by third-party providers after the engagement is complete.

13. Cancellation

Before work begins (before kickoff): Full refund of any deposit paid.

After kickoff but before client review: We'll deliver the work completed to date. Payment for completed work is non-refundable. Any deposit amount exceeding the value of completed work will be refunded within 15 business days.

After client review: The engagement is substantially complete. Full payment is due per the proposal terms. No refund for delivered work.

If Foundari needs to cancel: We'll communicate the reason, deliver all work completed to date, and refund any portion of the fee corresponding to undelivered scope.

14. Warranty

We warrant that the deliverables will function as described in the proposal at the time of handoff. If a defect in our work (not a third-party platform issue, not a change made by your team, not a new requirement) is identified within 30 days of handoff, we'll correct it at no additional charge.

This warranty covers defects in our implementation — things that don't work as specified. It does not cover ongoing maintenance, feature additions, platform updates by third parties, or changes to your business requirements after handoff.

15. Dispute Resolution

Same provisions as Diagnostic terms. Direct conversation first, mediation if needed, binding arbitration under AAA rules in Ohio.

16. Acceptance

By signing the proposal that references these terms, you acknowledge that you have read and agree to these Sprint Engagement Terms. These terms, together with the signed proposal, constitute the complete agreement for this engagement.