Clear scope. Clear expectations.

Last updated 16 October 2026

These are the working principles of the PatchDispatch marketplace. Builders post requests for their apps. Developers discuss the work and propose a scope, price, and delivery estimate. The parties agree the details before starting work.

Enquiries and assessment

Posting a request does not commit you to a developer or a purchase. Only post projects you are authorised to share. Published requests and their screenshots are visible to signed-in developers; conversations and proposals remain private to their participants.

Proposals and price agreements

A developer's proposal specifies the included scope, price in USD, and estimated delivery days. The builder can accept or decline it. A new proposal replaces a previous pending proposal in that conversation. Only one proposal can be accepted for a request. Account profiles are member-provided and do not imply platform verification or certification.

Work and payment

Accepting a proposal records a scope and price agreement and marks the request in progress. This version does not charge, collect, hold, or release funds. Agree payment arrangements, the provider's identity, access, dependencies, third-party costs, taxes, and any job-specific terms separately before work. Additional work requires a new agreement.

Delivery and review

Deliveries include the agreed changes, a demonstration where practicable, relevant checks, and plain-language notes. Code delivery and production deployment are separate unless the quote includes both. Production changes require the agreed authorisation.

Agree review periods, adjustments, support, and acceptance checks in the proposal before work starts. The builder marks the request complete after checking the result. Marking complete does not represent a payment or remove applicable customer rights.

Ownership and access

You retain ownership of your existing project. Rights in commissioned work, any third-party components, confidentiality, and access are specified in the written agreement. You must be authorised to share the project and grant the access needed.

Changes, cancellation, or a blocker

If the work cannot proceed as agreed, the parties should discuss what was completed, what is blocking progress, and the next options. Cancellation and refund handling follow the job agreement and applicable obligations. A launch check is limited to the checks listed in the scope; it is not a comprehensive security certification.

Questions

Use your project conversation to clarify the work. For questions about using PatchDispatch, use the contact form.