Credit-Union Playbook: The Script-Tag Path to a Verified Calculator Suite

The credit-union constraint is real: members deserve the planning tools the megabanks ship, and the IT roadmap has no quarter to build them. The embed path exists for exactly this shape of team.

Credit unions are the vertical this series wrote the embed product for, whether or not anyone planned it that way. The member-education mission is core to the charter; the calculator estate is usually a handful of aging vendor widgets or nothing; and the engineering capacity for an API integration may honestly not exist this year. The embed path changes the arithmetic: any page the credit union's CMS can edit can carry a verified calculator by adding a div and a script tag, with the maintenance, the constants, the verification link, and the disclaimer all living inside the frame. This playbook is the full path — selection, mechanics, governance — sized for a team of one.

The mechanics, in their entirety

An embed is two lines: a div naming the model, and the loader script. Prefill any input with a data-input-* attribute, set the height with data-height, and the script mounts an iframe rendering the full calculator — inputs, outputs, charts, the verification link to the model's spec, the disclaimer, and the attribution badge. Content inside the div is your fallback copy, shown only if the script is blocked. It is free with attribution — the badge inside the frame is the entire obligation — and the embed guide (/writing/embed-script-tag) covers every detail this paragraph compresses. There is no key, no contract negotiation, and no server anywhere on the credit union's side.

The starter suite for a member audience

Sequence it like a rollout, not a scavenger hunt: two calculators on the highest-traffic lending pages first, the wellness pair second, the housing pair third. Each page's embed can be prefilled to match its editorial context — the refinance explainer opens with a scenario resembling the article's example — which turns the content library the credit union already maintains into live illustrations at zero engineering cost per story.

Governance for a team of one

The embed path compresses governance to three habits. Check the badge and frame at each site redesign — the attribution must stay visible, and the embed's fallback behavior should be spot-checked on the templates that matter. Skim the changelog occasionally — the frame updates itself, constants and versions included, but a credit union that wants to know when a calculator's behavior changed reads /models/changelog like any other integrator, and the annual review (/writing/annual-model-review) has a one-afternoon version even a one-person team can run. And route member questions well — the spec link inside every frame means "where does this number come from" has an answer a member-service representative can literally click.

When the credit union outgrows the frame

The embed path is a floor, not a ceiling. The day the credit union wants saved scenarios in online banking, envelopes in member records, or an assistant in the mobile app, the API path is waiting with the same models at the same versions — an embed-first launch loses nothing and teaches the team which calculators members actually use before any build begins. The upgrade decision then arrives with usage data attached, which is a better position than any build-first roadmap starts from.

• ✓Start with two embeds on the highest-traffic lending pages; expand by usage.
• ✓Prefill embeds to match each page's editorial scenario.
• ✓Keep member-entered rates — no rate-sheet prefills, ever.
• ✓Verify the badge and fallback at every redesign.
• ✓Skim the changelog quarterly; run the one-afternoon annual review.
• ✓Graduate to the API when saved scenarios or member records need envelopes — same models, same versions.

The mission fit, plainly

The credit-union movement's pitch is that the institution is on the member's side. A calculator layer with published specs, sourced constants, truthful sentinels, and a visible verification link is that pitch, rendered in software — and the embed path prices it at attribution, which is to say at the cost of saying who did the math. Few product decisions let a community institution close a capability gap with the largest banks in an afternoon of CMS edits. This is one, and the whole path is documented in public.