Sales process, actually followed.
Keep your
CRM in line.
Define what your team needs at each stage. Liney asks reps for what's missing, keeps your CRM current, and gives RevOps a pipeline they can trust.
- No setup beyond connecting
- No sales call
- Free while in beta · 8 of 10 spots left
Every rep.
Same process.
Set what each stage needs. Liney asks every rep for anything missing as they update the deal, the same way for the whole team.
See how it works- Company
- Contact
- Amount
- Next step
- Next step
- Close date
- Decision maker
- Next step
- Close date
- Contract term
- Close date
- Won reason
Northstar Analytics · Qualification.
Know when something falls out of line.
A live count of each rep's open deals: gone quiet, past close date, no next step, missing a required field. Plus a daily history.
By rep
| Rep | Deals | Gone quiet | Past close | No next step | Missing fields |
|---|---|---|---|---|---|
| Alex R. | 24 | 3 | 2 | 5 | 3 |
| Sarah T. | 18 | 4 | 3 | 6 | 5 |
| Chris M. | 16 | 2 | 1 | 4 | 2 |
| Jordan K. | 11 | 1 | 2 | 3 | 4 |
| Taylor S. | 9 | 2 | 0 | 1 | 0 |
Northstar is one of Alex’s: no next step, a required field empty.
Every change is
accounted for.
See what changed, when it changed, and who changed it. Undo Liney updates for up to 30 days.
- Today 1:02 PMRiversideAmount $35,000 → $42,000, noteSarah T. via LineyUpdated
- Yesterday 4:21 PMSummit HealthNext step, close date, taskChris M. via LineyUndone
- Sep 18 10:03 AMEverwoodStage → Qualification, noteJordan K. via LineyUpdated
- Sep 16 9:12 AMPinecrestStage → Closed won, won reasonTaylor S. via LineyUpdated
- Sep 15 3:40 PMMaple RidgeStage → Closed lost: your CRM wanted a lost reasonSarah T. via LineyDidn't land
Update Northstar at the top of the page and your line lands here.
For reps, it's still one line.
They say what happened. Liney finds the deal, fills what it can, and asks only for what's missing. They review it. Then it goes to your CRM.
See it in actionNorthstar needs line one first. Update it at the top of the page.
Oh, sheet!
Your pipeline just got easier to fix.
Click a cell to change it, and filter to what needs attention.
| Deal name | Company | Stage | Amount | Close date | Next step | Decision maker |
|---|---|---|---|---|---|---|
| Northstar | Northstar Co. | Qualification | $42,000 | Sep 30, 2026 | Demo with CTO | Missing |
| Riverside | Riverside Ltd. | Qualification | $15,000 | Oct 30, 2026 | — none — | John Carter |
| Summit Health | Summit Health | Contract | $28,000 | Oct 15, 2026 | Send contract | Dana Lee |
| Maple Ridge | Maple Ridge | Proposal | $12,000 | Sep 29, 2026 | — none — | Missing |
| Everwood | Everwood Inc. | Qualification | $8,500 | Nov 20, 2026 | Intro call | Missing |
Sample deals. Northstar is the one from the top of the page.
Northstar is
still waiting.
The line’s already typed. Answer Liney’s question and press Update, and the rest of the page follows.
- Lines typed
- 0
- Fields filled
- 0
- Liney asked for
- —
- Reps chased
- 0
- Time
- —
Sample deal. Nothing went to a real CRM.
Your process,
built in.
Liney reads your stages and fields, and learns what each stage needs from your deals. Mark a field required and every rep gets asked for it. Ready in about two minutes.
See the setup screens- Discovery
- QualificationAmount
- ProposalDecision makerCompetitor
- ContractContract term
- Closed wonWon reason
Required field set by your adminLikely learned from your deals
Not on HubSpot?
Connect your own CRM in about an hour.
Liney talks to a CRM through one small contract: push your fields and deals, take a write and an undo, sign your reps in. Hand the prompt to your coding agent and it builds that side against your CRM. In our clean-room runs, agents starting from the prompt alone had the checker green in under twenty minutes, in Node, Python and Go.
For developersConnect our CRM to Liney. Read https://www.liney.ai/developers/llms.txt and build what it describes: push our schema and records, take /liney/write and /liney/undo (or poll the outbox in pull mode if our server has no public URL), sign reps in from our CRM. Then run the checker until every case is green; its lines say what to change. Our team on Liney: https://www.liney.ai/yourteam Test key: lk_test_•••••••••••• Connection secret: not in this prompt. It is in LINEY_SECRET in the server's environment (our connection card showed it once). Read it from there to verify Liney's signature and to sign sign-in tokens, and never write it into a file, a prompt or a log. The checker's first case tells you if the server hasn't got it. Checker (push mode): LINEY_URL=https://www.liney.ai LINEY_KEY=lk_test_•••••••••••• npx liney-check https://<our endpoint> Checker (pull mode, with our poller running): LINEY_URL=https://www.liney.ai LINEY_KEY=lk_test_•••••••••••• npx liney-check --pull Local server with no public URL: LINEY_URL=https://www.liney.ai LINEY_KEY=lk_test_•••••••••••• LINEY_SECRET=<from the env> npx --yes --package=liney-check liney dev http://localhost:<port> (forwards Liney's calls to it; then run the checker with --pull)
- One prompt. Your agent reads the contract and builds your side of it.
- A checker that tells the agent what to fix, one line per case.
- Live when it's green.
Reps only see what
they already see.
Liney connects through each rep's own CRM account and works within their existing permissions. No new access layer to manage.
PrivacyWhy not Breeze, ChatGPT or Claude?
AI can update a deal.
Liney runs the process.
Breeze Assistant, ChatGPT and Claude can all update HubSpot from a sentence now, and Liney uses Claude underneath. What Liney adds is the part around the AI: the same rules for every rep, undo on every line, and a pipeline you can watch getting cleaner.
| Breeze Assistant | ChatGPT / Claude | Liney | |
|---|---|---|---|
| Who it’s for | Each person, in HubSpot | Each person, in a chat | The whole team |
| Updates HubSpot from a sentence | Yes | Yes | Yes |
| Which fields the AI may change | Not in HubSpot’s docs | Set per tool, not per field | Your admin picks, per field |
| Undo | Not in HubSpot’s docs | Can’t delete what it made | Any line, for 30 days |
| Pipeline health | A data completeness score | Build it yourself | Daily, rep by rep |
| Best at | Quick questions and edits | One-off questions | Keeping HubSpot current |
Free for the first 10 teams.
We’re working closely with a small group of RevOps teams while Liney is in beta.
8 of 10 spots left
Free
- 100 lines a month for your account
- The sheet, with no limit
- Nothing billed during the beta
$29 per month, per rep
- Unlimited lines
- $24 per month, per rep, billed yearly
- Beta teams: 50% off the first year
- Cancel any time
Quick answers.
I read every piece of feedback myself, and there's a thumbs down under every line for when Liney gets one wrong.
PaulPaul Dalton, who built Liney · hello@liney.aiWhat counts as required?
Fields your admin sets for each stage, plus your CRM’s own required fields. Liney also suggests fields your deals usually have by then.
Does it work with our custom fields and pipelines?
Yes. Liney reads your own pipelines, stages and fields when you connect, and your team admin picks which fields reps can change.
Only deals?
Deals, contacts and companies. A line can update the ones you have, and add new contacts, companies or deals.
Does it work on a phone?
Yes. Add it to your home screen and it opens like an app.
Does it read our email or calendar?
No. It only reads the line a rep types. A meeting coming up becomes a “Send invite” task.
Anything it can’t do?
Changes made straight in your CRM don’t get Liney’s questions. And Undo takes back what a line changed or added, but not a link it made between records that were already there.
A cleaner pipeline
starts with one line.
8 of 10 beta spots leftNo setup beyond connectingNothing written without your click