Innerlogic / Product and building / 2025 to 2026
From prototype to product
Surveys at Innerlogic used to be built in a custom admin that no customer could ever see. We wanted customers to be able to build their own.
I built the survey builder in v0, an AI tool for building apps, and our front-end engineer brought it into the app and connected it to our systems. In 2026 I started working on it directly, mostly with Claude Code. Customers build their own surveys with it today, and we still help the ones who are less comfortable with the technology.
Starting with the layout
The part I’m proudest of is the layout, and it happened early. Before adding much to the builder, I used AI to plan how it would look and where new functionality would live as we added it, so the interface wouldn’t get clunky. I ended up with the question list on the left, the content in the middle, and advanced options on the right. I still use AI for strategy before I build anything.
Building it in v0
I’d never worked in a coding environment and I didn’t have access to our code, so I built it in v0. Back then you had to fork a chat when it got too long, or the tool would get bloated and start making things up. I’d have it summarize what had changed and carry on in a new fork, and when something broke I’d restore an earlier version. Through 2025 that added up to 77 forks and about 42,000 lines of code.
Handing it over
We first tried the code as a test, to see if it would work in our new app. I didn’t have access to GitHub, so I shared the raw code with our front-end engineer. They said it looked clean, and it worked directly in our new codebase. They connected it to our systems over the next few months, while I kept building in v0 until the project was finished.
Working in the code myself
In January 2026 I moved to Claude Code and started committing to the app myself. Over the next few months I merged about 16 improvements to the builder, including autosave and a warning before you lose changes. A colleague building a healthcare customer’s survey reported that the most common question types were buried under structural items, so I regrouped the “Add survey content” menu into “Ask a question”, “Track progress”, and “Set up structure”, moved scale questions to the top, and added search.
Being able to make those changes myself gave me more agency, and it was a eureka moment. I could see product management folding into a product builder role, and a different path for a product career than the one I’d been on. I’m now part of the development team, and I ship code daily.