Engagement model

Our engagements are project-based. You bring a concrete database concern—migration risk, runaway reporting queries, or a schema that no longer matches how the product stores data—and we agree on scope, timeline, and fees before billable work starts.

Intake and boundaries

The first step is a short call or email thread to confirm engine version, approximate data volume, and whether we can work against staging. We document assumptions about read-only access, change windows, and who owns backups. If the problem sits outside relational design (for example, pure front-end performance), we say so early.

Assessment projects

A technical assessment typically includes execution-plan review for your heaviest queries, an entity-relationship walkthrough, and a written memo with prioritized recommendations. You receive SQL examples or migration sketches where they help your team implement fixes internally.

Implementation support

When you want hands-on help, we join your repository or migration tooling for a bounded number of days. Tasks might include index rollout scripts, query rewrites, or pairing with your ORM layer. We time-box the work so you always know when the engagement ends.

Advisory retainers

Some teams keep a lightweight advisory slot for monthly schema reviews or release gate checks. Retainers are month-to-month with hours capped; unused hours do not roll over unless we agree otherwise in writing.

Fees and invoicing

Fees are quoted in THB after scope is defined. Invoices are issued to the legal entity named in our agreement. Payment terms are stated on each invoice; we do not publish fixed price lists because every workload differs.

Next step

Read the contact page to share your schema context, or call our Bangkok line if you prefer to talk through urgency and access constraints first.