Payment and engagement policy

Working With Our Team vs Individual Developers

• •All official projects handled by Anointed Coder are managed internally through our team structure.
• •We do NOT accept payments through Fiverr or freelance platforms for team-managed projects.
• •If a client chooses to work directly with an individual developer, that relationship is strictly between the client and the developer.
• •Anointed Coder provides no support, guarantees, or oversight for individual arrangements.
• •We are not responsible for delivery, communication, or outcomes outside our team structure.

Payment Method

• •All payments must be processed through our official invoicing system.
• •This ensures proper documentation, secure transactions, and transparent tracking.
• •No informal or untracked payments are accepted.

Upfront Payment Requirement

• •This may increase depending on project size and complexity.
• •It is not negotiable below 25%.
• •No work starts without upfront payment.

Scope & Milestone Agreement

Before payment, the following must be agreed upon:

• •Clear scope must be defined.
• •Milestones must be agreed.

This ensures accurate pricing, structured execution, and no confusion.

Payment Flexibility

• •We support milestone-based payments for larger projects.
• •Payment structures can be flexible based on scope.
• •However, minimum upfront requirements still apply.

Late Payments

• •We may pause work when a required deposit, milestone payment, or approved invoice is overdue.
• •Late payment may mean suspended work, revised timelines, interest where legally permitted, and reasonable collection costs.
• •You may not withhold undisputed amounts because of an unrelated issue. If you dispute an invoice, tell us promptly and in reasonable detail so we can resolve it.

Scope Changes

Any additional features outside the agreed scope will be quoted separately. Changes are welcome but must be documented and priced before implementation.

Changes to scope, features, integrations, timeline, or complexity take effect only through a written change order approved before the work continues. Informal messages, calls, or requests do not automatically change the agreed scope.

Timeline Policy

• •Timelines depend on scope and client responsiveness.
• •Delays in feedback may extend delivery timelines.
• •Timelines and pricing may be adjusted when delays or changes are caused by missing content or credentials, late feedback, delayed approvals, unavailable personnel, third-party vendors, API changes, regulatory review, platform outages, scope changes, unforeseen technical issues, or changes to the agreed assumptions or dependencies.

Client Responsibilities

Clients must:

• •Provide clear requirements, content, and any necessary assets.
• •Supply the credentials and access needed to build, test, and deploy the work.
• •Give feedback and approvals promptly, and keep the right people available.

Refund Policy

• •No refunds once development has started.
• •Partial refunds only if no work has been delivered.
• •Discovery and consultation fees are non-refundable.

Support & Maintenance

• •Limited post-launch support is included.
• •Extended maintenance is available as a separate arrangement.

Ownership & Source Code

• •You receive the source code and ownership of the custom work built for your project after full payment.
• •Our reusable components, libraries, internal tools, and pre-existing materials remain ours, and third-party software, APIs, and open-source components stay under their own licences.
• •Handover (repository access, documentation, and deployment details) is provided once the project is accepted and paid in full.

Acceptance & Warranty

• •Each project includes an agreed review period. We will fix work that materially fails the agreed written specification during that correction period.
• •This does not cover new requests, scope changes, changes you make yourself, third-party failures, unsupported setups, or misuse.
• •We do not guarantee error-free or uninterrupted operation unless we state so in writing.

Compliance & Regulated Work

• •Projects involving regulated, financial, health, gambling, blockchain, or personal data may need additional security, privacy, or compliance terms agreed before work begins.
• •You remain responsible for your own licensing, regulatory compliance, and business model. We build to your specification and are not your legal or financial adviser.