Understand the consequence
Vinci lets hardware teams ask physical questions while the design can still change.
Vinci × SVZ · Digital partnership proposal · Release 01: websiteConcept 01 · The promise
Physicscananswerback.
Ask a design what happens next. See the physics on the object, understand what must change, and decide before it is built.
A website for physics that answers back. The first release of an embedded digital partnership: the foundation for how Vinci is understood as it grows.
Bring a design or reference photo
STL, OBJ, ZIP · JPG, PNG, WebP. Read locally in your browser; nothing is uploaded.
Peak–
- YYou
Upload this part. Put the ‘top’ sources on the bottom of the top si layer. Put the ‘bottom’ sources on the top of the bottom si layer.
What am I looking at
The board from Vinci’s own demonstration: 2_PCB_A64-OlinuXino, 18 layers. Every number is the demo’s. The interface and the field between the verified points are an SVZ reconstruction, not Vinci’s software.
Drop the design file. Say where the power is, in a sentence.
Confidential
Prepared for Vinci’s leadership · September 2026 · Formal pitch, Friday September 18
The vision is the spine of this site. One loop is the proof it’s real: upload a design, ask it a question, trace the physics, leave with a decision.
An opening product story
A better time to ask.
Before the design becomes hardware. Before a late discovery becomes a redesign. Start with a question, then see the full product story in the same workspace.
See the idea before learning the interface.
The object, the conversation and the evidence stay together. Choose a physics tab or a recent study, move through the steps, and compare the two visual directions without changing the study.
The same story, two visual directions
This is the same working demo as the homepage, not a separate interpretation. The thermal values come from Vinci’s demonstration. Time-dependent and warpage treatments remain illustrative, with their evidence boundaries visible in the workspace.
Future scenarios: the same story on a different object
Illustrative future applications, not current deployments, solver results or an agreed product roadmap.
Why lead with “Physics can answer back”?
“Physics has shifted left” names the strategic shift. It may still need translating for someone outside a software or simulation workflow. Our recommendation is to make the benefit obvious first: ask a design, see the physics, decide before it is built. Keep the category line, but let the object explain it. This is a messaging hypothesis to validate with Vinci’s audiences, not a claim that audience testing has already happened.
Two landing pages · the first release of the new messaging
The current landing page can be replaced in one to two weeks. The messaging is what has to be right.
The interactive demo above shows how a visitor learns the product in one flow; it is a teaching device, not what the marketing is built around. Both directions carry the same messaging and the same flow. Choose one, and the first landing page of the new site ships while the full build begins.
Landing page · Direction A
Concept 1 · modern, product-led
The category line up top, the living mark as the brand behaviour, the working product below the fold. A new visual system built for the message.
Open this direction
Landing page · Direction B
Currently on brand · Vinci’s type and palette
The same messaging and the same interactive flow inside the identity Vinci already owns. Proves the story does not depend on a redesign to land.
Open this directionSection 02 · What the brief is really asking
What the site does today, what it costs, what it must start doing, and which part of one system fixes it.
Make Vinci understood as the intelligence infrastructure for hardware engineering.
You told us what the current site gets wrong. Read across a row and the relationship is the point: each flaw has a cost, each cost has a fix, and every fix is one part of the same system. Nothing on this page is a separate idea.
The site today your words
Sells the product, not the category. Leads with simulation speed and resolution.
What it costs
A reader learns Vinci is a faster tool. The vision, the intelligence infrastructure for hardware engineering, never gets said.
What it must start doing
Say the category first, then let the product prove it.
Fixed byThe category line and the lead message →The spine of this proposal
Make Vinci understood as the intelligence infrastructure for hardware engineering. Not a faster simulation tool. One recommendation; everything on this page is an expression of it.
- 01How it soundsThe tone sheet: direct, specific, solver-accurate. Consequence before mechanism.Section 03 · Tone sheet →
- 02What it says firstThe plain-language promise first, then the category line and supporting hero concepts.Section 03 · Messaging →
- 03How it looksYour mark, given behavior: the thermal spectrum as the one saturated thing on screen.Section 06 · Field as brand →
- 04How it shows the productThe object leads. Ask, trace, decide, in one conversation.Section 07 · Instrument →
- 05Who it is written forFour audiences, in your order, each with a first screen and a path.Section 04b · Audiences →
Section 03 · Current messaging → future direction
Your system, evolved. Three hero concepts that test one line, and the tone sheet the whole team can use.
Current messaging → future direction.
Your system, evolved, not swapped. Left is what the site says now. Right is the direction, in your own words wherever you gave them to usVinci’s languageSVZ recommendation
LayerCurrent messagingFuture direction
Category lineMessaging system
Simulation tools haven’t kept pace with modern design complexity.
The intelligence infrastructure for hardware engineering.Vinci
Lead claimHomepage H1
Solver accuracy at 1000× speed.
Physics can answer back. Know how a design will behave before it is built.SVZ
The product nounGlossary rule
“Physics AI foundation model”, lowercase, plural-adjacent.
Foundation Model for Physics. Capitalized, always singular. The world’s first.Vinci
Precision wordsTone sheet
“No meshing” · “solver-grade”.
“No human meshing” · “solver-accurate”. The meshing happens; the model does it.Vinci
ScopeCategory page
Semiconductor packaging.
Semiconductors are the proof, not the limit. From chip to package to board to system.Vinci
How the physics is framedProduct pages
Vinci-Thermal, capabilities, modules.
One system that reasons across domains, over time, at full resolution. Never a suite.Vinci
ProofClaims register
Numbers without conditions: 240×, 360×, 1000×.
Five public claims, each with its condition on the same line. Lead with what the speed changes.Vinci
Who it speaks toAudience order
Simulation engineers.
Technology leaders and market makers first, then engineering leadership, then the specialists who will check us.Vinci
Type and colourType system
Overpass Mono + Crimson Text, static. Colour used decoratively.
The same pair, given a screen scale. Colour reserved for physics: if it is saturated, it means something physical.SVZ
The markIdentity behavior
The circle acts as a fixed mark.
The thermal field becomes a behavior across marks, masks, objects and data surfaces.SVZ
Example hero H1 and paragraph five concepts, one system
The hero at the top of this proposal cycles through these. They are not competing options: each one tests the same category line from a different angle, with the plain-language promise first and the category language explained in context.
Concept 01 · The promise tests Plain-language entry · the product supplies the proof
Physics can answer back.
Ask a design what happens next. See the physics on the object, understand what must change, and decide before it is built.
Evolved fromSVZ expression of Vinci’s shift in when physics arrives. Lead recommendation, not audience-tested copy.
Supporting product languageProduct invitation Talk to your hardware before it’s built. A supporting line for a product page or call to action, rather than another opening slide.
Deliverable · Tone and Messaging Sheet v0.1 · built from your booklet and your September 13 response
How Vinci sounds, in one sheet the whole team can use.
Direct, technically credible, declarative. We let proof do the selling. Our enthusiasm is specificity.
- Consequence before mechanism
- What changes for the reader, then how it works, then the evidence, then the category name.
- Specific over superlative
- A number with its condition beats an adjective. Never “game-changing”, “revolutionary”, “we’re thrilled”.
- The engineer decides
- The model does multi-step setup and runs. The engineer directs it and decides what the results mean. Never “AI replaces engineers”.
- Describe the shift, not the competition
- No competitor names, ever. “Legacy solvers” or “leading commercial FEA” is as pointed as it gets.
- No exclamation marks
- If a slide is shouting, it isn’t Vinci yet.
Vinci VIN-chee, like Leonardo. “Vinci4D” is legal paperwork and the email domain only.
Section 04 · Direct response to the brief
How the site creates belief at three depths, the process behind it, and what each of your six readers needs to be true.
The website has to create belief without asking engineers to suspend disbelief.
Vinci does not need one story for executives and another for engineers. It needs one story with deliberate depth: consequence first, product behavior next, evidence always within reach. The first-time visitor understands the category; the engineer who challenges the claim can inspect it.
See the behavior
A real question, a real object, a resolved field, and a decision, not a cloud of category language.
Inspect the proof
Methods, conditions, validation, limits, and technical content stay attached to the claim.
How, exactly · follow one number
Every number on the site travels with its conditions. Here is the path, end to end.
Belief is not a tone of voice. It is a process an engineer can audit: where a number came from, the record that holds its conditions, the label it wears, what each depth of reader sees, and the check that refuses to publish it naked. Pick one of Vinci’s own numbers and follow it.
- 01
Source
Vinci’s public demonstration, August 31, 2026 · the 18-layer board · transcript line
- 02
Register record
- Source
- Proof-library recording, timestamped; SVZ transcript
- Condition
- Static conduction · top h = 5000, bottom h = 500, sides adiabatic · 1600×1600
- Status
- Demo-verified
- Limitation
- One board, one run. Not a benchmark; not transient.
- Reviewer
- Vinci engineering · named on engagement (R33)
- 03
Label on the page
Current Vinci evidence
The same six labels run through this proposal and will run through the site. The label is generated from the record; nobody types it.
- 04
Three depths
- 5 sec
- “The hottest point is 83.9 °C, and Vinci can tell you why.”
- 50 sec
- The board, the hotspot on the object, the layer that blocks the heat. One trace.
- 5 min
- Boundary conditions, resolution, the sweep table: h = 125 fails at 95.7, h = 144 passes at 94.5.
- 05
Release check
Publishes: source + condition + status + limitation present. Reviewer pending → label says so until named.
The technical process behind it
- A claims register, as a CMS collection. One record per number or statement: source, condition, status, limitation, reviewer, approved-on. It starts from your handbook and your September 10 response on day one of onboarding.
- Every published number references a record. Copy does not carry numbers as text; it carries a reference. Change the record, and every instance updates, condition included.
- Labels are generated, not typed. The status on the record decides the label on the page. Six labels, one source of truth, no drift between sections.
- Release QA blocks a publish that fails the rule. A number without a condition, a claim without a status, a customer name anywhere: the release does not go out. The check runs in your Slack channel through SVZ OS, and the log stays.
- Review windows are the ones you set. Two business days for claims, non-compressible, with a named engineering reviewer (R20, R33). The record shows who said yes and when.
- 01
One site for technical and non-technical audiences
Build progressive depth instead of splitting the story: consequence in five seconds, product behavior in fifty seconds, and inspectable evidence in five minutes.
- 02
Relevant SaaS and infrastructure work
Patreon, Instead, Traversal, Ambient.ai, Oasis, and Saildrone demonstrate the same operating pattern: complex products, high-scrutiny audiences, and systems built to evolve after launch.
- 03
The actual day-to-day team
The people named here do the work. The senior pod runs the account; specialists enter for the narrow things nobody should staff full time, always through a named owner on the team.
- 04
A point of view on the inspiration set
Borrow restraint, immediacy, and institutional confidence, but not anyone else’s costume. Vinci should differentiate through visible product behavior and evidence competitors cannot show.
- 05
A team that understands the product
The instrument, the loop on the real board, and the physics rules we held ourselves to came from public evidence. With Vinci, inference becomes access: your engineers, solver outputs, customer questions, and approved claims. This is the opening argument, not the finished work.
- 06
Timeline and the path from positioning to launch
One overlapping program, dated around your October freeze, with the gate owners you named. Narrative, architecture, design, and development move together, with four dated moments where Vinci says yes before the next phase begins, and no handoff where strategy gets lost on its way to production.
Who is reading this, and what each of you needs to be true
One proposal. Six readers. We wrote to each of you.
The founder, the strategist, the day-to-day owner, engineers, finance, and the community team will read this for different reasons. Here is the decision each of you is making, where we have answered it, and what you told us on September 10: the full ledger of what you sent and what it changed is in section 12.
You need to know we see Vinci as the intelligence infrastructure for hardware engineering, not a prettier simulation company.
We do. The category is the intelligence infrastructure for hardware engineering; Continuous Physics Reasoning is where it begins; semiconductors are the proof, not the ceiling. Every visual starts with physics Vinci has shown publicly, and every extension is labelled for what it is.
Shown inWhat the brief is really asking · The recommendation · One system, two reasoning domains: your roadmap, in your order
Where we areYou told us: the three things the site gets wrong, the language you lead with and never use, the numbers you share. Applied throughout; still open: how the finalists are scored.
You want a partner who challenges the brief, connects the website to the whole customer experience, and stays strategic after launch.
We disagreed with the brief where it mattered (one story with depth, not two audiences) and we made the site the persistent counterpart to Opus’s event program rather than a brochure beside it.
Shown inDirect response, including the reference-set position · How the site turns an event into a community · The team and the operating system after launch
Where we areYou told us: five in the room, the full ninety minutes as our pitch on the vision. Still open: the scoring, and where Opus and the site meet, which you and Lauren decide.
You need the senior quality in this pitch to survive delivery without you becoming the integration layer for several agencies.
The senior team named here runs the account, with one lead point of contact per time zone, in practice the same person every day. Ownership, approvals, releases and decisions live in #svz-vinci with a system that remembers, so you never ask “who has this?”
Shown inThe team, coverage, and SVZ OS · Four decisions, by date, around your freeze
Where we areYou told us: daily async, the Monday call and page, you as one voice back, two-day review windows, the October freeze. Built into the plan; nothing still open.
You need the site to stay technically honest, and this team to translate the product without inventing capability.
Every quoted number in this document is a transcript number. The field is labelled illustrative where it is; the instrument is labelled a reconstruction; convection is a boundary condition, not a flow we solved.
Shown inThe loop, demo-verified · The instrument, with its truth boundary · Only the physics you ship
Where we areYou told us: which domains ship, how to say it, the two public studies, the formats you ingest, solver-accurate and deterministic as the anchors. Still open: the benchmark methodology and two named reviewers.
You need “embedded” to mean a team you can direct, not an open tab of hours, and an offer controlled enough to buy.
One partnership at four levels. Vinci steers, SVZ delivers; the level sets what you can ask for and the capacity we hold. Thirty days’ notice moves you up, forty-five moves you down, the contract holds throughout, and more than the level carries is agreed before it starts, never discovered on an invoice.
Shown inThe partnership: first quarter, levels, and terms
Where we areYou told us: acceptance authority at each gate, and that procurement and the master agreement follow the decision. Still open: the owners for both, named after the award.
You need the digital system to extend the physical program, not compete with it or duplicate it.
Before, during and after each gathering, one narrative and evidence system carries the relationship forward. The site is where the room keeps talking.
Shown inBefore, during, after
Where we areYou told us: the calendar through Q1, the multi-year Opus engagement, John and Lauren deciding where physical meets digital. Still open: the Opus SOW, the flagship brief, and attendee data flow.
Before, during, after
How the site turns an event into a community.
The event is a moment; the site makes it compound. Here is the mechanism before, during, and after each gathering: what the site does, what a visitor can do, and what Vinci keeps.
The room fills with people who already understand the loop.
What the site does
- An event page that is a study, not a schedule: the demonstrated loop, the speakers’ questions, the physics on the object.
- Registration that asks one engineering question (what would you ask your hardware?) and seeds the session agenda with the answers.
- Pre-reads by role: five seconds for the executive, five minutes for the engineer, both pointing at the same evidence.
What a visitor can do
Register, bring a question, read the proof before the talk.
What Vinci keeps
A list of named people with a named question each, before the doors open.
Working with OpusOpus runs the room. We run everything that is not the room: the same story and the same evidence before anyone arrives and after everyone leaves, with one link between the two. Event dates, formats and audience come from their program; our surfaces are built to receive them.
04a · Who the site is for · your four audiences, in your order, as people
Four ICPs arrive. Each one is owed a different first screen.
You gave us the audiences in priority order. We turned each into a person, listened for what they hear, see, think and feel, then mapped the goal they came with to the benefit they want, to where on the site it lives, and to whether it is up front or a click away, and why. The paths they light are in 04b.
Reads forty companies a month. Has fifteen seconds for a homepage and a strong nose for a tool dressed as a platform.
- Hears
- “Physics AI” from six startups, “AI for CAE” from the incumbents, “simulation is a solved problem” from her partners.
- Sees
- A site that opens on speed multipliers and a semiconductor package. She files it under tools.
- Thinks
- “Is this a category or a feature? How big does it get after chips?”
- Feels
- Interested, impatient, allergic to adjectives.
Pains
- Cannot tell infrastructure from tooling in one screen
- Semiconductor framing caps the market in her head
- No business consequence stated, only technical benefit
Gains
- A category she can repeat in one sentence
- A visible path from proof (chips) to market (everything with a chip in it)
- Evidence that engineers already vote with usage
Main traitsAltitude firstPattern-matcherRepeats what is quotable
What Mara came for, and where the site answers it
- Up front
Size the opportunity in one screen
- So they get
- Decide in fifteen seconds whether to spend fifteen minutes
- Lives at
- Home hero · category line
- Why there
- Her first audience position (R10) earns the first screen.
- Up front
See the market beyond semiconductors
- So they get
- A thesis she can defend to her partners
- Lives at
- The physical stack · chip to system to everything
- Why there
- It answers “stops at semiconductors”, the brief’s second flaw.
- One click
Confirm the depth is real
- So they get
- Confidence the category has a moat
- Lives at
- Research index · adoption curve
- Why there
- Proof, but not before the thesis.
2 of Mara’s 3 goals are answered on the first screen. The rest are one click away, on purpose: the site gives each reader their depth, not everyone’s. See the path this lights →
Composite, fictional people built from Vinci’s audience notes of September 13. Portraits are generated illustrations, not photographs. Order is Vinci’s.
04b · Connected journeys · your four audiences, in your order
One site. Four arriving questions. Every path connected.
You gave us the audiences in priority order. Each one arrives holding a different question, so each one needs a different first screen, but they all land on the same proof, and the paths cross. Select an audience to light its way through the site.
- Home · the vision, then the loopArrive
- Category page · physics has shifted leftArrive
- Research index · the public studiesProof
- How it works · upload, ask, trace, decideProof
- The instrument · a real board, driveableProof
- Proof library · the two cleared studies + the webinarProof
- Benchmark page · demonstrates, once methodology landsProof
- Ingest · GDS, OASIS, STEP, IPC-2581, ECxmlProof
- Events · before, during, afterProof
- Executive briefing · the Q1 flagshipNext
- Technical evaluation workspace · bring a partNext
- Talk to Vinci · the conversation, not a formNext
Arriving question
“How big is this, and why now?”
What answers it
The category page carries the consequence in one screen; the research index shows the depth is real; the adoption curve shows engineers already vote with usage.
The next step the site offers
The executive briefing around the Q1 flagship: a seat, not a form.
3 of this path’s 5 stops are shared with another audience. That is the point: one story, read at four altitudes.
Your calendar feeds every path
The dates you named. Each becomes an audience before it happens and a community after. The mechanism is in Before, during, after. The freeze is respected; the announcement is yours, and the site is built to carry it.
- Sep 2026SemiWiki webinar · the open-source-design studyDated
- Sep 2026TSMC OIPDated
- 1–20 OctReview freeze · homepage takeover for the October 6 announcementNo gate inside
- Oct 2026SEMICON WestDated
- Q4 2026Plug and PlayDated
- Q1 2027The flagship · tentative, may shiftTentative
Reference-set position
Borrow the standard. Refuse the sameness.
You named two, and we agree. We take the function each one performs and refuse the visual habits that would make Vinci look like one more AI company. No competitor is named or compared; every borrowed function must survive on Vinci’s own proof.
Anthropic
- Borrow
- Enthusiasm expressed through specificity rather than adjectives; research credibility carried by the work.
- Avoid
- Performing like a research lab when the product can carry the proof. Vinci’s object answers back, so let it.
Palantir
- Borrow
- The operating-model argument: consequence-led, institutional, built for the reader who runs a program.
- Avoid
- Broad platform language that outruns the evidence. Every claim on Vinci’s site keeps its conditions attached.
Section 05 · The recommendation
Four moves that make physics the behavior of the brand, the product story and the proof.
Make physics the behavior of the brand, the product story, and the proof.
Your vision, built: the digital expression of the intelligence infrastructure for hardware engineering.
Build one connected Vinci experience where physics is not illustrated after the fact. It becomes the brand behavior, the interaction model, the proof system, and the product interface.
- 01
Field as Brand
A simulation-inspired field becomes the reusable identity behavior.
Heat enters, moves, settles: the mark performs the first beat of the loop before a word is read.
- 02
Object as Instrument
The product object becomes the place where questions, physics, and decisions meet.
Ask the object why, trace the cause, sweep the condition, read the verdict. The demonstrated loop, driveable.
- 03
Evidence as Trust
Every public claim keeps its source, condition, status, and limitation attached. No customer is named. No number leaves its conditions.
83.9 °C is a run, 144 is a threshold, 29 is a model: each number carries what kind of truth it is.
- 04
Motion as Explanation
Time reveals cause, response, comparison, and consequence.
The sweep is an axis you move along. 125 fails and 144 passes on the same object, in the same frame.
Section 06 · Field as brand
Your mark, given behavior. What stayed, what moved, and where the same field travels.
Your mark already holds the physics. We gave it behavior.
Your brand guide says it plainly: the energy gradient is derived from thermal-modelling visualisations, applied as an irregular mesh: the physics made visible. We took that literally. The ball stayed. The bed stayed. The palette stayed. Heat now enters, moves, settles, and answers the pointer: the mark moves the way physics moves.
Current · VINCI Brand Guide 2025
“Evoking the movement of energy through a surface by leveraging the brand palette derived from common thermal modeling visualizations, but applied as an irregular mesh to add subtle physicality.”
Energy gradient · p.10
- Light#E6E6E6230 · 230 · 230
- Dark#48484872 · 72 · 72
- Cool#5C08FD92 · 8 · 253
- Ambient#ED1379237 · 19 · 121
- Hot#FFC63A255 · 198 · 58
- Signpost
- Overpass Mono
- Book
- Crimson Text
Suggested · the same mark, alive
- KeptThe circle, the wordmark, the palette, the mono signpost.
- KeptThe guide’s own metaphor: energy moving through a surface.
- ChangedThe gradient is computed, not painted: a field that moves the way heat moves.
- ChangedType gets a screen pass (scale, weight, tracking) and a display option for category moments.
Truth boundaryBrand behavior inspired by simulation. It becomes an evidence surface only when Vinci’s own data drives it. You said “open to changes”; this is the smallest one.
Live · move the pointerDirection A · the mark as a thermal object01 / 10
A01Blank start
Nothing is on screen until heat exists. The arriving pigment draws the circle.
Same solver. Same palette. Only where the heat is born and how it travels changes.
Seven ways the heat can arriveThe Direction-A entrances, rendered at 30 fps. Tap one to load it above; the long form is on Behind the mark.
Where it travels · click one
Live · same solver
01Logo
The mark arrives as heat, settles, and answers the pointer. Beside the wordmark, it is the logo; alone, it is the loader.
Brand behaviour · SVZ concept
Additional concepts under the markDirection B derives the field from the product itself (the demo’s cluster, board footprint, sweep and stack) and a third direction keeps the same field in the engineering colormap as the evidence surface.See all directions on Behind the mark →
Section 06b · How Vinci works
The demonstrated loop in ten beats with the demo’s own numbers, and the five public claims you approved, each with its condition.
Upload. Ask. Trace. Decide. The loop the world needs to understand.
The demonstrated workflow, in product order, with the product’s own numbers. The first result is a starting point. The value begins when the engineer asks the object a question and gets a decision back.
Thermal study · 2_PCB_A64-OlinuXino18 Layers
Thermal · steady-statethis studyThermal · in timesame systemThermo-mechanicalstress · warpageone system · no customer data in training
Demo-verified valuesSVZ interface reconstruction
You
Upload this part. Put the ‘top’ sources on the bottom of the top si layer. Put the ‘bottom’ sources on the top of the bottom si layer.
Chat to the physics
Peak–
Demo-verified
Every quoted line is a transcript line. 18 layers, 83.9 °C baseline, 39 % / 68 % concentration, 54.1 % Top Si resistance, 125 fails, 144 passes, under 24 minutes.
Illustrative model
The field between verified values, the 29 modelled sources, and the nine unlabelled layers. Convection is a boundary condition, not a solved flow.
SVZ reconstruction
Interface, choreography, and explanatory copy. Not Vinci’s product implementation.
Claims register · first five entries · approved September 10
Your public numbers, kept in one register the whole site quotes from.
The five claims you approved become the first entries in a claims register built into the CMS. Each entry is a structured record: figure, what it means, the condition it carries, what kind of truth it is, source and status. Pages never type a number; they reference an entry, and the template renders the figure with its condition every time. That is what makes a number safe to publish at speed.
- Nothing goes stale
A new benchmark, a legal word, a retired figure: you change the entry once and every page that quotes it changes with it. No orphaned headline on a page nobody remembers.
- Marketing ships without re-asking engineering
Your named engineering reviewer signs an entry once. Pages reuse it without a new review, so the two-day claims window is paid once per claim, not once per page.
- Engineers see the same number everywhere
Same figure, same condition, in the hero, the proof page and the benchmark. Consistency is the first thing a skeptical engineer checks, and the register makes it automatic.
Entries 01–05 Source: Vinci response, September 10, item 07 · Status: approved, quoted with conditions
- 01
1.2Bdegrees of freedom
A full-resolution thermal solve at 3 µm, in about 219 seconds, on one node.
Vinci-stated · measuredConditionQuoted with its resolution and runtime. No manual meshing or setup.
- 02
~1 hvs ~16 hours
A 200-case design-of-experiments study, run as one job.
Customer-reportedConditionThermal, from one customer’s prior workflow. Not a transient claim.
- 03
4,800 → 25,600simulations
One team’s usage in consecutive thirty-day periods: engineers ask more when asking is cheap.
Adoption · usageConditionAn adoption figure, shown as a dated curve. Never a speed claim.
- 04
up to 1000×faster
The consequence first (decisions while the design can still change), then the multiplier.
Vinci-stated · measuredCondition“Up to.” Quoted with the workflow it replaced, never as a standalone headline.
- 05
0customer designs in training
No customer data trains the Foundation Model for Physics.
PolicyConditionPolicy, quoted as written.
Rule 01 · Vocabulary
Solver-accurate, never solver-grade. Deterministic: identical geometry, materials, boundary conditions and loads produce identical outputs. The benchmark page demonstrates rather than asserts, once the methodology arrives; it reads from this register.
Rule 02 · Native ingest
- GDS
- OASIS
- STEP
- IPC-2581
- ECxml
The site names exactly these formats. Anything else is a conversation with your team, not a drop zone.
Rule 03 · Who is named
No customer, logo, design or dataset, on or off the record. Future industries are labelled as ambition. The two public studies and the open-source-design webinar carry the proof.
Section 06c · One system, two reasoning domains
What the product reasons about today, the roadmap in your order, and where the same model goes next.
One system, reasoning across domains, over time, at full resolution. A roadmap the site grows with.
The demonstration showed conduction. Today the system reasons across thermal behaviour, steady-state and time-dependent, and thermo-mechanical behaviour, stress and warpage: expressions of one Foundation Model for Physics, never modules or a suite, with no training per customer. We put them on one board, then built the roadmap as a publishing system: each new domain moves from Roadmap to Live when Vinci has the product and proof to say so. A list is more trustworthy than “unlimited.”
- Live · this is the demo
01
Thermal reasoning · steady-state
Where heat goes at steady state, through every layer of the real part.
OutputPeak 83.9 °C · one hotspot · the cooling requirement
Demo-verified values on the demo board
- Live · shipped
02
Thermal reasoning · time-dependent
The same board through time: how fast it heats, where it lingers, when it settles.
OutputTime-resolved temperature histories
Illustrative treatment · live capability, not exercised in the demo
- Live · February 2026
03
Thermo-mechanical reasoning · stress and warpage
What the heat does to the shape: stress and displacement across the stack as layers expand differently.
OutputWarpage and displacement fields
Illustrative treatment · live capability, not exercised in the demo
The roadmap, in Vinci’s order
- Thermal convection (CFD)Next · 1
A boundary condition on this board today. The sweep in the demo moves it; a solved flow field is the next row.
- Electromagnetics (EM)Next · 2
Electrical and magnetic behaviour on the same manufacturing geometry.
- Cross-domain and coupled reasoningNext · 3
Shared geometry and conditions across domains. Coupling is intrinsic to the system, not a feature added later.
- Remaining physicsFurther out
Each arrives as a row changing state here, never as a module.
Order and framing as stated by Vinci, September 2026. Adding a domain is a row changing state here, not a rebuild. The same sentence we hold the instrument to.
Where the same system goes · the markets Vinci names
- AI accelerators and inference silicon
The proof: power density rising faster than packaging can follow.
- Data centers
The same system; the board, the rack and the room.
- Automotive, EVs and batteries
Inverters and battery structures that live or die on thermal margin.
- Aerospace, defense and drones
Long qualification cycles where earlier physics changes the schedule.
Illustrative. These are the markets Vinci names; we have not invented objects or results for them, and the site must not imply a deployment in any of them.
The sentence this roadmap writes · the blank is the market list
Ask a hot board why,
before it’s hardware.
Demonstrated · the object on this page
On the site, a row that changes state is a page that changes state · proposed information architecture, two of the Release 01 templates
- /physicsOne page per physics
Thermal and thermo-mechanical reasoning today; convection, electromagnetics and coupled reasoning as rows in the same template.
A status field (Live · Next · Roadmap) decides what each page may claim. Adding a physics is publishing an entry, not a project.
- /industriesOne page per market
AI accelerators and inference silicon · Data centers · Automotive, EVs and batteries · Aerospace, defense and drones.
Proof-gated: a market page publishes only when Vinci has a real object and a real result for it. Until then the hub carries the list as Vinci states it.
- /proof-library · /research · /blogThe collections you already run
Each row that changes state ships with a proof-library entry, the research it rests on, and one release post.
Editorial follows the roadmap order. The site never announces a physics before the product does.
Section 07 · Object as instrument
The demo board as a driveable object. Ask it the 95 °C question yourself.
Ask the part. It answers with a reason.
We built a working prototype of Vinci’s product surface so we could design with the real thing in front of us instead of a picture of it. Every layer is there, every number is the demo’s, and you can drive it: probe a column, isolate a layer, move the cooling and watch the verdict flip. It is ours to experiment with. It is a marketing surface we can shape however the story needs, and it is deliberately not a solver until Vinci’s own data is behind it.
Resolving the live object
SVZ concept prototype
A working prototype, built by us from the public demonstration so we could design against the real object. Not Vinci’s software.
Open in its own tab ↗Chat to the physics
You don’t type next to the part. You talk to it.
The composer and the object share one frame, so a question lands on the thing it is about. This clip carries the same grammar into an avionics enclosure: ask where the heat is peaking, get the cause on the object, approve the fix, watch the field change. A sketch of where it could go, not a product Vinci has shown.
Illustrative industry extensionCurrent Vinci evidence
Geometry, 18-layer stack, 1,020 sources, the demonstrated conditions, the 95 °C design target, and the sweep result: h = 125 fails, h ≈ 144 passes.
SVZ concept prototype
The interface, the controls, the explanations, and the field between the verified points are ours, computed in the browser.
Where it goes
The same instrument, driven by Vinci’s own model and solver output. Then it stops being a prototype.
Section 08 · Motion as explanation
Films and motion where time explains cause, each one labelled for the kind of truth it carries.
Motion shows cause, response, and consequence.
One motion grammar carries identity, product behavior, industry context, and proof. Each film answers one question; together they make the system easier to understand.
Vinci Motion · the web library ↗Tokens and six primitives, running live from the library code. Proposed deliverable.SVZ concept study
The identity has a behavior, not just a final frame.
Silent visual film. A warm thermal source fills the circle, settles into violet, and reveals the supplied Vinci wordmark.
Identity integration proof
From simulation to identity
A physical field travels from computation into an automotive object and returns as the Vinci mark. This is an integration proof for a future application, not a final campaign film and not a current Vinci result.
SVZ concept film · Illustrative future applicationOne future-product film system
Three industries. One explanatory grammar.
Each preview is an illustrative future-product demonstration, not a current Vinci deployment.
Aircraft thermal
An aircraft thermal question moves from context to a visible field and engineering consequence.
concept edit · native re-render and sound design required for final deliveryAutomotive power electronics
An automotive component becomes the surface for a thermal story without presenting invented product controls.
concept edit · native re-render and sound design required for final deliveryBattery transient
A battery module carries a transient field through time, then resolves into a legible result.
concept edit · native re-render and sound design required for final deliveryProof of process
Show the first step beside the produced result.
The sheet is the first-step proof of work: a bounded visual sequence derived from an approved frame set. The motion is the produced result. Keeping them together makes the production claim inspectable.
Approved sequence sheet
Silent visual study showing the thermal field progressing across the battery module.
Section 08b · Iconography
A glyph set that only names what the product does. Colour carries meaning in exactly one place.
The mark, extended. Twenty-eight readouts in the logo’s own physics.
The Vinci mark is a circle containing a temperature field. That gives the identity something most brands have to invent: a rule. Every icon is a boundary that contains a state: the same object as the logo, at small scale. It carries the mark into navigation, product surfaces, proof, and loading states without a second visual language.
The set · 28 glyphs · five groups
Nothing the product doesn’t do. The reasoning domains, the five-step loop, the objects, the evidence, the site. Hover a glyph for where it lives.
Physics
Only what the product reasons about today: thermal, steady-state and in time; thermo-mechanical. Colour carries meaning here.
The loop
Upload · First result · Ask why · Sweep · Decide. The hero’s five steps.
Object
What is being simulated: board, die, stack, hotspot, condition, probe.
Evidence
The trust layer: thresholds, verdicts, claims with sources, receipts.
Site
The current site’s real sections: nav and footer on day one.
Where they earn their keep
Thermal · steady-state · this studyThermal · in timeThermo-mechanical · stress, warpage
Proof · thermal · PCB
Minimum top-surface convection for a 95 °C ceiling
h = 125 fails · 95.7 °C
h = 144 passes · 94.5 °C
Demo-verified · source attached
Running the study…
Section 09 · What SVZ already demonstrated
Six things built before anyone asked: a real frame of each, and what kind of evidence it is.
What we built before anyone asked us to.
Six things, built in a few weeks from one public demonstration and a small approved asset set. Each card names what it is, what kind of truth it carries, and where to use it. With access to Vinci’s people, roadmap, and solver output, this becomes the beginning, not the limit, of what the team can build.
What this is evidence of
This is the work: understand the product to the layer, keep what Vinci already owns, and make it mean more. The sphere stayed. We found the physics inside it, then carried that physics through identity, interface, proof, and motion. One idea, doing six jobs.
See the work behind the mark ↗
01Identity behaviour
The living mark
Your mark already held the physics; we gave it behavior. One WebGL solver, the palette of the mark, ten motion concepts, frame-exact renders.
SVZ concept studySee it ↓
02Product-expression prototype
A working prototype of the product surface
The 18-layer board from the demo as a driveable object: probe a column, isolate a layer, move the cooling, watch the verdict flip. Built from public evidence; not Vinci’s software.
SVZ concept prototypeSee it ↓
03Messaging system
The messaging system
Four homepage messages tested inside one system, with a tone sheet, type system and copy direction behind them. Current vs recommended, row by row.
Proposed deliverableSee it ↓
04Motion library
Vinci Motion
A web motion library written as code, not mood: heat rise, field settle, sweep, trace, respond, count. Shared eases and durations so product, brand and site move as one system.
SVZ concept studyOpen ↗
05Product story · homepage hero
The loop, on the real object
Upload → first result → ask why → sweep → decide, on the demo’s board, with the demo’s numbers and a real file drop. No field before a study, a real probe column, a re-solved sweep.
Current Vinci evidenceSee it ↓
06Operating model
The operating model
The named senior team, follow-the-sun coverage, specialists when the work calls for them, and SVZ OS in Slack: the proposal becomes the way the account is run.
Proposed deliverableSee it ↓
Current Vinci evidenceSVZ concept studySVZ concept prototypeIllustrative industry extensionProposed deliverableFuture roadmap hypothesis
Section 10 · The partnership
Retain SVZ: the dated plan around your October freeze, four levels, and the terms that let us move at this pace.
Retain SVZ as Vinci’s digital operating partner. The website is what we build first.
One senior team, embedded with Vinci, scaling to what each quarter needs. Release 01 (the complete site, strategy through launch) is the first thing it builds, at Scale. After launch the same people carry the event runway, product proof, community and category releases at the level the roadmap asks for. Below: the dated plan, the four levels, and the terms that let us move at this pace.
Quarter one · Release 01
The complete site, strategy through launch. The first thing this team builds.
Five workstreams run as one program. Click any of them for the full process: what happens, who leads it, what Vinci does, what comes out, and the decision you make at the end.
Release 01 · at Scale · a representative first quarter
What a first quarter with this team looks like.
A floor, not a ceiling. The figures below are the launch minimum we commit to; a quarter at this pace typically produces twelve to twenty pages and around a hundred assets, and the site keeps growing after launch. Vinci sets the objectives each quarter and can ask for anything in the level’s wheelhouse; we estimate before we start, build, and report every week. A thirteenth page is a roadmap item, not a change order.
- Committed at launch
- 12 primary pages
- A typical quarter at this pace
- 12–20 pages · ~100 assets
- Running alongside, every week
- AEO/SEO agents on the technical side of the account: indexing, structured data, answer-engine visibility, redirects
- 12Primary pages at launch · minimum
- Each with its own brief, built for the job it has to do; none is stretched from a template. Twelve is where the site opens, not where it stops: a quarter at this pace runs twelve to twenty.
- 6Reusable templates
- News, proof, research and events publish from one system. Vinci’s team ships without waiting on an agency, including this one.
- 40Component variants
- A design system in code, not a style guide in a PDF. Every new page is assembled from parts that already match.
- 1Custom product interaction
- The physics working on the page, not a screenshot of it. You have already used the prototype: the instrument above.
- 3Forms
- Validated, routed and tested end to end. No lead lands in an inbox nobody owns.
- 3Integrations
- The tools Vinci already runs, connected and proven before launch day, not on it.
- ~70Existing URLs
- Every current address mapped, redirected or retired on purpose. Nothing Vinci has earned in search is left behind; the inventory is built on www.getvinci.ai across all eight post types, and the count is confirmed before Gate 1.
- 2Review rounds before each decision
- How the dates hold. You see every decision coming, and you are never asked to make one cold, and none falls inside your freeze.
The strategy underneath
- Competitor and reference analysis
- Messaging hierarchy and tone
- User stories and journeys
- Information architecture and sitemap
- Claims and evidence register
- Brand expansion into the digital world
- Opus working sessions and the event runway
- Digital release planning
Also in the first 90 days
- SVZ OS built around Vinci’s site: agentic workflows for publishing, review and monitoring
- AEO/SEO agents servicing the technical side of the account: indexing, structured data, answer-engine visibility, redirect health
- Roughly a hundred production assets across the quarter: frames, renders, motion, diagrams, social cuts
- Source code and CMS ownership
- Documentation and training
- Redirect and SEO report
- Performance and QA receipts
- 15 business days of stabilization
Dated around your October freeze · four decisions, with their owners
The phases overlap. The decisions are yours, and you always see them coming.
You asked us to set the gate calendar by date, working backwards from the freeze. We did: no approval falls between October 1 and 20, and the onboarding month does the work that needs no gate. Dates assume signature by the end of September and move with it, day for day. Click any phase for the full process.
Selected work · Live external proof
Complex products whose stories are expensive to get wrong.
Six live examples across community, AI, infrastructure, security, and autonomous systems.
Patreon
Brand, visual, and web work for a global product whose value depends on making complex creator and community relationships feel immediate.
Visit live site ↗Instead
Strategy, brand, and scalable web experience for software that must explain expert work to operators, firms, and business owners.
Visit live site ↗Traversal
Strategy-to-launch website work followed by continuous high-frequency releases for an AI SRE operating in mission-critical systems.
Visit live site ↗Ambient.ai
Ongoing category, website, customer-story, event, CMS, and technical QA work for an always-on reasoning platform.
Visit live site ↗Oasis Security
Enterprise repositioning, technical story, modular website, and an ongoing growth system for security infrastructure.
Visit live site ↗Saildrone
Multi-phase web and brand work for autonomous hardware speaking to operators, government, partners, and the public.
Visit live site ↗How Vinci will know it is working
Measure belief, proof, action, and operating velocity.
Comprehension
Can a new visitor explain Vinci’s category and consequence after the opening sequence?
Proof engagement
Do qualified visitors inspect methods, evidence, limits, and product behavior?
Evaluation intent
Does the public journey produce better-scoped technical-evaluation conversations?
Publishing velocity
Can Vinci release approved proof, events, and category narratives without rebuilding the site?
Release quality
Do accessibility, performance, analytics, SEO, redirects, and claim checks pass before release?
Operating response
Are ownership, decisions, blockers, approvals, and release history visible when leadership asks?
How much of us you want
One partnership. Scale into the agency team you need.
You steer priorities; SVZ runs delivery. The same senior core, operating system and specialist bench sit behind every level; each higher level adds the capabilities it names. The level sets what you can ask for and the senior capacity we hold for you. Move up with thirty days’ notice, step down with forty-five; the contract and the team’s availability hold at every level. Anything beyond the level is agreed before it starts, never discovered on an invoice.
Lvl 0After launch
Maintain
$35Kper month
Held capacity · about 140 senior hours each month
Unlocks after launch, stabilization and AI-workflow onboarding · not available at signature
Where the partnership rests between builds, never where it starts. A quiet quarter costs less; the contract and our availability hold.
What Vinci can ask for
- Revisions, tweaks and feedback on what exists
- Creative updates across the site and its assets
- CMS, publishing and release support
- SVZ OS runtime, database and maintenance
- Hosting, monitoring and release QA
- A dual-time-zone maintenance team, with emergency response
A month at this levelForty-five days’ notice to step into it. No net-new build; a build is a step back up to Scale, with thirty days’ notice.
Lvl 1
Foundation
$75Kper month
Held capacity · about 300 senior hours each month
The embedded team at steady state: the people who built the site keep it current, publishing, and ahead of the calendar.
Everything in Maintain, plus
- Strategy and positioning stewardship
- Brand and web system, kept evolving
- The research → proof → post publishing cadence
- Event pages and launch runways
- Content system and CMS training
- Answer-engine optimisation (AEO)
- Leadership focus, and one lead point of contact per time zone
A month at this levelDaily async in #svz-vinci, the Monday page and the Monday call. What a quarter looks like when the roadmap is publishing, not building.
Lvl 2Recommended · Release 01
Scale
$150Kper month
Held capacity · about 600 senior hours each month
Release 01, and any quarter that builds. The Vinci on the discovery call: a site that answers back, a digital counterpart to Opus, and a team that keeps building after launch.
Everything in Foundation, plus
- Executive and category consulting
- Product UX/UI alongside your engineers
- Next.js / React and full-stack engineering
- Generative-engine optimization (GEO) and proof architecture
- Custom agentic workflows for publishing, review and monitoring
- AI orchestration around the site and the digital release program
A month at this levelRelease 01 runs at Scale on the dated plan above. After stabilization, step to Foundation if the roadmap allows, or stay if it builds.
Lvl 3
Full Studio
$225Kper month
Held capacity · about 900 senior hours each month
When the story needs the stage and the screen: one team carrying it on the page, at the event, and on film.
Everything in Scale, plus
- A film and storytelling unit on call: Tasha Van Zandt and Sebastian Zeck
- Keynote, launch and go-to-market film
- Campaign narrative and event storytelling with Opus
- Surge capacity for the flagship event and category releases
A month at this levelOne-month minimum, timed to the brief. The level buys the team; production pass-throughs (crew, location, post) are quoted per brief.
Why four levels. A multi-year partnership has quiet quarters. Maintain removes the risk of paying for a team you do not need that month without losing the team. Scale is where the site gets built; Foundation is where it stays alive and ahead; Full Studio is for the months the story needs film.
In every level
- The named senior core
- The people who lead strategy, design, engineering, delivery and operations stay on the account at every level. Each level adds the units it names; substitutions need your approval.
- SVZ OS from day one
- Included at every level, with its runtime, database and maintenance: shared memory, named ownership, release checks and the Monday page inside the Slack channel we share with you.
- One lead point of contact per time zone
- Shea for the Americas, Nic for Europe, and in practice the same person every day, with the leadership team’s direct focus behind them.
- The specialist bench
- A hundred vetted relationships for the things nobody should staff full time, through the named team and never around it.
- Quarterly objectives, weekly reporting
- You set the quarter’s objectives. Anything in the level’s wheelhouse can be requested in Slack; we estimate it before we start and report every week. More than the level holds is agreed before it starts, never discovered on an invoice.
- One agreement
- 12 months · 90-day charter · month-six checkpoint · billed monthly in advance · level changes on notice: thirty days up, forty-five down.
- Onboarding month, on us
- October is your announcement window and our onboarding: access, the brief absorbed, the claims register started, the migration mapped, the measurement baseline set. No approval gate, no invoice. Billing begins November 1 with the 12-month agreement.
What we need from Vinci to move at this pace
You already set most of this. Lauren owns consolidated feedback: one voice back to us. Two business days for copy and design review; one for factual corrections; two, non-compressible, for claims, with a named engineering reviewer. Escalation Lauren → John → Hardik, twenty-four hours a step; anything that has not moved in seventy-two hours is named in the channel by item number. Access to the people and evidence behind the claims. Late inputs move dependent dates day for day, never quality.
Section 11 · The team and the operating system
The senior people on the account, follow-the-sun coverage, the specialist bench, and SVZ OS in your channel.
The proposal team is the delivery team.
Scott stays accountable for strategy and creative quality. Nic and Shea carry senior delivery across regions. Product, design, engineering, operations, illustration, and film sit inside the same named system, with a specialist network entering only when the work genuinely benefits from it.
Leadership + continuity
The people in the room stay on the account.
- 01
Scott Van Zandt
Founder & CEO · Executive Creative DirectorOwns the category thesis, creative direction, executive alignment, and the decisions that set the work’s direction.
- 02
Nic Warrington
Strategy & Delivery DirectorTurns discovery into the content architecture and roadmap, and opens each delivery day from Scotland.
- 03
Shea Lewis
US Delivery DirectorCarries daily senior coordination across strategy, design, production, and Vinci communication from Southern California.
- 04
Lauren McLaughlin
Director of Operations & Client ExperienceKeeps the right people on the work and makes sure Vinci always knows what is happening next.
- 05
Keyvon Nariman
Client Partner & Growth DirectorCarries the commercial relationship from onboarding through executive reporting and opportunity planning.
Product + design
A working pod with verified shared project history.
- 06
Bryce Komae
Lead Product DesignerTurns product truth into journeys, interaction systems, prototypes, and production-ready experience design.
- 07
Natalia Cacheiro
UX/UI & Art DirectorCarries interface craft, visual systems, art direction, motion language, and storyboarding.
- 08
Jackson Porter
Fine Artist & Illustration SpecialistBrings hand-painted image-making, traditional art, illustration, and authored visual texture to moments that should not feel machine-made.
Engineering
A publishing core Vinci can run, with custom software where the product story earns it.
- 09
Emanuel Skrobonja
Principal Application EngineerBuilds live instruments, data-driven field visualizations, and the integrations that connect the site to Vinci evidence.
- 10
Caelon Maybell
Senior Webflow & Front-End DeveloperBuilds the governed publishing core, responsive system, motion, CMS, and custom front-end layer.
- 11
Tom Dawson
Creative Director · Asia-Pacific DeliveryLeads the New Zealand Webflow Enterprise pod, extending production coverage and adding senior surge capacity.
Film + motion
Documentary craft for a company whose proof lives in the physical world.
- 12
Tasha Van Zandt
Film Director & CinematographerAward-winning director, cinematographer, and Emmy-nominated producer. Directs brand, product, and proof-of-process films so motion carries evidence rather than decoration.
- 13
Sebastian Zeck
Producer · Cinematographer · EditorProduces the film program end to end, from field production and cinematography through editorial finish.
Follow-the-sun coverage
A senior working day that keeps moving.
Scotland opens the day. New Zealand extends production in the other direction. Buenos Aires, Dallas, Chicago, and Los Angeles create deep overlap through the Americas. Vinci gets continuity, not four disconnected regional handoffs.
During agreed operating windows, critical items receive a senior acknowledgment within one hour. Launches and live events receive explicit named coverage rather than an implied 24/7 promise.
Americas East + Americas WestScott · Lauren · Keyvon · Shea · Bryce09:00 Pacific · 2 regions on
And when something unusual comes up
We operate from the senior team. The bench is for what you can’t staff full time.
The named team above is the system. When the roadmap calls for something unusually specific (a broadcast crew, a scientific illustrator, an accessibility audit), a specialist enters through one owner, does the work, and hands it back. Vinci gets the range of a network without managing one.
100+vetted specialist relationships, built over more than a decade
30active collaborators available around the standing pod
How the bench works
The senior team runs Vinci day to day. When a narrow need appears, one specialist enters through a named owner, does that one thing, and hands it back. You never meet a resource pool. Hover a lane to see who owns the door.
Selected film direction · Tasha Van Zandt
Technical stories with documentary gravity.
Explore Tasha’s full film portfolio ↗
Section 12 · What you sent, what it changed
Your September 10 answers, item by item, and the section each one changed. Then what comes next.
You answered forty of these on September 10. Here is what each one changed.
Your response document is the source; this page is the ledger. Every item below carries your number and links to the part of this proposal it changed. What we still want arrives once we begin. What needs both of us is marked to strategize together.
Open your response ↗Anything new before Friday: #svz-vinci, or Lauren to Lauren.
The session · Friday, September 18 · 90 minutes · Zoom
Friday the 18th: four of us, your five, ninety minutes on the vision.
You asked for a formal pitch on how Vinci’s digital presence should evolve. Four of us carry it; the room stays small enough to be a conversation. The people who will run the work day to day are the next call, and we are in person through the partnership, not just for the pitch.
4 on the pitch · 9 on the follow-up · in person through the partnership
The whole teamSection 11Across the tableHardik · Sarah · John · Sage · Lauren
- Scott Van ZandtThe vision, the brand, the creative argumentOn the call · Sept 18
- Keyvon NarimanThe partnership and its four levelsOn the call · Sept 18
- Lauren McLaughlinHow we work together: cadence, approvals, the channelOn the call · Sept 18
- Shea LewisDelivery and the dated planOn the call · Sept 18
- Nic WarringtonStrategy & Delivery · Europe point of contactMeet on the follow-up
- Emanuel SkrobonjaApplication Engineering · your engineering counterpartMeet on the follow-up
- Natalia CacheiroUX/UI & Art DirectionMeet on the follow-up
- Bryce KomaeProduct DesignMeet on the follow-up
- Caelon MaybellWebflow & Front-EndMeet on the follow-up
- Tom DawsonAsia-Pacific DeliveryMeet on the follow-up
- Jackson PorterIllustrationMeet on the follow-up
- Tasha Van ZandtFilm DirectionMeet on the follow-up
- Sebastian ZeckProduction & EditMeet on the follow-up
Received → applied
What you told us, and the section it changed
16 items · numbered as in your document
Format, attendees, and what a good ninety minutes looks like: your formal pitch on the vision.
ChangedThe session, recutThe three things the current site gets wrong: positioning the product not the vision, stopping at semiconductors, technical benefit without business impact.
ChangedWhat the brief is really askingSettled language and the never-list. The category line, Continuous Physics Reasoning, Foundation Model for Physics: singular, capitalised.
ChangedEvery headline on this pageThe five public claims, each with its condition on the same line; solver-accurate and deterministic, defined.
ChangedThe numbers you approvedThe roadmap in your order, and the correction: one system reasoning across domains, never three products.
ChangedOne system, two reasoning domainsTwo references: Anthropic and Palantir. PhysicsX dropped; no named competitor shapes the argument.
ChangedThe reference setFour audiences, in priority order: each with its arriving question, the proof that answers it, and the next step.
ChangedConnected journeysWhere the site sits in the customer experience; Opus and where physical meets digital.
ChangedBefore, during, afterThe channel, the Monday call and page, Lauren as one voice back, review windows, escalation, and the October 1–20 freeze.
ChangedThe dated plan and the working conditionsBrand source: Overpass Mono and Crimson Text, the palette, the energy gradient as a thermal mesh. Open to changes.
ChangedYour mark already holds the physicsThe editorial calendar: SemiWiki webinar, TSMC OIP, the October announcement, SEMICON West, Plug and Play, the Q1 flagship.
ChangedYour calendar feeds every pathEnglish only for Release 01; WordPress on WP Engine with eight post types on the www host; HubSpot forms today, Salesforce coming.
ChangedRelease 01 inventoryThe two studies we may show publicly; the formats you ingest natively (GDS, OASIS, STEP, IPC-2581, ECxml) stated exactly.
ChangedNative ingestNo customer is named, anywhere. Future industries are ambition language: semiconductors are the proof, not the limit.
ChangedEvidence as TrustAcceptance authority at the four gates (Lauren · Lauren and John · John · Hardik and John) set by date, backwards from the freeze.
ChangedFour decisions, by dateA multi-year engagement: the team that helps Vinci evolve over years.
ChangedScale into the agency team you need
Once we begin
Arrives with access: by secure link, from your partners, or as it is finished
7 items · numbered as in your document
The Product Naming Hierarchy: the page architecture and naming system we read before proposing a sitemap.Link returned no access; we work from the handbook and your corrections until it opens.
Design and motion source files, after your inventory pass with your design partner.
Photo and video library with rights per asset. One standing rule already applied: no customer designs, names or data.
Benchmark methodology and disclosure rules; two named reviewers and the turnaround you can hold for claims.We write to the two anchors you gave: solver-accurate, and deterministic.
Environments, the plugin list, the publishing workflow, and current analytics. Read-only CMS access by secure link.
Registrar, nameservers, Cloudflare, records, redirects and certificates. By secure link, never Slack or email.
Anything not yet numbered in your document, as it lands.
We strategize together
Decisions that need both teams in the room
7 items · numbered as in your document
How the finalists are scored, and when you decide.
How the product-conversation footage in your proof library is used on the site, and what the webinar recording adds once it is up.
The Opus SOW and roadmap, the flagship brief and community strategy, attendee data flow and joint measurement.
The benchmark page: what the site demonstrates rather than asserts, once the methodology is written.
The Salesforce hand-off: website integration is in scope; the migration itself is yours, and we build so it lands cleanly.
Procurement path, legal and security review, master agreement, billing. Owners named after the decision, as you noted.
When the continuity decision is made: with the award, or after Release 01.
The pitch · Friday, September 18 · on Zoom
Everyone knew it was coming. Let’s make sure the world knows who built it.
Choose SVZ as Vinci’s digital operating partner. The website is what we build first, and the team you have just met stays on for what follows, at the level each quarter needs. You sent what exists on September 10; this is the proposal it changed.
- Friday 18
- Ninety minutes on the vision, four of us on the call. Questions for engineering go to Emanuel on the follow-up.
- Follow-up
- The nine who deliver. Product, design, engineering and film, in the room with your team.
- On award
- Onboarding month, on us. Access by secure link, the channel opens, and the dated plan starts moving day for day from signature.
Before you go · 22 things in this proposal
Did you catch all that?
A lot of this proposal lives one click deep. Here is every one of those places in plain English, grouped by what you might want to do with it. Use it as a checklist; nothing here is new, it is all above.
Try it
- The opening demo↑The 95 °C question, asked and answered on the demo board.
- Concept 1, the product-led homepage↗New visual system, the Tide mark in the hero, the working product below. (opens in a new tab)
- Currently on brand, the second homepage↗Same messaging and flow inside Vinci’s existing type and palette. (opens in a new tab)
- The instrument↑The board as a driveable object: probe a column, move the cooling, watch the verdict flip.
- The instrument, full screen↗The same object in its own tab. (opens in a new tab)
Read the thinking
- What the brief is really asking↑What the site does today, what it costs, what it must start doing, and which part of the system fixes it.
- Current messaging to future direction↑Your words beside ours, and the tone and messaging sheet the whole team can use.
- The tone and messaging sheet↑Voice, say and never say, the five claims, three depths. Copy it as text.
- Your four ICPs, as people↑Who arrives, what they came for, and where the site answers them.
- Connected journeys↑The path each reader lights through one connected site.
- The claims register↑Your five approved numbers as entries 01 to 05, each with its condition.
See the work
- Behind the mark↗The field study: every variant of the living mark and the reasoning behind it. (opens in a new tab)
- Vinci Motion, the motion library↗The web motion library as code: eases, durations, staggers, thermal stops. (opens in a new tab)
- Living-logo alpha master, light surface↗Downloadable WebM with alpha. (opens in a new tab)
- Living-logo alpha master, dark surface↗Downloadable WebM with alpha. (opens in a new tab)
- What SVZ already demonstrated↑Six things built before anyone asked, each with a real frame and its status.
- Tasha Van Zandt’s films↗The documentary work behind the film unit. (opens in a new tab)
Decide
- The partnership↑Workstreams, the first quarter, the dated plan around your October freeze.
- The four levels↑How much of us you want, and what each level holds for you.
- The team↑The people on the account, follow-the-sun coverage, the bench, SVZ OS.
- What you sent, what it changed↑Your September 10 response, item by item, linked to what it changed.
- Your response document↗The source, on Google Docs. (opens in a new tab)
That is the whole proposal. Thank you for reading it.
Back to the top