Skip to main content
All articles

How to Write About Your Work Without Bragging

Ben Van AkenCo-Founder & CTO6 min read

A lot of small business owners in Flanders and across Belgium freeze when they sit down to post about their own work. The job went well. The customer was happy. And still the draft sounds wrong: too proud, too salesy, or like you are talking about yourself in a room where nobody asked.

The fix is not to stay quiet. It is to change what the post is about.

Useful posts about your work are not a speech about how good you are. They are a clear look at a real job, a real problem, or a real choice. When you aim at that, the bragging feeling usually drops away.

Start with the problem, not with you

Open with the situation the customer faced, not with your role in fixing it.

Compare:

  • “We delivered another great kitchen renovation this week.”
  • “This kitchen had a narrow layout and almost no natural light. The owners wanted more workspace without knocking through a wall.”

The second line is about the work. You are in the story later, as the person who did the job, not as the headline.

The same shift works for services that leave little to photograph. An accountant can open with the month-end mess a new client brought in. A bookkeeper can open with the receipt pile that sat beside the bank feed. A consultant can open with the decision the owner kept putting off. You still show up in the post. You just are not the opening act.

Show the process, not the trophy

A finished result without context can read like a flex. The steps that got you there read like craft.

Useful process details to share:

  • What you checked first, and why
  • A constraint that shaped the plan (budget, space, timing, regulations, a tool the customer already had)
  • A trade-off you explained, and which option they chose
  • One thing you would do differently next time on a similar job

Three short beats are often enough: what we found, what we decided, what that meant for the result. A short note on why the sink moved 40 centimetres often helps a future customer more than a polished trophy shot.

Be specific about what you did

Vague praise sounds like marketing. Concrete detail sounds like a job report.

Instead of “a beautiful result” or “another happy customer”, name the thing you actually changed: which wall came down and what that freed up, which report you rebuilt and what decision it made easier, which part of the process you simplified and for whom.

Specifics prove you were there, and they help the right reader think, “that is my situation.” Soft adjectives do neither. If a detail feels too technical, keep one plain sentence that translates it. “We moved the boiler so the cupboard could open fully” lands better than a list of product codes.

Credit the customer’s problem, not your cleverness

A post can still mention a clever fix. Frame it as a response to their constraint, not as proof that you are impressive.

“We came up with a smart solution” puts the spotlight on you. “The hallway was too narrow for a standard unit, so we built one to fit” puts the spotlight on the constraint. You still did the clever thing. The reader sees the problem first.

When you want to share a win, lead with what improved for them: fewer steps, less waste, a cleaner handoff, a clearer quote. Your method sits behind that outcome. People remember the relief more than the method name.

Let the work speak, then add one line of context

Photos, screenshots, short clips and before-and-after shots carry a lot of the weight. Your caption does not need to sell on top of them.

A useful pattern:

  1. Show the work.
  2. Add one sentence about the starting problem.
  3. Add one sentence about the choice you made.
  4. Stop.

Extra praise lines (“stunning”, “incredible team”, “couldn’t be happier with ourselves”) are where posts tip into bragging. If the image already shows the result, leave the applause out. When there is no strong visual, a short numbered list of what changed still works. Keep the voice factual, as if you are briefing a colleague.

Phrases that tip into bragging, and plain swaps

A few common openers are worth rewriting:

  • “Proud to announce…” → say what shipped, for whom, and what it solves
  • “Another successful project…” → name the project type and the constraint you worked around
  • “Our clients love…” → show a specific outcome, or skip the claim and show the work
  • “Best in class / market-leading…” → drop the label; describe what you do instead
  • “We crushed it…” → say what finished, and what the customer can do now

Warmth is fine. Self-congratulation is not. “Glad this one is in place” works. “We are the go-to experts for…” is the line that makes a sceptical owner close the tab.

Write as if a peer is reading

Before you publish, ask: would I send this to a fellow owner down the road, or would I feel awkward forwarding it? If it would feel awkward, trim the self-praise and add one concrete detail. Reading the draft out loud also helps: keep the lines that sound like you on a site visit, not like a brochure.

If someone else writes your posts

Handing the writing to a colleague, a freelancer or an agency does not remove the bragging risk. It can raise it, because the writer wants to make you look good and reaches for praise by default.

Give them raw material from the job: the customer’s starting problem, the constraint, the choice you made, and one photo or note from the work itself. Ask them to draft in that order. Your approval step is where you cut anything that sounds like a brochure. A short weekly note with two or three real jobs is often more useful than a long brand document full of adjectives.

Where Swiftly Marketing fits

If the awkward part is not the ideas but the weekly habit of turning real jobs into plain posts, that is the gap we fill: one post a day on the platform you choose, written from your everyday work, and you approve each one before it goes out. You stay the one who decides what is said in your name. We help you keep the feed useful without turning it into a sales pitch about yourself.

Pricing: one post a day

The short version

  • Open with the customer’s problem, not with your role.
  • Show a little of the process, not only the finished trophy.
  • Prefer concrete detail over soft praise.
  • Frame clever fixes as responses to constraints.
  • Let images and facts carry the weight; cut the self-applause.
  • If someone else writes for you, hand over raw job notes and cut brochure language on approval.

What job did you finish this week that you have not written about yet? Start with the problem it solved, and stop before the praise.

Comments

Loading comments…

One post a day, from the real job

Written from your everyday work. You approve each one before it goes out.

Book Your Free Intro Call →

15 minutes · No commitment · Talk to a real human