Jomtien Beach · Pattaya
Jomtien Network builds business websites, e-commerce platforms, web and mobile applications, AI systems, and the integrations that connect them. Tell us what the business needs to do. We define the product and the scope before anyone writes code.
Reply by email within one working day
01 — What we build
01
Marketing, service, and hospitality sites for businesses that need a customer to understand the offer and act on it. Structure, original visual direction, responsive build, content integration, and search foundations.
Multilingual where the audience needs it. Hosting, domain, and business email where the agreed scope includes them.
02
Storefronts that take real money. Catalogue and stock structure, cart and checkout, Thai and international payment methods, shipping and fulfilment rules, tax handling, customer accounts, and order operations for the people packing the boxes.
Payment provider, currency, and tax treatment are decided in discovery, not assumed.
03
Portals, dashboards, booking systems, and internal tools shaped around a workflow that already exists on paper, in a spreadsheet, or in someone's head. User roles, data model, permissions, and acceptance criteria come first.
If a well-configured off-the-shelf tool would do the job, we say so before quoting a build.
04
iOS and Android products for customers or for staff. Supported platforms, offline behaviour, backend services, device permissions, testing, and release process are defined in scope before the build starts.
Store accounts, review handling, and who owns them are settled in writing at the start, not at launch.
05
Assistants and automation grounded in your own content and data — answering from retrieved sources rather than guessing, with the cases it must refuse defined up front. Document handling, enquiry triage, drafting, and summarising.
An AI feature ships with the evaluation that shows it works, a human check on anything irreversible, and a running cost you approve first.
06
Payments, messaging, authentication, accounting, booking channels, and reporting connected through documented APIs so a record is entered once instead of three times.
Every integration depends on the other system's API terms and rate limits. Those get checked during discovery.
Underneath all six
Product care — hosting, monitoring, backups, security updates, releases, and support, under a written maintenance scope. A system nobody maintains is a system that fails quietly.
02 — Which product
Most enquiries start with a problem, not a product. Here is roughly how the problem maps to the build. It is a starting point for the conversation, not a quote.
If the problem sounds like
“Customers can't find us, or they find us and leave.”
Usually a business website — structure, proof, and a clear action. Sometimes only the content and speed need fixing, which is cheaper than a rebuild and we will tell you so.
If the problem sounds like
“We want to sell online without paying a marketplace cut.”
An e-commerce platform. The build is the easy half — payments, stock accuracy, shipping rules, and returns are what decide whether it works.
If the problem sounds like
“Bookings live in a notebook and a LINE chat.”
A web application. Staff need it on a browser, customers need one reliable way in, and both need the same source of truth.
If the problem sounds like
“Staff are on their feet, not at a desk.”
A mobile application — but only if it needs the camera, offline use, location, or notifications. If it does not, a web app on a phone costs less and updates faster.
If the problem sounds like
“We answer the same forty questions every day.”
An AI system grounded in your own documents, with an honest “I don't know” and a handover to a person. Worth doing when the volume is real and the answers are already written down somewhere.
If the problem sounds like
“The same order is typed into three systems.”
An integration. Often the cheapest project on this page and the one that saves the most hours per week.
03 — Work
Ten open-source tools built and published by the engineer behind this site. Each one checks something risky before it ships — a migration, a redirect map, a cron schedule — and each runs entirely in your own browser, uploading nothing. Source is public, so you can judge the work rather than take our word for it.
01
Reviews a Supabase migration for row-level-security holes before you merge it.
02
Finds loops, chains and HTTPS downgrades in a redirect map before it reaches a server.
03
Compares the environment variables your code reads against what each environment actually has.
04
Simulates a whole cron manifest to show jobs colliding in the same minute.
05
Checks a CSV against a typed contract before the file reaches a production importer.
06
Diffs a Docker Compose file for privileged mode, socket mounts and exposed ports.
07
Checks a Cloudflare Turnstile setup for missing server-side verification.
08
Turns secret metadata into a rotation queue, without ever reading a secret value.
09
Reviews Terraform lockfile changes without downloading or executing them.
10
Turns an open-invoice CSV into an aging ledger and a collection queue.
Client project case studies are held back until the businesses involved approve the copy, the images and the outcomes in writing.
04 — Process
Stage 01
You bring
The business problem, the current workflow, who uses it, and any deadline that is real.
You get
A written scope: product type, user roles, integrations, constraints, and what success means. Gate: you approve the scope before design starts.
Stage 02
You bring
Content, brand material, and decisions on the flows we put in front of you.
You get
Information architecture, user flows, and an interface you can click through. Gate: you approve the prototype before the build starts.
Stage 03
You bring
Accounts and access for the systems we connect to, and answers when a real edge case appears.
You get
The product built inside the approved boundary, with working software to review as it lands. Gate: acceptance against the criteria agreed in stage one.
Stage 04
You bring
A decision on the maintenance scope, and the sign-off to go live.
You get
Testing, release, monitoring, backups, and a written handover of what you own. Gate: ownership of domain, code, accounts, and data is documented, not assumed.
05 — How we work together
Value here means not paying for work you do not need. Three times on this page we point you at the cheaper answer: fix the content and the speed instead of rebuilding, use a well-configured off-the-shelf tool instead of a custom build, put a web app on a phone instead of shipping to two app stores. A budget is won or lost in those decisions, not in a headline price.
Path A
For a business that needs a clear, fast presence and knows roughly what it wants. Fixed scope, fixed set of sections, fixed price.
Path B
For e-commerce, applications, AI systems, and integrations. The estimate comes after the scope exists, because an estimate before that is a guess with a number attached.
Six questions. No price at the end — a written estimate, after a person reads it.
06 — Local
We work in the same time zone as your staff, in a market where a booking system has to handle Thai and English, low season and high season, and a payment method a European card processor has never heard of.
That context is the reason a local build is worth more than a cheaper template from somewhere that has never seen a Jomtien low season.
07 — Questions
If customers need to find you and act, a website. If staff or customers need to do something repeatedly with saved data, a web application. A mobile app only when it needs the camera, offline use, location, or push notifications — otherwise a web app on a phone is cheaper and updates faster.
Website packages have a set price, and we send the current one with its inclusions in writing. Everything else is estimated after discovery. A number given before the scope exists is a guess, and guesses are how projects end in an argument.
Yes, and we will first check whether you need one. If the structure is sound and only the content, speed, or mobile layout is failing, fixing those costs less than a rebuild.
Ownership is written into the scope document at the start of every project, covering source code, domain, hosting, store accounts, and customer data. Ask for those terms in writing before you sign anything — with us or with anyone else.
Sometimes. It is worth it when the same questions arrive in volume and the answers already exist in writing. It is not worth it when the volume is low, the answers change constantly, or a wrong answer costs you a customer. We will say which case you are in.
Yes. Both languages are written and reviewed properly, with a typeface that renders Thai correctly. We do not ship a machine-translation widget and call it bilingual.
Product care: hosting, monitoring, backups, security updates, and support under a written scope with agreed response expectations. It is a separate agreement from the build, and you can decline it.
08 — Contact
Describe the current workflow, who uses it, and the deadline if one is real. You do not need to choose the technology before contacting us.