A clear plan, shared responsibilities.

What happens, and who does it.

1. Describe the need

   You describe the business, your customers and what the website should help them do. The public planner provides a preliminary range; I review the request before quoting.

2. Agree the scope and price

   I prepare the proposal, inclusions, outside costs and exact BPS price. You review it and record your decision; BPS acceptance is recorded separately. For paid projects, the 20% deposit must be verified before onboarding is authorized.

3. Complete your invited workspace

   I issue the project invitation. You provide the guided answers, rights-cleared logos, photos, content and provider details. I review them and request clarification or explicitly approve any asset waiver. Do not upload passwords or verification codes.

4. I prepare and build

   The approved plan, materials and checklist guide the private build. I select the foundations, create the customer-specific design, configure the agreed features and test them. The workspace organizes the work; it does not automatically finish or launch the website.

5. Review one clear version

   You review the website and provide the one consolidated revision included in your proposal, where applicable. I make the agreed changes and return the revised version. New scope or additional rounds are reviewed and quoted separately.

6. Approve and prepare launch

   You approve the finished version. The remaining balance is due after that approval, before launch. You authorize any required provider access; I confirm account readiness and the agreed release checks. Payment does not replace final approval.

7. Launch and hand over

   I release the approved site in the agreed customer-controlled environment, check its live entry points and provide the source and operating handoff. The 30-day defect-correction window follows launch under the agreed terms.

Facts from you. Website copy shaped with your permission.

You provide or approve the facts about your business and the wording you want to keep. Within the agreed content scope, you choose whether I lightly edit your text, use it exactly as supplied, or draft missing copy from your facts for your review. You approve the final facts and wording before launch.

Additional copywriting, research or pages beyond the agreed content scope are reviewed and quoted separately. Policy drafting is included only when specifically agreed.

A schedule agreed for your project.

Your project schedule is agreed during scope review. Timing depends on project complexity and the availability of required content, assets, access and customer approvals. Your requested timing in the planner starts the discussion; it is not a promised delivery date.

A checklist with recorded results.

The Website Build Master Checklist stays with the project packet. Relevant checks cover the selected features, content, access, testing and handoff. Items that do not apply remain marked N/A. Including the checklist is not the same as completing its checks; I record results and unresolved provider work before release.

What you control, and what stays dependent.

Your domain and selected provider accounts stay under your control, with provider bills paid directly. The agreed handoff includes project source, approved content and assets, account and deployment information, and operating guidance for you or another qualified developer.

The handoff is designed so another qualified developer can take over your website if you choose to move away from BPS.

Source delivery is subject to the agreement and applicable licenses. It does not transfer ownership of BPS Factory technology or third-party software. The selected hosting and services remain dependencies; moving to another host may need development work.

There is no mandatory BPS website-management subscription. You remain responsible for provider renewals, account access and ongoing maintenance after handoff. The agreed 30-day defect-correction period follows launch; new pages, redesigns, extra features and later changes are separately scoped. A customer backup schedule and recovery checks must be configured for the delivered system.

Keep the existing site working while I build.

The replacement is prepared privately. After review and provider readiness, I plan redirects and the controlled cutover, verify the live paths and retain rollback information during stabilization. Domain changes require your authorization.

You approve provider subscriptions and enter authentication or consent steps yourself. Their charges, policies and availability remain separate from BPS work.

Start with what you know.

Explore price and scope, Start a project, or explain a question first. Existing projects can use website support.