Contact us

The Struggle of Trying to Look Busy for Clients

by Arif Ikhsanudin, Backend Developer

You’ve just sent an update to a client and now find yourself staring at your screen, wondering what to do next.
Looking busy can feel like a full-time job on its own.

The Invisible Clock

Clients often measure effort by visible activity: emails, messages, status updates.

  • A paused Zoom call is interpreted as “offline”
  • Delayed responses feel like a red flag
  • Idle time equals suspicion

So we scramble to appear busy, even when the real work is done or waiting for client input.

The Busywork Trap

Trying to look busy leads to a cycle of pointless tasks:

  • Tidying up files that don’t need tidying
  • Writing notes you’ll never read
  • Overexplaining progress in emails

The irony? You’re working harder to look productive than actually producing results.

Mental Exhaustion

This isn’t just a time problem—it’s a mindset problem.

  • Constantly checking if the client is watching
  • Feeling guilty for moments of quiet
  • Second-guessing if what you send “looks enough”

It drains focus and creativity faster than a tight deadline.

Smart Alternatives

You can break the busywork cycle without losing trust:

  • Send concise, meaningful updates rather than hourly check-ins
  • Keep a visible progress log clients can review asynchronously
  • Batch small tasks during gaps instead of forcing activity

Quality beats quantity. Clients care about outcomes, not the illusion of nonstop effort.

Embrace Real Productivity

Looking busy is tempting, but real influence comes from actual work:

  • Deliver value consistently
  • Communicate clearly about blockers and progress
  • Trust that your client values results over appearances

Trying to look busy is exhausting—but working smart and showing results is liberating.

Scale Your Backend - Need an Experienced Backend Developer?

We provide backend engineers who join your team as contractors to help build, improve, and scale your backend systems.

We focus on clean backend design, clear documentation, and systems that remain reliable as products grow. Our goal is to strengthen your team and deliver backend systems that are easy to operate and maintain.

We work from our own development environments and support teams across US, EU, and APAC timezones. Our workflow emphasizes documentation and asynchronous collaboration to keep development efficient and focused.

  • Production Backend Experience. Experience building and maintaining backend systems, APIs, and databases used in production.
  • Scalable Architecture. Design backend systems that stay reliable as your product and traffic grow.
  • Contractor Friendly. Flexible engagement for short projects, long-term support, or extra help during releases.
  • Focus on Backend Reliability. Improve API performance, database stability, and overall backend reliability.
  • Documentation-Driven Development. Development guided by clear documentation so teams stay aligned and work efficiently.
  • Domain-Driven Design. Design backend systems around real business processes and product needs.

Tell us about your project

Say Hej

Our offices

  • Copenhagen
    1 Carlsberg Gate
    1260, København, Denmark
  • Magelang
    12 Jalan Bligo
    56485, Magelang, Indonesia

More articles

Stop Creating Branches You Never Clean Up

Stale branches are not just clutter — they create confusion about what is active work, slow down tab-completion, and make it harder to understand the state of the repository at a glance.

Read more

Hiring a Senior Backend Developer in Singapore Takes 9 Weeks and S$120K — There Is a Better Way

Nine weeks ago you posted the job. Today you have two maybes, one lowball counteroffer, and a product launch that can't wait any longer.

Read more

Eventual Consistency: The Trade-off You Make When You Scale

Eventual consistency is a specific, well-defined trade-off — not a vague guarantee. Understanding what you are actually agreeing to when you accept it prevents a category of bugs that are hard to find and harder to fix.

Read more

You Don't Have to Migrate Everything at Once

Incremental monolith decomposition — extracting one service at a time while keeping the monolith operational — delivers value earlier, reduces risk, and lets you stop when the architecture is good enough rather than when the plan says you are done.

Read more