Terms of Service

iMORPHr provides professional software services, including business consulting, Frappe and ERPNext implementation, application configuration, workflow design, integrations, custom module development, reporting, system enhancements, DevOps and related technical advisory work.

These terms apply to use of this website and to service engagements unless a separate signed agreement, statement of work or proposal expressly overrides a specific section.

Work usually begins from a written proposal, statement of work, estimate or email confirmation that describes the expected scope, deliverables, commercial model and assumptions. Unless explicitly stated otherwise, timelines and effort estimates are based on information available at the time they are prepared.

If project facts change, hidden complexity appears or the client requests work outside the agreed scope, iMORPHr may update the timeline, fees, milestones or recommended approach before continuing.

The client is responsible for providing timely access, approvals and accurate information needed to perform the work, including:

• business process details, sample data, and required workflows
• access to hosting, ERPNext/Frappe environments, source code and third-party accounts
• named decision-makers who can review and approve milestones promptly
• lawful rights to the data, software, credentials and systems supplied to us

Delays in client responses, unavailable stakeholders, incomplete specifications, or inaccurate information may delay delivery and may require replanning.

Fees may be fixed-price, milestone-based, retainer-based or time-and-materials, depending on the engagement. Payment terms will be stated in the relevant proposal or invoice. Unless otherwise agreed in writing, invoices are due within the stated payment period and may pause ongoing work if they remain overdue.

Taxes, government charges, payment gateway fees, hosting costs, licensed third-party tools and other pass-through expenses are the client's responsibility unless expressly included.

Software projects often depend on third-party APIs, hosting providers, open-source packages, framework upgrades, client-side testing and internal business decisions. iMORPHr is not responsible for delays caused by those external dependencies or by client-side inactivity.

Material changes to scope, data migration complexity, reporting requirements, integrations or user acceptance expectations may be treated as change requests and priced or scheduled separately.

Subject to full payment of undisputed fees, the client receives rights to the custom deliverables specifically created for the client under the applicable engagement, excluding iMORPHr pre-existing materials, reusable know-how, internal tools, templates, accelerators and general development practices.

Open-source components, including Frappe, ERPNext, Elixir, Phoenix, libraries and community packages, remain subject to their own licenses. Nothing in these terms transfers ownership of third-party software.

iMORPHr may configure, extend or integrate third-party services, cloud platforms, plugins, payment tools, messaging services or client-managed infrastructure. We do not control those services and are not responsible for their outages, pricing changes, security incidents, feature removals or policy changes.

The client remains responsible for maintaining appropriate vendor accounts, subscriptions, backups, access controls and legal compliance for the systems it owns or operates.

Unless a separate support or maintenance arrangement exists, delivery of a project, enhancement or milestone completes the relevant engagement obligation. Any post-go-live fixes, optimisation, enhancements, hosting assistance or operational support may be handled under a new scope or support plan.

The client should review delivered work promptly and raise acceptance issues within a reasonable period. If no material issue is raised after delivery or go-live, the work may be treated as accepted.

Each party should treat non-public business, technical, commercial and operational information received from the other party as confidential and use it only for the purpose of the engagement. This does not apply to information already public, independently developed or lawfully obtained from another source.

iMORPHr will perform services with reasonable skill and care consistent with normal professional practice. Except for that commitment, the website, advice, deliverables, code, integrations and services are provided on an "as is" and "as available" basis.

We do not warrant uninterrupted operation, bug-free performance, fitness for a particular business outcome or compatibility with every third-party environment, especially where the solution depends on external providers, evolving open-source ecosystems or client-managed infrastructure.

To the maximum extent permitted by law, iMORPHr will not be liable for indirect, incidental, special, consequential, exemplary or punitive damages or for loss of profits, revenue, data, business opportunity, goodwill or anticipated savings.

To the maximum extent permitted by law, iMORPHr's aggregate liability relating to the website or any engagement governed by these terms will not exceed the amount actually paid to iMORPHr for the specific services giving rise to the claim during the six months preceding the event that caused the claim.

Either party may end an engagement for material breach if the breach is not cured within a reasonable period after written notice or as otherwise stated in the applicable proposal or agreement. On termination, the client remains responsible for fees accrued for work performed up to the termination date.

iMORPHr may update these website terms from time to time. The latest version will be published on this page with the updated effective date.

For legal or commercial questions about these terms, please contact iMORPHr through the website contact page before starting a project.