MetriFi
FAQ

Your questions, answered.

Several answers below simply confirm that nothing changes on the MetriFi platform compared with a traditional website build. Where that’s the case, we say so.

Projects and pricing

How a website project runs, and how pricing works.

How long does a project take?

It depends on the size and scope of your website. You’ll get a timeline with your proposal.

How much does it cost?

It depends on your website and the plan that fits it. See Pricing for what each plan includes, and schedule a call for a proposal with your exact pricing.

What happens after launch?

Launch is just the beginning. MetriFi keeps helping you make your website better: your conversion funnels are monitored and benchmarked against other credit unions and banks, and when a page underperforms, we design improvements and A/B test them.

This continuous process is what makes your website better and better at converting visits into loans and accounts.

Strategy and fit

Why the MetriFi platform is the right choice, and how it holds up over time.

How does performance compare to a traditional WordPress site?

AI websites dramatically outperform traditional server-based websites like WordPress. Your pages are pre-built into finished HTML and served from the location closest to each visitor, so there is no server software assembling the page on every visit and no database to wait on. Pages load quickly and stay fast even under heavy traffic.

Faster pages also tend to help with search rankings and conversions, since both search engines and visitors reward sites that load quickly.

What happens if Claude changes its model?

AI models keep improving, so a newer model is typically more capable than the one before it.

A model change also cannot affect your live website. Your site is already built and published as finished pages. The AI only edits a draft when you ask it to, and you preview and approve every change before it goes live.

You are also not tied to any single AI company. Many AI assistants can make these edits, so if one is not performing well, you can use another.

What happens if we stop working with MetriFi?

You are not locked in. The complete source of your website is preserved and fully portable, so it can be moved to other hosting if you ever choose to.

Compliance and accuracy

How regulated content stays correct: disclosures, accessibility and rates.

How are required disclosures kept accurate and consistent?

Every disclosure is stored once, as your institution’s own approved language, in a single source on the site. Pages reference a disclosure by name rather than pasting its words, so the exact approved text appears everywhere it is used and cannot drift from one page to another. Change it in that one place and it updates site-wide.

The approved wording is entered through the platform and stored exactly as given. The AI never writes or edits disclosure language itself.

There is also a safeguard at publish time: if a page requires a disclosure that has not been given real approved text, the site refuses to publish rather than show a missing or incorrect one. Disclosures can also be attached directly to a rate, so when a rate changes, its disclosure moves with it.

How is ADA compliance reviewed and tested?

This does not change on the MetriFi platform. We complete the ADA statement of work in our agreement: before launch, we scan the site and resolve the issues the scan identifies. After launch, we rescan on a quarterly basis and report the results to you.

How are rates updated?

This works the same as a traditional build, and AI makes it easier. Your rates live in one central location on the site, so there is a single source of truth. Updating them in that one place updates them everywhere they appear.

You tell the AI which rates to change, or upload your latest rate sheet, and it updates them for you. You confirm the changes before they publish. You can also schedule rate changes to publish automatically at a future time.

Already a MetriFi client whose site is on WordPress? ADA compliance and rate updates are not materially different on the AI website platform. They work the way they do for you today.
Security and reliability

How the site is secured, where data lives, and what happens when something goes wrong.

How is security audited?

This does not change on the MetriFi platform. Before launch, and on a quarterly basis after launch, we run security scans so we can catch and address vulnerabilities.

The platform’s architecture also reduces what can be attacked in the first place. The site is built as static pages with no database, no plugins, and no login-based admin dashboard, which removes the most common targets in a traditional website breach.

Where does our member data live, and is it secure?

Your website itself stores no member data and has no database. Sensitive actions like online banking, account opening, and loan applications happen inside the vendors’ own secure systems, not on the website. There is no pool of member data on the site for an attacker to reach.

What kind of uptime can we expect?

Your site is served from a globally redundant edge network with no single server to fail, so it is built for very high availability. There is no single machine that can go down and take the site with it.

What is the disaster recovery plan?

Our architecture is the disaster recovery plan. Traditional disaster recovery exists to answer what happens when the server dies, data is lost, or a change breaks something. Our setup answers all three by design, not after the fact.

Every version of your site is stored and reversible, so any bad change is undone by instantly republishing the last good version, usually within minutes, with no data loss. The site has no database to corrupt.

It is served from a globally redundant network with no single server to fail, and the complete source of your site is preserved independently, so even if the hosting provider has a disruption, the site can be moved and republished elsewhere.

Disaster scenarioWhat happensRecovery time
Bad change / site breaksEvery version is reversible; republish the last good version.Seconds to minutes
Site content lost or corruptedA full history of the site is preserved; republish from any point.Minutes
“Data loss”There is no database, so there is nothing to corrupt or lose.Effectively zero risk
Hosting provider issueStatic pages stay served from the global network; worst case, the same source republishes to another host.Hours, and rare
Account compromiseRevoke access, restore from the preserved source, republish clean.Minutes once detected
DNS / domain issueRecover through the domain registrar and repoint DNS.Hours

In the rare event of a platform-wide provider outage, your site’s source is fully portable and can be republished on alternative infrastructure. For any urgent issue, see “Who supports it when something breaks?” below.

How does it integrate with online banking, account opening, loan applications, and third-party tools?

This does not change on the MetriFi platform. Online loan and account applications are simple links to the third-party tools. Embedded integrations, such as online banking, use the code the vendor provides.

Already a MetriFi client whose site is on WordPress? Security audits and your integrations are not materially different on the AI website platform. They work the way they do for you today.
Running your site

Day-to-day editing, who is allowed to publish, and how support works.

How are updates managed?

You make day-to-day edits just by chatting with an AI assistant. You describe the change you want in plain language. You never touch any code or technical tools.

Every change is drafted first, so you can preview it before it goes live. When you approve it, it publishes to your website. A full history is kept, so you can roll back to any previous version at any time.

Nobody on your team has to talk to an AI to request a change. Every draft comes with a review link: open the site, click any element to leave a comment, or edit the text right on the page. Those comments and edits are recorded against the exact element you clicked, and the AI applies them, so staff who would rather not chat with an assistant still have a simple way to give feedback and request changes.

Because nothing publishes until you approve it, and every prior version stays available, a mistake never goes live unseen, and if one ever slips through it is undone in seconds by republishing the last good version.

Who can make changes, and can we control who is allowed to publish?

Yes. Access is managed with team roles, so you decide who can make changes and who can publish them live:

RoleDraft changesPublish liveManage membersBilling & team
OwnerYesYesYesYes
AdminYesYesYesNo
EditorYesYesNoNo
ContributorYesNoNoNo

The Contributor role is especially useful for review and approval: staff can prepare and draft updates, while a smaller group of Editors, Admins, or Owners reviews those changes and publishes them live.

Who supports it when something breaks on a Saturday night?

Our team is on call 24/7/365 for emergencies. If something breaks, you submit an emergency support ticket. Our team is notified instantly and begins investigating and working on the problem right away. Response times are covered by the SLA in our agreement.

Campaign landing pages

These apply when you’re building a standalone campaign landing site. If your full site is built on your own domain, your SEO carries over unchanged.

Does a separate landing site hurt our main website’s SEO?

No. A landing site and your main website do different jobs. Your main site is where you build organic search rankings over time; a landing site is where you convert the traffic you send to it from ads, email, and campaigns. Adding a separate site does not remove pages, links, or authority from your main domain, so your existing rankings are unaffected.

Would a subdomain be better for SEO than a separate domain?

Not in any way that matters. Search engines mostly treat a subdomain, like offers.yoursite.com, as a separate site from your main domain, so ranking strength does not reliably flow between them. A subdomain is a fine choice if you want your brand in the address, but pick it for that reason, not for SEO. The only setup that truly builds your main site’s rankings is a page that lives inside your main site itself, which is a different tool for a different goal.

If SEO is our goal, is a landing site the right tool?

No, and that is the important part. A landing site is built to convert intent-driven traffic into applications and account openings, not to rank in search. If organic search visibility is the goal, the investment belongs in content on your primary domain, where authority accumulates over time. Tell us your goal and we will tell you which of the two it calls for.

Let’s talk

Didn’t see your question?

Schedule a call and ask us directly. We’ll answer it, and add it here if others are likely to ask it too.