The rules behind
the work.

Every project begins with a human review. We assess the problem, clarity of the brief, technical feasibility, fit with our capabilities, capacity, security and ethical considerations, and whether the stated budget appears compatible with the requested scope.

A submission is not accepted automatically. We may request additional information, move a project into discussion, issue a quotation, decline to quote, or reject the project with a recorded reason. Rejection before any work begins does not create a development fee.

A quotation contains the price, currency, scope, deliverables, exclusions, revision limit, expected timeline and any special conditions. It is stored as a versioned record. The client can accept it, request modifications or reject it.

Once accepted, the quotation becomes the baseline. The client cannot unilaterally change approved pricing or scope. Material changes require an authorized change request, which may result in a new quotation version and adjusted timeline.

Estimates and indicative budget ranges are not binding quotations. They are used to align expectations during review.

Project-specific communication takes place in the project thread. Messages, attachments and status changes are retained with the project. Administrative decisions are recorded in the project activity and audit trail.

Do not send credentials, private keys or card information through ordinary messages. A secure handover channel will be agreed where credentials form part of the delivery.

Work begins only after the quotation is accepted and any separately agreed deposit requirement is met. Milestones and progress notes are published to the dashboard. Clients are expected to review updates and provide timely feedback.

Timeline changes caused by client delays, missing dependencies, third-party outages or agreed scope changes are recorded. We do not promise a delivery date that has not been stated in an accepted quotation.

When development is complete, the project enters client review. The client reviews the work against the accepted scope and may request revisions within the stated revision limit. Revision requests outside the accepted scope are handled as new work.

A project is not considered handed over until the completion review is closed, the invoice is paid and verified, and an administrator records the release of final deliverables.

Standard terms: payment after completion and client review, before final handover. Any deposit arrangement must be stated in the accepted quotation.

Payments are linked to a project, client, invoice and provider reference. The platform does not mark a payment successful based on a frontend callback alone. Where a payment provider is configured, server-side verification and signed webhooks are required. Where payment is recorded manually, an authorized finance administrator must verify the external transaction and the action is audited.

Never store raw card information. Use the configured payment provider or an approved bank-transfer process.

Completed professional services are generally non-refundable where permitted by law. This does not override mandatory consumer rights, statutory remedies, fraud protections or obligations arising from non-performance.

We distinguish between:

• Project rejection before any work begins.
• A platform-side inability to deliver the agreed work.
• Duplicate, unauthorized or clearly erroneous transactions.
• Work not performed or materially not as agreed, subject to review.
• Rights that cannot be excluded under applicable law.

Refunds or corrections may be processed by an authorized administrator where legally required or where the verified record supports it. No page on this platform claims that refunds are impossible in every circumstance.

If we cannot take on a project, the project record will show the decision and a client-facing explanation configured by the administrator. You may submit a revised brief in future if circumstances change.

A rejected submission is not an admission that the idea is invalid. It may reflect fit, timing, capacity, clarity, risk or another constraint.

If something has gone wrong, contact support with the project reference before escalating. We will review the accepted scope, project activity, messages, payment evidence and handover record. Where the platform is unable to deliver the agreed work, the situation is handled in good faith and in accordance with applicable law.

We may place a project into Disputed status while a payment, delivery or conduct concern is reviewed. This does not by itself determine the outcome.

This policy is version 2026-01. The version in effect when a project is submitted and when a quotation is accepted is recorded with the project. Questions can be sent to studio@formaproj.com or through contact.