General Terms (application development)

1. What this covers (and what it doesn't)

• These terms apply to custom application development (design, build, iterations, delivery).
• Hosting/operations/support after delivery only apply if explicitly agreed (e.g. in an SLA).
• Customer purchasing terms do not apply unless we accept them in writing.
• In case of conflict: (1) agreement/quote + scope, (2) DPA (privacy), (3) SLA (if any), (4) these terms.

2. How we work (modern, iterative)

• We work in short cycles: working previews, frequent releases, clear progress. Less meetings, more shipping.
• Scope is direction + priorities. We learn as we build and adjust based on reality.
• Async by default, sync when it matters (decisions, alignment, demos).

3. What we need from you

• One empowered product owner (feedback + decisions).
• Timely input: goals, content, brand assets, access to systems, test accounts, etc.
• If input is missing, timeline and cost may shift. We then decide together: pause, continue on assumptions, or simplify scope.

4. Timeline, delivery and expectations

• We plan based on what we know today. Dates are indicative unless explicitly agreed as strict deadlines.
• We prefer incremental delivery: each increment is usable and can go live unless agreed otherwise.
• We don't guarantee business outcomes (conversion/revenue). We build software; impact is a shared job.

5. Scope, changes and additional work (flexible, not vague)

• We don't lock scope just to pretend certainty. We steer on value, priority and clarity.
• A request is additional work if it falls outside the agreed scope or requires extra effort beyond the agreed budget.
• No bureaucracy needed: a short change message with (a) what, (b) why, (c) impact on time/cost, (d) your approval is enough.
• We handle change by swapping scope, adding budget, or timeboxing to 'good enough'.
• If requirements are intentionally open, we steer on outcomes and priorities (not on a locked spec document).

6. Acceptance without the drama (rolling acceptance)

• Acceptance is continuous, not one big final sign-off.
• For each delivery you have 7 days to report blocking issues (reproducible, with steps). We can adjust that period if needed.
• Minor issues don't block acceptance. We put them on the backlog and plan them.
• Using the software in production counts as acceptance of what's live at that moment.
• We fix defects based on impact (severity), not on who shouts the loudest.

7. Fees, invoicing and payment

• Fees are in EUR and exclude VAT unless stated otherwise.
• We work fixed scope/fixed price or time & materials (or a mix). This is stated in the quote.
• We invoice per phase, monthly or based on hours (as agreed). Payment term: 14 days unless agreed otherwise.
• If payment is late, we may pause work. We may charge interest/collection costs as legally permitted.
• We may request (partial) prepayment or additional security when reasonable.

8. Intellectual property (ownership, no lock-in)

• After full payment, IP rights in the custom deliverables transfer to you unless agreed otherwise.
• Frameworks, libraries, open source and standard components remain under their respective licenses.
• We deliver source code in a repo (preferably in your org). You keep the keys.
• We may reuse general know-how and generic building blocks, without reusing or leaking your confidential information.

9. Third-party licenses and accounts

• We may use third-party tools/services where it makes sense (e.g. analytics, email, maps, hosting).
• Third-party costs (licenses, APIs) are charged through if agreed or reasonably necessary.
• You provide/authorize production accounts and access unless agreed otherwise.
• If a third party fails (API outage, vendor policy change), that's not automatically our liability. We'll help mitigate if needed (may be additional work).

10. AI tooling (speed without burning your secrets)

• We use modern dev tools (including AI) to build faster.
• We treat your code/data as confidential and avoid putting sensitive data into public AI tools when not necessary.
• If your project has stricter constraints (no external tooling), we align upfront and adjust our workflow.

11. Security, privacy and GDPR

• We apply reasonable security measures and follow common best practices, but no system is 100% risk-free.
• If we process personal data for you, a DPA applies: you are controller, i7 is processor.
• You decide what data is processed and confirm you are allowed to process it.
• You remain responsible for your content, legal texts and compliance settings unless explicitly agreed otherwise.

12. Confidentiality

• We keep confidential information confidential (also after the project ends).
• We impose the same duty on any third parties we engage.

13. Warranty and bugfixes

• We aim for high quality, but software is complex and never perfect.
• After acceptance, a 3-month bugfix period applies for reproducible defects within scope (not new features).
• Issues caused by changes in third-party services, browsers or your environment are not automatically included.
• Outside that period we can help based on a new agreement (support retainer, SLA, or hours).

14. Liability (fair, not unlimited)

• We are only liable for direct damages caused by a material breach after written notice and a reasonable remedy period.
• Liability per event is capped to the fees paid by you in the relevant year (ex VAT), with a maximum of €25,000 (ex VAT).
• We are not liable for indirect damages and not for third-party software/services failures.
• These limitations do not apply in case of intent or willful recklessness of our management.
• You must report damages within 30 days after you discovered (or should have discovered) them.

15. Force majeure

• Force majeure may suspend obligations. If it lasts longer than 30 days, either party may terminate in writing with pro-rated settlement.

16. Termination, pausing and handover

• You can stop. We can stop. We'll agree how to wrap up and what to hand over.
• If you materially breach (e.g. non-payment), we may pause or terminate.
• We support handover; handover hours are invoiced at the agreed hourly rate.
• Work delivered up to the termination date remains payable (plus any reasonable costs incurred).

17. Portfolio (only if it fits)

• We like to show what we build.
• We only use your name/logo or case details with your permission. For sensitive projects: default no.

18. Updates to these terms

• Sometimes terms must evolve (law, security, tooling).
• If we update these terms, we will announce it in time. For ongoing projects, changes only apply when reasonable or legally required.

19. Law and disputes

• Dutch law applies.
• Disputes go to the competent court in Rotterdam (NL), unless mandatory law says otherwise.