B2B Website Improvement: Cost Drivers and a 90-Day Roadmap
Tomohiro Iida · Published August 2, 2026 · Updated September 7, 2026
The cost of improving a B2B website is not set by how many articles are produced. It is set by how far the analysis goes, how much implementation is included, which access permissions are granted, and how far post-release verification extends. This guide explains the differences between those scopes and sets out a 90-day process with deliverables and completion criteria.
The phrase “website improvement” can mean listing issues found in public pages, tracing implementation-level causes using real measurement data, or specifying and shipping changes through to post-release verification. Comparing prices without matching those scopes is not a comparison.
What this guide covers and what it does not
This guide covers the cost structure of commissioning B2B website improvement and the process when it runs over 90 days: the types of support, deliverables and completion criteria per phase, division of work when an existing production partner is in place, and the items to check when comparing quotations.
- Not covered: the cost breakdown of AIO work on its own, which is handled by the separate article on AIO cost structure.
- Not covered: project-specific quotation amounts, which vary with page count, implementation setup, and access permissions.
Cost is determined by four scopes
- Research scope: public information only, or also GA4, Search Console, CMS templates, and source code.
- Implementation scope: specification only, production implementation by the provider, or implementation by the internal team or existing production partner.
- Permission scope: which tools and repositories are accessed, at what permission level, and for how long. Areas without granted access are not asserted from guesswork; confirmed facts and confidence levels are stated separately.
- Verification scope: technical checks immediately after release only, or also a comparison against a baseline period.
When these four are not aligned, a narrow scope simply looks cheaper. Align them before comparing figures.
Four types of support
Support divides into a public-information diagnosis, a connected-data diagnosis, an improvement specification, and delivery support. They build on each other, so a later stage cannot be commissioned on its own.
| Type of support | What is examined | What is produced | Access required |
|---|---|---|---|
| Public-information diagnosis | HTTP status and redirects, initial HTML, rendered DOM, title, description and canonical, robots.txt and sitemap, headings and body structure, internal links, JSON-LD, CTA and form paths | Priority issues, evidence URLs, confirmed facts, direction of improvement | None (public information only) |
| Connected-data diagnosis | Search Console and GA4 data, CMS templates and content models, routing and rendering, metadata generation, JSON-LD sources, redirect and header settings, GTM and GA4 event configuration | Confirmed facts, root causes in code or configuration, confidence level, affected scope | Read-only GA4 and Search Console; CMS or repository access where required |
| Improvement specification | Confirmed facts, root causes, business priorities | Target URL, component or setting, change, reason, completion criteria, verification method, suggested owner, estimated effort, success metric | Provision of business information |
| Delivery support | The specification, client priorities, implementation setup | Owners and deadlines, sharing with the existing production partner, post-release checks of HTML, metadata, structured data, and GA4 events | Internal approval and release decisions |
How the 90 days are divided
Netsujo divides an initial 90-day engagement into 0–30, 31–60, and 61–90 days. This is an internal working guideline rather than a universal rule, and the split changes with page count and implementation setup.
Days 0–30: establish the current state and priorities
- Confirm business information: target customers, value provided, priority offerings, constraints.
- Diagnose public information, then real data and implementation.
- Capture baseline figures for the comparison period.
- Organize symptoms, affected URLs, and business impact.
- Agree the priority issues.
Days 31–60: finalize specifications and start implementation
- Produce improvement specifications and obtain client approval.
- Assign owners, reviewers, and deadlines.
- Share with the existing production partner and resolve questions and specification gaps.
- Implement, review, and decide on release.
- Where measurement is not yet in place, design and implement GA4 events in parallel.
Days 61–90: verify the release, measure, and hand over
- Check the production release, layout, HTML and metadata, structured data, redirects, and canonical tags.
- Confirm that GA4 events fire as designed.
- Compare against the baseline period (Netsujo uses a 28-day comparison as a working guideline).
- Review remaining issues and decide the next order of work.
- Hand over ongoing operation.
Checks available immediately after release and figures that only become measurable after a period are treated separately. Because rankings and AI answer placement are affected by external factors, this comparison observes change and does not guarantee an outcome.
Inputs, deliverables, client tasks, and completion criteria
| Phase | Inputs | Main deliverables | Client tasks | Completion criteria |
|---|---|---|---|---|
| Days 0–30 | Public site, business information, read-only GA4 and Search Console access | Symptom list, affected URLs, baseline figures, priority issues | Confirm target customers and sales goals, grant access, approve priorities | The targets to fix and the metric and baseline period are agreed |
| Days 31–60 | Agreed priority issues, information on the implementation setup | Improvement specifications covering target URL, change, reason, completion criteria, verification method, suggested owner | Internal approval, assignment of implementers, decision on commissioning the production partner | Targets, owners, and deadlines are set and implementation has started |
| Days 61–90 | Released changes, baseline-period data | Post-release check records, event measurement results, plan for the next cycle | Production release, sharing the release date, deciding the next priorities | The release and measurement are confirmed and the next issue is decided |
Dividing work with an existing production partner
An existing production contract does not need to be replaced. Diagnosis and specification, implementation, and post-release verification can be assigned as separate roles.
| Role | Responsibility |
|---|---|
| Diagnosis and specification | Analysis, evidence, improvement specifications, prioritization, implementation tracking, measurement |
| Client | Confirming business information, setting priorities and release decisions, internal approval |
| Internal team or existing production partner | Estimating, design decisions, production implementation, deployment |
| Support provider (Netsujo) | Plan-dependent human review, decision support, coordination with the production partner, post-release checks, limited implementation support |
- Who implements in production.
- Who makes the release decision.
- Who performs post-release checks.
- Who decides when a specification gap appears.
What increases cost and what reduces it
The following are Netsujo working guidelines rather than universal rules.
| Tends to increase cost | Tends to reduce cost |
|---|---|
| Multiple domains or subdomains | A single domain and a limited set of core pages |
| Many target pages, or multiple languages | Production implementation handled by the internal team or existing partner |
| Several generations of CMS or templates in use at once | GA4 and Search Console already configured, with access granted quickly |
| A wider share of production implementation commissioned externally | Documented business information: target customers, value provided, priority offerings, constraints |
| Measurement not yet in place, so baselines must be built first | An agreed approver and release-decision route |
| Design production, new page production, or CMS migration included | Standard-scope limits and the handling of work beyond them agreed in writing before work starts |
Items to check when comparing quotations
| Item | What to confirm in the quotation or proposal |
|---|---|
| Target scope | Domains, number of pages, languages |
| Research scope | Public information only, or GA4, Search Console, CMS, and repository as well |
| Granularity of deliverables | An issue list only, or target URL, change, completion criteria, and verification method |
| Implementation ownership | Who implements in production and how much implementation support is included |
| Post-release verification | Whether both immediate technical checks and a later comparison of figures are included |
| Duration and cadence | Contract term, meeting frequency and length, delivery cycle |
| Limits and overage | Standard-scope limits and the procedure for issuing a change estimate |
| Client tasks | Which permissions, information, and approvals the client provides, and when |
| Contract and payment terms | Application method, payment method, payment timing, renewal and termination |
| What is not guaranteed | What is explicitly not promised regarding rankings, AI answer placement, and enquiry volume |
The final item matters most. Rankings and placement in AI answers are affected by external factors, so ask for the basis of any statement that promises them.
Mark every item as included, extra cost, client task, or undecided
Listing the items is not yet a comparison. Do not read work that is absent from a quotation as either included or unnecessary. Fill each cell below with “included”, “extra cost”, “client task”, or “undecided”, and do not proceed to a contract decision while anything is still undecided.
| Comparison item | What to confirm in the quotation | Work and conditions left with the client |
|---|---|---|
| Diagnosis target | Public pages only, or measurement data and implementation as well | Read access, target URLs, business information |
| Improvement specification | An issue list, or proposed changes with acceptance criteria | Deciding which measures to prioritise and whether to proceed |
| Coordination with the existing production company | Who is told what, and how often | Checking the existing contract, approving additional quotations |
| Implementation | How far changes go: copy, CMS, code, tags | Specification changes, added pages, other systems |
| Production release | Whether operator, approver, and conditions are decided | Release access, internal approval, permitted release windows |
| Post-release checks | How far checks go: display, form receipt, measurement | Verification accounts, receipt owner, incident contact |
| Re-measurement | Who owns the period, metrics, and comparison conditions | Recording concurrent changes such as ads or pricing |
| Closing and handover | Whether specifications, change history, open issues, and access revocation are included | Deciding the next operational owner |
A company that already has implementers may only need to buy the diagnosis, the specification, and the missing part of the delivery management. A company without implementers still needs a team to make the changes, however many issues the diagnosis finds. This is an illustrative example, not a recommendation of a particular plan.
Nor do the stages have to be bought in order from one supplier. If a valid diagnosis or specification already exists, confirm its evidence, target, and date, and it may be possible to commission only the remaining implementation and verification.
Start by extracting only the “client task” column
When a quotation arrives, first pull out only the client-task and undecided cells. If a stage has nobody able to own it, decide one of three things: add it to the scope of support, commission the existing production company, or leave it out this time.
- The pages and the user action you want to change
- The work and deliverables included in the contract
- The work performed in-house or by the existing production company
- The conditions under which extra cost arises
- Who owns implementation completion, release verification, and effect measurement
- The undecided items to resolve before contracting
“A specification will be delivered” and “enquiries will increase” are separate things to confirm. The first is checked against deliverables and acceptance criteria; the second is observed after release against a period and a metric. If you narrow scope to reduce cost, still record who picks up the stages you removed.
How Netsujo plans map to this process
Netsujo offers three SIGNAL plans: recurring diagnosis, delivery support with a three-month minimum, and a fixed 90-Day Initial Improvement engagement with no automatic renewal. The pricing and standard-scope basis used here is the service contract effective date of 2 August 2026; the service page remains the source of truth for current terms.
The 90-day initial improvement plan corresponds to the process described above. All sales-related pages are diagnosed, while human standard delivery is capped at up to ten core pages and up to thirty hours in total, whichever is reached first. Work beyond the standard scope is quoted as a change estimate before it begins.
- Out of scope: new web design, full site redesign, CMS migration, large-scale coding, backend development, membership features, e-commerce features, external system integration, photography, video, illustration, high-volume article production, and specialist legal or medical review.
SIGNAL does not guarantee search rankings, placement in AI answers, enquiry volume, or revenue.
Summary
Key takeaways
- How far the analysis goes.
- How much implementation is included.
- Which permissions are granted, and for how long.
- How far verification extends.
Over 90 days, agree priorities in the first 30, finalize specifications and implement in the next 30, and verify, measure, and plan the next cycle in the final 30. Setting completion criteria for each phase makes progress observable. When comparing quotations, align scope before comparing figures.
We review target scope, implementation setup, and access, then explain the process and what each plan covers.
Discuss which plan fits your scopeNetsujo SIGNAL pricing and service details
How to judge an SEO and web improvement partner
How to write a web improvement specification
How to improve a site without replacing the production company