TinTinWorkflows
GitHubSign in

Open-source marketing system designed for coding agents

Install a battle-tested, self-improving marketing system in 15 minutes instead of writing it from scratch.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp
claude code~/projects/virvid

›How could Tin help me grow virvid.app?

Good fit. I read the repo and your Search Console export.

Three systems fit: organic growth, content, and a Monday note on what to try next.

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

›

used by founders and engineers from

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

Say the outcome you want.Tin builds the system, then improves it every week.

Growth systemvirvid.app · week 7
7 loops running300 bid changes2 need you
now · fri 23:30
↻ measure → researchEvery Sunday, what moved becomes next week's plan.

It lives in your agent and your repo.Nothing ships without you.

Your coding agent already knows how. Tin is an MCP server. Ask how it could help, and it reads the repo 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 growth
you rank on page two for “video API for agents”. Weekly audits, answer pages, and the canonical fixes.
Content
a launch post each time you ship, drafted from the changelog in your voice.
What to work on next
a Monday note that reads Stripe and Search Console and says what to try.

Plain files, with git history. Your voice, research and every draft live in the repo, where your agent can read them.

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.

Start with people who already know you. The people in your orbit, ranked by your ICP.

People

All peopleICP fitNot connected yet
2 selected
NameHeadlineICP fit ↓LinkedIn
Maya LindqvistFounder, payroll for remote teams0.84Connected
Daniel OkaforCo-founder, Fieldline0.78Not connected
Priya RamanCEO at Stackwell, data tools0.74Connected
Jonas WeberSolo founder, shipping Ledgerly0.69Not connected
Sofia MarchettiFounder & CEO, Patchbay0.66Invited oct 14
Amara OseiFounder, Tidewell0.66Not connected

You approve what ships. Drafts arrive as a pull request or a one-click publish. Nothing goes out on its own.

Answer page: what an iMessage API costs

Read
content.answer_page · run_0512 · today 09:04 · 1,420 words

The draft answers the question people ask AI assistants most about your space. Say how it ships.

Connection requests · 5 people who reacted to your posts

social.linkedin_engagers · today 08:40

Weekly brief · four posts moved, one slipped

project.weekly_brief · tue 09:00

A full marketing stack,from templates.

See every workflow →

Claw Messenger, four months in.From $45 to $2,105 a month.

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

monthly recurring revenue
$2,400$1,200$0
$2,105
marchaprilmayjunejuly

Open source,Apache 2.0.

Read the code
Every workflow is text in the repo.
Run it on your machine
Your keys, your data, your schedule.
Change a workflow
Edit the file and send it back.
Bring your own skills
One command turns them into workflows.
Repo on GitHub →

Growth engineers,for your team.

We set Tin up inside your environment, on your repo and your data, and adapt the workflows to the way your team already works. Your team keeps engineering it through their coding agents, and the code stays yours after we leave.

Talk to us →

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

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