About Service Stonebase

Why we exist

Service Stonebase started when client work kept exposing the same gap: capable engineers, earnest Scrum rituals, and still a delivery rhythm that buckled whenever a Thai agency juggled three overseas stakeholders at once. Coaching that only recited textbook agile did not help. Hands-on programming consulting paired with facilitation craft did.

How we work with teams

We sit in the ceremonies, read the board history, and talk to the people who escalate at 10 p.m. Advice stays concrete: change this planning agenda, cut that WIP column, rewrite the definition of ready so client briefs stop arriving as half-stories. When we leave, the working agreements should still make sense without us.

Thailand context

Our office sits in Pattaya — close enough for Bangkok day trips, quiet enough for intensives that need a room without the usual office interruptions. Many of our engagements mix on-site days with remote coaching for engineers based elsewhere in Southeast Asia.

Values we hold

• Say the awkward thing early. Soft retrospectives that avoid naming the real blocker waste everyone’s calendar.
• Respect the client reality. Service teams do not control every brief; coaching must account for late scope and translation gaps.
• Leave artefacts people will use. Short working agreements beat ninety-page playbooks nobody opens.

Credentials, plainly

Our coaches bring years of delivery leadership inside software service organisations, plus facilitation practice earned running planning rooms and difficult retros — not a wall of logos. When a credential matters for your procurement process, we share it during intake.