From Social Post to Signed Contract, in One Chat
With Pacten connected to Claude or ChatGPT, one conversation can take a client from a social post to a signed contract and an invoice. You ask in plain words, Pacten prepares each step and shows you exactly what will happen, and nothing is scheduled, booked or sent until you say yes. Here is one week, step by step.
Meet the agency
Juniper & Row is a four-person brand studio in Dublin. Aoife runs it. She keeps Claude open all day for writing, and Pacten connected to it for everything else. The client in this story, Okafor Logistics, is fictional, and so is everyone at it.
Each step below shows three things: what Aoife types, what Pacten prepares, and her yes.
Monday: design Thursday's post and schedule it
Aoife wants to share a recent project, a rebrand for a family bakery.
She types: "Design Thursday's post for Instagram and LinkedIn about the bakery rebrand: three images, before and after, and a short caption. Schedule it for 9 AM."
Claude writes the caption and designs the images. Pacten prepares: schedule "Bakery rebrand, start to finish" to Instagram and LinkedIn for Thursday at 9:00, Dublin time, with the caption and images shown.
She says yes. Pacten schedules it. Nothing goes out on the spot: the post waits for Thursday at 9.
Two details worth knowing. If someone on the team cannot approve posts, their post waits for a teammate who can, then goes out at its time. And if a channel is not connected, the preview says so and leaves it out, rather than failing on Thursday morning. More on running a calendar like this in our guide to building a social media content calendar.
Thursday: a lead replies
By lunchtime, Tomás, the marketing lead at Okafor Logistics, has messaged on Instagram. Their brand looks tired before a big trade fair.
She types: "Add Tomás Reyes from Okafor Logistics as a lead. He came from Instagram. Here's his email. Note: wants a brand refresh before their spring trade fair."
Pacten prepares: add Tomás Reyes as a new lead, with his email, his company, Instagram as the source, the stage New, and the note.
She says yes. Tomás is in the CRM, in the leads inbox, with the note for the team. Had he already been a client, Pacten would have said so and pointed to his existing record instead of adding him twice.
Thursday: book the discovery call
She types: "Book a 30-minute video call with Tomás next Tuesday at 10, and invite Cian."
Pacten prepares: book "Discovery call" in Meeting Hub on Tuesday at 10:00, Dublin time, with Tomás and Cian, by video.
She says yes. Pacten sends the invite. If Tuesday at 10 had clashed with something in Aoife's or Cian's calendar, Pacten would have asked first. It never books on a guess.
Tuesday: write the proposal
After the call, Aoife pastes her notes into the chat.
She types: "Write a proposal for Okafor Logistics from these notes: a brand refresh in three phases, with a price table."
Pacten prepares: write "Okafor Logistics brand refresh" in Doc Hub, with the text and the table shown.
She says yes. The proposal is saved in Doc Hub as a draft for the team. It is shared with nobody yet, so Aoife reads it and tightens a paragraph in Pacten first.
Tuesday: send it, with a note
She types: "Send the Okafor proposal to Tomás, with a note: here's what we discussed, happy to walk you through it on Friday."
Pacten prepares: send "Okafor Logistics brand refresh" to Tomás Reyes, naming his address, the subject and the note.
She says yes. Tomás gets an email with his own link to read the proposal and respond, and Aoife can see when he opens it. If anyone had edited the proposal between the preview and her yes, Pacten would have stopped and asked her to prepare it again, so what Tomás reads is what she approved.
Friday: turn it into a contract and send it for signature
Tomás says yes on Friday's call. Aoife asks Claude to write the services agreement from the proposal, which Pacten saves in Doc Hub the same way. Then:
She types: "Make the Okafor agreement into a contract."
Pacten prepares: make "Okafor Logistics services agreement" into a draft contract. Pacten reads the value, dates and governing law the text states, for Aoife to check. Nobody is asked to sign yet.
She says yes, and checks the terms in Pacten.
She types: "Send it to Tomás for signature, with a short note."
Pacten prepares: send it for signature, naming every signer and the address each link goes to. The agreement is frozen as it reads now.
She says yes. Each signer who has not signed yet gets an email with their own signing link. The links never come back into the chat, and Aoife can ask Claude at any time who still has to sign.
The following week: invoice and the pay link
She types: "Draft the invoice for phase one of the Okafor brand refresh, due in 14 days."
Pacten prepares: a draft invoice to Okafor Logistics, with the lines, the tax, the total, the currency and the due date. The workspace's currency is euros, so the invoice is in euros unless Aoife names another one.
She says yes. The draft is saved in Finance. Nothing is sent.
She types: "Send it."
Pacten prepares: email the invoice to Tomás, showing the amount, the subject, and what he gets: the invoice, what it is for, the due date, a pay link and how to pay.
She says yes. The invoice is issued and emailed. A week later Aoife asks, "Has Okafor paid?" Claude checks Finance and answers, with the client's pay link while money is owed and the receipt link once it is paid. Invoices only go out once a way to be paid is set up in Finance. For more on keeping this in one place, see how to keep track of clients, bookings and invoices.
What you still do yourself
- You say yes to every step. Each preview names who, what and when. Nothing happens until you confirm, and every change is logged "via Claude".
- You sign. If you are a signer, your link arrives by email like anyone else's, and you sign it yourself.
- Money moves only when your client pays the link. The connector can prepare invoices and reminders. It cannot take or move money.
- Your accountant still files. Pacten keeps the day-to-day books and sits alongside your accounting software for tax returns.
- You read before you send. The proposal and the agreement are yours to edit in Pacten before anything goes out.
Want to try this week yourself? See what the connector can do on the Pacten MCP page, then follow the setup guide. It takes about two minutes.
Frequently asked questions
- Does this work in ChatGPT as well as Claude?
- Yes. The same Pacten tools work in Claude and in ChatGPT. Each person connects with their own Pacten sign-in, and sees only what their role allows in Pacten.
- Does my client know I used Claude?
- The emails your client receives are the ones Pacten sends when you use the app: the meeting invite, the proposal link, the signing link and the invoice. Inside your workspace, each change is marked "via Claude" so your team knows how it was done.
- What happens if Claude gets a detail wrong?
- You see it in the preview first. If a name, date, amount or address is wrong, say no, tell Claude the right detail, and Pacten prepares it again.
- Does scheduling a post publish it straight away?
- No. Pacten schedules it for the date and time you gave, in your workspace's time zone. If you cannot approve posts in your workspace, it waits for a teammate who can.
- Can it sign the contract or take the payment for me?
- No. Signing links go only to the signers by email, and money only moves when your client pays the link on the invoice.