The cost of a FinTech website redesign depends on the pages you need, the content your team must prepare and approve, the connected systems and the work involved in moving the existing site. A useful quote separates those jobs and states the assumptions behind them.
Ask each supplier to price the same work and state the running costs separately. The worksheet below helps you compare the proposals and see which tasks would still sit with your team.
Start by separating the marketing website from the financial product. A public product page and a CRM enquiry are a different brief from account opening, identity checks, payments or a customer dashboard. Be explicit about which is being priced.
Count the different page types and the content work
A page count helps, but it does not tell the whole story. Twenty pages using one proven template can involve different work from five pages with distinct product explanations, data displays and forms.
Ask each supplier to list the templates included. Typical marketing-site examples include product, integration, customer story, article and campaign pages. Then record how many existing pages need moving into each template and who supplies their content.
“Content supplied by the client” deserves a closer look. Does that mean approved final copy, product notes to turn into copy or an existing website that still needs editing? Who prepares diagrams, customer permissions and current fee information? Those are real tasks even when they sit outside the agency’s price.
Budget for the approval process your team uses
Name the people who can confirm product facts, fees, claims and required disclosures. Establish how their review fits into the project and whether the proposal includes changes following that review.
Where financial-promotion requirements apply, your designated specialist needs to define them for the material being published. The FCA’s overview explains that requirements vary by product. Do not assume a website proposal includes that specialist work or regulatory approval.
Ask what happens if approved content arrives late or changes after a template has been built. A clear proposal explains the dependency and the route for agreeing extra work. It should not quietly turn an unknown review process into a guaranteed launch date.
Price the connections as working journeys
For each form or integration, name the destination, fields, expected behaviour and failure handling. “HubSpot integration” can mean several different things. It might cover an embedded form, a mapped enquiry workflow or additional custom processing.
Ask whether the quote includes access setup, implementation, realistic tests, handover and responsibility after launch. Check what happens if a third-party system or product API needs work from another team.
Our Webflow and HubSpot integration guide provides broader reading on that connection. For a quote, bring the actual form and intended destination rather than a list of tool logos.
Ask us to scope the website you actually need
Our FinTech website service covers the public website, CMS and agreed enquiry connections. Share the current site, intended audience and known systems. We can use those to identify the work that belongs in a proposal and the decisions that still need an owner.
Include the work needed to move the existing site
A redesign may need a content inventory, URL mapping, document checks and redirects. Forms, analytics, scripts, campaign links and product sign-in routes also need a plan. Ask who checks them before release and who investigates a problem afterwards.
Our website migration planner can help organise the current URLs and decisions. Google’s site-move guidance is clear that URL changes require preparation and monitoring; a redesign should not be sold with an unsupported promise that rankings cannot change.
Preserving useful URLs and familiar content can reduce the amount that changes at once. That decision belongs in the brief, before someone prices a replacement for every page.
Separate the build price from running costs
Make a second list for the costs that continue after launch:
| Cost | What to establish |
|---|---|
| Website platform and domain | Supplier, account owner, renewal and relevant limits |
| CRM and connected services | Existing versus new subscriptions and expected usage |
| Integration infrastructure | Who operates it and what usage affects the bill |
| Website maintenance | Included tasks, exclusions, response arrangement and change process |
| Content work | Who updates product facts, documents, campaigns and resources |
| Specialist reviews | Who checks changes requiring product, legal, privacy or accessibility expertise |
Use current supplier prices for the plan you actually need. Ask whether third-party charges are paid directly by you or included in a management fee. Confirm what happens to accounts and access if you change agency.
A lower build fee does not automatically mean a lower total commitment. Equally, a large support allowance may be unnecessary if your team handles routine publishing and has clear technical cover elsewhere.
Compare proposals using the same worksheet
Copy this table into your evaluation document. Fill the last column for each supplier with included, excluded, optional or awaiting a decision, followed by the relevant price or assumption.
| Workstream | Evidence to request | Supplier scope and cost |
|---|---|---|
| Content and structure | Page inventory, templates and content responsibilities | Record the proposal detail |
| Design | Included layouts, assets and review process | Record the proposal detail |
| CMS and editing | Fields, roles and a demonstration of routine publishing | Record the proposal detail |
| Forms and integrations | Field map, destinations, tests and handover | Record the proposal detail |
| Migration | URL decisions, redirects, documents and release checks | Record the proposal detail |
| Approval | Review owners, dependencies and included revision scope | Record the proposal detail |
| Launch | Responsibilities, live checks and correction process | Record the proposal detail |
| Ongoing ownership | Supplier accounts, documentation, fees and maintenance scope | Record the proposal detail |
Compare the gaps as well as the totals. If one proposal assumes approved copy and another includes writing, they are pricing different work. If neither includes migration ownership, it remains an open task regardless of how polished the presentations look.
Use a smaller scope when the unknowns are large
You may not need a complete redesign to answer the first question. A product-page review, a CMS planning exercise or a test of one enquiry route can establish what a larger project needs.
Ask for the output of that first piece of work: a page brief, content model, integration specification or migration inventory. It should help you make the next decision even if you choose a different supplier for the build.
When you are ready to compare proposals, send us the site and the scope you have so far. We can discuss what is clear, what needs investigation and what your team would need to supply.
A few useful answers
Why can two website quotes differ so much?
They may include different templates, writing, approval rounds, integration behaviour, migration and handover. Compare each workstream and its assumptions rather than only the final total.
Should running costs be separate from the build?
Yes. Identify platform and domain costs, connected-service subscriptions, integration operations, maintenance, publishing work and any specialist review separately.
Does a FinTech website quote include the financial product?
Not automatically. Public marketing pages and CRM enquiries are a different scope from identity checks, account opening, payments or a customer dashboard. State the boundary before pricing.
