How to showcase a tailored graphic-design, reporting, and pricing platform — and walk a client through it live.
An enterprise buyer doesn't get sold by a features list — they get sold by watching something that already looks built for them. The showcase has two layers: one they can look at alone before a call, one you unlock together on the call.
Layer 1 does the work before you're in the room — it's what you send 24–48 hours ahead so the prospect arrives already impressed. Layer 2 is what you unlock live, and the unlocking itself is the demonstration: a login gate is the fastest, cheapest way to make "custom-built" visible instead of just claimed.
| Layer | Component | Purpose |
|---|---|---|
| 1 · Showcase no login | Landing page | Brand impression — this is where "custom design" and "user-friendliness" get proven by feel, not claimed in a sentence |
| Sample report | An anonymized or generic example of the data-driven summary format, so the format is familiar before their own version is revealed | |
| Design gallery | Portfolio of prior brand/asset work — the visual proof behind the graphic-design pricing module | |
| Open teaser calculator | Generic version of the Estimate Engine — lets them play before they've given you anything | |
| 2 · Pilot gated login | Client-branded login | Their name, their logo, their colors on the splash screen — the moment described above |
| Admin dashboard | CRM-lite view — milestones, project status — what running the relationship with Vivere would actually look like day to day | |
| Data-driven report | SWOT / summary built from their own public info — gated per our standard: strengths & weaknesses shown, full opportunity/threat analysis behind a signed retainer | |
| Pricing / Estimate Engine | Same config-driven engine as the showcase teaser, pre-seeded with modules that match their actual business | |
| Design calculator | Brand kit, asset-pack, and illustration pricing rendered in their brand colors where possible |
This is the single highest-leverage tactic in the whole playbook, and it costs almost nothing: before the call, pull what's publicly available about the prospect — logo, brand colors, industry, a competitor or two — and pre-populate the pilot with it.
Prepared for fieldWalking in with this already done reframes the entire meeting. Instead of "let us show you what we could build," it's "here's what we already started — let's finish it together." That reframe is worth more than any slide.
A live run is roughly 20 minutes. Each beat below has what's on screen, what you click, and a talk-track line — adapt the wording, keep the sequence. The sequence is built to end on something they built, not something you told them.
| They say | You say |
|---|---|
| "Is this really custom, or a template with our name pasted in?" | Point back to the login, the colors, and the report — all built from their own public information before today. |
| "How did you get our data?" | Entirely public sources — your own site, public listings, public socials. Nothing private, no assumption of a relationship that doesn't exist yet. |
| "What's the real number?" | The range they just built together is a planning figure. Final pricing is confirmed in a scoped proposal after a discovery call. |
| "Can we get real admin access to try it ourselves?" | Yes — once a scoped pilot period is agreed. Today's login is the preview of that, not the product itself. |
Be exact with yourself about what the pilot actually is before you're exact with the client about it. Overselling a demo shell as production-grade security is the fastest way to lose trust with an enterprise buyer the moment their own security team asks a follow-up question.
| Component | In the pilot | In production |
|---|---|---|
| Login | Single shared demo password behind a client-branded splash screen | Per-client isolated account, real roles — reuses the SIGNAL app's per-client login pattern |
| Report | Pre-built once from public data, static for the meeting | Live-refreshing, tied to real data sources once scoped |
| Pricing engine | Same open config-driven engine as the public teaser, pre-seeded with their likely modules | Same engine, wired into the CRM to save and track real quotes |
| Admin dashboard | Read-only mockup with representative sample milestones | Real project data, real task state |
The pilot proves the idea. Going live means turning each shell in Section 6 into the real thing, in order of what's actually risky versus what's just work. Below is the concrete punch list, plus which model should carry each step — because handing routine build work to the top-tier model wastes budget, and handing the one security-sensitive decision to anything less risks getting it wrong.
| Step | What it involves | Model | Why |
|---|---|---|---|
| 1. Polish the public showcase | Wire the real contact flow, remove the pilot's noindex tag, add it to vivereweb.com's nav |
SONNET 5 | Well-specified UI and copy work — Sonnet's default lane |
| 2. Real per-client login | Design, then build, isolated client accounts — reusing the SIGNAL app's per-client login and data-isolation pattern | FABLE 5 to design → SONNET 5 to build |
The one genuinely security-sensitive call in this whole build. Get the architecture right at the top tier, then hand the well-specified implementation to Sonnet |
| 3. Live data-driven reports | Replace the static pre-built sample with reports generated from real per-client data sources | SONNET 5 | Mechanical integration once the data sources and template are chosen |
| 4. CRM-connected pricing | Save quotes built in the Estimate Engine into Vivian instead of just localStorage | SONNET 5 | Follows Vivian's existing integration patterns — routine wiring |
| 5. Security & privacy review | Full review of the login, data isolation, and storage before any real client data touches the tool | FABLE 5 | The highest-stakes checkpoint in the rollout — a mistake here is the expensive kind, not the fast-to-fix kind |
| 6. Rate calibration | Replace placeholder PRICING values with numbers back-tested against 3–5 real past engagements |
SONNET 5 | Plenty of model for the spreadsheet-style analysis — the actual rate decision stays a business call for Joe and Mike, not a model's to make |
This plan gets sharper with your read on it. Use the fields below — your goals for this build, the skills you're bringing, anything else on your mind. It saves right here in your browser, so the next time this page is opened here, your notes are still in it.