Applications & Portals
Custom web applications, iOS and Android apps, portals and the internal systems behind them, built around how your organisation already works, with the code and the accounts in your name.
The problem, in your words.
Our whole operation runs on one shared spreadsheet that five people edit at once, and every Monday somebody spends the morning fixing what broke over the weekend.
Customers email to ask where their application has got to, and the only honest answer is: let me find out who has the file.
We paid an agency for an app a few years ago. It still works, mostly, but we never got the code and the agency has stopped replying.
Built in the Philippines
Our Philippines team in Iloilo builds applications for local government units, agencies and community organisations, including work that has to run where the signal does not. The Western Visayas Investment Guide mobile app was developed with NEDA Region VI and launched by the DEPDev Region VI Council. Quotes are given in pesos, and the code is yours.
This is the page for the thing you actually want built. Custom web applications, iOS and Android apps, and the portals your customers, the public, volunteers or staff log into, each with roles that decide who can see and change what. Behind them sit the systems nobody photographs: case management, booking and registration flows, CRMs and registries, dashboards and reporting, and the integrations that stop your team copying data from one screen to another. When an old system is holding everyone back, we replace it and move the data across.
Some of what that has meant in practice: a crowdfunding platform with one-to-one gift matching for a uniformed youth organisation, a multilingual helpline app for migrant workers, and a hotline, case management and caregiver app for a dementia care organisation. In the Philippines we built a delegate app for a national youth jamboree of about 40,000 delegates and an investment guide app for a regional planning agency, both made to keep working on a weak signal. We also make our own products: Certainty, a help desk with tickets, tasks, chat, meetings, a client portal and its own MCP server, and JoinNests, which runs registration, committee approvals, renewals and e-certificates for associations. Our DuitNow QR and PayNow QR libraries are open source.
A typical engagement starts with a free conversation and a look at whatever you use today, spreadsheets and WhatsApp groups included. We write down what the first release must do and, just as usefully, what it will not do yet. Then we build in short cycles and show you working screens every week or two, so the people who will use it every day can tell us what is wrong while it is still cheap to change. The scope says how long the first release takes; small internal tools are short, portals with several roles, payments and integrations take longer.
It runs on modern, widely used web and mobile technology, hosted with mainstream cloud providers such as Cloudflare and AWS, in accounts registered to your organisation. The code lives in your own repository from the first commit. Nothing sits on a private framework only we understand, so another competent developer can pick it up, and if you decide to leave us, that is a handover, not a hostage negotiation.
The price is quoted in ringgit or dollars, fixed for the scope we agree in writing, and what it costs to run each month (hosting, app store fees, any paid services) is in the quote too. The engineers who scope your build are the ones who write it: our team in Malaysia and Singapore, with our Philippines team for field and low-connectivity work. After launch you can call on us for support, keep an engineer on a FlexiTech retainer, or run it yourselves with the documentation we leave behind.
From first chat to handover.
Show us how it works today
We sit with the people doing the work, look at the forms and spreadsheets, and write the problem down in your words.
Agree the first release
A fixed-price scope for the smallest version that genuinely helps, with running costs and later phases listed separately.
Build it in the open
Working screens every week or two, in your own repository, so you can test and change course before it gets expensive.
Launch and hand over
We move your real data across, train your team and leave documentation someone new can follow.
Stay, or go
Keep us for support or a FlexiTech retainer, or take it in-house; the code and the accounts are already yours.
Where we have already done this.
- Product, In production
Certainty
Certainty HelpDesk puts tickets, tasks, live chat, meetings and a client portal in one place, so a request is never retyped into a separate project tool. Help desk and project delivery, with a record you can point at.
See the product - Product, Live since 2025
JoinNests
JoinNests is membership management for organisations done duct-taping Google Forms to WhatsApp to Excel: registration, committee approvals, renewals and e-certificates on one platform, priced in ringgit on the page.
See the product
Things people ask us.
How long does it take to build an app or a portal?
It depends on how many kinds of user it serves and how many other systems it talks to. The scope says how long the first release takes; small internal tools are short, portals with several roles, payments and integrations take longer. We tell you early if anything changes it.
How much does it cost?
We quote in ringgit or dollars, fixed for the scope we agree in writing, and the quote also lists what it costs to run each month: hosting, app store fees and any paid services. If you want more later, that is a new, separate quote, not a surprise on the old one.
Do we own the code, and who hosts it?
You own it. The code lives in a repository in your organisation's name from the first commit, and the hosting, domain and app store accounts are registered to you. We work inside them with access you can revoke at any time.
Can we move to another developer later?
Yes, and we plan for it from the start. It is built on widely used technology rather than a private framework, with documentation written as we go. If you move to another developer or an in-house team, we hand over properly.
What if the one person who understands the system leaves?
That is exactly why we document as we build and keep everything in your accounts rather than in someone's head, ours included. A new staff member or another developer can pick it up from the documentation, and our team can step in while you rehire.