Skip to content

UI/UX design companies · Buyer persona

Know if your portfolio reader is a founder, a product head or a developer.

A buyer persona for a UI/UX design company describes the people who hire a design team, what each needs to see, and what worries them before signing. GullySales works on the written profiles of your three or four real buyers, based on your past enquiries and conversations with your own clients.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Realistic editorial illustration of software development companies at work in India

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.

Last updated 18 Oct 2026.

For UI/UX design companies

Where it usually goes wrong, and what we would do.

  • “The founder wants an answer to a business problem”

    A first-time founder with a thin budget asks whether the app will keep users. Talk of design systems and component libraries does not reach them. They need to hear what a sprint will tell them before they spend on a full build.

  • “The product head is judging process and risk”

    A product manager at a larger firm asks how designers work with their team, how research is shared and what happens to the files. Their worry is a vendor that disappears after delivery or produces work developers cannot build.

  • “The developer lead has a veto without a title”

    The person who will build the design reads the files and the handover. A design that ignores platform limits makes them an opponent. Showing them how components and specifications are passed on wins an ally inside the buyer's company.

  • “The approver in a bank or insurer is different again”

    A digital head in a regulated firm works through committees and cares about accessibility, language and approvals. The material that suits a start-up founder will not satisfy them, so the proof and the tone need to change.

What we do

What we deliver for UI/UX design companies.

Every deliverable, what it covers for you, and the result it is there to produce. Nothing here is an extra.

  1. Buyer profiles

    One page each for the founder, the product head, the developer lead and the corporate approver, covering goals, doubts and what they check first.

    Result: Profiles you can hand to anyone writing for you.

  2. Past-enquiry review

    A reading of your last enquiries to see who wrote in, what they asked and which ones became sprints.

    Result: A list of patterns drawn from your own enquiries.

  3. Objection list per buyer

    The concerns each persona raises, such as price against a freelancer or fear of handover, with the answer you give.

    Result: A reference for calls and written proposals.

  4. Proof map

    Which case study, sample or page answers which persona's first question.

    Result: A guide on what to send to whom.

  5. Interview questions for clients

    A short set of questions to ask recent clients about how they found and chose you.

    Result: Evidence from real buyers in place of assumptions.

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

Know who opens the portfolio, because a founder, a product head and a developer each look for something different.

Founder choosing a first design partner
Wants to see the studio has built an app like theirs and asks who will actually work on it.
Product head in a scaled company
Wants a process they can fit into existing sprints and a studio that works with their developers and their design system.
Developer lead asked to find a studio
Looks at the handoff: specs, states and how design questions are answered during the build.
Marketing head commissioning a website
Wants a studio that understands the brand and the landing page, and a way to test the result.
Procurement or finance contact
Asks for scope, the contract form and the payment stages before anyone else sees the portfolio.

Who it is for

This is written for these UI/UX design companies.

  • Product design studios for start-ups
  • Mobile app design specialists
  • Enterprise and SaaS dashboard design firms
  • Design system and component library builders
  • UX research and usability testing consultancies
  • Website and landing page design studios
  • Service design firms for banks and public bodies
  • Product design teams embedded with a client by the month

Not for

It is not the right fit if.

  • You have not interviewed any past client, so personas would repeat what the studio assumes about founders.
  • You get a few enquiries a year, all through referral, and the person who referred already told you who decides.
  • You hope a persona will set your fee, but fee pressure comes from freelancers and overseas studios, not from buyer type.

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. 1

    Understand the current view

    We start with how your team currently describes the customer, since the gap between belief and reality is the finding itself.

  2. 2

    Audit past enquiries and sales

    We look at recent enquiries and closed deals to see who actually bought, not who was assumed to buy.

  3. 3

    Interview customers and staff

    Structured conversations with recent buyers, held as talk about the last purchase and not a questionnaire. We ask what happened before they called, who else was involved and what they compared. Customers agree before we contact them, and their answers are reported without names.

  4. 4

    Build the personas

    Findings are written into short, usable persona documents rather than a long report.

  5. 5

    Apply to your marketing

    We show where each persona should change a page, an ad or a script you already have. The sales team reads the drafts and says which ring true. A persona they do not recognise is rewritten.

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.

  1. 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.

  2. 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.

  3. 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.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Do we need a persona if we only get a few enquiries?
Yes, and a small number helps. A handful of enquiries is enough to see who writes in and who signs. The profiles can then be adjusted as you speak to more clients.
Can one persona cover founders and product heads?
Rarely. Their budgets, doubts and ways of deciding differ. Keep them as separate profiles and use the same case studies framed for each.
Can one persona cover founders and product heads?
No. A founder wants to see the studio understands the idea; a product head wants to see a process that fits a running team. They read the same portfolio for different reasons, so their pages and the first call should differ.
Do we need a persona if we only get a few enquiries?
A short one, yes. With few enquiries each loss matters more, so write down who asked, who decided and what they asked before signing. A page of notes from the last enquiries is enough to change the first call, and it grows as more arrive.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.
What do you need from us?
Your brief, and a conversation. After that, access to whatever this work touches, such as your website, your accounts or your enquiry record, and time with the people who handle your enquiries.
What if we are not happy with the work?
Tell us and the plan changes. Everything is reported against the baseline, so a number that is not moving is visible to both sides. The term is in your written scope, and the refund and cancellation policy sets out the rest.

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.