Custom Web App or More Spreadsheets? A Guide for Singapore SMEs

Updated 1 November 2026. A guide for Singapore SMEs deciding whether to build a custom web app. The parts on copyright and customer records are general information, not legal advice. For your own contract, ask a lawyer.

The short answer: build a custom web app when one daily job runs across several people and no ready tool fits it without workarounds. If a tool already fits, or the volume is small, do not build. Before you pay any software house, get two things in writing: who owns the code, and how your customer records are handled.

Here is why those two matter. In Singapore, the person who writes the code owns it by default, even when you paid for it. And if your vendor breaks PDPA rules while handling your customers' personal details, the law can hold you responsible.

The checklists we read tell you to own the code but skip the why. This guide explains it with IPOS and PDPC's own rules.

When the spreadsheet starts costing you

It usually starts small. Leads go into a spreadsheet, quotes into a Word template and client updates onto WhatsApp. Then you add a booking app, a CRM trial and an invoicing tool, and each one does part of the job.

The real cost is not the subscriptions but the copying. Someone types the same customer into three places. A follow-up is missed because it sat in one person's chat. Nobody can see, on one screen, which leads became jobs.

A custom web app joins those steps into one system built around how your team works: a lead tracker, a quotation system, a client portal or a dashboard. That can save real hours.

It can also become a new problem if the developer stops answering. One user on a HardwareZone thread wrote this after a paid tool stopped working and the seller went quiet: "I don't think it is nice to ignore customer emails when the product stop working." The questions below are there so that never happens to you.

When a custom web app is worth it, and when it is not

This is our view from building systems for clients. Be honest about which row you are in.

A simple test: can you describe the one job the system must do in two sentences, and name who will use it every day? If you cannot, you are not ready to brief a software house yet.

Who owns the code you paid for

This rule is easy to miss. Copyright covers software: IPOS says copyright protects "works like novels or computer programmes" (IPOS). And on who owns it, IPOS is direct:

"In general, the person who created the work (i.e. the author) owns the copyright in the work." (IPOS, updated 8 January 2026)

IPOS adds that this covers commissioned work too: work the author was paid to make. The author and the person who commissioned the work "can agree in writing that someone else will own the copyright instead".

So if your contract says nothing, paying for the app does not, in general, make the code yours. The software house, or the developer who wrote it, usually keeps the copyright.

IPOS also says that work created during employment belongs to the employer automatically. So if the software house's own staff write your code, the software house, as their employer, would in general own it first. You need it transferred to you, in writing.

IPOS describes two ways to pass on copyright. An assignment transfers ownership. A licence only lets someone use the work in agreed ways, while the owner keeps it. Ask which one your contract gives you.

Access is not ownership either. Being invited to view the code repository is useful, but it does not change who owns the copyright. Get both: the written transfer, and the code and accounts in your name.

Your customer data is still your problem

Most business systems hold personal data: names, phone numbers, addresses, job details. If your software house hosts or stores that data for you, PDPC says it will likely be your "data intermediary" (PDPC guide on data protection clauses, 2021). The same guide says:

"A Customer will be liable for any act done, or omission, by the Contractor in the course of processing personal data on behalf of the Customer where such act or omission amounts to a breach of any Data Protection Obligation." (PDPC, 2021)

In that guide, you are the "Customer" and the software house is the "Contractor". So if your vendor breaks PDPA rules while handling your customers' details, that is your risk, not only theirs.

Breaches have deadlines. PDPC's guide says the contractor must tell you about a data breach "without undue delay". If you assess it as a notifiable breach, you must tell PDPC as soon as practicable, and no later than three calendar days after your assessment. So your contract should say how fast the vendor tells you, and who does what.

The same guide includes sample clauses for this kind of contract. PDPC adds that using them does not by itself make you compliant, and that you should get legal advice if you are unsure. Show the clauses to your lawyer, not just to the developer.

10 questions to ask a software house before you pay

Use these with any vendor, including us. A good software house will answer them without fuss.

1. Who will own the code? Ask for the copyright to be assigned to your company in writing, not just a licence to use it.
2. Where will the code live? Ask for a code repository in your company's own account, with the vendor added as a user.
3. Whose name are the accounts in? Hosting, domain, database and app store accounts should be in your company's name.
4. What do I get at handover? Admin logins, documentation and a short guide to how the system is set up.
5. Where are my customer records stored, and who can see them? Ask about backups, user permissions and how you export your records if you leave.
6. What happens if there is a breach? Ask how fast they will tell you, and put it in the contract.
7. How is payment split? Pay per stage, against work you have tested and accepted. Agree what "accepted" means before work starts.
8. What is out of scope? Get the scope in writing, and ask how new requests are quoted before extra work starts.
9. What does maintenance cover after launch? Bug fixes, security updates, hosting and small changes are often priced separately. Get it in writing.
10. Who writes the code? In-house staff or outside freelancers? It affects who owns the code first, and so what the transfer clause must cover.

If an answer is vague, ask again. If it stays vague, that is your answer.

Should the same company do your SEO?

It depends on which part you mean. An internal app, such as a staff dashboard or a quotation tool behind a login, does not need SEO, because it has no reason to appear in Google.

Your public website is different: that is where new customers find you, on Google and in AI answers. One team for both helps when the two share records, for example when every website enquiry flows straight into your lead tracker and you can see which page brought which customer.

So judge the build on the questions above, and judge SEO on its own terms. If one company does both well, good. If not, two specialists who agree how records pass between them work just as well.

What we have built

This section is about our own service, and it is short on purpose. These are systems we built and run, with clients kept anonymous:

• A lead tracker for a Singapore renovation contractor. Since 3 September 2026 it records the page each visitor first landed on, and whether they enquired by form or by WhatsApp. We wrote up what that tracker taught us about lead counts.
• An hourly product feed for a Singapore car leasing and sales client. It keeps the client's Meta ads catalogue in step with its listings.
• app.singrank.com, our client dashboard. Every client gets this live dashboard, showing enquiries and rankings (SingRank). The enquiry records come from SingRank Pixel, which records WhatsApp clicks and contact-form sends.
• Websites. singrank.com itself, and two sites built from scratch with Node.js and Astro, with a CMS the team can edit: BatamGems and CariKerjaDiBatam.

On our projects, ownership, hosting, account access, data location and export are agreed before development starts. See the business software we build.

How we price it, and how to start

We do not publish one price for software, because a lead tracker and a client portal are different jobs. New websites and software are priced by quote once we see the scope. Work outside the agreed scope is quoted first and starts only after you approve it. Details are on our software and automation services page.

Other services are priced separately (other services and prices). A one-hour phone consultation is S$150, if you want a second opinion on a quote you already have.

WhatsApp lead follow-up and automation is from S$500/month, plus a setup fee quoted after we see your workflow. Our SEO and GEO plan is S$750/month (SEO and GEO pricing). If you plan to automate customer messages too, read what you may automate on WhatsApp first.

Not sure if you should build at all? Send us a WhatsApp with the one job you want the system to do and the tools you use today. We reply within 1 working day and tell you whether a ready tool, an automation or a custom web app fits. Sometimes the honest answer is "keep your spreadsheet".

FAQ

How much does a custom web app cost in Singapore?

There is no fair single number. The price depends on what the app must do, how many types of users it has, which tools it must connect to, and how many records it holds. A quote that comes before anyone asks about your workflow is a guess. At SingRank, software is priced by quote once we see the scope, and extra work is quoted before it starts.

Who owns the code if my contract says nothing?

Under IPOS's guidance, the person who created the work owns the copyright by default, and that includes work someone was paid to make. Work made by employees belongs to their employer. So if the contract is silent, the developer or the software house usually keeps the copyright. The fix is a written assignment to your company. This is general information, not legal advice; ask a lawyer to check your contract.

Should I build custom or use a SaaS tool?

Use the SaaS tool if it already fits the job and your team actually uses it. Build custom when one daily job runs across several people and every tool you tried needs workarounds, or when customers need their own login to see their records. If your tools work but records get copied between them, try connecting them with an automation first.

Do I need a data clause if the app only stores customer names and phone numbers?

Names and phone numbers are personal data. If your vendor hosts or stores them for you, PDPC's guide says it will likely be your data intermediary, and you can be liable if what it does with them breaks PDPA rules. PDPC publishes sample data protection clauses for these contracts. Using them does not by itself make you compliant, so have a lawyer review the final wording.