GSD (get-shit-done) vs OpenAI Realtime API Fine-Tuning

“GSD's five-step workflow (initialize → discuss → plan → execute → verify) with wave-based parallel execution and schema drift detection is the closest thing to a formal engineering discipline for Claude Code projects. The quality gates alone have saved me from shipping broken APIs multiple times.”

“The primitive is clean: bake domain knowledge and voice persona into model weights instead of stuffing a system prompt at runtime and hoping latency doesn't crater. The DX bet is that developers would rather manage a fine-tuning pipeline than engineer around context-window constraints on a streaming audio connection — and for production voice apps, that's the right call. The moment of truth is running your first fine-tuned eval against a base-model call and hearing the difference in domain terminology handling; if that gap is real, the 1.5x pricing surcharge is justified. What I want to see is whether the fine-tuning data format for Realtime matches the existing text fine-tuning schema or introduces a new audio-specific format — the docs had better be explicit about that, or the onboarding experience falls apart immediately.”

“The upfront initialization and thorough planning phase is a real time investment — probably overkill for straightforward CRUD tasks or one-off scripts. GSD shines on complex, multi-milestone projects but adds ceremony that can slow you down when you just need something built quickly.”

“Direct competitor here is ElevenLabs with custom voice models plus Cartesia's low-latency API — neither offers true model-weight customization at the reasoning layer, which is where this actually differs. The scenario where this breaks is the small-to-mid developer who doesn't have 50k+ high-quality voice interaction turns to produce a fine-tune worth the effort; you'll pay the 1.5x premium and land roughly where a well-engineered system prompt would have gotten you. What kills this in 12 months isn't a competitor — it's OpenAI shipping a native "voice persona" config parameter that makes fine-tuning unnecessary for 80% of use cases, collapsing the value prop. What would have to be true for me to be wrong: enterprises in healthcare and fintech actually need weight-level domain lock that can't be prompt-engineered out, and they pay for it.”

“GSD is one of the first serious attempts to bring software engineering discipline to AI-assisted development — not just prompting tricks but a reproducible methodology with verification steps and context management. As AI coding scales, the teams with structured workflows like this will outproduce those freewheeling with prompts.”

“The thesis is falsifiable: by 2027, brand-differentiated voice agents will require model-level customization because prompt-engineered personas will be commoditized and detectable, and enterprises will pay a premium for agents that are behaviorally distinct at inference rather than cosmetically distinct at runtime. The dependency that has to hold is that latency-sensitive streaming voice remains a specialized inference problem that OpenAI controls tightly enough to charge for customization — if open-weight audio models like a future Whisper successor close the quality gap, this pricing power evaporates. The second-order effect that nobody is talking about: fine-tuned Realtime models start creating measurable brand equity in voice, the same way custom fonts created visual brand equity in the 2000s, and agencies will charge to build them. OpenAI is early to this specific primitive — weight-level voice persona — and the infrastructure play is to become the registry where those trained assets live.”

“Even as a non-developer building internal tools, GSD's discussion and planning phase surfaces requirements I hadn't thought of before any code gets written. Describing what I want built and watching it execute reliably — with a verify step confirming it actually works — changes how I think about building with AI.”

“The buyer is clear: contact-center and voice-AI SaaS companies that already run Realtime API in production and need differentiation from the next vendor running the same base model — this comes out of their AI infrastructure budget, not an experiment fund. The 1.5x pricing is smart architecture: it scales with consumption so OpenAI captures margin on the exact customers getting the most value, and it creates a switching cost because a fine-tuned model becomes a proprietary asset baked into a customer's deployment. The moat question is whether the fine-tuned weights constitute durable differentiation or whether OpenAI can deprecate the model version and force a re-train — that deprecation risk is a real enterprise objection that needs a clear policy answer before large deals close.”