Legal technology companies · Buyer persona
Describe the partner, the junior and the counsel as three different buyers.
A buyer persona for a legal technology company is a written profile of each person who influences the sale: the one who approves, the one who uses and the one who checks security. GullySales works from your sales calls and trial records to describe what each person worries about and which question decides them.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What buyer persona means
A buyer persona is a plain description of the kind of customer who actually buys from you. It includes what they search, what worries them and who else they ask before deciding. GullySales builds this from real enquiries and past sales rather than a generic template, then uses it to write every page and advert.
Also for legal technology companies
- Digital marketing for legal tech companies
- Lead generation for legal tech companies
- SEO for legal tech companies
- Social media marketing for legal tech companies
- Content marketing for legal tech companies
- CRM for legal tech companies
- Follow-up systems for legal tech companies
- WhatsApp marketing for legal tech companies
Sales and marketing for legal technology companies, the overview.
Last updated 14 Nov 2026.
For legal technology companies
Where it usually goes wrong, and what we would do.
“The approver rarely opens the product”
A managing partner decides on a colleague's word and a short demo. They ask about confidentiality, cost per seat and whether the juniors will cope. Give them a one-page answer, because they will not sit through a feature tour.
“The user has no power but can end the deal”
A junior who finds the product slow or hard will stop using it, and the partner will not renew. The persona for the user should list the working jobs the product must make easier, such as entering a next date in a few steps.
“The in-house buyer has a process”
A general counsel's team works through IT, procurement and sometimes finance. Their persona includes the questions in the order they ask them, and the pilot they need before a contract.
“The channel adviser is a persona too”
A bar association officer, a law college teacher or a compliance consultant gets asked which software to use. Their need is a short, honest summary they can repeat without risk to their name.
What we do
What we deliver for legal technology companies.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
Persona sheets by role
One sheet each for the managing partner, the junior user, the in-house counsel and the IT reviewer.
Result: Each sheet names the worry, the deciding question and the proof wanted.
A buyer map by segment
A chart linking each segment to the roles involved and the order in which they join the decision.
Result: The sales team sees who to reach after the first contact.
Objection and answer pairs
The doubts raised by each role, matched to a plain answer and the page that holds it.
Result: A rep can answer any doubt with a link.
A call-note template
A short format to record role, problem, forum and next step after each sales call.
Result: Persona sheets are updated from real calls.
A message guide per persona
Wording notes for emails and pages aimed at each role.
Result: No page speaks to the partner and the junior in one voice.
How the result is measured
- Enquiry match to persona
- Conversion rate by persona
- Content aligned to persona
Recorded as a baseline before work starts, so every later report has an honest comparison.
Who is asking
Write down who asks about your product and what they need first.
- Managing partner of a mid-size firm
- Wants to know about data safety, cost per seat and whether the juniors will use it. Give a security note and a plan for onboarding the team.
- Junior associate who found the tool
- Wants to know if it saves time on the diary and drafts. Give a sandbox with sample matters, and a one-page summary to forward to the partner.
- Solo advocate in a district court
- Wants a diary that works on a phone and costs little. Show hearing reminders and cause list entries, and say which courts are supported.
- General counsel of a company
- Wants intake, approvals and a record of who signed what. Offer a walk-through of the workflow and answers to the company's vendor checklist.
- Legal operations or IT head
- Wants hosting details, access control and export. Have an answer sheet ready, since this reader decides whether the purchase proceeds.
- Paralegal or clerk who handles the file
- Wants to know how stamping, filing and reminders happen daily. A short guide in plain words wins this person, who is the daily user in the firm.
Who it is for
This is written for these legal technology companies.
- Case management and practice management software
- Legal research and judgment search platforms
- Contract lifecycle and contract review tools
- E-signing and stamping platforms
- Compliance and regulatory tracking software
- Court and cause list tracking tools
- Legal document automation tools
- Legal marketplaces and lawyer-discovery platforms
Before you decide
When this may not be the right fit.
- You have not yet spoken to ten buyers, so the personas would be guesses written to look like findings.
- Your product serves only one role in practice, so splitting it into several personas would add paperwork and no insight.
- You plan to use the sheet only as a poster, when its value comes from changing what the sales calls say.
Before you decide
Agree the work. Know how to judge it.
Buyer persona for legal tech companies: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
Write the decision the research must support, such as entering a market or choosing a buyer group. Separate what you know from sales records from what the team currently assumes.
Make the scope clear
Agree which buyers to speak to, which sources to review, and what access you can provide. Include lost enquiries and people who chose another supplier, where they are willing to take part.
Check the work in use
Look for source dates, sample limitations, and evidence that disagrees with the preferred answer. A recommendation should show how it follows from the findings.
Know when to change course
Do not treat a few positive conversations as proof of demand. Test the proposed offer with an actual buying decision before committing to a wider launch.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from legal technology companies. Anything missing is noted in the written scope, with who will supply it.
- Notes from lost and won deals
- Any written reason for a lost or won deal, however short, helps us see who mattered. A spreadsheet or the CRM export is enough. Without it, the sheets rely on sales memory, which favours the latest and the pleasantest deals.
- Introductions to three customers
- Three customers who agree to a conversation: a buyer, a user and, if possible, one who stopped. You make the introductions. If none agrees, we build the sheets from calls alone and label them as unconfirmed by customers.
- Recordings or notes of trial sessions
- How a junior behaves in the first session tells us who the product really serves. Notes will do. If no records exist, we ask the sales team to take them for the next trials, and the sheets are marked as first drafts.
- The security and procurement path
- A description of how in-house teams reached the decision: who ran the questionnaire, who asked for references, who signed. If it has not been written down, we reconstruct it from emails, and the in-house sheet stays short.
- The sales lead for a role-play
- The person who runs demos must test the objection answers aloud. An answer that reads well can still fail on a call. If this person is absent, the answers stay untested and may break at the first difficult question.
How it works
How the buyer persona work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Choose the roles that touch a sale
We start from your last deals, won and lost, and list every role that spoke: the managing partner who signed, the junior who used the trial, the IT reviewer, the adviser who recommended you. You tell us which roles you meet in each segment, and we agree how many persona sheets are worth writing before any interview is booked.
- 2
Pick the records and customers to read
We ask for call notes, trial logs, lost-deal reasons and a few customers willing to talk. We prefer a mix: a firm that bought, one that stopped using the product and one that never started. You choose the customers and make the introductions, because a lawyer will not talk to a stranger who has not been introduced.
- 3
Interview the user and the approver separately
We speak to the associate who ran the trial and to the partner or counsel who approved it, in separate conversations. We ask how they found you, what they feared, what the product replaced and who they asked. You listen to the recordings with us, so you hear the exact words each role used.
- 4
Check each finding against deal records
Every statement on a persona sheet must be traced to an interview or a record. A claim that the approver never opens the product, for instance, is checked against trial logs. You correct what is wrong, and we drop what cannot be shown, so the sheets rest on evidence and not on assumption.
- 5
Pair objections with answers your team can give
For each persona we write the objections heard, such as where the data sits or whether the juniors will use it, with an answer that your product can honestly support. You and the sales lead test the answers in a role-play, and any that sounds like a promise of accuracy is rewritten.
- 6
Compare later calls with the first sheets
After the team has used the sheets, we read new call notes and trial records against them and note where a persona was wrong or missing. You decide what to change, and the call-note template carries the revised fields forward, so the next set of sales calls adds to the record.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 0, foundation. The audit comes before it, and sales management keeps it running.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2 · you are here
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
How many personas do we need?
Where do the details come from?
What if our buyers differ by city or court?
How do we handle the lawyer who dislikes technology?
Do we need a separate persona for the advocate who dislikes technology?
Who in our team should own the persona sheets?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for legal technology companies
Related work to consider.
Closest to this: strategy and research
Also for legal technology companies
Or start from the overview: sales and marketing for legal technology companies.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.