agoráconversations
§ what this is

A catalog, not a platform.

agorá conversations is a public catalog of hand-crafted, harness-engineered customer-support workflows for solo CS consultants serving B2B SaaS clients. Every workflow is a YAML file the buyer can read, preview interactively, and connect into Claude or ChatGPT. The runtime that enforces the harness is closed, hosted, and invisible.

The buyer pays for reliable conversations that don’t go off-script — not for software, not for a platform, not for AI access. The product is the catalog and the guarantee that what’s in it works.

The brand sits between two poles. Editorial — a curated catalog of artifacts treated as objects worth describing carefully. Engineering — deterministic harnesses, formal schemas, public source. The visual system holds both. The voice holds both. The product is the held tension.

Open YAML. Closed runtime. Differentiation is enforcement, not secrecy. You can read every workflow before subscribing, and you can read every workflow after cancelling. What you pay for is the harness around them — the part that keeps the conversation on the rails the YAML describes.

The conversation layer. Your client’s systems handle the rest.

§ principles

Five things the catalog won’t bend on.

01

Deterministic over generative

Every workflow runs as stepwise execution against a published schema. The harness rejects free-form responses outside the declared flow. The runtime is closed because closing it is the value — if you could run it yourself, the catalog would be a list of suggestions instead of a guarantee.

02

Instrumented by default

Confidence floors, escalation reasons, step transitions, and every classifier decision are recorded for every run. The harness is a flight recorder before it is a chatbot. If you can’t read what it did, you can’t trust what it does.

03

Honest about boundaries

Each workflow description ends with what it doesn’t do. Refund intake doesn’t check policy. Invoice clarification doesn’t reach the billing system. The boundary is part of the product. Hiding it is how AI tools earn the eye-roll.

04

Solo-first, not solo-only

The persona is the solo CS consultant deploying workflows at multiple B2B SaaS clients. Practices of any size are welcome — but the catalog is shaped by what one operator can audit, not what a procurement team can buy. Pricing follows the same shape.

05

Consultant as author

The reader of these YAML files is the practitioner who deploys them. Personalization tunes a workflow to one client’s voice; bespoke commissions author new ones. Either way, the artifact stays legible to the person responsible for its behavior at the customer’s end.

§ lineage

Reference voices, and what this isn’t.

influences

  • iA WriterRestrained, specific, deeply opinionated about craft. Treats writing tools as objects worth describing carefully.
  • Linear (documentation)Precise technical writing that respects the reader's time. Plain behavioral language without performance.
  • Stripe API referenceSpecifics over abstractions. Every claim backed by example. The voice trusts the reader to be smart.
  • The Browser Company (Arc, early)Confident without being breathless. Treats the product as worth caring about without insisting the reader cares.
  • PinboardA small, opinionated, financially honest one-person product. The voice never apologizes for being one person.

These voices are studied, not copied. Each gets the brand somewhere closer to where it should land. None of them are this — that’s why all five are listed instead of one.

what this isn’t

  • Not a platformThere is no SDK to install, no admin console to administer, no roadmap of platform features to follow. The product is the catalog and the harness behind it.
  • Not a modelagorá doesn’t train, fine-tune, or host models. It uses your client’s Claude or ChatGPT, calls them through the harness, and constrains the output. BYO keys is supported.
  • Not a marketplaceWorkflows aren’t community-contributed. The catalog is curated by one operator. New workflows ship daily after launch — the cadence is the calendar, the curator is the proof.

Operated by Diego Marono. The product is bigger than its operator; the operator is the proof the product is bounded.