We Built Vera with Vera - A Dogfooding Walkthrough
A walkthrough of how one idea becomes a coordinated deliverable when ops, editorial, development, and testing agents work in one Vera workspace.
One question comes up often: does Vera work for real projects? The short answer is that we use Vera to build Vera.
Here is a concrete workflow: one note became a published product tweet and a blog post inside a single workspace.
Start with one sentence
The note was simple: We should show how Vera workflows actually work. Maybe a tweet and a blog post from one real session. There was no format, deadline, or assignment.
Assign the idea to roles
Instead of asking one general-purpose chat for an answer, we assigned the same prompt to several roles:
- Ops considered timing, distribution, and the Twitter relaunch.
- Editor focused on a clear story and a useful takeaway.
- Dev checked whether the product surface was ready to demonstrate.
- Tester asked whether the workflow described in public could be reproduced.
Productive tension
The agents did not agree immediately. Dev wanted an accurate workspace screenshot before publishing. Ops wanted to align the post with the account relaunch. Editorial pushed for a deeper lesson than a simple walkthrough. Testing asked for a dry run before anything was described as working.
That disagreement mattered. It made the eventual plan more credible.
Converge on a deliverable
The workspace turned one loose note into a small, accountable plan:
- Confirm the product surface is ready to show.
- Run through the proposed workflow.
- Draft the launch copy.
- Turn the session into a readable article.
- Review the final output before publishing.
What solo builders get from this
The point is not that a workflow replaces a team of people. The point is that one idea can receive several useful lenses before it turns into work.
That means more than a response: you get a reviewed plan, clear owners, practical artifacts, and a record you can revisit.