Contact us

Handling Clients Who Think You’re a 24/7 Developer

by Arif Ikhsanudin, Backend Developer

It starts with a “quick message” at night.
Then suddenly, you’re expected to reply at 2 AM like it’s normal.

Spot the Pattern Early

It rarely begins as a big problem. It creeps in slowly:

  • Late-night messages “just this once.”
  • Weekend pings that feel urgent but aren’t.
  • Expectations of instant replies, regardless of time zone.

If you don’t set limits early, the client will set them for you.

Set Clear Availability

You don’t need to be available all the time to be professional:

  • Define your working hours clearly from the start.
  • Share your time zone and response window.
  • Use simple language like: “I’ll respond during business hours.”

Clarity removes guesswork—and prevents resentment later.

Don’t Reward Bad Timing

This is where many people accidentally create the problem:

  • Replying instantly at midnight trains the client to expect it again.
  • Fixing non-urgent issues on weekends sets a new “normal.”
  • Being too flexible early makes boundaries harder to enforce later.

Consistency matters more than occasional flexibility.

Create a System for Urgency

Not everything is urgent, but some things truly are:

  • Define what counts as an emergency.
  • Offer a separate channel or agreement for critical issues.
  • Consider charging extra for after-hours support if needed.

Structure helps separate real urgency from convenience.

Stay Firm, Stay Polite

Pushing back doesn’t have to feel confrontational:

  • Acknowledge messages without solving immediately: “Got it, I’ll check this tomorrow.”
  • Repeat your boundaries calmly if needed.
  • Avoid over-explaining—simple and clear works best.

Professional boundaries build respect, not conflict.

Closing Thought

Being available 24/7 isn’t a sign of dedication—it’s a fast track to burnout.
Protect your time, set expectations early, and teach clients how to work with you—not the other way around.

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

When the Client Forgets to Pay You (or Pretends They Did)

It’s awkward, frustrating, and more common than you think. Handling unpaid invoices gracefully can save relationships—and your sanity.

Read more

The Decorator Pattern in Ruby — Clean Code Without the Bloat

Decorators solve the problem of adding behavior to objects without subclassing, but Ruby gives you several ways to implement them — each with different tradeoffs around interface fidelity, performance, and testability.

Read more

Spring Boot and Message Queues — RabbitMQ, Kafka, and Choosing Between Them

RabbitMQ and Kafka both move messages between services, but they solve different problems. RabbitMQ routes messages to consumers. Kafka retains an ordered log that consumers read at their own pace. The choice determines your system's capabilities and constraints.

Read more

Why Your Git Workflow Is Slowing Your Team Down

Most teams blame slow delivery on unclear requirements or code complexity. The actual bottleneck is often the Git workflow — specifically the conventions around branching, reviews, and merging that nobody thought through when the team was two people.

Read more