A deal assistant embarrasses you by inventing: a headcount nobody recorded, a budget nobody mentioned, a close date drawn from nowhere. This template restricts every fact to the Pipedrive record and the deals it searched, and marks anything absent as unknown. Codex works well on bounded record-to-record tasks where the boundaries are stated this explicitly.
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Ingrid Halvorsen
Nordvik Marine AS, fleet maintenance rollout for 45 vessels
EmailDeal #4821, New Business pipeline
NoteDeal created from the website demo form and assigned to Ingrid. Organization Nordvik Marine AS, Bergen, 340 employees, coastal freight. Value 62,000 EUR annually, stage Qualified, source Website Demo Request. Contact Ola Sandnes, Head of Fleet Operations, ola.sandnes@nordvikmarine.no. The form notes say maintenance for 45 vessels currently runs in three spreadsheets, they failed a safety audit in June, and they want to be live before the winter charter season starts on 1 November.
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Pipedrive
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Deal playbook
How you work a new deal - the first activity you book for each deal size or source, how fast it has to happen, and what your note needs to tell a rep before they call. The agent books and writes from this and nothing else.
Handoff rules
The deals you never want worked automatically - the values, accounts, sources, or wording in a deal that mean a person should pick it up before anything is booked.
Runs on Codex
Preselected for this page — connect your Codex account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
The note has a What is missing half precisely so gaps get recorded rather than filled. That structure suits a literal harness.
One read, one search, one note, one activity, one Slack line. Short concrete sequences are where this harness is fastest.
No, because value, stage, pipeline, owner and probability are all off limits and the template wires in only note and activity creation. If a field looks wrong it says so in the note and leaves the field alone. Your reporting sees a new activity and a note, nothing more.
Free to start. Guided setup, a test run against staged conversations, and it's live.