Somebody Will Ask What the Page Said in March. Most Sites Cannot Answer.
A financial website is not a brochure, it is a continuous stream of published claims — rates, illustrations, risk wording, comparison tables, a promotion that ran for six weeks. At some point somebody asks what a specific page said on a specific date, and the honest answer from most content systems is a shrug and a request to check an archive nobody set up.
No credit card required · 30-minute call · No obligation to sign up
Six things you may be asked about a date that has passed
Every one of these is a normal question in this sector, and every one of them is unanswerable if the site only knows its current state.
- What the rate was that weekDisplayed, not what the source system held
- Which risk wording was liveBefore or after the change
- Who published itAnd who signed it off
- How long the promotion ranTo the day, not the month
- What the calculator returnedWith those inputs, under those assumptions
- What the page it replaced saidAnd whether the old URL still resolves
The fifth row is the one that catches people. A calculator is not content, so it is rarely versioned, and its assumptions change quietly — a rate table updated, a rounding rule adjusted, a default input changed. Reproducing what somebody was shown last spring requires the calculator’s assumptions to have been versioned too, and almost nobody does that until the first time they are asked.
A content system that only knows the present tense
Most websites are built to answer one question: what does this page say now. That is the entire model — edit, save, publish, and the previous state exists only in whatever the CMS happened to retain. For most businesses that is fine. For a firm whose pages are financial claims, it means the site cannot answer questions that will certainly be asked, and the gap is discovered under time pressure rather than in a planning meeting.
Building for it is not exotic; it is a decision to treat every publish as an event rather than an overwrite. What changed, who made the change, who approved it, when it went live and when it stopped. Kept as records rather than as a revision feature that gets pruned when the database grows. The practical test is whether somebody non-technical can produce the answer without a developer, because the request will arrive on a Friday and the developer will be on leave.
Sign-off belongs in the same system for the same reason. An approval recorded in email is an approval nobody can find in eighteen months, and one recorded in a workflow tool that has since been replaced is worse, because the trail confidently stops. Holding it against the page means the evidence travels with the thing it is evidence about.
Calculators need the same treatment and rarely get it, because they do not look like content. Version the assumptions, stamp each result with which version produced it, and keep the old ones. It is a small amount of work at build time and it is the difference between reconstructing what a customer saw and explaining why you cannot. None of this is compliance advice — it is a description of what we build so that your compliance function can answer its own questions.
- ✓Publishing is an event, not an overwrite — What changed, who by, who approved, live from when to when.
- ✓Non-technical retrieval — The request arrives on a Friday. The developer is on leave.
- ✓Sign-off held against the page — Email is unfindable in eighteen months. A replaced workflow tool is worse.
- ✓Version the calculator too — Its assumptions change quietly and it is almost never versioned.
- ✓Old URLs keep resolving — A withdrawn product still has links and bookmarks pointing at it.
Most sites are built to answer one question: what does this page say now. That model cannot answer the question this sector actually gets asked.
What a financial build has to keep
Six things, and all of them are about a date that has already passed.
Publishing as an Event Log
Every publish recorded with what changed, who changed it, who approved it, and the window it was live for. Records, not a revision feature that gets pruned.
Point-in-Time Retrieval
Pick a page and a date, see what it said. Usable by somebody non-technical, because the question arrives at short notice and rarely reaches a developer first.
Sign-Off Against the Page
Approval held with the content it approves, so the evidence travels with it. Email trails and retired workflow tools both fail the same way, eighteen months later.
Versioned Calculators
Assumptions versioned, results stamped with the version that produced them, old versions kept. A calculator is not content, which is exactly why it is never versioned until it needs to be.
Scheduled Start and End
A promotion with a real end date that the system enforces, rather than a reminder somebody sets. Expiry that depends on memory is expiry that does not happen.
Withdrawn Products Still Resolve
The URL outlives the product, and links and bookmarks keep pointing at it. A page that stays and states the position beats a 404 that says nothing.
What clients say
Real clients, quoted in their own words — published with their permission.
“Ghalib’s clear guidance has helped improve our website’s SEO performance.”
“It was a pleasure working with Ghalib and his team.”
“We’re very thankful to Ghalib and his team for building a fully-functioning website for our business.”
More of them, in full, on our reviews page.
— Our Proprietary Methodology —
The Visibility Framework™, applied in Finance
The method doesn’t change by market. What it’s pointed at does.
Audit & Discovery
What the current site earns, where it leaks, what your competitors do better, and what the new one must achieve. Ends in a written scope and a fixed price — not an estimate that grows.
Structure & Design
Sitemap, wireframes and user journeys agreed before decoration, then a design system applied consistently. You approve the shape before we make it beautiful.
Build & Test
Front end, back end, CMS and integrations, on a staging site you can see from day one. Tested on real devices, real screen readers and real slow connections.
Launch & Improve
Redirects verified, analytics connected, handover recorded — then we look at what real visitors actually do and fix what the design assumed wrongly.
Honest, No-Nonsense Commitment
The price we quote after discovery is the price you pay — if we underestimated the work, that is our problem, not a change request. And on any rebuild, if organic traffic drops because of something we did at migration, we fix it at our cost, however long it takes.
Website Development pricing for Finance, in USD
Quoted per build, with the record-keeping included rather than optional — retrofitting it means rebuilding how content is published, and by then the gap has usually already been noticed by somebody else. This is not compliance advice. We build so your compliance function can answer its own questions; what those questions are is theirs to define.
Marketing Site
Content and claims, no calculators.
- Publishing recorded as events with sign-off
- Point-in-time retrieval by a non-developer
- Scheduled start and end dates, enforced
Site & Tools
The usual one. Calculators and rate tables too.
- Everything in Marketing Site
- Versioned calculator assumptions, stamped results
- Withdrawn products that keep resolving
- Optional: bundle in SEO or Social Media
Enterprise
Multiple brands or formal approval chains.
- Multi-stage approval with delegated roles
- Export built for an external reviewer
- Separation of brands with shared components
- Optional: combine all 4 services for full-funnel growth
Every plan is scoped around your market — get a free audit and we’ll recommend what fits, priced in USD.
What you’re actually committing to
Most agencies keep this in a contract you only see after the sales call. We would rather you knew now, because it is the question everyone asks second — right after the price.
- A fixed price, agreed before we startQuoted after discovery, not estimated on a call. If the work takes longer than we thought, that is our risk — the price does not move unless you change the scope.
- 50% to begin, 50% at launchNo large upfront payment held for months, and nothing owed until the site is live and you have seen it working.
- You own everythingDomain, hosting, code repository, design files and content — all in your name from day one, and still yours if we never work together again.
- No proprietary lock-inStandard, widely-used technology only. Any competent developer can take the site over, and nothing stops working because you stopped paying us.
- Two rounds of revisions per stageIncluded at wireframe and design stage, where changes are cheap. Beyond that, or after sign-off, changes are quoted before any work starts.
- 30 days of support after launchBugs and small tweaks included as standard. A care plan afterwards is optional, never automatic, and cancellable with 30 days’ notice.
These are the terms as they appear in the agreement itself — nothing here is softened for the website. The full wording lives in our terms and conditions, and you get the agreement to read before anything is signed or invoiced.
Finance Website Development questions, answered
Related Website Development pages
Same service, different angle — by market, by discipline and by platform.
Could you answer the March question?
Free 30-minute audit · No obligation · Response within 24 hours
Get in touch with Ghalib Ashrafi HQ
Ghalib Ashrafi takes on work for brands in six markets — the UK, USA, UAE, Saudi Arabia, Australia and Pakistan. Every enquiry gets a reply within 24 hours.