Client project · 2026

Revver renewal portal

Security hardening and a brand restyle for Revver's Salesforce-connected renewal portal, delivered as a subcontractor to CRM Infusion: signed, expiring customer links in place of raw account IDs, every endpoint gated, and a flow that finally looks like Revver.

Project shape
Systems Design 15%Infra 5%DevOps 10%Data 0%AI 0%Backend 35%Frontend 35%
Leading
Backend35%Frontend35%Systems Design15%
Minimalist coral line art on paper: a signed link badge and an hourglass lead into a browser window showing a survey card with a paintbrush resting on its corner, then a padlocked shield, a cloud, and a stack of documents, with a crossed-out debug panel above the path and the brand spectrum strip along the base.

The problem

Revver, the document-management company, wanted renewals to run without a rep on every account. CRM Infusion built a self-serve portal for it: a customer opens a link, answers a short survey, plans their seats, and gets renewal offers priced from their live Salesforce contract, with larger expansions routed to a booked call.

The portal worked. Two things were still between it and a confident rollout. Customer links identified accounts by their raw Salesforce ID, which meant the link itself was the only thing standing between a customer and someone else's renewal data. And the flow didn't look like Revver, which matters on a page whose whole job is to get a customer to trust an offer.

What we did

We joined late, as a subcontractor to CRM Infusion, with a narrow brief: make it safe, make it look right, and leave it easier to work on.

  • Signed, expiring links. We replaced raw account IDs with signed tokens that expire after 14 days, plus a small script to mint them. All three API endpoints (contract lookup, offer selection, and the AI-written offer taglines) now return 401 without a valid token, and the page stops leaking its URL through the referrer. The signing code has no dependencies, and it ships with tests for both the tokens and the endpoints.
  • A restyle measured from the real site. We matched the flow to revverdocs.com using values taken from the live site, moved about 400 lines of inline styles into a proper theme stylesheet, and swapped a hand-drawn logo for Revver's real one. We verified it end to end against a Salesforce sandbox.
  • A cleaner customer view. We pulled an internal testing panel out of the customer-facing flow, so customers see their offers and nothing about how they were calculated.
  • A local dev server. A dependency-free server that mimics the hosting platform's request handling, so the next person can run the whole flow on a laptop without deploying.

Status

Delivered to CRM Infusion in August 2026. A small engagement, by design: the portal was already built, and the job was to close the gaps that would have made a rollout risky.

Work

Have a system that needs this level of attention?

See how we evaluate a new engagement.

Start a conversation