The short answer: phased delivery starts with an overall picture of the project, then decides what the company needs now and what can wait. Each phase has a scope, cost, deliverables and an acceptance criterion, with documentation the next phase builds on. The aim is to spread the investment by priority and reduce repeated work, while any future change stays easy to assess and price. “Without paying twice” means less rework and duplicated cost, not a guarantee that nothing is ever redone.
In 40 seconds
Related: Web Design Services — or see every industry we serve in B2B marketing.
- Splitting an invoice is the same work with no agreed plan, so something gets rebuilt; phasing is one overall picture, then a first phase the rest builds on.
- Six lines per phase: scope, cost, deliverables, acceptance criterion, what you provide, exit terms.
- Phase order combines technical readiness, commercial priority and financial capacity; a launch date or cash flow can legitimately move a phase.
- A simple project may suit a single delivery; a broader growth plan can grow gradually from a small start.
“If we split it, we will pay more in the end, and the company will leave us halfway”: what is right in that fear
Owners of construction, engineering and manufacturing companies raise this whenever the project grows beyond a simple website. Most of it is justified. Price each part when its turn arrives, with no picture connecting them, and you pay more: every part is re-quoted, and part three is built on a part one never designed to carry it. End the relationship halfway without documentation and you hold half a website nobody else can easily finish.
The error is in the conclusion: “so I pay for everything at once or I do not start.” Agree the overall picture first. Start with a first phase that settles what the rest builds on, then execute the phases by what the company needs now and what can wait, each with an acceptance criterion and exit terms, its outputs yours and documented even if you stop. Phasing does not require a particular project size; whether it fits is decided by scope, priorities and budget, not by a financial threshold. Part one covered why to begin with a clear first phase; this article covers the phases after it.
The foundation that is settled before anything is built
The first phase of a large project is not “design.” It is the set of decisions that, once documented, reduce the need to rebuild what follows:
- Sitemap and information architecture: every page the site will have, marked “build now” or “later phase.”
- Templates and components: a handful of templates generate most pages, each designed and reviewed once; a page needing a new template gets one with a clear scope and cost.
- CMS and data model: which fields each page type carries, who can publish, and how a section is added without a developer (see the web design service page).
- Tracking plan: what counts as an inquiry, where it is recorded and how its source is known, so forms are not rewired every phase.
- Content responsibilities: who writes, who approves, and what assets your team delivers by when.
How to write one phase so you can accept it or reject it
A phase you cannot mark “accepted” or “not accepted” is an instalment, not a phase. Each needs six lines:
- Scope: what is included, and what is excluded unless agreed in writing: extra templates, integrations, content writing.
- Cost: a fixed figure, and where it sits in the overall estimate.
- Deliverables: named files, pages and documents, not “progress.”
- Acceptance criterion: a test your own team can run without the vendor.
- What you provide: content, images, decisions and reviewers, with dates; how a delay on your side affects schedule and cost is set in the agreement, not judged when it happens.
- Exit terms: files, documentation and access to what was delivered, handed over at each phase’s acceptance under the agreement, so the right to stop is real.
An illustrative example for a large bilingual website, not a mandatory template: the number and order of phases follow your scope and priorities.
| Phase | Scope | Deliverables | Acceptance criterion |
|---|---|---|---|
| 1. Foundation (2–4 weeks) | Sitemap, UX flows, prototypes, visual and technical direction, asset specifications | Documents and prototypes any implementer can build from | Signed sitemap and approved prototypes |
| 2. What sells (4–6 weeks) | Core templates, CMS, service or product pages, RFQ page, tracking | Live site with the priority pages in your buyers’ main language, plus the phase’s files and agreed admin access | Templates passed review; a test inquiry lands where agreed; your team publishes a page alone |
| 3. Breadth (4–8 weeks) | Secondary sections and the second language on existing templates, plus agreed new components | The remaining pages; second language for priority pages | New pages pass the template checks; added components have an agreed scope and cost |
| 4. Extras | Interactive sequences, CRM or ERP integrations, advanced search | Each extra documented; remaining access completed under the agreement | Integrations tested with real records; your team runs the site without the vendor |
Later phases mostly reuse phase two’s templates, but that is not a rule: a new component, when needed, gets a clear scope and cost.
What you need now, what can wait, and when moving on becomes logical
Build now what sells or converts; the rest waits. Sells: the service or product pages buyers ask about, the RFQ page, tracking, and your buyers’ main language. Waits: sections that please the inside of the company, advanced interactions, third-party integrations.
The order of phases, and when you move on, combines three things: technical readiness, a signed acceptance of the previous phase; commercial priority, such as a missing section sales asks for, a tender season needing a projects page, or a new market needing the second language; and financial capacity, what the company can invest now. A launch date and cash flow genuinely shape the order: an exhibition in three months may move the projects page ahead of the second language. If no reason appears, stopping after phase two is sound.
The two ways people actually pay twice, and the clauses that reduce them
- Changing the foundation halfway. After phase two someone asks for a page type no template fits, or reorders the sitemap. The clause: any foundation change is a written change order with a cost and its effect on later phases, so it stays assessable and priceable.
- Switching vendors without documentation. The relationship ends before the source files and documentation are handed over. The clause: each phase’s acceptance hands over design and source files, documentation and access to what was delivered, with domain and hosting registered for your company and documented from day one (see the no-vendor-lock-in ownership checklist).
When one delivery is enough, and when a growth plan is executed gradually
A simple project may suit a single delivery: an ordinary B2B website from $600 is one scope and one delivery, and a CRM setup from $600 in four to six weeks is a single phase by nature. A broader growth plan can be executed gradually even from a small start: the priority pages today, then the second language, CRM and integrations as their reasons appear, as long as the overall picture is written and the first phase documented. A hard launch date, such as an exhibition or a tender, does not rule phasing out; it orders it: what the date requires goes first in one compact scope. Phasing does not suit a project where nobody on your side can accept each phase on time.
Six questions before you sign a phased project
- What is the overall picture, and what are phase one’s scope, cost and deliverables?
- Which templates are built in phase two, and how is a new component priced if a later phase needs one?
- What is each phase’s acceptance criterion, and can my team apply it without you?
- Which files, documents and access do I receive at each phase’s acceptance?
- What is out of scope, and how is a change order priced and reflected in later phases?
- Are the domain, hosting and CMS in my company’s name from day one, and how does the agreement treat a delay on my side?
When we’re the right fit — and when we’re not
VadeCom is the right fit if you are a construction, engineering, manufacturing or supply company planning a project that grows over time and want a complete picture executed in phases, documented to reduce rework, with every output handed over with clear access for your team. We write the picture and its phases with scope, cost, deliverables and acceptance criteria, and hand over each phase’s files and access at its acceptance; a project that suits a single delivery we write as one scope. We are not the right fit if you want the lowest total price in any arrangement, or if nobody on your side can decide between phases. Send your project description through the form on our site.
Related reading
- B2B website design with documented source handover
- CRM implementation for B2B sales teams
- Part one: start with a clear first phase
- No-vendor-lock-in ownership checklist
- VadeCom — B2B marketing agency, Egypt and the Gulf
FAQ
Does phasing a project raise the total cost?
It may equal the one-shot price or slightly exceed it because of the handover and review between phases. It buys decision clarity, the right to stop with what was built documented, and less repeated work.
What must be decided in phase one?
The sitemap, the templates and components, the CMS and data model, the tracking plan, and content responsibilities. If one changes later, the documentation keeps the change assessable and priceable.
When should I move to the next phase?
When a signed acceptance of the previous phase meets a commercial priority, such as a missing section buyers ask for or a new market needing the second language, and the financial capacity to fund it. A launch date and cash flow genuinely shape the order.
What do I own if I stop after phase one?
The sitemap, prototypes, visual and technical direction and asset specifications, documented so any implementer can build on them; the contract must state this before you pay.
Should I phase a small website or a CRM setup?
Usually not. A B2B website from $600 or a CRM setup in four to six weeks is one delivery. Phasing fits by scope, priorities and budget, not by a financial threshold; a growth plan can start small and expand gradually.
