How Should Website Design Payments Work?

A website payment schedule should protect the developer's reserved time without forcing the business to pay for an undefined promise. For a small, well-scoped business website, payment in full or a 50/50 split may be reasonable. Larger redesigns, migrations, ecommerce work, and custom functionality may need staged payments.

The percentage matters less than what exists when each payment is due. A deposit should follow a written page and feature scope. Final payment should follow a review of the agreed website and a defined handoff or launch process.

What a website deposit is supposed to do

The developer allocates calendar time, begins information architecture and content work, prepares the design system, and may configure project services before a live site exists. An initial payment confirms that the business is ready to provide decisions and materials.

A deposit should not purchase a mystery. Before paying, the business should know the page inventory, included functions, content responsibilities, design process, estimate, schedule assumptions, and ownership terms.

Common website payment schedules

Full payment for a small defined job

Paying in full may be sensible for a brief repair, landing page, focused performance improvement, or other short engagement with a provider the business has evaluated.

For a complete website, full advance payment concentrates risk on the buyer. If this structure is used, require a precise scope, review checkpoints, account visibility, start date, cancellation treatment, and delivery definition.

Fifty percent to start and fifty percent at acceptance

This is simple and proportionate for many small-business websites. The first payment reserves and starts the work. The second follows completion of the approved pages and functions.

The agreement should identify whether final payment occurs before production launch, immediately after launch, or after a short acceptance window. It should also state what the client receives after payment.

Three or more milestones

A larger website may divide payment across discovery and content structure, approved design direction, completed development, migration and quality review, and launch.

Each stage should create something inspectable. "Design complete" might mean approved high-fidelity layouts for named page types. "Development complete" might mean all scoped pages and forms work in staging across the supported devices.

Hourly or periodic billing

Hourly billing can fit repair work, ongoing iteration, complex migrations, and projects whose requirements will evolve. It should include a rate, estimated range or cap, reporting cadence, and approval rule for work outside the current scope.

A buyer comparing models should read why website design quotes differ; the same seven-page request can include radically different content, design, migration, and quality work.

Example schedule for a $3,000 business website

At Vertinus's published $49.99 hourly rate, $3,000 represents roughly 60 hours. A focused informational site could use:

• 50 percent to begin: approve the page list, included functions, content plan, estimate, schedule, and account responsibilities.
• Review checkpoints: confirm structure, message, visual direction, responsive pages, forms, and launch details while work progresses.
• Final balance at acceptance: verify the scoped pages and functions, resolve blocking defects, and complete the ownership and launch handoff.

The companion guide explains what a $3,000 website budget can realistically build and which additions tend to exceed that boundary.

How Vertinus website billing works

Vertinus creates a written scope and estimated hours before work begins. The client may pay in full or use a 50/50 schedule for the approved estimate.

Project work is billed at $49.99 per hour for time actually worked, up to the approved estimate. Vertinus absorbs extra hours needed to complete the agreed scope. Client-requested additions are estimated and approved separately.

After final payment, the client owns the completed project code, interface work, and project-specific deliverables. The client also remains the owner of the domain, including when Vertinus manages it under optional Managed Website Care.

Content delivery is part of the schedule

Website projects often wait on service details, team biographies, testimonials, photography, legal language, prices, locations, credentials, and final approval. A payment schedule cannot solve missing business facts.

The scope should state what the client supplies, what the developer drafts or edits, when materials are due, how delays affect the launch, and whether additional rewriting is billable.

A fair agreement does not require the developer to hold a launch slot indefinitely while content is missing. It also should not declare unfinished placeholder pages accepted merely because the client was late.

Define revisions without using "unlimited"

A revision adjusts an approved direction within scope. A change adds a page, function, integration, audience, language, or substantially different direction.

Instead of promising unlimited revisions, define the review points, responsible approver, feedback method, response window, and included type of correction. Consolidated feedback from one decision-maker usually protects the budget better than a nominal round count.

Connect final payment to website acceptance

Acceptance criteria for a business website may include:

• Every scoped page exists with approved content.
• Navigation, calls to action, forms, and confirmations work.
• The site responds correctly on agreed browsers and screen sizes.
• Page titles, descriptions, canonical URLs, sitemap, and indexing controls are configured.
• Images are optimized and performance is reasonably tested.
• Accessibility checks appropriate to the scope are complete.
• Analytics and consent behavior are configured where included.
• Redirects and migration checks are complete where applicable.
• Domain, hosting, repository, and administrator access are documented.

Agree on the treatment of minor defects. Blocking problems may prevent acceptance; small non-blocking items can enter a written correction list with dates.

Keep hosting and care separate from the build payment

A website quote may combine design, development, domain, hosting, software licenses, maintenance, edits, and search services into one number. Separate them so the business can compare the initial build with the continuing obligation.

Vertinus Managed Website Care is optional at $50 per month. It covers managed hosting, one standard-priced domain, DNS, SSL and CDN configuration, monitoring, backups, deployment management, and reasonable routine technical maintenance. New pages, copy changes, features, integrations, premium tools, and unusually high usage are separate.

Plan for cancellation and handoff

The agreement should explain written notice, fees earned for completed work, unearned payment treatment, delivery of usable work in progress, domain and account transfer, replacement hosting, and the deadline for retrieving materials.

If the developer controls the registrar, production account, or repository, confirm the transfer process before paying the deposit. The client should not discover during a disagreement that leaving means losing the domain or rebuilding the site.

Website payment warning signs

• A large full payment is requested before the pages and features are defined.
• The deposit is described as nonrefundable without explaining cancellation or earned work.
• There is no staging review before the final balance.
• The developer owns the domain or refuses account access.
• Final payment depends on subjective "satisfaction" rather than acceptance criteria.
• Content, revisions, and client delays have no written process.
• Hosting, licenses, and renewal charges are hidden inside the project price.
• Search rankings or lead volume are guaranteed as conditions of the build.
• The business cannot receive the code and move to another provider.

Use payment to confirm progress, not create conflict

A good website schedule keeps scope, client decisions, visible progress, payment, launch, and ownership aligned. Neither side should reach the end believing that a different project was promised.

When comparing providers, normalize the exact deliverables first and then compare when money becomes due.