Zolesco

Free buyer planning tool

Turn a vague website idea intoa comparable scope brief.

This tool does not estimate an automatic quote. It identifies the planning complexity and workstreams that should be explicit before you compare website proposals, timing or ownership terms.

Method

A planning heuristic, not a hidden price calculator.

The score only helps surface coordination risk. The same page count can produce very different delivery work when migration, content, APIs, multilingual content or approval structure changes.

  1. Step 1

    Select the current project state and approximate page range.

  2. Step 2

    Record content, integration, migration, brand, language, approval and timing conditions.

  3. Step 3

    Use the resulting complexity band as a planning signal, not as an automated quote.

  4. Step 4

    Put the highlighted workstreams into the written scope before comparing price or schedule.

Private by design: these selections are calculated in your browser. The tool does not submit them to Zolesco, require registration or call an external API.

1. What are you doing?

A rebuild usually carries migration and continuity responsibilities that a new site does not.

2. Roughly how much public content?

Count meaningful pages or page groups, not every small component.

3. How ready is the content?

Content uncertainty often changes both sequence and review effort.

4. What must the site connect to?

Custom data or workflow integrations need discovery beyond normal website delivery.

5. What is the search/migration context?

For a new site, choose the lowest-risk option unless there is another migration dependency.

6. Is the visual identity ready?

Brand work should be explicit rather than hidden inside website revisions.

7. How many languages?

Multiple languages add content, review and URL-architecture responsibilities.

8. How many people approve the work?

More stakeholders increase coordination even when the page count stays the same.

9. Is the launch window compressed?

A fixed date does not remove QA, migration or client-input dependencies.

What the output covers

A complexity band, your selected planning conditions and the workstreams that should be visible in a written proposal.

What it deliberately avoids

No guaranteed price, launch date, rankings, leads or ROI. Those depend on real scope, client inputs, technical constraints and external systems.

Where to go next

Compare the brief against published pricing, the redesign cost guide and delivery terms before deciding whether a scope discussion is useful.

Read the cost guide