From payment to production: what actually happens

Unlike the other articles in this series, this one is not general industry knowledge — it describes AlphaBlue’s own delivery process, so you know what to expect after payment and what we’ll need from you along the way. Other providers work differently; this is how we work.

The journey at a glance

Stage	What happens	What we need from you
1. Payment and onboarding	We confirm the purchased scope, project contact and the material still needed	Share or confirm the available business information and assets
2. V1 design direction	We prepare a viewable direction for the visual tone, color, main layout, information hierarchy and primary calls to action	Decide whether this is the right direction and give one consolidated round of feedback
3. V2 detailed build	After V1 approval, we develop the agreed pages with real content, responsive details and in-scope forms or integrations	Check facts, content, actions and the agreed feedback points in the complete preview
4. QA and production	We test the approved site, confirm public details, domain, forms and handover responsibilities, then publish	Approve publication and verify the live result

Before V1: payment does not mean every material is already complete

Payment confirms the project and its purchased scope. It does not mean you must arrive with a finished sitemap, polished copy and a folder of professional photographs. We can begin from a business name, a short explanation, posters, a social page or an existing profile, then organize what is usable and identify what is still needed.

The delivery schedule starts from the material-readiness point stated for the order, not simply from the payment timestamp. This keeps the timing tied to inputs the build actually depends on.

V1: approve the design direction

V1 is a design-direction proposal, not the final detailed website. It lets you judge concrete choices that are difficult to describe from a blank page:

• how the logo or wordmark is used;
• the color and visual character;
• the main layout and information hierarchy;
• the direction of the primary calls to action.

Some non-critical content may still be clearly marked as placeholder. That is intentional: V1 asks whether the overall direction is right before detailed work is built on top of it. Only after you approve that direction — or explicitly ask us to proceed from it — does the project enter V2 and the direction becomes the basis for detailed production.

V2: review the real content and working details

V2 develops the approved direction into the agreed website: real service information, copy, images, responsive details, and the forms or integrations included in the written scope. This is the right stage to check:

• names, prices, hours, policies and other facts;
• whether each page explains the business correctly;
• whether buttons, contact paths and forms do what was agreed;
• whether the consolidated V1 feedback has been carried through;
• whether anything is missing from the purchased scope.

The number of included feedback rounds depends on the package and order confirmed at purchase. A correction within the agreed direction is a revision. A new store, portal, payment flow or other materially new requirement is a scope change: it is welcome for discussion, but it is assessed separately rather than being silently added to a revision round.

QA, production and handover

After final approval, we verify the public business details, responsive display, contact actions, in-scope form submissions, domain and security setup, and the production version. We then publish and hand over the access and ongoing-service responsibilities included in the order.

If the project is waiting for a customer decision or material, we record that state rather than pretending work can continue without the required input. The applicable response windows, restart conditions and any additional fee must come from the order terms, not from an improvised promise in chat.

If you need to cancel

AlphaBlue’s current policy allocates the one-time website build fee across four earned milestones:

Milestone	Current allocation
Project start and requirements	5%
V1 design direction	30%
V2 detailed production	45%
QA, publication and handover	20%

If a customer cancels, completed milestones and evidenced work already performed in the current milestone are taken into account. As a reference, cancellation before human work starts can leave 100% of the one-time website build fee refundable; after project start and requirements, 95%; after V1 has been sent, 65%; and after the complete V2 preview, 20%. After publication and handover, there is no change-of-mind refund for that completed build. Actual non-refundable payment or third-party costs are considered only where they were disclosed, incurred and allowed by applicable law.

These are reference positions for customer-initiated cancellation, not a limit on statutory rights or remedies where AlphaBlue has not performed, a material defect exists, or the delivered work does not match the written scope. The exact calculation, partial work, legal protections, payment-channel rules and processing time are governed by the current Refund and Cancellation Policy. Staff should not invent a percentage or promise a refund amount in conversation.

---

This article describes AlphaBlue’s current delivery process at a customer-facing level. The purchased order, current package page and Refund and Cancellation Policy remain authoritative for scope, feedback rounds, timing and cancellation terms.