Interactive calculator
A clean inputs-to-results experience built to the Figma spec — prospects model their workload and see ROI, payback, and productivity estimates instantly on a calculated results page.
Projects
Client case study
Neo4j Business Value Calculator
An IDC-validated, lead-generating web tool that quantifies the ROI of a graph database — and renders a branded, customer-proofed PDF report on demand.
- ROI Payback & productivity, quantified per workload
- PDF Branded report generated server-side on submit
- ≤20 Customer proof points matched dynamically
- 1 Self-contained “code island” — portable by design
The challenge
Turn “trust us, it's worth it” into a number
Neo4j's sales and marketing teams needed a way to show prospects the concrete business impact of moving a workload to a graph database — not a brochure claim, but IDC-validated estimates for ROI, payback period, and productivity grounded in real customer outcomes.
The tool had to do three things at once: compute a credible result from a few user inputs, capture the lead through Neo4j's existing Marketo stack, and convert — by handing the prospect a polished, on-brand PDF report they could take back to their own stakeholders. And it had to be built as a portable drop-in, not welded to WordPress.
The solution
A calculator, a gated form, and a PDF engine
Marketo-gated report
Neo4j’s delivered Marketo form is embedded as-is — no custom fork to keep in sync. A JS layer hijacks submission to build the PDF first, then releases the form for clean lead capture.
Server-side PDF
On submit, WordPress assembles the full report HTML and renders it to a pixel-accurate, branded PDF via a headless-Chromium service running on AWS.
Dynamic proof points
The report personalizes itself — querying Neo4j’s customer-story library and matching on industry & use-case taxonomies to surface the most relevant logos and outcomes.
How it works
The architecture
A WordPress front end orchestrates a dedicated PDF microservice on AWS, with brand assets served from Neo4j's CDN and an optional archival path to S3.
- WordPress Calculator UI + Marketo modal; builds inline report HTML.
- Gotenberg / Chromium Headless render on AWS ECS Fargate, token-secured.
- Branded PDF Logos & proof points pulled from dist.neo4j.com.
- Lead + archive Marketo captures the lead; PDF optionally archived to S3.
Engineering highlights
The decisions that made it clean
- “Code island” architecture. Built as a self-contained drop-in with no reliance on WordPress conventions or in-WP story data — so it can be lifted and re-homed anywhere later.
- Use the form as delivered. Embedding Marketo’s own form (rather than a custom rebuild) eliminated an entire class of sync-and-drift maintenance.
- Submission hijacking done right. The PDF builds first; the Marketo form is only released once the report returns or safely times out — calculator-only fields are stripped before submission.
- Secrets where they belong. Service URL and token live in a WordPress admin settings page backed by the database — not in a wp-config.php that’s generated on the fly in production.
- Archival without exposure. S3 upload is wired and tested but disabled by default — reports are internal record-keeping only, ready to enable behind presigned URLs if ever needed.
- Cross-org repo sync. The PDF service stays mirrored between the agency and neo-technology org repos, with CI/CD running from Neo4j’s side.
The stack
Built with
- WordPress
- Marketo
- Gotenberg
- Headless Chromium
- AWS ECS / Fargate
- Amazon S3
- CloudWatch
- CloudFront CDN
- AWS SDK (PHP)
- Figma
- GitHub Actions CI/CD
Approach
Ship something testable, then negotiate from strength
“Use what's staged live as the starting point to negotiate what else they want.”
Rather than designing the perfect form in a vacuum, the team got a working, on-brand version onto staging first — giving stakeholders something concrete to react to, and keeping scope conversations grounded in a real artifact.
- Delivered PDF microservice deployed on AWS Fargate with token auth, TLS, and CI/CD.
- Delivered Calculator + Marketo-gated modal built to the Figma design, wired to the PDF build.
- Delivered Dynamic customer-story matching and tested S3 archival path.
- In flight Final infra hardening on render-time asset egress, then stakeholder review.
The result
A sales asset that pays for itself
The finished tool gives Neo4j's field teams a self-serve way to put a credible number on the value of graph — and sends every qualified prospect away with a branded, customer-proofed report. Because it was built as a portable code island, it isn't locked to one site: it's an asset Neo4j can move, reuse, and extend.
A representative example of how Red Bridge pairs marketing-site engineering with real cloud infrastructure to turn a campaign idea into a durable, lead-generating product.
Have a campaign idea worth productizing?
We pair marketing-site engineering with real cloud infrastructure. Tell us what you're building.