Custom software development for Thai organisations
We design and build web, mobile and enterprise systems around the way your organisation works, and integrate them with the systems you already run. One team takes it from design to go-live, with working software to review every few weeks.
Services in this pillar
Each service has its own page with scope, approach and buyer questions.
Web Application Development
Browser-based internal systems, customer portals and back offices, built around how your staff and customers work.
Mobile Application Development
iOS and Android apps built in Flutter from one codebase and connected to your existing systems.
Enterprise Software Development
Internal systems for multi-step workflows, approvals and audit trails across departments, built to run for years.
System Integration & API Development
APIs and interfaces that move data between your systems and partners, with monitoring that shows when something stops.
How the four services fit together
Many projects here use more than one of these services. A customer portal is a web application, but it usually has to exchange data with an ERP or an identity provider, and staff in the field may need a mobile app. We plan these as one project with one team, so the interfaces are designed at the same time as the screens.
Finished examples include the wholesale ordering platform for MEMO Clothing, the PDMO's public debt management system, where we were part of the delivery team, and GMMTV's e-book apps. If you are still deciding whether to build at all, Solution Architecture is the usual first step.
What buyers ask us before starting a build
How do we know whether to build or buy?
List every place where the closest off-the-shelf product does not fit how you work, then price what it would take to close those gaps: integrations, process changes, workarounds and the yearly cost of keeping them. If that total is well below the cost of building, buy the product. We can work through the comparison with you, and sometimes the result is that you do not need us.
Who owns the code and the intellectual property?
You do, from the first commit. That covers the source repository, the deployment pipeline, infrastructure definitions and documentation. We aim to leave every project in a state where your own team, or another vendor, could take it over.
Can you take over a system another vendor built?
Usually, yes. We start by reviewing the code, the tests, the deployment process and the documentation, and we tell you what we find, including when a rebuild would cost less than repairing what is there. The first few weeks are slower while we learn the system, and the estimate includes that time.
What happens if we bring development in-house later?
We plan for it from the start. Documentation and infrastructure as code are kept up to date during the project, and we run knowledge transfer sessions with your developers while the work is still active. Moving development in-house is a normal way for an engagement to end.
Next step
Start with a conversation
Tell us about the problem you are trying to solve. A senior person reads every inquiry and replies with our view of fit, scope and cost, including when another option would suit you better.