Skip to content
GullySales
Tell us what you need

Personal branding · Technology

The hiring manager reads your code, and your peers can smell a ghostwriter.

Personal branding for a software engineer is a narrow thing.

Tell us what you needor call +91 80958 58589

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

A professional shares her expertise in a recorded interview

In one paragraph

Personal branding for a software engineer is a narrow thing. It is one hiring manager opening your repository, and an audience of other engineers who can tell when copy was written by an agency. GullySales writes and runs it from a regular conversation, and says so when you do not need it.

Also written for

Software engineer, Developer, Full-stack engineer, DevOps engineer.

Where this sits

For software engineers and developers

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

  • “The readme is the portfolio”

    A recruiter screens on keywords and the engineer taking your technical round opens the code. A project with no readme, no tests and a commit history of one enormous push has already answered their question.

  • “This audience punishes marketing in public”

    An engineer who reads a post that was clearly written by somebody else says so, in the comments, under their own name. There is no version of this that works unless the thinking is yours.

  • “What you built belongs to your employer”

    The architecture you are proudest of is the company's, and so is most of the detail that would make writing it up interesting. Your contract decides where the line sits between the general problem and their system.

  • “Many of you should not pay anybody for this”

    If you already have a repository people use and you can write a clear readme, the gap is a weekend, not an engagement. We would rather say that in the first conversation than take the money.

What we do

What we deliver for software engineers and developers.

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

  1. A profile a technical reader accepts

    Your GitHub, LinkedIn and personal page written around what you have shipped and operated: the stack, the scale, the on-call rota. No adjectives about being passionate.

    Result: A hiring manager reaches the interesting part in thirty seconds.

  2. The hour that usually starts with an outage

    The one you debugged at two in the morning, the migration you did badly the first time, or the library you gave up on and why.

    Result: Writing in your own register, from an hour you did not spend typing.

  3. One project explained properly

    A readme, an architecture note and a short piece covering the problem, the two approaches you rejected, and what broke once it was in production.

    Result: Something to send instead of a CV.

  4. Talks and the open-source trail

    A conference abstract, the meet-up talk in Bengaluru, the issues you answer and the reviews you leave, kept visible under one name rather than four handles.

    Result: Messages from people who found your answer to their problem at one in the morning.

  5. The parts that are not code

    What you are like in a review, and what you do when an estimate turns out to be wrong, written plainly, because it is the thing an interview cannot test.

    Result: Fewer rounds spent proving you are not difficult to work with.

How the result is measured

  • Enquiries that name you or came through your profile
  • Searches for your name, from Search Console
  • Profile views and connection requests from your industry
  • Speaking invitations, press enquiries and podcast requests
  • Posts published against posts planned, and what held up the rest

Recorded as a baseline before work starts, so every later report has an honest comparison.

Read the full personal branding page

How it works

How the work runs for software engineers and developers

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

    Work out whether this is even your bottleneck

    The first conversation covers how enquiries reach you today. If the company's own site is the weaker link, that comes first, and we say so.

  2. 2

    Search your own name with you

    We look at what a buyer sees today: every profile, old listing and photograph. Some of it you will want taken down, and some of it only you can take down.

  3. 3

    Agree what you will and will not say

    The subjects you know cold, the ones that belong to your clients, and the lines your regulator or association draws. Written down before anything is published.

  4. 4

    Rebuild the profiles

    The bio page, LinkedIn and the directories that matter in your field, done once and done properly.

  5. 5

    The routine

    Interview, drafts, your approval, publication. The interview is the only part that needs you, and it is the part that cannot be skipped.

  6. 6

    Hand it over

    The subject list, the drafting notes and the calendar are yours. If you would rather keep it running yourself, that is a fair outcome.

Before you hire anyone

The first thing to do yourself.

It costs nothing, and it shows what a buyer sees before they ever call you.

  1. Search your own name and your practice or business name in a private browser window, and list the first ten results.
  2. Open your profile on each major platform and check that the name, photo, description and contact details agree.
  3. Ask two people who recently chose you what they looked up first, and write down their answers.

Judge any provider

What to ask any agency or ghost-writer.

Useful whoever you choose, including us.

  • Who writes my words, and do I approve everything before it goes out?
  • Which of my own details and claims will you need to check with me before publishing?
  • What will you not write because of the rules my profession follows?
  • Whose account do the profiles and the content sit in, and what happens to them if we stop?
  • What do you count as a result, and what will you not promise?

Where this fits

Three pieces of sales work, in this order.

GullySales builds every engagement from three pieces of sales work. This page is not one of them, but the same three steps apply to the business behind it.

  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

    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.

Tell us what you need
Will you write posts as me?
We draft from the recording of your own interview, and you edit before anything goes out. If a sentence is not something you would say in a code review, cut it. Your readers write software for a living and they notice long before a recruiter would.
My employer owns my work. What am I allowed to publish?
Read your employment agreement, and the client contract on top of it if you work on client projects. Most permit writing about general technique and forbid naming systems, customers and data. We ask what is off limits at the start and keep the draft well inside it.
Is this worth paying for on a salary?
For plenty of engineers, no, and we say so. If your code is already visible, spend the money on a conference ticket instead. It is worth buying when you are moving into consulting, into a staff role decided on influence, or into a market where nobody has heard of your last employer.
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 what is being changed and how many of the people who matter see it. 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 the work touches, such as your profiles, your website or your accounts, and time with the people who can answer our questions.
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.

Technology

Personal branding for the rest of the technology.

Or start from personal branding.

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.

Tell us what you need