Manual Testing and QA in Singapore

No GST is charged on our invoice, and the invoice says so. Whether you account for it under reverse charge depends on your input tax position: IRAS's guidance is that a GST-registered business making only taxable supplies is not impacted, a partially exempt business or one with non-business receipts accounts for GST on imported services in its own return, and a business that is not registered should ask its accountant, because an exempt business importing more than S$1 million of services in a year can be required to register. We would rather your accountant confirmed your position before the first invoice than reconciled it at year end.

We build to it rather than claiming a certificate. The consent, purpose limitation and notification obligations shape the forms and the data model; retention limitation means records are deleted on a schedule rather than kept indefinitely; access and correction requests are features with a queue behind them rather than a manual database job. Processing happens in India, so the transfer limitation obligation applies, and the processor agreement we sign sets out the comparable standard of protection the Act asks for. The obligation to design for early is breach notification: an organisation has three calendar days from determining a breach is notifiable, which means one likely to cause significant harm or one affecting 500 or more people, to tell the PDPC, and answering what was in the breach is only possible if the logging existed beforehand. Appointing a Data Protection Officer is your obligation rather than ours, and we will say so if a design choice would make that person's job harder.

Not PSG. The Productivity Solutions Grant funds pre-scoped packages from pre-approved vendors for Singapore-registered companies, and a custom build from an overseas team is not that shape, so we will not pretend it is. The Enterprise Development Grant is assessed project by project against its own criteria, and whether a build like yours qualifies is a question for Enterprise Singapore or your grant consultant to answer before the scope is written rather than after a budget has assumed it.

We can supply what a due-diligence pack asks for, accept audit and access rights in the contract, and name every sub-processor that touches your data. What we will also tell you in the first conversation is what we do not hold: we are not SOC 2 or ISO 27001 certified, and our security page says so in those words. Whether an engagement with us is a material outsourcing arrangement under the MAS guidelines, and what that requires of you, is your compliance team's determination, and it changes the contract before it changes the code, so it belongs in week one.

Manual testing is a real person using your software against a plan, walking the actual flows and judging whether each one works and feels right. Automated testing is code that re-checks known paths on every build. Manual is better for new features, changing interfaces, and exploratory and usability work; automation is better for re-running a large, stable regression suite fast. Most teams need both, and manual QA is the honest first step because it finds bugs without you building a test framework first.

Yes. Manual QA is a standalone service, so you do not need us to have built the product. Send a staging URL or a build and tell us what it is supposed to do. We write a test plan and run functional, regression, exploratory, cross-browser, and cross-device passes, then hand back bug reports your developers can act on. We test our own builds the same way, so the discipline is identical whoever wrote the code.

Every issue is logged so an engineer can reproduce and fix it without asking us what we meant: a clear title, numbered steps to reproduce, expected versus actual result, the environment (browser, device, OS, build), and a screenshot or recording with the relevant console error. We log into your tracker, whether that is Jira, Trello, GitHub Issues, Linear, or a shared sheet, in the format your team already uses. Each bug gets a severity and priority so the blocker is fixed before the cosmetic issue.

Yes. We verify your product across Chrome, Safari, Firefox, and Edge, and across real phones, tablets, and desktops on iOS and Android. Layout and interaction bugs often show up in only one browser or on one screen size, so we test the matrix that matters for your users rather than assuming a build that works on one laptop works everywhere.

It depends on scope: how many flows, how many browsers and devices, and whether you want one release tested or ongoing cycles. We do not publish a single rate that falls apart on a real brief. Send the build and what it should do, and we write a test plan and quote one flat INR number against it, with GST, inside 24 hours. Overseas clients can be invoiced in USD, CAD, GBP, or AED.