The rule we set at the start of April was simple: every piece of social content for Habitu's own channels gets created, checked, scheduled, and published through Studio. No shortcuts to native apps, no "just this once" Buffer drafts, no manually uploading the image after the fact. If Studio couldn't handle it, Studio was broken and we needed to know that before our restaurant clients did.
Thirty days later: a lot worked, a few things broke badly, and we shipped five bug fixes that would never have surfaced from simulated usage or a QA script. This is the honest account of what happened.
What Worked Well
The inspiration panel was genuinely useful. The panel that surfaces scout output, trend ideas pulled from pinned sources and Reddit, ranked and transformed by the Stage 2 classifier, changed how we plan content. Before it existed, content planning was a weekly conversation that started with "what should we post this week?" After it existed, the conversation started with "here are 10 ranked ideas from the scout run, which three do we take?" The frame shift is not subtle. You go from blank page to selection problem, and selection problems are much faster to resolve.
Voice check caught real issues. We were skeptical about whether a voice rubric applied to our own content would add anything, we know the Habitu voice well, or thought we did. In practice, the check surfaced two recurring issues: a tendency to hedge in the second paragraph of strategy posts ("this can sometimes help with...") that the rubric correctly flagged as a voice violation, and a pattern of using competitor names as implicit anchors in openings ("Unlike Punchh, Habitu...") that the rubric flagged as framing from a position of weakness. Both were real, both had been in our content for months unnoticed. The check found them consistently.
The Cmd+K palette made the multi-surface workflow usable. Studio v2 ships with a unified shell, five surfaces (dashboard, content, scout, media, settings) accessible from anywhere via Cmd+K. In practice, the ability to jump from scout output to draft editor to media library without breaking flow is the difference between a tool you use continuously and one you open, complete a task in, and close. Small UX decision, large practical impact.
What Broke
Reddit 403s sent us through a two-driver pivot. We've written about this in the scout architecture post, but the experience from the content side was: the inspiration panel went quiet for five days while we debugged, reverted the playwright driver, and integrated the easyapi/reddit-posts-search-scraper. The cost was a full week of the scout feed returning near-zero Reddit signal, which meant relying entirely on the website-source track. Not catastrophic, but it confirmed that Reddit is a high-value source that warrants a stable driver, the ideas that come out of r/Entrepreneur, r/Foodservice, and the fast-casual communities are materially different from what the editorial sources surface.
IG publish failed silently on the first live post. The Instagram publish integration hit Meta API error 9004 on our first real post, not in staging, in production on a post we intended to go live that morning. Error 9004 is a pre-flight failure that fires when the media object hasn't passed Meta's internal readiness check before the publish call lands. The fix required adding a HEAD check before the publish request and a diagnostic hint in the error response so the operator knows whether to retry or escalate. Commit: "IG publish — pre-flight HEAD check + diagnostic hint on Meta error 9004." The fix was straightforward; the discovery was unpleasant. It would have been worse if our first client had hit it instead of us.
The voice check was looping 7+ rounds. At the rate we were creating content, two to three posts per day across platforms — the iteration count on voice check became immediately obvious as a cost and UX problem. We were watching Claude run 7 refinement passes on drafts that were already close to on-brand, and then the Apply button was replaying stale findings because of a useCallback closure bug. The full fix is in the voice-check post, but the trigger was real usage, not code review.
The max_tokens setting on the inspiration fetch was too low. Longer scout runs, bigger source lists, more Reddit posts in a single batch, were returning truncated classifier output. The classifier would produce 8 idea objects, then hit the token ceiling mid-JSON and return a malformed tail. The parser recovery code caught most of it, but 2-3 ideas per run were being silently dropped. Commit: "inspiration max_tokens bump + parser truncation recovery." In testing we'd only run small source lists. In real usage, the source list grew to 14 pins within the first two weeks.
The Meta-Lesson
Every single bug listed above was invisible in testing and obvious in use. The 9004 error required a real IG business account doing a real publish attempt. The token ceiling required a real source list grown over real weeks of adding sources. The voice-check loop required real content volume, you don't notice 7 rounds when you're running 5 checks per week; you notice it immediately when you're running 15.
There is a version of Studio development where we build the feature, write unit tests, run the QA script against a staging environment with 3 pinned sources and 2 test posts, declare it ready, and hand it to clients. That version would have shipped all four bugs into production. Dogfooding is not a nice-to-have for a content tool. The product's value proposition is that it handles the edge cases so the operator doesn't have to. That claim cannot be tested in a sandbox.
We're now in month two of continuous self-use. The bug rate has dropped sharply, the low-hanging issues are gone, but we're still finding smaller friction points weekly that don't rise to the level of bugs but do rise to the level of "this would make a restaurant content manager quietly stop using the feature." Those are the ones that matter most and are hardest to catch any other way.
Studio ships as part of the Habitu platform. If you're a restaurant brand managing social content across multiple platforms and want to see how the scout + voice-check + publish workflow looks in practice, the branded apps overview covers the publishing surface, and we're happy to walk through Studio specifically on a call.