Clear answers before
the project begins.

Ready-to-Build products have published starting prices for a predefined core scope. Custom Development is quoted after requirements review because the architecture, functionality and delivery needs are specific to the project.

It is the starting price for the stated core scope. Add-ons, integrations, custom requirements and third-party services can change the final project price.

No. The displayed total is indicative until Clear Handover Labs reviews the configuration and confirms the final Scope of Work, project price and estimated delivery schedule.

Payment milestones are set out in the approved proposal or project agreement. Development begins after scope approval and the required commencement payment; the full project price is not taken from the initial configuration.

Only where the scope or additional requirements change, or where agreed external assumptions require revision. Any resulting price or schedule impact is confirmed before the related work proceeds.

A predefined product architecture and core feature set that provides a faster, more predictable starting point than beginning from a blank specification.

Yes. Branding, selected functionality, available add-ons and appropriate integrations can be configured within the product's supported architecture.

We review the requirement and may provide an add-on, a custom quotation or recommend Custom Development where the change would materially alter the standard product.

Yes. Additional functionality can be scoped after launch through a separate project, Change Request or suitable Care Plan.

Yes. Custom Development covers mobile applications, web platforms, SaaS products, marketplaces, AI-powered products, business systems, automation and suitable existing-product work.

Submit the project brief with the business idea, problem, users and likely requirements. You can then choose a 30-minute discovery call or continue by email.

No. You can begin with the business idea, problem or desired outcome. Discovery and requirements review help translate that context into a defined product scope.

We discuss the objective, users, key workflows, priorities, constraints, likely integrations, indicative budget and target timing. It is not a commitment to begin development.

Ready-to-Build timelines vary by product and configuration. Custom-project schedules are confirmed after requirements review and depend on scope, integrations, approvals and customer dependencies.

The Scope of Work is the approved definition of deliverables, included functionality, assumptions, responsibilities, exclusions, price, schedule and payment milestones for the project.

The new requirement is assessed for its effect on scope, price and delivery. Work proceeds only after the impact and route forward are confirmed.

A Change Request is the structured process used to document, assess and approve work outside the current Scope of Work.

Depending on the project, this may include timely feedback and approvals, content, brand assets, policies, third-party accounts, access, data and subject-matter decisions.

Yes, where AI serves a defined purpose such as assistance, matching, document understanding, search, recommendations or workflow automation.

Provider and model selection depends on the project requirements, data, expected usage, capability, region, risk and commercial constraints.

No. AI outputs can vary and may be incomplete or incorrect. Appropriate user communication, controls and human review should be defined for the context, especially for high-stakes decisions.

Unless explicitly included in the proposal or Care Plan, third-party AI usage and subscription charges remain separate from Clear Handover Labs development pricing.

Ownership, source-code access, licensing, reusable components and intellectual-property terms are defined in the project agreement before development begins.

Developer-program, store and related provider fees remain the customer's responsibility unless the approved proposal explicitly includes them.

Cloud and hosting costs are separate unless a stated allowance is included in the proposal or Care Plan.

Payment-gateway account, transaction and related fees are charged under the provider's terms and remain separate unless explicitly stated.

External API subscriptions and usage charges remain separate unless specifically included in the approved project or Care Plan scope.

It covers defects where agreed delivered functionality does not operate according to the approved Scope of Work during the 30 days after launch.

Support, maintenance and further development can continue through a Care Plan, separately scoped work or an approved Change Request.

A Care Plan is not automatically required, but it provides defined ongoing support for products that depend on hosting, third-party services, integrations, operating systems or continuing development.

Yes. Ongoing improvements, new features, integrations and optimization can be planned through an appropriate support or development arrangement.

Yes. Arabic and English functionality can be included where it forms part of the approved project requirements.

Yes. Right-to-left interface support can be designed and built where it is included in the project scope.

Yes. Clear Handover Labs is being established in the United Kingdom with a focus on businesses across the GCC, Arab markets and internationally.