One link, five pages, and the exact prompts to pick up the build from here.
A self-contained pricing-calculator pilot for pitching custom enterprise builds — graphic design, reports, billing, animation, admin tooling — priced transparently and built to double as something Vivere uses on its own site. Five plain HTML files, no build step, no framework, no dependencies. Every dollar figure traces back to one PRICING config object per file, so rates can be tuned without touching the interface.
The flagship "physical calculator" — LCD display, keypad, receipt tape, client-detail sidebar.
Slider-and-toggle version of the same engine. Shares saved state with the calculator.
The pricing formula, storyboard frames, best practices, rollout ladder.
Sales walkthrough script, objection handling, next-steps roadmap, notes box.
The one page in this set that's actually safe to send a real prospect or link from vivereweb.com. No internal strategy talk — just the teaser calculator, a sample report, and design work.
The full punch list with a model recommendation for each step lives in pitch-playbook.html, Section 8. Short version:
| Step | Model |
|---|---|
| Polish the public showcase, wire a real contact flow | Sonnet 5 |
| Design + build the real per-client login (isolated accounts) | Fable 5 to design → Sonnet 5 to build |
| Wire reports to live data instead of the static sample | Sonnet 5 |
| Connect the pricing engine to the CRM | Sonnet 5 |
| Security & privacy review before real client data touches it | Fable 5 |
| Calibrate placeholder rates against 3–5 real past engagements | Sonnet 5 (final call on rates stays with Joe/Mike) |
Paste the orientation prompt into a fresh Claude session first — it works on any model, since it's just context. Then paste whichever task prompt matches what you're starting on. Each one is self-contained; none of them assume the session has seen this conversation.
I'm continuing the Vivere Estimate Engine project — a self-contained pricing-calculator pilot Vivere built to pitch custom enterprise builds (and to use on our own site). Everything lives in one folder with 5 plain HTML files, no build step, no framework, no dependencies: - index.html — the flagship "physical calculator" (LCD display, keypad, indicator lights, printable receipt tape), with a side taskbar for entering client details (company/contact/project) that print onto the receipt - dashboard.html — a simpler slider-and-toggle panel version of the same pricing engine; shares saved state with index.html via the localStorage key "vivere-estimate-pilot" - storyboard.html — internal doc: storyboard frames, the pricing framework/formula, best practices, rollout ladder - pitch-playbook.html — internal doc: the sales walkthrough script for pitching this kind of build to a client, objection handling, a pilot-vs-production honesty table, and a "Next Steps to go live" section with model-assignment guidance - showcase.html — the ONLY customer-safe page of the five; a public teaser calculator, a sample report, and a design gallery, meant to actually be shown to a real prospect or linked from vivereweb.com The pricing math lives in a PRICING config object duplicated near the top of index.html, dashboard.html, and a condensed version in showcase.html — every dollar figure in the UI traces back to that one object. All current rates are placeholders; they have not been calibrated against real past Vivere engagements yet. It's deployed to Cloudflare Pages already at https://vivere-estimate-engine.pages.dev (project name vivere-estimate-engine, production branch master). Read all 5 files before doing anything else. Once you've read them, tell me what you understand the project to be in a few sentences, then wait for me to tell you which next step to start on.
Polish showcase.html so it's ready for a real prospect to see, not just a demo of the concept. Specifically: replace the mailto:hello@vivereweb.com placeholder with our real contact flow (ask me for the actual link or form if you don't have it), remove the noindex robots meta tag once we're ready for it to be found by search, and add a link to it from vivereweb.com's navigation. Don't touch the pricing engine or the other four files — this step is presentation-layer only.
Right now, "logging in" to this pilot is a single shared demo password behind a client-branded splash screen — there's no real account system behind it. Design the real version: each client company gets its own isolated account, so no client can ever see another client's saved quotes, uploaded details, or report data. There should be two roles — an admin view (Vivere team, full access to pricing and client data) and a client-viewer view (that client's own data only, read-only where appropriate). We already have a similar per-client login and data-isolation pattern built for the SIGNAL app elsewhere in Vivere's systems — ask me for details on that pattern before designing this from scratch, since we may be able to reuse it directly. Don't write the implementation yet — first give me the account/data model and the auth flow, and flag anything that needs a real decision from me before you build it.
The PRICING config object in index.html and dashboard.html is full of placeholder numbers. Help me calibrate it: I'll give you the scope and final price of 3-5 real past Vivere engagements. For each one, translate its scope into the calculator's parameters (calculators, blocks, pages, design assets, org size, etc.), run it through the existing compute() formula, and show me how far off the calculator's estimate lands from what we actually charged. Then suggest specific rate adjustments in the PRICING object to close the gap, and show the same back-test again with your suggested rates applied.
This live URL is enough for reviewing and clicking around — nothing to install, works in any browser. But to actually edit or build on it, Mike needs the real files, not just the link.
estimate-calculator folder — 5 files, well under a megabyte, zero dependencies — and sends it over (email, Slack, Drive — whatever's easiest).