Turn signups into pipeline
PQL scoring for every trial signup: enriched, scored on your ICP, the first session read, a play chosen by your rules and a deal opened for the right rep.
- Starts
- New signup
- Steps
- 7
- Checks and gates
- 0
- A person decides
- Never, runs alone
Trigger · Event
New signup
A signup event in the product opens the run, so the first message and the rep's brief are ready while the person is still in their first session.
Claude runs the rest autonomously
- 1
AI enriches the person and the company.
Apollo.ioApollo.io
The signup's title, seniority and company size, funding and industry come back from two sources, so a name and a work email are enough to start.
LinkedInLinkedIn
- 2
AI checks the CRM and billing for the account.
HubSpotHubSpot
Any account, open deal, customer status, paying subscription or earlier signup from the same company comes back, so a signup from a customer goes to its owner and not to sales.
StripeStripe
- 3
AI scores fit against your ICP.
The signup is scored on your own profile, and one below the bar goes self-serve with the product's own onboarding and nothing more.
- 4
AI reads what they did in the first session.
PostHogPostHog
The systems they connected, the colleagues they invited, what they created and where they stalled come back with their times, which is what the messages will name.
- 5
AI chooses the play from your activation rules.
Your own rules pick sales-assist, an enterprise hand-off or nurture from the fit and the first session, with the timing of the call, and the rule is named.
- 6
AI drafts the first-week messages.
GmailGmail
Three messages are planned for the first week and the first waits as a draft in your voice, naming what they did and proposing the call, never sent.
- 7
AI opens the deal, brief the rep.
HubSpotHubSpot
For sales-assist and enterprise the deal opens for the rep your rules name, with the signup, the fit, the first session and the play, and the rep gets the brief and the draft.
SlackSlack
A trial signup is the warmest lead a product-led company gets and the one it handles worst. The person is in the product right now, connecting a tool, inviting a colleague, hitting the free limit. The automated welcome email went out at the same moment to everyone, saying the same thing to a founder with nine staff and a head of operations at a company of six hundred. Sales hears about the signup on Friday, in a list, and writes to the ones whose company names they recognise. The rest convert or do not on their own.
Every piece of a good first week is already there. The company and the person are in a database. The CRM and billing know whether the company is a customer, a deal or new. Product analytics knows what the person did in their first hour. Your profile says who fits, your activation rules say which fitting signups get a call and when, and the person your signups hear from has a voice. The run reads those together in the minutes after the signup, drafts the first message around what the person actually did, and puts the right ones in a rep's hands.
What you get
Every signup is, within minutes, a known person at a known company, checked against the CRM and billing, scored on your profile, read for what they did in their first session, and given the play your activation rules call for, with the first week's messages drafted in your voice around what they did, and, when the play is sales-assist, a deal open for the right rep with the brief in their hands.
What a signup is read against
The run opens on a signup event in PostHog. It reads:
- The person and the company, from Apollo and LinkedIn: industry, headcount, funding and location on the domain, and the person's title, seniority and tenure.
- The account, in HubSpot and Stripe: any account, open deal and owner, whether the company is a customer, any paying subscription, and any earlier signup from the same company on a free plan.
- The first session, from PostHog: the systems connected, the colleagues invited, what was created, where the person stalled, and whether a free-plan limit was hit, each with its time.
The first message is drafted in Gmail and the rep is briefed in Slack.
What makes product-led sales hold up
The CRM and billing are read before fit is scored. A signup from a paying account or from a company with an open deal is not a new lead: it goes to that account's owner as one line, with no play and no draft, because a second person from a customer is an expansion conversation and the owner has it. A third signup from one domain in a month is a buying committee forming, and the brief says so.
Fit decides whether sales should care; the first session decides what sales should do. The signup is scored on your profile, and one below the bar goes self-serve, with the product's own onboarding and nothing from this run, which is what keeps the reps' queues worth opening. Among the fitting, your activation rules choose the play from what the person did: a connected system or an invited colleague earns a sales-assist call on day three, a company above your enterprise line a hand-off the same day, and no activity yet a nurture sequence with a check on day seven. The run names the rule on the deal, so the next person who opens it knows what was decided and on what.
The messages name what the person did. The first is drafted now, in the voice of the person your signups hear from: one thing they did in the product, one thing it does that they have not tried and that fits their role, and the call proposed with a time when the play calls for it. No feature list, no figure your proof points do not mark citable, and never sent by the run. The two that follow are planned with their due days and drafted on day three and day seven from what has happened in the product since, so a signup that connected a third system on Wednesday gets a Thursday message about that and not the one planned on Monday.
In a rep's hands while the session is still open
For sales-assist and enterprise, the deal exists before the rep hears about it, on the company, with the rep your routing rules name as owner, the signup as its source, the fit and its reasoning, the first session and the play. The rep gets one message: who signed up, from where, what they did in the first hour, the play and the rule behind it, and where the draft is. For nurture, the plan is written on the contact and nobody is told yet. A signup is in a rep's hands while the person is still in the product, which is the only time the first message is worth reading.
The prompt
The real prompt behind the steps above, detailed enough that an agent with the same tools can run it as written. The Run buttons copy the full version, which also carries the steps for connecting those tools.
# Turn signups into pipeline
You have access to a company and people database, LinkedIn, a CRM, a
billing system, product analytics, an email account, and a messaging
tool. Run this for **[the signup that just landed]**.
## 1. Enrich the person and the company
A signup is a name and an email. From the email's domain, find the
company in the company database: industry, headcount, funding and
location. Find the person on LinkedIn by name and company: their
title as written, their seniority, how long they have been there.
A personal email domain is matched on the name alone, and a signup
whose company cannot be found is carried on with what the form gave:
a signup is not dropped for being hard to enrich, since the product
will tell you more than any database within a day.
## 2. Check the CRM and billing for the account
Search the CRM on the domain and on the email: any account, any open
deal with its owner, any contact already known, and whether the
company is a current customer. Search billing on the domain: any
paying subscription, and any other signup from the same company on a
free plan, with their dates.
A signup from a current customer or from a company with an open deal
is not a new lead. It goes to that account's owner in step 7, with
no play chosen and no message drafted: a second person from a paying
account is an expansion conversation, and the owner has it. A third
signup from one domain in a month is a buying committee forming, and
the brief says so.
## 3. Score fit against your ICP
Score the signup on **[your ideal customer profile: segment, size,
geography, role, and what disqualifies]**. A signup below the bar is
**self-serve**: it gets the product's own onboarding and nothing from
this run, and the run stops here for it, reporting why. Fit is read
from who they are; what they did comes next and sets the play, not
the fit.
## 4. Read what they did in the first session
From product analytics, read the signup's events since they arrived:
which tools or sources they connected, whether they invited a
colleague, what they created, where they stalled, and whether they
hit **[a free-plan limit]**. Keep the facts with their times. A
signup that connected two systems and invited a teammate in an hour
is a different conversation from one that opened the product and
left, and the messages in step 6 name what they did.
## 5. Choose the play from your activation rules
Read the fit and the first session against **[your activation
rules: which signups get sales-assist, which an enterprise hand-off,
which the nurture sequence, and the timing of each]**. The starting
rule: a fitting signup that connected a system or invited a colleague
is sales-assist, with a call proposed on day three; a fitting signup
from a company above **[your enterprise line]** is an enterprise
hand-off, with the call proposed the same day; a fitting signup with
no activity yet is nurture, three messages over the first week and a
check on day seven. Name the rule.
## 6. Draft the first-week messages
Plan three messages for the first week, each tied to something they
did or did not do, and draft the first one now as an email from
**[the person your signups hear from, in their voice notes]**: one
thing they did in the product, named; one thing the product does that
they have not tried and that fits their role; and, for sales-assist
or enterprise, the call proposed with a time. No feature list, no
figure your proof points do not mark citable. **Create it as a
draft. Never send it.** Record the other two messages with their due
days, so the day-three and day-seven runs draft them from what has
happened since.
## 7. Open the deal, brief the rep
For sales-assist and enterprise, create the deal on the company with
the rep **[your routing rules]** name as owner, the signup as its
source, the fit and its reasoning, the first session and the play.
Add the person as a contact. Post one message to the rep: who signed
up, from where, what they did in the first hour, the play and the
rule behind it, and where the draft is. For nurture, write the plan
on the contact and tell nobody yet. For a signup on an existing
account, post one line to its owner and stop.
## Output
Report: the signup, what was found about the person and the company,
the account's history in the CRM and billing, the fit and its
reasoning, the first session's facts, the play and the rule, the
three messages planned and the one drafted, the deal created and the
rep told, or why the signup went self-serve, to nurture or to an
existing account's owner.
Why run it with Tulina
A prompt helps one person. A process moves a team.
Pasted into a chat, the prompt above works once, for whoever pasted it. In Tulina, "Turn signups into pipeline" becomes a process the team shares, that keeps its history, runs on its own, and stays inside the same security perimeter as the tools it calls.
The whole team works on the same one
PersonalTeamOrganisation
A process lives where it belongs: yours, your team's or the whole organisation's. Whoever runs it can improve it, and everyone starts from the best version instead of explaining the job again.
Every edit is a version
v1v2v3
Each change is a new version with the previous one kept, so a bad edit is undone by restoring an earlier one. Every run records the version it followed, and what a run teaches goes back into the process.
It runs without you
schedulewebhookon demand
A hosted agent runs the process on Tulina's own infrastructure, on a schedule or when an event arrives, and keeps going when you close the chat. Nothing to host. Every run is tracked to its outcome.
Inside the same security perimeter
vaultrolesrun log
Credentials stay in the vault, never in the prompt. Roles decide who may run what, every call is logged, and a step a person has to approve waits for that person.
Questions about AI product-led sales
Related processes
Processes that share tools with this one. The shared tools are lit.
Catch churn signals and answer them
Usage falling away shows up in analytics before anyone notices on a call, and the drop is read against the account's history into one reactivation email.
- Shares
- PostHog, HubSpot
Weekly schedule4 steps →
Follow champions who change jobs
Each week, champions at won accounts are checked for a new employer, the new company is scored on your ICP, and a warm deal opens with a note for the right rep.
- Shares
- HubSpot, LinkedIn, PostHog, Gmail
Weekly schedule7 steps →
Expand accounts from usage
Each morning, accounts near a plan limit or on a feature their plan lacks get an offer priced on your packaging rules, an expansion deal and a drafted proposal.
- Shares
- PostHog, Stripe, HubSpot, Gmail
Daily schedule7 steps →