TinTinWorkflows
GitHubSign in

Open-source marketing system designed for coding agents

Why would you build marketing processes from scratch when you can install a battle-tested, self-improving marketing system in 15 minutes?

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

used by founders and engineers from

  • Y Combinator
  • MIT
  • Harvard University
  • Meta
  • Google
  • Nvidia
  • McKinsey & Company

A self-improving marketing system, out of the box

Tell your coding agent the system you want to build. Tin builds it with fine-tuned workflows that run every week on your own company data, with evaluation scaffolding and a self-improving loop.

Organic growth system
Reads where you nearly rank
Search Console + your repo
Audits the site every week
Technical SEO and AI visibility
Writes the pages that answer
Four a week, in your voice
Checks the quality
Evaluations on every run
Gets approval for critical outputs
You review and merge
Analyzes the data
Analytics, rankings and what changed
See what this did for Claw Messenger ↓

What every system is made of

Your coding agent already knows how to use it

Tin is an MCP server. Add it, and whole marketing systems show up as tools next to the ones your agent already has. Ask it how Tin could help your project. It reads the repo and the skills you already use, and answers.

claude code~/projects/virvid
›How could Tin help me grow virvid.app?

This is a good fit. I read the repo, your Search Console export and the skills you already keep in .claude/skills.

Three systems I would set up:

Organic growthyou rank on page two for “video API for agents”. Weekly audits, answer pages, and the canonical fixes.
Contenta launch post each time you ship, drafted from the changelog in your voice.
What to work on nexta Monday note that reads Stripe and analytics and picks one experiment.

Your release-notes skill becomes the first step of the content system, so nothing you wrote is lost.

Turn on organic growth first? The first audit takes about four minutes.

›

A full marketing stack from templates, in minutes

Each workflow is tuned on real projects. Pick a system and its workflows start running on a schedule. More land every week.

available todaycoming in Septembercoming
Organic growth
Content
Product QA and activation
What to work on next
Cold outreach
Measurement
Paid ads
Directories and listings
Lifecycle and retention
PR and podcasts

The more it knows about your company, the better the marketing

The code is yours, so you can hand it everything a new marketing hire would take months to learn, and give it live access to the same tools.

Customer interviews
Pages that answer the objections people actually raise
Positioning and voice
Every draft in your words, not a template's
Search Console
Pages built for the queries you already rank near
Stripe
Outreach aimed at the segment that upgrades
Support inbox
FAQ and answer pages from real questions
Your repo
Site fixes and launch posts straight from what shipped
Analytics
Experiments pointed at where the funnel leaks
Past campaigns
It repeats what worked and drops what did not

The more you connect, the more it can do

connectedcoming
Google Search ConsoleGitHubClaude CodeCodexCursorGoogle Docs and DriveGoogle Workspace (Email & Calendar)Google Analytics 4PostHogMixpanelPlausibleStripePolarVercelNetlifyWebflowFramerWordPressShopifyMeta AdsGoogle AdsLinkedIn AdsReddit AdsResendLoopsMailchimpHubSpotAttioNotionSlackDiscordXLinkedInRedditYouTubeProduct HuntAhrefsSemrushBing WebmasterIntercomCal.comTypeformCanvafal.ai

The next run starts with what you know.

Tin’s growth knowledge, your company context, and the work that comes out of it. Plain files your coding agent can read over MCP.

Keep your instructions, content, research, and outreach together. Every run has something to build on.

Files

    • # Scanning a project
      Read what exists before proposing anything.
      1. Sitemap, robots, canonical tags
      2. What the site says it is for
      3. Where it nearly ranks
    • # Answer pages
      One page for one buyer question, in your words.
      Answer in the first two lines, then show the work.
    • # Technical SEO
      Crawlable, canonical, fast enough. In that order.
      Fix what blocks the crawler before writing anything new.
    • # Virvid memory
      Product: a video API for agents. Live since 2026-03.
      Buyers ask: which video API works with an agent framework.
      ## Sources
      6 runs, latest 2026-09-15.
    • # Positioning
      Virvid is a video API for agents, not for editors.
      Against: APIs that assume a human presses render.
    • # Writing style
      - Short sentences. One idea in each.
      - We for the team, you for the reader. No one else.
      - Say the number, the file, the date. Never “seamless”.
      - End on what happens next, not on a summary.
    • ---
      title: Video API for agents: what to check before you build
      status: draft, waits in Decisions
      ---
      Most guides start with the SDK. Start with the failure modes.
    • # 2026-Q4
      Three answer pages, one launch post, one case study.
      Ships weekly. Reviewed Mondays, in Decisions.
    • # Changelog: scheduled runs
      Runs start on their own now, on the schedule you set.
      What you do differently: nothing.
    • graph LR
      ask["Message arrives"]:::step
      check["Conversation check"]:::step
      send["Reply"]:::step
      ask --> check --> send
    • name,company,reason,selected
      Priya R.,Loom for agents,asked about pricing in June,yes
      Marcus T.,Aviato,met at YC demo day,yes
    • # Campaign: design partners
      2 people on the shortlist, both asked us first.
      One email each. No follow-up without a reason.
    • # AI visibility
      5 buyer questions, asked with and without search.
      Found 2, mentioned 1, shortlisted 0.
      Absent from: “video API for agents”, “agent video generation”.
    • # Scan: virvid.app
      42 pages read. 3 issues, 2 questions for you.
      No canonical on /docs. One title used on 6 pages.
    • # Week of 2026-09-15
      Moved: audit done, one PR merged.
      Needs you: nothing.
      Smallest next step: publish the answer page.
    • # Signup QA, 2026-09-15
      Ran the signup as a new account. 4 steps, 1 dead end.
      The verification link expired before the email arrived.
    • 12 more
  • # AGENTS.md
    This project runs on Tin. Before proposing work:
    1. Read company-wiki/INDEX.md.
    2. Check reports/ for the latest audit.
    3. Write in the voice in skills/writing-style/SKILL.md.
  • # Virvid
    A video API for agents.
    This folder is the marketing project Tin keeps for it: knowledge, drafts, reports, all as files with history.

Bring your own workflows, or tweak ours

Your skill files become workflows in one command. Ours are text in the repo: change a step, and the next run uses it.

~/.claude/skills/launch-post/SKILL.md
--- name: launch-post description: Launch post from a merged PR --- Read the PR. Read voice.md. Draft 400 words…
$ tin import ~/.claude/skills/launch-post
→ content.launch_post created → runs on every merge to main → draft lands in Decisions → first run: next merge
~/.claude/skills/launch-post/SKILL.md --- name: launch-post description: Launch post from a merged PR --- Read the PR. Read voice.md. Draft 400 words…
$ tin import ~/.claude/skills/launch-post → content.launch_post created → runs on every merge to main → draft lands in Decisions

Case study

project
Claw Messenger · clawmessenger.com
sector
Developer tools
timeline
25 March → 27 July 2026 · 124 days
From $45 to $2,105 a month in four months

Claw Messenger gives AI agents an iMessage number. It had five paying customers when we handed it to the system in March. By late July it had 257, and the SEO, outreach, site fixes and weekly brief were all run by the agent.

monthly recurring revenue
$2,400
$1,200
$0
$2,105$2,105
march
april
may
june
july
Five workflows that created this growth:
content.answer_page
Four posts brought 12,103 visitors in July
site.health_improve
Eleven site fixes in the first week
outreach.email_shortlist
137 emails to founders who fit the customer file
project.task
A reseller tier the day after a customer asked
project.weekly_brief
A brief every Tuesday. The founders approved the queue from it

Open source, Apache 2.0

Read it, run it on your own machine, change a workflow and send it back.

Read the code
Every workflow is a folder: the steps, the inputs it reads, its evaluations, and who tuned it last.
Self-host
One Docker command. Your machine or a small VM. Same workflows as the hosted version.
Bring your own
Your skill files become workflows in one command. Ours are text in the repo; change a step and the next run uses it.
Growing community
New workflows land every week from people running Tin on their own projects. Send yours back with a pull request.
Ege ÖzgirinEmre Şarbak

Made by Ege Özgirin, who built AI agents at Oda and then Keke, his own autonomous AI artist, and Emre Şarbak, who helped build social-impact organizations LaunchCode, Kodluyoruz, Patika, Rise In and SuperSense. Marketing is the new bottleneck for people to benefit from technology. That is what we are solving.

also open, from us
with.md · MIT
Personality Machine · MIT
Personaplex fine-tuning

Turn your growth team into growth engineers

Our growth engineers set Tin up inside your environment, connect it to your repo and your data, and adapt hundreds of finetuned workflows to the way your team already works. Your team can continue engineering your self-improving growth system through their coding agents.

Talk to us →
what we bring
Forward-deployed growth engineers, on site or in your Slack
The stack running in your own environment, on your own data
Hundreds of finetuned workflows, adapted to your product
New workflows developed and automated with your team
Your team controls the code after we leave, but benefits from open-source updates

Add Tin to your coding agent

Run this once in your terminal. It connects Tin to your agent and opens the sign-in. Then ask your agent to grow your project.

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