When a nearby tool shuts down, be ready for its users
When a tool near yours shuts down, drops its free plan, reprices or relicenses, its users go looking. Tin finds the event, checks that your product can honestly take them, and writes a dated kit: their export mapped to your product, the import gap, and ready inputs for a migration page and an importer.
codex mcp add tin --url https://app.tin.computer/mcp
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.
- 01Looks for shutdowns, free plan removals, repricing and relicensing near your product, or checks an announcement you paste.
- 02Verifies the event and its deadline from the source, not on trust.
- 03Checks that your product can take those users without claiming features it lacks.
- 04Maps their export to your product, names the import gap, and saves the kit. Quiet weeks end with a short watch list.
Run Tin's sunset rescue weekly so we hear when a tool like ours is shutting down.
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 knows your import formats and data model, so the export mapping says exactly what carries over and what is lost.
All workflows →Runs well with.Workflows that feed this one, or follow it.
Questions.
What if no tool is shutting down?
Quiet weeks end with a short watch list. It does not invent an event.
Does it build the importer?
No. It writes the inputs for one: the export fields, how each maps to your product and what does not carry over.
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.
codex mcp add tin --url https://app.tin.computer/mcp