BESPOKE · 10,000-100,000 THB

Work no package covers, priced against its scope

A site that looks like nothing else, or a system your staff use every day. No two are alike, so there is nothing to add to a cart here — it starts with a conversation.

The numbers

10,000-100,000
range (THB)
by scope
delivery
3 rounds
revisions included
1 year
cover after handover

What counts as bespoke

If one of these sounds like what you have, describe it and I will scope it.

  • 01

    A site nobody has built before

    The layout and the interactions are designed for this job, not a template recoloured.

  • 02

    A system your staff use

    The daily work — records, queues, reports that someone is currently keying by hand.

  • 03

    Handed over, not held

    All the code with setup notes, so your own team can take it on whenever you have one.

  • 04

    Connected to what you run

    Talks to the API or the database you already have, instead of replacing it.

Why there is no button to buy it

A fixed package can carry a price because every job inside it has the same shape. Bespoke work does not: the price comes from what has to be built, not from a page count.

How it gets priced

  • A conversation: who uses it, what for, how often
  • The scope written down, including what the price does not cover
  • A price and a date before anything starts, and no obligation if it does not fit

What to have ready

  • How the work is done today, and where it is done by hand
  • Real examples of the data or the files in use
  • The budget you have in mind, so the scope can be shaped to it

Frequently asked

Why is the range so wide?

Because the work is. A bespoke showcase site sits near the bottom; a system with several roles that talks to what you already run sits near the top. The real figure is agreed with the scope.

Can our own team take the system over later?

Yes. All the code is handed over with setup and deployment notes. Nothing is locked to me.

We are not sure what we want yet. Can we still talk?

Yes. Describing the problem is enough; most scopes come out of the first conversation rather than a document.

Describe it first, price it second

Who uses it, what for, and the budget you have in mind.

Get in touch