TinTinWorkflows
GitHubSign in

Newsletters and communities with a written way in

Tin looks for newsletters and communities your buyers already read that take outside work through a documented route: a featured-tool slot, reader submissions, a showcase thread, or a sponsorship with a published rate. It checks each one's rules and drafts the submission in your voice.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp
Newsletter placements
outreach.newsletter_placements
outputreports/outreach/newsletters/{run_id}.md
guardrailNever submits, pays, signs up, posts or contacts anyone. A budget of 0 keeps the list to free placements.
needsA Tin project. A growth plan and feature map supply the buyers and the product facts each submission cites.
required inputsnone
optional inputsfocus, geography, budget_usd, max_picks

What the workflow does.The same steps, every run.

A Tin workflow is a repeatable job: declared inputs, a bounded run and a defined output.

  1. 01Reads who buys, the market, the budget and your hard no's from the growth plan.
  2. 02Finds specific newsletters and communities with a standing, documented way in, and skips anything that has to be guessed.
  3. 03Verifies each placement's rules and price, and leaves out paid slots above your budget.
  4. 04Drafts one submission per placement, skipping placements drafted in earlier runs.
ask your agent

Find five newsletters or communities our buyers read that accept submissions, and draft each one.

What every workflowcomes with.

Battle tested on real products

These are the workflows we run for real companies. Claw Messenger went from about $45 to $2,105 in monthly revenue in 124 days on them. Each one has declared inputs, bounded execution and tests, and anything public waits for your review.

See the case study →

Open source: read it, fork it, self-host it

Apache 2.0. Every workflow is a folder in the repository: the steps it runs, the data it reads and what it is allowed to do. Change it, or run the whole system on your own machine.

Open the repo →

Runs on the agent that already knows your product

A good submission cites one concrete thing the product does. Your agent knows which features are real and which are still on a branch.

All workflows →

Questions.

Does it cover podcasts and conferences?

No. Talks and podcasts have their own workflow, and campus events have another.

Will it pay for a sponsorship?

No. It reports published prices within the budget you set. Booking and paying stay with you.

Is Tin really open source?

Yes. Tin is licensed under Apache 2.0 and the source is at github.com/tin-computer/tin. You can read every workflow, change it, and self-host the whole system.

Which coding agents can run Tin workflows?

Any agent that speaks MCP, including Claude Code, Codex and Cursor. There is also an API, and the same projects run in the browser at app.tin.computer.

Why run marketing from a coding agent?

Because it already knows your product. It has the repository open, so it fills workflow inputs accurately, reviews output against what the product really does, and can act on the results in the same session.

Add Tin to your coding agent.It takes one command.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp