Your pipeline, moving on its own.
Deepline remembers where every account is, even when the next step is weeks away.
Build your first EngineSee where every
account is.
Every account sits in one stage you named, with the step that put it there. The stage is saved with the account, not held in a run, so it outlasts any single attempt to move it.
Your motion takes weeks.
Your tools think in runs.
Research on Monday, approval on Wednesday, outreach on Friday, a reply two weeks later. Most teams hold that together with a status column, a few automations and someone who remembers what is done. Accounts stall halfway, a rerun pays for research you already have, and nobody can say where an account is without digging.
Three parts, all yours.
An Engine is built from Plays and your database. Each step runs as its own Play and finishes. The database holds every account in between, so the next step can come minutes or weeks later.
Read the Engines docsYou name the stages.
Use your own words for your own process, like new, researched, approved and contacted. Deepline does not impose a funnel.
Each stage runs a Play.
Research, qualify, draft or route: the same Plays you already use, one for each step.
Every move is saved.
Each stage has its own table in your database with the input, the result and the next stage. The next step reads what the last one wrote.
Built for work
that takes weeks.
An Engine keeps the process moving between runs, through failures, and while it waits on people.
See where everything stands.
Every account sits in one named stage. See how many are waiting on review, and which step put each one there.
Pick up where it stopped.
When a run fails partway, the retry finds the finished steps and continues from there instead of writing a second result.
Wait for people and events.
An account can stay in review until someone approves it, or until a webhook or schedule brings the next event. Nothing has to stay open.
Your rules, written down.
Which moves are allowed, what counts as ready and when an account is done are stated, not guessed from a stray column.
When you don’t need one.
If the job ends after one step, like enriching a list or building a report, a regular Play is simpler. Use an Engine when accounts move through several stages over time and you need to see and retry each move.
An Engine runs your rules. It cannot write them for you. If your team cannot yet say what ready means, settle that first.
Read what a Deepline Engine isTry it with your agent.
Paste this into Claude Code, Codex or any agent with Deepline set up.
/deepline-engine Build an engine for account review. Accounts start as new, get researched, then move to ready when they fit our ICP or to needs review when the evidence is mixed. Show me the stages and tables before publishing.
Set up Deepline.
Paste this into your agent once. Then come back for the prompt.
Paste into your agent
Install and set up the official Deepline CLI globally from npm (package: deepline) by following https://code.deepline.com/INSTALL.md. After setup, continue my existing task if I gave one. Otherwise, present the guide's four starter choices verbatim, with each of the first three requests starting with /deepline-gtm.