Operate Quiver.

Bootstrap

Start with the system, not a blank prompt.

Quiver is an agentic developer-marketing system. It keeps product context, customer evidence, active work, shipped output and measured results connected so people and agents operate from the same approved state.

1. 01

   Create the workspace

   Name the organization and choose its slug. Hosted workspaces get a shared address at your-slug.quivergtm.dev.

2. 02

   Choose the team size

   Founder includes up to three seats. Team includes unlimited seats. Both hosted plans include the current hosted feature set.

3. 03

   Connect a model account

   Add Anthropic, OpenAI, Google, OpenRouter or another OpenAI-compatible endpoint. Your account determines model cost and usage policy.

4. 04

   Initialize the context

   Paste the website or describe the product. Quiver drafts the starting model; you review assumptions before relying on it.

5. 05

   Take an agent key

   Onboarding ends by handing you an MCP key, shown once, plus your workspace MCP URL. Browser clients can sign in with OAuth instead.

6. 06

   Run the first session

   Choose Strategy, Create, Feedback, Analyze or Optimize. Every session starts from the active approved context.

7. 07

   Close the loop

   Save the work, move it through production states, log the result and review what should change before the next cycle.

Architecture

The system model

Quiver applies familiar engineering properties to developer marketing. These are product behaviors—not a metaphor layered over generic chat.

Team boundary

Workspaces and team access

• Each hosted workspace has its own subdomain, context, team, provider keys, tokens and tenant-scoped data.
• Admins manage billing, provider keys, tokens and team access. Members operate the product. Other workspace users are read-only.
• Invite teammates from Settings → Team. Founder supports three seats; Team supports unlimited seats.
• People can belong to multiple workspaces and switch from the sidebar. Each workspace keeps its own operating state.

Model layer

Models and keys

• Quiver sends model calls directly through the provider account you connect; Quiver does not resell or meter model usage.
• Add providers in Settings → AI providers. Keys are encrypted at rest and are never displayed again.
• Set one default model or select different models for session modes, research processing, performance synthesis and utility jobs.
• OpenRouter can provide access to multiple model families through one account. OpenAI-compatible endpoints can use their own model identifiers.
• Test connection sends a small request so you can verify the key and model before saving.

Agent runtime

Session modes

Modes give the agent a job boundary and load the context most relevant to that job. Pick one directly or describe the outcome you need and let Quiver route the session.

Source of truth

Marketing context

The active context stores the product model agents should use: positioning, ICP, messaging, customer language, proof, hypotheses and brand voice.

• Make a direct edit when the new fact is already confirmed.
• Use proposal review when research or performance suggests a change that still needs judgment.
• Every save creates a version. Inspect the history or restore an earlier state when needed.
• The active version is injected into every session automatically.
• Assumption marks context drafted without direct evidence. Confirming or correcting the field clears the marker.

Production state

Artifacts and explicit states

• Artifacts move through Draft → Review → Approved → Live → Archived.
• Revisions preserve version lineage instead of overwriting the decision history.
• Link artifacts to campaigns so later sessions can see the initiative they belong to.
• Moving work to Live creates a later reminder to record results and close the loop.

Operating scope

Campaigns connect the work

A campaign is the scope that connects an initiative's sessions, evidence, artifacts, content, tasks and performance. It is how Quiver keeps the plan, execution and outcome traceable.

• Use status, priority, owner and dates to distinguish planned work from active execution.
• Attach new sessions and artifacts to a campaign when they serve an existing initiative.
• Use campaign performance summaries to review linked outcomes without reconstructing the work from separate tools.

Content infrastructure

Content, with an interface

Content in Quiver keeps markdown, production state, SEO and social metadata, authorship, tags, repurposing lineage, distribution records and metric snapshots together.

• Use All, Calendar and Draft views to inspect the editorial system from different operating perspectives.
• Link derivative content to its source so repurposing preserves lineage.
• Log metric snapshots over time instead of replacing the last known result.
• Record a distribution for every place a piece went live. The URL is required, because it is what later matches analytics data back to the piece.

GET https://quivergtm.dev/api/public/content
GET https://quivergtm.dev/api/public/content/[slug]

Release notes

Changelog, drafted from merged pull requests

A changelog is a content type, not a separate product. Entries are content pieces with contentType: changelog, so they move through the same draft and published states, carry the same SEO and tags, and are served by the same public Content API as everything else.

1. Your agent drafts. Point it at the pull requests you merged since the last entry. The changelog-drafting skill tells it how to turn them into release notes: grouped by user-visible change rather than by commit, leading with what someone can now do, internal refactors left out, one short paragraph each. It saves the result through MCP as a draft.
2. You review and publish. The draft lands in Content like any other piece. Edit it, tag the release (a tag such as v2.4.0 becomes the release label), and publish when it reads the way you want it to. Nothing is published on your behalf.
3. It appears on your site. Published entries are served by /api/public/content?contentType=changelog, so your site renders them wherever you want. Quiver’s own changelog, at /changelog, is that API rendered — full entries inline, newest first, grouped by month, with its own RSS feed.

Quiver never talks to GitHub. Your agent already has whatever repository access you gave it; Quiver’s job is to store the entry, keep its history and publish it.

Evidence layer

Customer research

Store calls, interviews, surveys, reviews, forums, support tickets, social posts, community exports and field notes beside the work they should influence.

• AI processing extracts summaries, themes, sentiment, Voice of Customer quotes, product signals and hypothesis evidence.
• Star important quotes so approved customer language can inform Strategy and Create sessions.
• Track whether evidence validates, challenges or is neutral to an active hypothesis.
• Generate a Linear-ready clipboard payload when needed. Quiver does not currently write directly to Linear.

Feedback loop

Performance changes what happens next

• Log quantitative metrics and qualitative observations in the UI or through MCP.
• Use synthesis to capture what worked, what did not and what the evidence can actually support.
• Review proposed context updates as pending, approved or rejected.
• The close-the-loop queue surfaces shipped work that is still waiting for results.

Tasks turn recommendations into owned work

The built-in task system is part of hosted Quiver and is not included in the open-source edition.

• Attach tasks to campaigns, artifacts, content, research and sessions.
• Strategy, Feedback, Analyze and Optimize sessions can propose next steps. Select the useful ones, assign an owner and create them in the system.
• Use assignees, due dates, reminders and dashboard queues to keep work accountable.
• Moving an artifact to Live creates a “Log results” task due in 14 days for the person who shipped it.
• Operate tasks over MCP with list_tasks, create_task, update_task and complete_task.

Feedback

Reporting a bug or requesting a feature

The speech-bubble button in the workspace header, next to notifications and the theme toggle, opens the feedback form from anywhere in the app. One form covers both — it asks whether you are reporting a bug or requesting a feature, so there is nothing to choose before you start typing.

The form can also receive three optional fields describing the situation, so nobody has to ask what you were doing: userEmail, replayUrl — a link to your PostHog session replay, so the exact session can be watched back rather than reconstructed from memory — and quiverContext, a single line holding your workspace, plan, user id and role, the page you were on and the id of the object it shows, the deploy’s git commit and environment, your browser, viewport, timezone and locale, and the last few JavaScript errors your browser raised.

Those three are sent on every submission but are only recorded if the form declares a hidden field with the matching name; Fillout ignores the rest. So a form that declares none of them still works perfectly, and adding one starts capturing it immediately with no change to Quiver.

Nothing you wrote is attached automatically. No prompts, session messages, artifact, content or research bodies, context values, object titles or API keys are ever included — only what you type into the form itself.

Agent interface

MCP server

MCP lets compatible agents read and write Quiver through structured tools. Your agent environment can keep its broader context and connections while Quiver remains the system of record for developer-marketing work.

https://<your-workspace>.quivergtm.dev/api/mcp

{
  "mcpServers": {
    "quiver": {
      "type": "http",
      "url": "https://<your-workspace>.quivergtm.dev/api/mcp",
      "headers": { "Authorization": "Bearer qvr_..." }
    }
  }
}

Packaging

Deployment and billing

• Both hosted plans include the current hosted feature set and differ by seat allowance.
• Annual billing costs ten months—two months free compared with monthly billing.
• The hosted trial lasts 14 days, requires a card and can be canceled at any time.
• Manage cards, invoices, plan changes and cancellation through Settings → Billing.