Free tools

Understand the scope before asking for a quote.

A website brief can hide very different kinds of work behind similar page counts. Product configuration, external systems, content preparation and the release process all affect what needs to be designed and tested. This guide helps organise those inputs before a conversation about implementation.

Illustrative toolbox: project scoping and launch preparation.

Use this tool in your browser.

How to use this project scope guide

A website brief can hide very different kinds of work behind similar page counts. Product configuration, external systems, content preparation and the release process all affect what needs to be designed and tested. This guide helps organise those inputs before a conversation about implementation.

The result is an indicative scope level rather than a commercial estimate. You can change the choices to see which dependencies matter, then copy the resulting summary or carry it into an audit request. The summary contains only the options you selected; it does not establish a delivery schedule or a commitment to build.

How the guide scores scope

Each selected choice contributes a documented complexity weight. A larger template band adds more than a smaller one; custom checkout, subscriptions and inventory integrations contribute more than a simple presentation choice. The highest contributors are shown so the result is explainable rather than a mysterious label. Focused totals up to 7 points, Standard 8–15, Complex 16–25 and Custom architecture above 25. Project type adds 1–7; a Next.js or headless platform adds 4; successive size bands add 0, 2, 4 or 6. Features add 2 each, except subscriptions and custom checkout at 4. Integrations add 2 each, except ERP or inventory at 4. Design adds 0–3, content help adds 3, and timeline preference adds 0–3. These weights are review prompts, not effort units or prices.

What a conversation would confirm

The exact workflows, existing code, data quality, platform limitations and acceptance checks still need review. A scoped proposal may combine or separate work differently from this guide. The model is draft guidance and should be adjusted when the owner confirms the approach.

Questions about this tool

Is the result a quote?

No. It is a structured scope guide based on your selections. A quote follows a review of requirements, dependencies and the work that is actually agreed.

Why does headless affect scope?

A separate frontend introduces application, publishing and integration responsibilities. Whether those responsibilities are justified depends on the operating need rather than a platform label alone.

Can I change my answers?

Yes. Try another set of choices and complete the guide again. A summary can help you compare scope options without sending information to a server.

What should I send with the summary?

Add the business goal, any existing public site and the problem you want solved. Do not include passwords, private records or API credentials.

08 / Start a project

Let’s build something dependable.

Send a short brief about what needs to work better and get a direct reply from Abdullah.

  • Direct response from Abdullah
  • NDA-friendly
  • No-obligation first conversation