Give Claude the outcome
Describe the market, offer, constraints, and target result.
Give Claude or Codex a revenue outcome. Trevra composes modular skills to research, qualify, prepare outreach, follow up, invoice, and collect—while evidence, approvals, and every run stay under your control.
spawn gtm --goal "book qualified founder calls"run_8f2agtm.visibility-auditrecordedrun_8f2bgtm.score-leadrecordedrun_8f2cgtm.outreach-draftpreparedrun_8f2egtm.outreach-sendawaiting yousha256:4f21b8…c7e0Use Claude Code, Codex, or another capable agent as the operator. Trevra supplies the contracts, runtime, ledger, evidence, and approval boundary.
Describe the market, offer, constraints, and target result.
The agent selects typed modules and records the plan.
Research, scoring, critique, and preparation can run immediately.
External writes wait behind your workspace policy.
Every module declares its inputs, outputs, side-effect class, approval requirement, and version. The public catalog is generated from the executable registry.
gtm.visibility-auditv1.0.0Probe a domain for how readable it is to AI shopping assistants and answer engines.
gtm.score-leadv1.0.0Deterministic fit scoring with a human-readable reason for every contribution.
gtm.outreach-draftv1.0.0Produce a deterministic, compliance-footed outreach draft for a lead.
gtm.channel-preparev1.0.0Shape a draft to one channel and run the result through the copy critic.
Models interpret commercial context. Deterministic software controls permissions, state transitions, money, approvals, and external writes.
external_writes:
default: require_approval
outreach.send:
max_recipients: 5
confidence_min: 0.84
delay_minutes: 30
scope.change:
delegation: forbiddenThe public site and catalog deploy at Cloudflare’s edge. The product runtime stays portable: managed by Trevra or deployed into infrastructure you control.
Managed updates, authentication, integrations, backups, and a shared module catalog.
Fork the repository, deploy Express and PostgreSQL, connect your own providers, and keep the ledger inside your environment.
Hosted and self-hosted deployments use the same module contracts and approval model.
You give Claude Code, Codex, or another agent a GTM outcome. The agent calls Trevra modules, while Trevra records the run and stops at the approval boundary for consequential work.
Only inside the policy you set. Consequential actions can require manual approval, and the exact approved payload is hashed before execution.
Modules are versioned through GitHub and declare their schemas, side effects, and approval requirements. Validation and tests run before a catalog release.
Yes. The application uses PostgreSQL, the runner is open, and the ledger, evidence, configuration, and exports can remain in infrastructure you control.
Connect a workspace, install the first modules, and let your agent prepare the next revenue action—with receipts.