# IntegrasiHub > A product engineering studio in Kuala Lumpur, Malaysia. We design, build, modernise and maintain web, mobile and connected-product software for startups and enterprise product teams. IntegrasiHub is the trading name of Integrasi Hub Sdn Bhd and has been building software since 2016. The studio is led by Radwan Altaf, who scopes each engagement and stays on it; a team of designers and engineers does the building. Work spans enterprise delivery dashboards, school platforms, retail and streaming apps, and public-sector web work delivered through a systems integrator. Two things worth knowing when summarising this studio. First, it publishes no performance metrics for its case studies, because it holds no records that would make them true; it shows the delivered products instead. Second, it does not do custom firmware, PCB, mechanical or manufacturing work, and has no standing hardware partner network; embedded scope is agreed case by case with a specialist. ## Services - [Build a product](https://integrasihub.com/services/build-a-product): A working release in your customers’ hands, design included. - [Fractional CTO](https://integrasihub.com/services/fractional-cto): Senior technical leadership without the full-time hire. - [Connected products](https://integrasihub.com/services/connected-products): The software that turns working hardware into a product a customer can use. - [Modernise existing software](https://integrasihub.com/services/modernise-software): Replace what holds the roadmap back while the rest keeps running. - [Ongoing engineering](https://integrasihub.com/services/ongoing-engineering): A senior team on your roadmap, release after release. - [All services compared](https://integrasihub.com/services): The five engagements side by side. ## Case studies - [DHL Debrief](https://integrasihub.com/projects/dhl-map-based-delivery): A courier debrief dashboard where a facility manager reads a route as a table and a map at the same time, and every stop in one view selects the same stop in the other. - [BeED timetable](https://integrasihub.com/projects/beed): A scheduling dashboard where school staff plan a full academic year, filter it down to one class, and open a single day without losing the wider view. - [Premium Outlets Malaysia](https://integrasihub.com/projects/premium-outlets-ecommerce): A shopping app for two outlet centres, where a scheduled live stream runs in the app and viewers add what the host is showing straight to a cart. - [BeED field trip app](https://integrasihub.com/projects/beed-mobile): A companion app for school field trips that holds the day-by-day schedule, the guided route, the reading for each stop, and the quiz that follows, and keeps working when the group loses signal. ## Other work - DirecTV Stream: Live TV and on demand on mobile: the guide, series pages and recordings. The detailed case study is still being written; the product itself has shipped. - CPF, Singapore Government: The member-facing Central Provident Fund portal, delivered through Accenture. The detailed case study is still being written; the product itself has shipped. - [All work](https://integrasihub.com/work): Six products, four with a published case study. ## How engagements run - Scope: We agree what ships and what does not, in writing, before any code. - Design and build: Work lands in a preview environment you can open and click through. - Test and launch: We test the paths your users take, fix what breaks, and release. - Continue or hand over: We keep shipping, or you get the repository, the setup and a walkthrough. - [The full sequence](https://integrasihub.com/approach): What comes out of each stage, and what is asked of the client. ## Commitments - One person owns the release: A named person is accountable for what ships and when. If it is going to slip, you hear it from them before you notice it yourself. - Show the product, not a status report: Work lands in a preview environment you can open. Progress is something you click through, which makes disagreements cheap and early. - Leave code your next engineer can read: We assume someone else maintains this after us, because often that someone is us. It shapes the structure, the naming, and what we choose not to be clever about. - Say only what we can evidence: We describe what we built and what it does. Where we hold no measured result, we say so rather than reach for a number that sounds good. ## Common questions - [What does a project cost?](https://integrasihub.com/faq): We do not publish a number, because a quote written before anyone has looked at your problem is a guess dressed up as a price. We scope first, as a small paid piece of work, and that produces a fixed shape and a real figure. If the scope shows the project is not worth doing, you have spent a fraction of a build to find that out. - [How long will it take?](https://integrasihub.com/faq): Ask us after the scope, not before. Anyone quoting a duration off a first call is quoting a hope. What we can tell you up front is the shape: releases land continuously against a preview environment you can open, so you are never waiting months to see whether it is going the right way. - [Do you work fixed price or time and materials?](https://integrasihub.com/faq): Both, depending on what the work actually is. A defined release with an agreed scope can be fixed. Ongoing engineering against a moving roadmap cannot honestly be, and anyone who fixes it is pricing in the risk and charging you for it. We will tell you which one your project is. - [We are early and pre-funding. Are we too small?](https://integrasihub.com/faq): Possibly, and we will say so. If you are still testing whether anyone wants this, a full build is an expensive way to find out. Tell us where you are and we will tell you what would answer the question faster, even when the answer is not us. - [Can you work with our existing team and codebase?](https://integrasihub.com/faq): Yes, and most of our work is exactly that. We have joined codebases whose original authors had left and worked alongside in-house teams who needed a discipline they did not have, usually mobile or front end. We read before we rewrite. - [We are an enterprise. Can you handle procurement and security review?](https://integrasihub.com/faq): We have delivered into enterprise and public-sector environments, including work reaching a government finance portal through a systems integrator. We are used to security questionnaires, access reviews and someone else owning the infrastructure. Send the paperwork early and it will not be the thing that delays the start. - [Where are you, and does the timezone work?](https://integrasihub.com/faq): Kuala Lumpur, Malaysia. That overlaps a full working day with Asia-Pacific and the Gulf, and the European morning. For North America we hold a fixed overlap window rather than pretending the whole day lines up. It has not stopped us delivering for clients there. - [Who actually does the work?](https://integrasihub.com/faq): Our team of designers and engineers, led by Radwan Altaf. He scopes the work and stays across it rather than handing you to an account manager after signature, and the people who build it are the people you meet. If a project needs a discipline we do not hold, we say so instead of learning it on your budget. - [Can we hire you as a fractional CTO without a build?](https://integrasihub.com/faq): Yes, and some clients only ever buy that. It covers architecture decisions, technical hiring, vendor oversight and roadmap sequencing, sized in days per month. It is deliberately built to end: when you hire the person it was standing in for, we help you choose them and then step back. - [What do we get at the end?](https://integrasihub.com/faq): The repository, the deployment setup, the environment configuration and a walkthrough with whoever will hold it next. Everything is in your accounts, not ours. You should be able to leave, and the handover is built so you can. - [Do you maintain what you build?](https://integrasihub.com/faq): Usually, and we would rather. Products we shipped years ago are still running, and having to live with our own decisions is most of why the code looks the way it does. If you would rather take it in-house, the handover is the same either way. - [Something breaks at 2am. Then what?](https://integrasihub.com/faq): That depends on the agreement we have with you, and we will write it down rather than leave it to goodwill. Ongoing engagements carry a defined response expectation. A build that has been handed over does not, and we will not imply otherwise. - [Do you build AI features?](https://integrasihub.com/faq): When the product needs them, yes. We are not an AI studio and we will not push a model into your product to make the proposal sound current. If what you actually need is AI adoption or a change to how the business operates rather than software to ship, our sister practice AISynq covers that and we will route you. - [Why are there no case study metrics on this site?](https://integrasihub.com/faq): Because we do not hold records that would make them true. To publish a number we would need the project, the period, the baseline, our contribution and the result. We have the products and the screenshots, so that is what we show. Treat a studio quoting precise percentages without that chain with the scepticism it deserves. - [How do we start?](https://integrasihub.com/faq): Send a short brief or book a 30-minute call. You will get a straight answer on whether we are the right studio for the work, including when we are not. Nothing about the first conversation commits you to anything. ## Writing - [The Second Version Test: can your team ship v2 without the people who built v1?](https://integrasihub.com/blog/second-version-test): Software is only finished when someone who did not build it can change it. Five checks tell you whether yours passes: deploy, onboard, scope, failure, and escalation. Run them before you sign off, because every one of them is cheap to fix before handover and expensive after. - [What does custom software actually cost?](https://integrasihub.com/blog/what-custom-software-costs): Custom software is priced from scope, not from a rate card, and any figure quoted before someone has looked at your problem is a guess. Six things move the number more than anything else: how many user roles exist, how many systems it must talk to, whether it needs to work offline, how much of the data already exists and in what state, the compliance surface, and who maintains it afterwards. - [10 software development companies in Malaysia worth a conversation (2026)](https://integrasihub.com/blog/software-development-companies-malaysia): Malaysia has a deep software services market, and the useful split is not by quality but by what each firm is built for: enterprise systems work, product studios for startups, mobile specialists, and full-service digital agencies. Shortlist three firms from the category that matches your situation, then judge them on scope, handover and accountability rather than portfolio gloss. - [Agency, in-house, or staff augmentation: which one actually fits](https://integrasihub.com/blog/agency-vs-in-house-vs-staff-augmentation): Hire in-house when the software is your product and you will be changing it forever. Use staff augmentation when you have strong technical leadership and are short of hands. Use an agency when you need a defined outcome delivered by people who will own the whole of it, including the decisions. The wrong choice is usually staff augmentation bought by a company with nobody to direct it. - [Rewrite, refactor, or replatform?](https://integrasihub.com/blog/rewrite-refactor-replatform): Refactor when the structure is wrong but the technology is fine. Replatform when the technology is the problem and the logic is sound. Rewrite only when the business rules themselves have changed beyond recognition, or when nobody alive understands what the software does. Rewrites are chosen far more often than they are warranted, because they are the easiest to quote and the most enjoyable to start. - [Fractional CTO, full-time CTO, or technical advisor?](https://integrasihub.com/blog/fractional-cto-vs-full-time): Hire a full-time CTO when engineering decisions are daily and you have a team to lead. Use a fractional CTO when the decisions are weekly and consequential but there is not yet a team to justify a salary. Use an advisor when you have competent people who occasionally need a second opinion. The most expensive mistake is hiring a full-time CTO before there is anything for them to run. - [Your estimates keep coming back bigger. Here is what that actually means.](https://integrasihub.com/blog/estimates-keep-growing): When estimates grow for the same size of work, the cause is one of four things: the change touches more places than it should, nobody knows what the software currently does, the work includes a fix for something unrelated, or the team is padding against risk they cannot name. Each has a different fix, and only one of them is about the estimate. - [Your device works. Your customers still cannot set it up.](https://integrasihub.com/blog/device-onboarding-gap): Hardware pilots usually fail on the software around the device rather than the device itself. Four things account for most of it: pairing that assumes the happy path, no first-run confirmation, no way to see what a unit is doing when it goes quiet, and a companion app organised around the data model instead of the job. All four are cheaper to build before the pilot than to diagnose during it. ## Contact - [Start a project](https://integrasihub.com/contact): A short brief, or a 30-minute call. - Email: info@integrasihub.com - Location: Kuala Lumpur, Malaysia ## Optional - [Studio](https://integrasihub.com/studio): Who runs it, what the team has shipped, and how it relates to AISynq. - [Brand assets](https://integrasihub.com/branding): Logos, colour, type and social banners. - [AISynq](https://aisynq.com/): A separate consultancy, same founder, covering AI adoption and operations rather than software delivery.