Repositioning as practitioner-publisher
Note: Retroactive log - reconstructed from commit history and session notes.
We dropped “build in public” from all site copy and repositioned Venture Crane as a practitioner-publisher contributing field notes to AI-native development operations.
What We Did
The original site positioning used “build in public” framing - the idea that transparency about process and costs was itself the value proposition. After a 3-round, 6-role PRD review process and founder review, we killed it.
The problem with “build in public” is audience confusion. It signals a creator-economy content play - livestreams, follower counts, journey narratives. That’s not what this is. Venture Crane is a development lab that happens to publish what it learns. The publishing serves two functions: contributing to the emerging discipline of AI-native development operations, and generating proof-of-work content for one of the portfolio ventures focused on content automation.
The reframe changed three things across the site:
Tagline: “The product factory that shows its work” became “A development lab building real products with AI agents.” The elaboration text now reads: “Venture Crane is a solo-founder venture studio powered by multi-agent development teams. We build the tooling, use it to ship products, and publish what we learn - operational methodology, real costs, honest failures. Not a tutorial. Not a pitch. Field notes from a working operation.”
“Product factory” retirement: Every instance of “product factory” was replaced with “development lab.” The distinction matters - a factory implies assembly-line output, a lab implies experimentation and methodology.
Content framing: Articles are “processed retrospectives and technical articles,” not “journey updates.” The audience is “fellow practitioners,” not “followers.” Success is measured by peer connections and citations, not subscriber counts.
The PRD amendment documents the full rationale, synthesized from the review process. The competitive context section identifies Harper Reed, Simon Willison, and Latent Space as adjacent voices, with Venture Crane’s differentiation being the organizational and multi-product perspective: fleet operations, cross-venture context management, portfolio-level kill decisions, and operational costs.
What Surprised Us
The phrase “build in public” had only been on the site for a few days, but it had already shaped how we talked about the project internally. Killing it required updating not just site copy but also the PRD, the about page, and the RSS feed description. Positioning language propagates fast - even a short-lived framing creates references everywhere. The cleanup touched 4 files in the website codebase and the full PRD in the main repository.