Quire
The content engine that onboards with a URL.
I envisioned Quire as a marketer, then built it as a marketing engineer - prototyped on Lovable, pair-coded with Claude and GPT, put in motion as the production layer of an AI-native content engine. Not a vendor tool. A system I designed, shipped and now run.
Why traditional content ops break under AI velocity
Content teams used to be bottlenecked by writing. AI removed that bottleneck. The new bottleneck is everything around the writing - briefs that take longer than the draft, blank pages that paralyze, output that sounds nothing like the brand.
Generic AI writing tools generate text. They don't fix the loop. Quire fixes the loop.
How Quire works
Three layers, working in sequence:
Ingests the company's site, blog, sales material, and conversations. Builds a structured understanding of voice, positioning, and audience before a single draft is generated.
Each stage owns a specific decision: angle, audience, structure, draft, voice pass, fact pass, hook, CTA, finish. Stages are inspectable. You see what changed and why.
Five content buckets, each with its own voice protocol. No em-dashes by default. Sentence case. No fluff. The output sounds like the brand because the system is grounded in the brand.
The three frictions Quire eliminates
- The brief.
- Onboarding is a URL. The Context Engine reads what's already there.
- The blank page.
- Drafts arrive grounded in real signals, not LLM hallucinations.
- The silence.
- Loop-driven feedback turns every published piece into a context signal for the next one.
What I owned
Positioning, GTM narrative, and product direction. I shaped the loop thesis, the bucket voice methodology, and the onboard-with-a-URL framing that anchors how Quire enters the market.
How Quire feeds the broader content engine
Quire isn't a standalone tool. It's the production layer of a content engine that includes campaign planning, distribution, and measurement - powering flagship campaign content, conference collateral systems, and the day-to-day publishing rhythm.
The team workflows it changes: writers move from blank-page anxiety to draft refinement. Marketing leads spend less time briefing, more time deciding what's worth publishing.
Where it is now
Live. Currently running the entire content pipeline with AEO (Answer Engine Optimization) in mind - every piece is structured so it can be retrieved, quoted, and cited by the systems that increasingly mediate B2B discovery.