VIRTUVIS · CONSTRUCTION TECHNOLOGY
Surface problems before they reach the site.
Helping teams see, cost, coordinate, and correct a project before uncertainty becomes physical.
Reduce rework
Target reduction in corrections caused by design/site mismatch
Improve cost accuracy
Target improvement in estimate-to-actual variance
Detect issues earlier
Target increase in problems identified before execution
Protect design fidelity
Target improvement in alignment between approved design and built outcome
Design decisions and budget consequences lived in the same workflow.
ROLE
Product design · Interaction design · Product architecture · Design system
AUDIENCE
Architects · Engineers · Project Managers · Clients
DURATION
3 months
Apr ‘24 - Jun’24
PROJECT STAGES
Design · Development · Coordination · Construction · Verification
THE REALITY
The tools were connected.
The project wasn’t.
Each tool was good at its own job. The breakdown happened between them when design intent, cost impact, approvals, and site changes had to be carried from one system to the next by people.
The problem wasn’t missing software. It was losing context between decisions.
Autodesk Revit
Design and modeling
Bluebeam
Drawings and takeoffs
Navisworks
Clash detection
Procore
Project management
OpenSpace
Site capture
The design existed. The certainty didn’t.
Construction projects move through drawings, material choices, approvals, cost estimates, engineering reviews, and site execution. When those decisions live across disconnected files, calls, messages, and tools, teams lose visibility into what changed, what it costs, and whether execution still matches the intended design.
design
cost
approval
engineering
site
actual outcome
Revision mismatch
Hidden cost impact
unclear approval
clash wrokaround
site deviation
reality
Small mismatches compound into a different building
Harder to detect
later in the process
More expensive
to change
Higher risk
to project success
One project. Five different definitions of “right.”
ARCHITECT
Protect the design intent.
Iterations · Materials · Feedback · Approvals · Downstream change
ENGINEER
Make the design buildable.
Clashes · Specifications · Tolerances · Site evidence
PROJECT MANAGER
Keep the project predictable.
Cost · Timeline · Approvals · Dependencies · Risk · Progress
CLIENT
Understand what they are approving.
Visualization · Alternatives · Cost consequence · Progress · Confidence
INVESTOR / VC
Believe the platform can scale how projects get delivered.
Differentiation · Efficiency · Scalability · Product credibility
PRODUCT PRINCIPLES
The rules that guide every experience, decision and feature
Make consequence travel with the decision.
Cost · time · buildability stay attached to the choice.
Different views should never create different truths.
Role-specific views, one shared project state.
Keep uncertainty digital for as long as possible
Resolve issues while they are still reversible.
Treat reality as feedback, not the finish line
Site evidence updates the project state.
THE PRODUCT
A connected experience from intent to execution
SEE
Establish the shared reference.
COST
Expose the consequence of change.
VERIFY
Reconcile the model with reality.
COORDINATE
Turn consequence into ownership.
Design explorations that shaped the final model
The final direction kept the building dominant while keeping consequence and coordination adjacent.
Too fragmented
Too dashboard-led
- Too generic
01 / SEE
Make the unbuilt building understandable.
Before cost or coordination could mean anything, everyone first needed to understand the same proposal.
02 / COST
Cost belonged beside the choice, not after it.
Virtuvis connected materials and specifications to their cost impact while those choices were still reversible.
03 / COORDINATE
Turn impact into clear ownership and action.
Turn impact into clear ownership and action.
DESIGN KNOWLEDGE
Keep context attached to the choice.
Materials and building elements were organized as part of the project decision, not as isolated references.
PROJECT OVERVIEW
Surface uncertainty before it becomes a problem.
Project health, risk, activity, and unresolved decisions were surfaced early so teams could focus attention before issues became expensive.
PROJECT MANAGEMENT & BUDGETING
Turn project decisions into a plan.
Budget, milestones, dependencies, and ownership stayed connected so teams could see what a decision affected, who needed to respond, and when it became critical.
04 / VERIFY
Keep execution true to intent.
Catch deviations while they are still recoverable.
SEE / VERIFY IN CONTEXT
See intent where it becomes real.
AR extended the same project model into physical space so teams could understand scale, placement, and how the approved design related to the actual site.
ON-SITE MONITORING
Check reality against what was approved.
Once construction began, Virtuvis used the approved project state as the reference for tracking progress, spotting deviations, and keeping site execution connected to design intent.
Looking Back
The system was strong. The moments within it needed more depth.
Virtuvis resolved the larger product architecture more fully than the interaction detail. With more time, I would deepen the states, edge cases, feedback, and decision logic and bring every workflow to the same level of precision.
NEXT PROJECT
INFINITHEISM · SPIRITUAL PRODUCT ECOSYSTEM
Consistency without sameness.
Designing a connected spiritual ecosystem while letting each experience keep its own purpose.
3 months · Feb ‘24 - May ’24
VIRTUVIS · CONSTRUCTION TECHNOLOGY
Surface problems before they reach the site.
Helping teams see, cost, coordinate, and correct a project before uncertainty becomes physical.
Reduce rework
Target reduction in corrections caused by design/site mismatch
Improve cost accuracy
Target improvement in estimate-to-actual variance
Detect issues earlier
Target increase in problems identified before execution
Protect design fidelity
Target improvement in alignment between approved design and built outcome
Design decisions and budget consequences lived in the same workflow.
ROLE
Product design · Interaction design · Product architecture · Design system
AUDIENCE
Architects · Engineers · Project Managers · Clients
DURATION
3 months
Apr ‘24 - Jun’24
PROJECT STAGES
Design · Development · Coordination · Construction · Verification
THE REALITY
The tools were connected.
The project wasn’t.
Each tool was good at its own job. The breakdown happened between them when design intent, cost impact, approvals, and site changes had to be carried from one system to the next by people.
The problem wasn’t missing software. It was losing context between decisions.
Autodesk Revit
Design and modeling
Bluebeam
Drawings and takeoffs
Navisworks
Clash detection
Procore
Project management
OpenSpace
Site capture
The design existed. The certainty didn’t.
Construction projects move through drawings, material choices, approvals, cost estimates, engineering reviews, and site execution. When those decisions live across disconnected files, calls, messages, and tools, teams lose visibility into what changed, what it costs, and whether execution still matches the intended design.
design
cost
approval
engineering
site
actual outcome
Revision mismatch
Hidden cost impact
unclear approval
clash wrokaround
site deviation
reality
Small mismatches compound into a different building
Harder to detect
later in the process
More expensive
to change
Higher risk
to project success
One project. Five different definitions of “right.”
ARCHITECT
Protect the design intent.
Iterations · Materials · Feedback · Approvals · Downstream change
ENGINEER
Make the design buildable.
Clashes · Specifications · Tolerances · Site evidence
PROJECT MANAGER
Keep the project predictable.
Cost · Timeline · Approvals · Dependencies · Risk · Progress
CLIENT
Understand what they are approving.
Visualization · Alternatives · Cost consequence · Progress · Confidence
INVESTOR / VC
Believe the platform can scale how projects get delivered.
Differentiation · Efficiency · Scalability · Product credibility
PRODUCT PRINCIPLES
The rules that guide every experience, decision and feature
Make consequence travel with the decision.
Cost · time · buildability stay attached to the choice.
Different views should never create different truths.
Role-specific views, one shared project state.
Keep uncertainty digital for as long as possible
Resolve issues while they are still reversible.
Treat reality as feedback, not the finish line
Site evidence updates the project state.
THE PRODUCT
A connected experience from intent to execution
SEE
Establish the shared reference.
COST
Expose the consequence of change.
COORDINATE
Turn consequence into ownership.
VERIFY
Reconcile the model with reality.
Design explorations that shaped the final model
The final direction kept the building dominant while keeping consequence and coordination adjacent.
Too fragmented
Too dashboard-led
- Too generic
01 / SEE
Make the unbuilt building understandable.
Before cost or coordination could mean anything, everyone first needed to understand the same proposal.
02 / COST
Cost belonged beside the choice, not after it.
Virtuvis connected materials and specifications to their cost impact while those choices were still reversible.
DESIGN KNOWLEDGE
Keep context attached to the choice.
Materials and building elements were organized as part of the project decision, not as isolated references.
PROJECT OVERVIEW
Surface uncertainty before it becomes a problem.
Project health, risk, activity, and unresolved decisions were surfaced early so teams could focus attention before issues became expensive.
PROJECT MANAGEMENT & BUDGETING
Turn project decisions into a plan.
Budget, milestones, dependencies, and ownership stayed connected so teams could see what a decision affected, who needed to respond, and when it became critical.
04 / VERIFY
Keep execution true to intent.
Catch deviations while they are still recoverable.
SEE / VERIFY IN CONTEXT
See intent where it becomes real.
AR extended the same project model into physical space so teams could understand scale, placement, and how the approved design related to the actual site.
ON-SITE MONITORING
Check reality against what was approved.
Once construction began, Virtuvis used the approved project state as the reference for tracking progress, spotting deviations, and keeping site execution connected to design intent.
Looking Back
The system was strong. The moments within it needed more depth.
Virtuvis resolved the larger product architecture more fully than the interaction detail. With more time, I would deepen the states, edge cases, feedback, and decision logic and bring every workflow to the same level of precision.
