governed autonomy for marketing
The whole funnel, on autopilot
One governed agent plans, drafts, and runs every stage from positioning to advocacy. You approve everything that ships.
One email at launch. Unconsented blasts are BLOCK-classed around here.
- AUTO
content.draft_articleRan on autopilot. Logged.
- APPROVAL
linkedin.publish_postHeld in your approval queue.
- BLOCKED
cold_email.unconsented_blastNo execution path exists.
Three risk classes from the live policy matrix. One gate before anything reaches the outside world.
Every stage of the funnel. One agent.
8 stages, all 46 channels, one approval queue. The shape is the strategy: demand generation narrows attention into customers, lifecycle marketing widens customers into advocates.
Then it loops. Case studies feed attraction, reviews feed activation, referrals skip the top entirely. Run end to end, a funnel behaves like a flywheel.
Measure wraps all of it
Measurement is not a ninth stage; it wraps all eight. The strategist plans from your goal and live metrics each cycle, so the next batch of work aims at the stage that leaks most instead of the channel that shouts loudest. A funnel is a chain, and the chain is its weakest link.
One agent, on a loop
Plan
Reads your goal and live metrics each cycle, finds the stage that leaks most, and picks the plays that fix it. Fresh work is skipped; its own load is capped.
Draft
Articles, posts, ad creative, outreach, briefs. Drafting is risk-classed AUTO and runs immediately, because a draft cannot hurt you.
Approve
Publishes, sends, and spend are held at the gateway. You approve or reject everything that leaves the system, from one queue.
Audit
Every action is appended to a hash-chained, append-only log. The chain is re-verified in the database, so edits cannot hide.
Designed around one question: what could go wrong?
Autonomy is a governance problem, not a model problem. So the guardrails are structural, not promises in a system prompt.
Every action passes one gate
Before anything runs, the gateway looks up its risk class. AUTO runs and is logged. REQUIRE_APPROVAL waits for you. BLOCK never runs: fake reviews, unconsented blasts, mass DMs, and paid link schemes have no execution path at all. An action with no policy row fails closed.
A log that cannot be quietly edited
Every action lands in an append-only log, each row hash-chained to the one before it. The database re-verifies the chain live; tampering breaks it visibly.
Kill switches
Stop one channel or the whole agent instantly. Irreversible actions, like money leaving, can never autopilot regardless of policy.
It markets itself, in the open
marketinque is customer zero: the agent runs the early stages of its own funnel in production. The guide and the blog attract, the free tools and the waitlist capture, and this page is the positioning. Every article was drafted by the agent and approved by a human before it went live.
Questions operators ask
- What can it do without asking me?
- Draft. Articles, social posts, ad creative, outreach drafts, audits, and briefs are risk-classed AUTO and run on autopilot, because a draft cannot hurt you. Anything that leaves the system (a publish, a send, a dollar of spend) waits for your approval.
- Does it really cover the whole funnel?
- Every stage from positioning to advocacy has channels the agent drafts for, and all 46 channels in the catalog map to a stage. The human moments stay human: sales calls, demos, and kickoffs are prepped by the agent with battlecards, objection pages, and scripts rather than performed by it.
- What stops it from publishing something embarrassing?
- Nothing publishes on its own. Every publish to a public channel is classed REQUIRE_APPROVAL and waits in your queue until you approve it. There are also kill switches, per channel and global, that stop the agent instantly.
- Can it spam people?
- No. Unconsented blasts, mass DMs, and fake reviews are BLOCK-classed in the policy matrix, which means no execution path exists for them. Legitimate outbound (cold email, ABM, social DMs) is drafted by the agent but consent-gated and human-approved before any send.
- How do I know the audit log is honest?
- Each action is appended to a write-once log where every row carries a hash of the previous one. The database re-verifies the whole chain on demand, so a deleted or edited row breaks the chain visibly on the governance dashboard.
- When can I use it, and what will it cost?
- marketinque currently runs one production deployment, its own funnel, while the governance model proves itself in the open. Pricing is not announced; the waitlist hears first. The platform is built lean on purpose: it skips fresh work, caps its drafting per cycle, and runs on a single small server.