Vivere · Internal Product Doc

The Estimate Engine

Storyboard, pricing framework, best practices, and pilot proof of concept for an enterprise build calculator.

Status: Pilot v0.3 — built Audience: Large-corporation prospects Date: July 7, 2026 Pilot: calculator unit · panel view
5+1Configurable modules
±15%Estimate band
1Pricing config object
0Backend required

1 · What This Is & Why

Large corporations don't buy from a "contact us" form. Their evaluators want to self-serve a ballpark number before they'll put a vendor in front of procurement. The Estimate Engine gives them that number in under two minutes — while quietly demonstrating the exact kind of interactive tooling Vivere builds.

The calculator prices six areas — five build modules plus an organization profile:

ModuleWhat it coversPriced by
01 CalculatorsInteractive estimators, ROI tools, configurators embedded in the client's site or portalCount × complexity tier
02 BillingPayments, invoicing, subscriptions, ERP/payment-provider integrationsFoundation + recurring + per-integration
03 BlocksReusable content-block library and page templates the client's team assembles fromPer block + per page template
04 PhysicsMotion & physics-driven interaction — scroll choreography, particles, simulated scenesScenes × fidelity tier
05 Graphic DesignBrand kits, logo & identity, asset packs, illustration, motion graphics, print collateral, social templatesKit + logo + per-piece rates by type
06 Org ProfileSize multiplier, SSO, compliance posture, WCAG pass, languages, support retainerFlat adders + multiplier + monthly tier
The double play The calculator is both a sales tool and a portfolio piece. Module 01 of the price list — "Calculators" — is the thing the prospect is currently using. That's deliberate: the demo is the product.

2 · Storyboard — The Six Frames

The pilot follows this exact user journey. Each frame below sketches the screen state and the emotional beat we're aiming for.

$0
live estimate
Frame 1 · ArrivalOne headline, one promise: "Enterprise build estimate, in real time." No form, no gate, no pricing PDF. Beat: relief.
01 · Calculators
$3.4k
module cost
Frame 2 · First sliderUser drags "number of calculators." The module header price and the sidebar total move instantly. Beat: "oh, this is real."

SSO · Compliance · WCAG · Languages
×1.2
large-corp factor
Frame 3 · Enterprise factorsOrg profile: size, SSO, compliance, accessibility, locales. Enterprise overhead is priced openly, not buried. Beat: trust.
$48k – $65k
estimate band ±15%
Frame 4 · The rangeAlways a band, never a point price. Breakdown bars show where the money goes, module by module. Beat: informed.
Frame 5 · Take it with you"Print / Save Estimate PDF" renders a clean one-page sheet — the artifact the evaluator forwards to their boss. Beat: armed.
Estimate → Discovery → Proposal
scoped & signed
Frame 6 · HandoffThe saved config becomes the discovery agenda. Sales opens the call with the prospect's own numbers on screen. Beat: momentum.

3 · The Pricing Framework

Everything the calculator shows traces back to one plain-object config — PRICING — at the top of the pilot's script. The interface never hardcodes a dollar figure. That separation is the framework:

CONFIG   (PRICING object — rates, multipliers, tiers)
   ↓
RULES    (compute(state) — pure function, no DOM)
   ↓
STATE    (user's slider/toggle selections, persisted to localStorage)
   ↓
RENDER   (module costs, range band, breakdown bars, print sheet)

The formula

moduleSubtotal = Σ module costs           // each: units × rate × tier multiplier
orgAdders      = SSO + compliance + WCAG + (locales × rate)
sizeOverhead   = moduleSubtotal × (sizeMultiplier − 1)   // mid 1.0 · large 1.2 · global 1.4
oneTime        = baseEngagement + moduleSubtotal + sizeOverhead + orgAdders
shownRange     = oneTime × (1 ± contingency)             // ±15%
timelineWeeks  = max(2, 4 × (oneTime ÷ $20k)^0.55)       // sublinear — budget adds crew, not calendar
monthly        = supportTier rate                        // separate line, never blended in

Design decisions worth defending

Rates are placeholders Every figure in the pilot's PRICING object is an illustrative starting value, not agreed Vivere pricing. Calibration against 3–5 real past engagements is step one of the rollout (Section 6).

4 · Best Practices

Distilled from what works in enterprise pricing tools generally, and from Vivere's own client-report experience:

  1. Ranges, never point prices. A single number reads as a quote and gets negotiated. A ±15% band reads as an honest planning figure and starts a conversation.
  2. Show where the money goes. The breakdown bars do more persuasion than the total. Evaluators need to defend the spend internally; give them the ammunition.
  3. Price enterprise overhead openly. SSO, compliance, accessibility, and localization appear as visible line items. Burying them in a multiplier is where trust dies in procurement.
  4. No gate before the number. The estimate is free and instant. The detailed proposal is what sits behind discovery — consistent with our gated-report standard for execution detail.
  5. The exit artifact is a document. Enterprise decisions travel by PDF, not by URL. The print sheet is a first-class feature, not an afterthought.
  6. Config over code. Anyone adjusting rates edits one object. If a rate change requires touching markup, the framework has failed.
  7. Persist the configuration. Evaluators return, tweak, and re-print. localStorage in the pilot; a shareable config URL in v2.
  8. Keyboard and screen-reader clean. Real range inputs, aria-pressed segmented controls, a polite live region on the total. A tool that claims WCAG passes as a line item had better pass one itself.
Anti-patterns to refuse Fake "calculating…" spinners to simulate depth · email-gating the ballpark number · point prices with hidden multipliers · "starting at" figures that no real configuration can produce.

5 · Pilot Proof of Concept

The pilot is live in this folder as a single self-contained HTML file — no build step, no backend, deployable to Cloudflare Pages as-is.

Youbuild me an estimated calculator with parameters — calculators, billing, blocks, physics, graphic design — for large corporations. I want a storyboard, best practices, a framework, and a pilot proof of concept.
AgentBuilt both halves: index.html — the working pilot (five modules + org profile, live range, breakdown bars, print sheet, saved config) — and this document covering the storyboard, framework, and best practices. Rates are placeholder values in a single PRICING config, ready to calibrate.

What's in the pilot (v0.1)

CapabilityStatusNotes
Five build modules + org profile✔ BuiltSliders, toggles, segmented tiers
Live estimate band ±15%✔ BuiltUpdates on every input, aria-live
Per-module breakdown bars✔ BuiltIncludes discovery base + enterprise overhead
Timeline + monthly support line✔ BuiltDerived from blended rate; support never blended
Print / PDF estimate sheet✔ BuiltOne-page, GVEC-adjacent print styling
Config persistence✔ BuiltlocalStorage, shared across both views; reset clears
Side taskbar — module subtotals + client details✔ Built (v0.3)Company / contact / project print on the receipt
Graphic design studio (7 asset types)✔ Built (v0.3)Kit, logo, packs, illustration, motion, print, social
Demo key (sample configuration)✔ Built (v0.3)One press loads a realistic large-corp config
Calibrated rates◻ OpenNeeds 3–5 past engagements as ground truth
Lead handoff (email config to sales)◻ Openv2 — optional, after the number is shown
Shareable config URL◻ Openv2 — encode state in query string

6 · Rollout Ladder & Next Steps

RungActionExit criteria
1 · CalibratePrice 3–5 completed Vivere engagements through the engine; adjust PRICING until it lands within the band on all of themEvery back-test inside ±15%
2 · StageDeploy to Cloudflare Pages staging; internal review on desktop + mobileJoe signs off on staging URL
3 · EmbedLink from vivereweb.com services page; watch which modules get configured most2 weeks of usage signal
4 · CaptureAdd optional "email me this estimate" — after the number is shown, never beforeFirst inbound configured lead
5 · ForkRe-skin per client vertical (the config-driven framework makes this a rates-and-colors job)First client-branded instance
Immediate next step Rung 1 — calibration. Nothing ships to a prospect until the placeholder rates are replaced with numbers back-tested against real engagements.