Only O1 and O2 use build-first, when included in the agreed proposal.
How build-first acceptance works
A commercial explanation for our website and business autopilot offers. Your written proposal confirms the details before any work begins.
Agree the complete scope, exclusions, inputs, access, build fee, review and handover terms first.
Review the whole functional build. Incomplete dependencies mean the build is not complete.
Explicit acceptance is your choice. Passing tests, review access and silence do not authorise a charge.
Decline and owe no build fee. No development deposit.
Agreed build and testing costs are covered before your decision. No mandatory incremental purchase is needed to review.
Your agreement sets the review window and refinements. Defects and new requirements are treated separately.
Evaluation access does not grant production use. Handover follows the agreed acceptance and payment terms.
Your supplied materials stay yours. Return, retention and removal arrangements are agreed.
Hosting, subscriptions, usage, care and future improvements require their own disclosed terms.
A summary, not a signed agreement.
Eligibility, inputs, complete scope, fee, review arrangements, data handling, handover, and support must be confirmed in the written proposal. This page does not create an order or authorize a charge.
What would you love
to take off your plate?
Tell us what’s getting in the way. We’ll start there.
Let’s find your first winClear scope. Real examples. No pressure to buy.