1. Parties and Purpose
This Two-Party Agreement is structured between the Client and Laravelone.co.in. It applies when the Client approaches Laravelone.co.in directly for project delivery, consulting, support, implementation, training, AI integration, or other managed services.
2. Laravelone.co.in Role
Laravelone.co.in remains the primary delivery and coordination owner for the Client. It may use internal team members, verified developers, consultants, vendors, subcontractors, or specialist contributors to complete the work. Laravelone.co.in may manage assignment, quality review, background verification where appropriate, internal payouts, statements, and delivery coordination.
3. Scope, Proposal, and Work Order
Laravelone.co.in reviews the Client requirement and may prepare a proposal, work order, scope note, invoice, milestone plan, hourly plan, retainer, assumptions, exclusions, timeline, and commercial terms. Work begins only after written acceptance and receipt of required payment or advance.
4. Client Responsibilities
The Client must provide accurate requirements, access, content, credentials, approvals, third-party account access, test data, brand assets, and timely feedback. Laravelone.co.in is not responsible for delay, additional cost, or incomplete delivery caused by missing client inputs, unclear scope, delayed approvals, unavailable third-party accounts, or client-side blockers.
5. Milestone, Hourly, and Retainer Tracking
Project-based work may be tracked through milestones, demos, review checkpoints, issue lists, and completion records. Hourly work may be tracked through time logs, work summaries, billing cycles, and supporting data. Retainer work may be tracked through monthly hours, priority support, available capacity, or agreed service limits.
6. Payments, Taxes, and Billing
The Client pays Laravelone.co.in according to the agreed milestone, retainer, hourly cycle, support plan, course fee, or project payment schedule. Applicable GST, TDS/TCS where relevant, gateway charges, bank charges, third-party costs, and statutory fees may apply. Payment delays may pause delivery, support, deployment, access, or handover.
7. Contributors, Payouts, and Commission
Where Laravelone.co.in assigns developers or contributors, Laravelone.co.in manages contributor selection, internal commission, payout calculation, payout timing, deductions, tax records, and settlement. The Client's contractual payment obligation remains to Laravelone.co.in unless a separate written triparty arrangement is signed.
8. Acceptance, Revisions, and Handover
The Client should review deliverables within the agreed review period and provide specific written feedback. In-scope defect correction may be included during the review period. New features, cosmetic changes, changed business rules, third-party API changes, or issues caused by client-side modifications may require additional fees. Final handover may include code, documentation, deployment notes, credentials transfer, or other agreed materials after payment completion.
9. Intellectual Property
Subject to full and final payment, custom project deliverables may be assigned or licensed to the Client as stated in the accepted work order. Laravelone.co.in retains ownership of pre-existing frameworks, reusable components, internal tools, templates, generic workflows, training content, demos, and know-how unless expressly assigned in writing. Open-source and third-party materials remain governed by their respective licenses.
10. Confidentiality and Security
Laravelone.co.in will use reasonable care to protect confidential Client information and project access. The Client must provide only necessary access, maintain backups, rotate credentials after completion, and avoid sharing sensitive data that is not needed for delivery. Security audits, penetration testing, compliance certification, or regulated-data handling must be expressly included in the scope.
11. Third-Party Services
The Client is responsible for third-party services such as hosting, domains, payment gateways, email/SMS services, AI APIs, app stores, SaaS subscriptions, paid libraries, and usage charges unless expressly included. Laravelone.co.in is not liable for third-party outages, price changes, API changes, account suspensions, or policy changes outside its reasonable control.
12. Refunds, Cancellation, and Project Pauses
Refunds and cancellations are handled according to the Refund and Cancellation Policy and the accepted scope. Amounts paid for completed work, work already commenced, reserved capacity, third-party expenses, gateway charges, taxes, and digital access may be non-refundable. Laravelone.co.in may pause work for non-payment, scope ambiguity, security risk, abusive conduct, unlawful requests, or unresolved dependencies.
13. Compliance and Legal Use
The Client must not request unlawful, infringing, deceptive, abusive, malicious, or unauthorized work. The Client is responsible for ensuring that its business model, content, data processing, payment flows, consumer terms, licenses, regulated-sector obligations, and tax treatment are legally compliant.
14. Indemnity
The Client agrees to indemnify Laravelone.co.in, its employees, contractors, and representatives from claims arising from client-provided content, unlawful instructions, intellectual-property infringement, third-party account misuse, inaccurate data, non-payment, tax non-compliance, or breach of this agreement.
15. Limitation of Liability
To the maximum extent permitted by law, Laravelone.co.in is not liable for indirect, incidental, consequential, punitive, loss-of-profit, loss-of-data, loss-of-business, or business interruption damages. Laravelone.co.in's aggregate liability for a specific managed engagement is limited to the amount paid by the Client for the disputed engagement during the preceding three months, unless applicable law requires otherwise.
16. Force Majeure
Laravelone.co.in is not liable for delay or failure caused by events beyond reasonable control, including natural disasters, epidemic, pandemic, fire, flood, war, terrorism, civil unrest, labor disruption, government action, court order, changes in law, power failure, internet outage, cloud provider outage, payment gateway failure, cyberattack, or third-party dependency failure.
17. Governing Law and Jurisdiction
This agreement is governed by and construed in accordance with the laws of India. Any disputes arising out of or in connection with this agreement shall be subject to the exclusive jurisdiction of the competent courts in Kerala State, India.