· Bridge Town Editorial · Releases · 4 min read
Weekly Product Notes: Notes, Billing, and Scenario Workflows
A retrospective on the third week of April, when Bridge Town added public notes, audience pages, Pro billing, dashboard hardening, and richer scenario analysis workflows.
This retrospective covers April 14 through April 20, 2026.
The third week of April connected several layers that had been developing in parallel.
Billing moved from naming to entitlement behavior, public content infrastructure came online, dashboards received a round of visual and security hardening, and scenario workflows became more project-centric. This was a week about making Bridge Town legible both inside and outside the app.
Pro billing became real product logic
Billing work moved beyond copy.
Bridge Town added Stripe dependencies and environment documentation, renamed plan language from Team to Pro, introduced plan middleware, wired the frontend billing page to the backend API, honored Stripe subscription status in entitlement checks, and added cancellation-state handling.
Sharing surfaces were also gated behind Pro plan checks. That creates a clearer product boundary: free users can explore and build, while team collaboration and sharing depend on the paid plan state reflected in the app.
The important part is that billing state stopped being just a settings-page label. It became part of authorization behavior.
Notes became a public publishing surface
The /notes system landed as a real content surface.
The work added normalized note schema, canonical routing, public notes UX, SEO and discovery signals, an editorial workflow, authoring guardrails, and replacement content that reflected Bridge Town rather than demo placeholders. The team also documented the decision to keep notes as Markdown-managed content for the first version.
That gave Bridge Town a durable place to publish product updates, operating guidance, and point-of-view content without bolting a separate CMS onto the product.
Audience pages gave the site a clearer conversion path
The marketing site also gained reusable audience-page infrastructure.
Bridge Town added a shared /for template, conversion CTA contracts, audience hero media contracts, SEO and LLM standards for audience pages, and canonical docs links. These pieces made it easier to publish targeted pages for different finance audiences while keeping metadata, hero media, and call-to-action behavior consistent.
The site became less like a generic landing page and more like a product surface that can speak to specific buyer and user contexts.
Dashboards were tightened for production
Dashboard work focused on making saved dashboards render reliably and safely.
The viewer shell, iframe responsiveness, asset-origin handling, and CSP behavior were corrected, then backed by smoke checks and visual acceptance coverage. Deploy health checks were aligned with the test-stage image, and saved-dashboard CSP smoke became part of the operational contract.
The point is straightforward: a dashboard generated from model output should be shareable and viewable without depending on permissive browser policy or fragile layout assumptions.
Scenario workflows became more finance-aware
Scenario analysis became more explicit and project-oriented.
Bridge Town shifted comparison flows toward project-level contracts, deprecated older server-side generation paths, added finance-aware diff summaries, deterministic finance table summaries, scenario workflow skills, selector support, and lightweight patch-model behavior. The run surface also moved toward a unified run() model with compatibility shims while the tool tier registry, tool search, resources, and prompts started to organize the expanding MCP surface.
This week made scenario work less about arbitrary branch diffs and more about explaining what changed in terms a finance team can use.
Infrastructure kept tightening
The week also included production and security hardening across several areas.
Work landed around ECS resource limits, task egress restrictions, flow-log retention, storage and capacity alarms, tfsec scanning, secret-detection failures, dashboard asset origins, Google Sheets retry and reconnect behavior, ORM index alignment, migration chain repair, and local execution entitlement gates.
These changes are not headline features, but they reduce the amount of unplanned operational risk behind the product.
What this means
By April 20, Bridge Town had a stronger public and commercial shape:
- Notes could explain what changed and why.
- Audience pages could speak to specific finance workflows.
- Pro plan state controlled product entitlements.
- Dashboards had safer rendering and deployment checks.
- Scenario comparison became more project-centric and finance-aware.
This was the week Bridge Town’s outside surface started catching up with the depth of the app itself.
