Kigo website projects start at US$1,500. See how existing content, integrations, migration and launch requirements change the cost of a redesign.
At Kigo, website projects start at US$1,500. That's our minimum project budget. For a redesign, the final price depends on what we can keep, what needs replacing and what has to keep working when the new site goes live.
Your current site is the starting point. It may already have useful service pages, articles people find through search, and forms connected to your team's tools. Each needs a decision before someone can estimate the work.
Our website cost calculator gives you a starting estimate for the build. Migration, content cleanup and the handover of your current site still need a separate review.
If you're planning your first website, the guide to professional website design costs covers that buying decision. Here, we'll look at the work involved in replacing an existing site.
Decide how much really needs changing
Open your site and write down the problems you're trying to solve. Be specific: “Our new service is missing” or “The quote requests reach the wrong person” gives us something useful to investigate.
A focused update may be enough if your page structure and editing tools still work. You could update the copy, replace photos or improve a particular interaction.
A larger redesign becomes more relevant when the structure, content and features need to change together. Replacing the platform adds another set of decisions about content, editing and connections to other systems.
I'd ask for a recommendation on what to reuse before approving a rebuild. Keeping a component still requires checking that it works with the proposed changes. The proposal should explain which parts have been reviewed and which need further investigation.
Make an inventory of the existing site
Start with a list of current pages and what should happen to each one:
| Decision | What the project needs to cover |
|---|---|
| Keep | Review the content and carry it into the new design |
| Rewrite | Assign someone to update and approve the material |
| Combine | Decide where the useful information belongs |
| Remove | Check whether visitors or other pages still depend on it |
| Add | Define the new content, layout and purpose |
Include blog posts, campaign landing pages, downloadable documents and language versions. A page that's missing from the main menu may still be receiving visitors.
Then list the functions: forms, bookings, payments, calculators and customer access. Record where information goes afterward. An enquiry might send an email, create a CRM record and notify someone else. Those connections need their own review.
Share the platforms and providers involved, and confirm who can grant access. Discovering halfway through the build that nobody can export the old content creates work that should have been discussed earlier.
Price the content move separately
Having existing content gives you a starting point. Moving it may still involve cleaning up formatting, matching images to pages, checking downloads and entering information into a different content management system.
Ask whether the move is automated, manual or a mixture. A sample migration can reveal what needs fixing before the whole archive is included in the estimate.
For a bilingual site, decide which pages have equivalent translations and which belong in only one language. Budget for reviewing both versions, including navigation and confirmation messages. Assign someone to approve any rewritten material before it moves.
Keep useful page addresses where possible. Google's site move guidance recommends mapping changed URLs and using redirects. Include that work in the quote.
Check the features behind the design
For Grupo Domo's bilingual website, we built service and industry pages, a guided shipment quotation flow and a cargo calculator. The calculator turns package dimensions into volume and volumetric weight.
These features show why a page list needs some detail. A quotation has steps, validation and a destination for the enquiry. A calculator has rules and results to check on a phone as well as a computer.
If you're redesigning a site with features like these, decide whether each one will stay, be rebuilt or be replaced by an existing tool. Explain what it does today before adding requests for new functionality. That gives the team a clearer basis for estimating the change.
Include the work around launch
Agree on how the existing site will stay available while the replacement is built and reviewed. A preview lets your team check the new pages before visitors see them.
You also need a plan for changes made to the old site during the project. If someone updates a service description after the content has been copied, decide how that update reaches the new version.
Before launch, check the important visitor journeys from beginning to end. Send an enquiry and confirm that the right person receives it. Test booking or payment steps if they're included. Review the contact details and links your campaigns use.
Name the person who approves the switch and who handles problems afterward. Ask what happens if an essential feature fails during launch. Preparing that response takes work, and it belongs in the scope.
Use phases when the whole project won't fit
You might start with the main service pages and enquiry journey, then rebuild a larger resource library later. Write down which parts stay on the current system and how visitors move between them.
Phasing can spread the work, but maintaining two systems or revisiting shared layouts also creates effort. Ask the team to explain those tradeoffs before assuming that several small releases will cost less.
The website redesign timeline example shows how content, approvals, development and testing fit together. Use it to discuss dependencies and your team's availability.
Compare quotes against the same decisions
Ask each provider to make these items visible:
- What stays, what changes and what still needs investigation.
- Which content and language versions will move, and who prepares them.
- Which features and connections will be preserved or rebuilt.
- What the launch checks, URL changes and follow-up fixes cover.
- Which current services continue, which end and whether subscriptions overlap.
Clarify how extra work is approved if the review uncovers something unexpected. A useful quote makes those assumptions clear enough that you can discuss them.
Share your current URL, the problems you want to solve and the tools connected to the site through our website design project form. Include any deadline or budget constraints so we can discuss a practical scope for the redesign.