CLEAR EXPECTATIONS

Before a project
begins.

These notes explain the inquiry process. Your accepted written proposal defines the terms of a specific project.

Inquiries are free

Submitting an inquiry allows Bay Area Apps to review your idea and respond. It is not a purchase, a reservation, an agreed deadline, or a guarantee that a project will be accepted.

Scope and approval

Work begins only after the parties agree to a written proposal and any stated deposit or other start conditions are met. That proposal should identify deliverables, price, milestones, review points, supported platforms, and what is outside the scope.

Changes and ongoing costs

New features or changes outside the accepted scope may require a revised quote and timeline. Domain, hosting, external service, and maintenance costs should be identified in the proposal rather than assumed to be included.

Payments

Use only the verified payment request associated with your project. The actual methods offered depend on the business payment account and your checkout. A click on a payment link does not establish that a payment was received. The project workspace distinguishes payment requests from verified payment records.

Ownership and handoff

The written proposal should explain ownership of source files, designs, domain names, service accounts, and supplied content. Any transfer conditions, third-party licenses, final acceptance process, and support period must also be agreed there.

Private project links

A private client link grants access to that project’s information. Keep it confidential and contact Bay Area Apps if it is lost or exposed. Public sharing of your project or a portfolio case study requires separate agreement.

Other Bay Area Apps brands

Pet-care and catering services have their own service descriptions and policies. These development-project notes do not replace those policies.

Questions

Contact info@bayareaapps.com before accepting a proposal if any part of the scope or payment arrangement is unclear.