TinTinWorkflows
GitHubSign in

Who pays and stays, from Stripe

Tin reads your Stripe subscriptions and compares the customers who keep paying with the ones who leave. You get the segment that stays, and the exact inputs to aim outreach, keyword research and a paid ads assessment at more people like them.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp
Paying customer segment
outreach.paying_segment
outputreports/outreach/PAYING_SEGMENT.md
guardrailRead-only. No model calls, and it starts no other workflow by itself.
needsThe Stripe connection, with a restricted read-only key.
required inputsnone
optional inputsretention_days, lookback_days, min_segment_size, exclude_domains, product_summary

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 subscriptions through a read-only Stripe key, leaving out your own and test email domains.
  2. 02Counts who kept paying past the retention window you set.
  3. 03Compares segments large enough to mean something.
  4. 04Writes ready inputs for the email outreach shortlist, the keyword plan and the ads assessment.
ask your agent

Use our Stripe data to find which customers stay past 60 days, and give me the inputs to aim outreach at them.

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

Your agent can fill in your staff and test domains from seed data and admin allowlists, so internal accounts do not skew the segment.

All workflows →

Questions.

Can Tin change anything in Stripe?

No. The connection uses a restricted key with read permissions only.

Does it run on a schedule?

It can run on demand or weekly.

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