Rebuilding a 12-year inspection product without losing the data
- Role
- designer who builds
- Scope
- product · marketing · migration
- Domain
- construction inspection
- Status
- rebuild in progress · 2026
Looks like a redesign. The hard problem is twelve years of inspection knowledge locked in .NET, Couchbase, Sync Gateway, and native iOS — while crews still need the same field workflows tomorrow morning.
I am rebuilding the product brain (Next.js, Expo, Supabase) so the business keeps its memory without staying trapped in the old stack.
2026 design work
ispect.appLanding page designs
Refactor
Cut jank, less noise, more automatic UI
Vue 2 / Vuetify 2 → Vue 2.7 + Tailwind. Vuetify stayed for complex tables but styles were stripped — effectively headless. Goal: modernize the design, reduce jank, show less information so the product feels more automatic.
Screens
Scale
Why iSpect exists: transparency in construction
With a decade of industry statistics, the web platform lets contractors and sub-contractors see project health in real time — issue counts, average completion time, who is performing before contracts are renegotiated.
Product surfaces
Brand
Identity that had to travel
Started 2012 in brand and UI; moved into implementation when craft alone was not enough. The logotype grew around the search mark and had to work on hard hats, people, and product screens — not just a marketing site.
Screens
Logotype with the search mark used since the beginning 
Hard hats usually cannot change color — branding works within the rules 