In This Guide
- Why proposals without an audit are built on assumptions
- What the audit actually finds and produces
- What you receive and keep
- How the audit fee fits into implementation
- Questions that come up
A Website Proposal Should Not Be a Guess
Most agencies will look at a site, ask a few questions, and send over a proposal. It may look complete. It may even feel reassuring. But if no one has really looked inside the site yet, the proposal is still based on assumptions.
Websites collect history. Pages get added for campaigns that ended years ago. Navigation gets patched instead of rethought. Plugins stay in place because they still sort of work. Content gets rewritten in one section and ignored in another. From the outside, a site can look functional enough. Inside, it can carry years of unresolved decisions.
That is usually where trouble starts. When a proposal skips the audit, one of two things happens. Either the budget gets padded to cover unknowns, or the project gets under-scoped and the cost grows once the real work begins. Neither is good for the client. One pays for uncertainty upfront. The other pays for it later, when the team is already in motion, and the fixes are more expensive.
That is why we start with the audit. It is the step that turns a website project from a guess into a plan.
A good audit answers a few questions before anyone starts building:
- What content should stay, change, or be removed
- What is structurally broken or holding the site back
- What work is actually required, and what is not
- What the safest and most cost-effective path forward looks like
This is not prep work in the casual sense. It is diagnosis, risk reduction, and planning.
What the Audit Actually Finds
The audit matters because it makes hidden problems visible. Not dramatic problems for the sake of drama. Real problems that affect scope, cost, timeline, and the quality of the final site.
We look at the site as it exists, not as everyone hopes it exists. That includes the content, structure, navigation, and the technical foundation beneath it. The point is not to generate a long list of observations. The point is to identify what is getting in the way, what can be cleaned up, and what needs to be addressed before implementation begins.
A recent audit is a good example. On the surface, the site looked fine. It was live, functional, and doing the basic job. Once we reviewed it properly, we found thin core pages, accessibility issues affecting the whole site, and technical decisions that limited how the site could be found and understood. None of that would have shown up in a quick proposal. The audit made it visible, gave it priority, and turned it into a plan.
That is the real value of this step. It does not just confirm what is already obvious. It finds the things that would otherwise show up halfway through the build, when the cost of changing direction is much higher.
What we are documenting is usually some mix of:
- Redundant, outdated, or conflicting content
- Structural issues in navigation and hierarchy
- Gaps between what the site says and what the organization actually needs
- Technical issues that affect performance, visibility, or maintainability
- Work that can be simplified, phased, or avoided entirely
Over time, that changes the whole project. Instead of carrying old confusion into a new build, the team starts from a cleaner understanding of what belongs there in the first place.
What the Audit Produces
Clients are much more comfortable paying for planning when the output is concrete. They should be. The audit is not valuable because we spent time reviewing the site. It is valuable because it produces working documents that the client can use.
The deliverables are built to guide decisions. They are meant to clarify what exists now, what should happen next, and what the implementation is likely to require. That is what turns a vague website conversation into something usable.
A typical audit includes:
- A full page and content inventory
- A review of site structure, navigation, and hierarchy
- A consolidation plan with clear keep, merge, and remove recommendations
- An updated sitemap and prioritized roadmap
- Estimate ranges for implementation based on what we actually found
In many cases, that is the first time the project starts to feel manageable. Once the site is laid out plainly, the conversation changes. The team can see what is essential, what is clutter, what needs real investment, and what can wait. That has a practical effect on the work. Decisions get better. Timelines get more credible. Budget goes toward the work that matters rather than cleaning up surprises later.
We have found that this is where trust usually improves. Not because the project suddenly feels smaller, but because it no longer feels vague.
What You Receive and Keep
This part matters, and we think it should be stated plainly. If you decide not to move forward with Giant after the audit, you will still keep the deliverables.
That changes the nature of the conversation. The audit is not a tool to unlock a proposal. It is a planning engagement with its own value. The roadmap, sitemap, scope boundaries, and estimate ranges are yours. You can move forward with us, take the documents to another firm, handle parts internally, or phase the work over time.
That is one reason strong clients tend to respond well to this process. They are not paying for vague thinking or a sales exercise. They are paying for clarity. And clarity remains useful whether the next phase happens with us or not.
What you leave with is practical:
- A blueprint of the current site
- A plan for what to simplify, reorganize, and remove
- A roadmap for future implementation
- Estimate ranges you can use for budgeting and comparison
We say this directly because we mean it. The audit is not designed to lock anyone in. It is designed to ensure that whoever takes the next step starts with an honest plan.
Why the Audit Fee Is Credited Toward Implementation
If you move forward with Giant, the audit fee will be credited toward implementation, as the audit is part of the project. It is Phase 1.
That point matters because it reflects how we actually work. The audit is not separate from the rebuild or migration. It shapes it. The implementation is better because the audit happened first. The estimate is stronger because the audit happened first. The scope is clearer because the audit happened first.
For most projects, the more relevant question is not whether the audit adds a cost at the start. It is what an inaccurate proposal costs when a project has to be re-scoped midway. That is where teams lose time, burn budget, and start making rushed decisions just to keep momentum.
We would rather handle the thinking upfront, while the options are still open. That is how we avoid overbuilding. That is how we avoid padded proposals. That is how we give clients pricing based on reality instead of assumptions.
All of our website projects begin this way for a reason. It is the most responsible place to start.
Questions That Come Up
Why can’t you just give us a rough estimate first?
We can give a broad range based on site size, platform, and the kind of work you think you need. What we cannot give you, at least not honestly, is a proposal with real accuracy before we understand what is actually in the site.
That distinction matters more than people think. A rough range can be useful for early budgeting. It is not the same thing as a scoped plan. The audit is what converts a general range into something you can actually make decisions from.
The reason we hold that line is simple. Without the audit, we are both guessing. One side just happens to be guessing in a nicer format.
What if we already know what we want?
That is often when the audit does the most work. A clear direction is helpful, but it does not always mean the underlying site is ready to support it.
Sometimes the audit confirms the plan and gives the team the confidence to move forward. Sometimes it surfaces problems that change the sequence or scope. Both outcomes are useful. It is much cheaper to adjust a plan than to revise a half-built site.
In practice, this is one of the biggest downstream effects of the audit. It reduces the chance that confidence gets mistaken for clarity.
Is the audit fee a significant cost on top of the project?
Usually, it is a small fraction of the implementation cost. And because it is credited toward the project if you move forward with Giant, it functions as the first phase of the work rather than as an extra line item hanging off the side.
The better question is what a bad scope costs. When projects are under-scoped, the budget rarely stays low. It just becomes unstable. That tends to be more expensive and a lot more frustrating than paying for proper planning at the beginning.
This is one of those decisions that looks bigger before the work starts than it does once the project is underway.
Do we get to keep the deliverables if we do not move forward?
Yes. You keep them.
That includes the planning documents, the updated structure, and the estimate ranges. You can use them with another agency, with your internal team, or as the basis for phased work over time.
We think that is the only fair way to do it. If a client has paid for planning work, it should belong to them.
The firms that do the best work tend to respect this part. Good planning should create freedom, not dependency.
Why We Treat the Audit as the First Real Phase of the Work
The audit is the first step in every website project we take on because it ensures the rest of the project is honest. It gives the client something usable. It gives the team something real to work from. And it keeps the bigger decisions from being made in a fog.
There is always pressure in this kind of work to move quickly. Get the proposal out. Get the project approved. Get into design. That can feel efficient at the start. Sometimes it even looks client-friendly. But speed at the wrong stage usually shows up later as rework, confusion, and unplanned costs.
We would rather start with a clear understanding of what is there, what matters, and what the site actually needs next. That is not a harder way to work. It is just a more grown-up one.
