Blog Details

Singapore SMEs can typically offset part of an AI chatbot's cost through the Productivity Solutions Grant (PSG), if the chatbot is a pre-approved off-the-shelf solution, or the Enterprise Development Grant (EDG), if it is a custom-built agent tied to a broader process upgrade. Either route requires applying and getting approval before you commit spend, and both pay out on a reimbursement basis after the project is done.

This article walks through what actually qualifies, how the two schemes differ for a chatbot project specifically, and the practical steps to avoid the most common mistake: paying for a chatbot build before checking grant eligibility.

Why chatbots are one of the most common AI grant use cases

Of all the AI projects Singapore SMEs bring to grant applications, chatbots are among the most frequent, for a practical reason: the business case is usually easy to articulate. Everyone understands what a chatbot does, the problem it solves (missed enquiries, slow response times, repetitive questions) is easy to describe in plain terms, and the outcome is visible almost immediately after launch. That clarity is genuinely useful when it comes to writing an application, but it also means the bar for standing out is about specificity: what exactly will the chatbot do, for whom, and what changes as a result, not just "we are adding a chatbot."

Which grant fits an AI chatbot project?

It depends on how "off the shelf" the chatbot is.

• PSG fits a chatbot project when you are adopting a pre-approved platform with light configuration, for example a widely used AI customer service tool that you set up with your FAQs and business hours.
• EDG fits a chatbot project when it is custom-built: trained specifically on your product catalogue, integrated with your booking or CRM system, or built as part of a wider automation of your customer service workflow.

Our earlier comparison, PSG vs EDG for AI adoption, goes into more depth on how to tell these apart. For a chatbot specifically, the test is simple: are you buying a product and configuring it, or commissioning something built around your business?

What costs can a chatbot grant application typically cover?

Before listing categories, it is worth setting expectations: qualifying costs are defined by EnterpriseSG's scheme rules, not by what feels reasonable to include. A cost that seems obviously project-related to you may still fall outside what the scheme recognises as qualifying, which is why checking the current guidance, rather than assuming, matters at the budgeting stage.

For PSG-eligible chatbot solutions, the grant generally supports part of the cost of the pre-approved software or subscription. For EDG-eligible custom chatbot projects, qualifying costs can include:

• Third-party consultancy and development fees for building and training the agent
• Integration costs (connecting the chatbot to your booking system, CRM, WhatsApp Business, or website)
• Software licensing or cloud hosting costs directly tied to the project

EDG can support up to 50% of qualifying costs for eligible SMEs, though the actual level depends on the project and current scheme parameters at the time of application. Neither scheme covers costs incurred before approval, and neither covers unrelated operating expenses. Always confirm current qualifying cost categories on the GoBusiness Grants portal, since these are set and updated by EnterpriseSG. If you want help mapping your chatbot idea against these categories before you apply, request a quote and we will scope it with you.

What does the process look like, step by step?

1. Define the chatbot's job. Is it answering FAQs, qualifying leads, taking bookings, or handling order status queries? A specific scope makes both the vendor proposal and the grant application stronger.
2. Check the PSG pre-approved list first. If a pre-approved solution genuinely covers your needs, this is usually the faster, simpler path.
3. If you need something custom, get a vendor proposal. A clear costing and technical scope is typically part of what an EDG application needs.
4. Apply via the GoBusiness Grants portal before starting work or signing a build contract that assumes grant support. This is the step that most often gets skipped under time pressure, and it is the one that matters most.
5. Build the chatbot once approved, keeping invoices, contracts, and delivery evidence for the claim.
6. Submit your claim with proof of spend and completed work to receive the reimbursed portion.

Common mistakes that cost SMEs their grant support

Mistake	Why it matters
Signing a chatbot build contract before applying	Work started before approval is generally not eligible for support
Assuming any chatbot automatically qualifies	The specific solution or project scope needs to fit PSG or EDG criteria
Not keeping proper documentation	Claims require evidence: invoices, contracts, proof of payment, proof of deployment
Expecting the grant to fund 100% of the cost	Both schemes are co-funding mechanisms with a supported percentage, not full funding

Why a chatbot's scope matters more than the "AI" label

Grant assessors are not evaluating whether something is technically AI, they are evaluating whether the project builds a real business capability. A chatbot that genuinely reduces response time, qualifies leads properly, or handles bookings without manual back-and-forth is a stronger story than "we added a chat widget." This is the same logic behind our article on the difference between a chatbot and a conversational AI agent: the more the solution behaves like a real operational tool rather than a scripted FAQ box, the easier it is to justify as a genuine capability upgrade.

If you want to see what a properly scoped conversational AI agent looks like before you approach either grant, our conversational AI agent development service page walks through what we build and how we scope it.

What does a chatbot project actually cost, before the grant?

We are not going to publish a specific price range here, since chatbot costs vary widely based on complexity: a pre-approved platform with light configuration costs very differently from a custom-built agent integrated with your booking system, CRM, and inventory. What is worth understanding is the general shape of the cost:

• Platform or development cost: the one-off (or subscription) cost of the chatbot software or custom build itself
• Integration cost: connecting the chatbot to your existing systems, which is often where custom projects add real cost and real value
• Ongoing running cost: hosting, subscription fees, or usage-based costs that continue after go-live, and which are typically outside what a grant covers

Our article on AI chatbot pricing in Singapore goes into more detail on how subscription versus custom-build pricing compares, which is useful groundwork before you decide which grant track even applies.

How does a chatbot's scope affect which grant track it fits?

The single biggest factor is customisation. A useful way to think about it:

Chatbot characteristic	More likely PSG	More likely EDG
Base platform	Pre-approved, off-the-shelf	Custom-built or heavily configured
Training data	Generic FAQ setup	Trained specifically on your catalogue, policies, or processes
Integration	Minimal or none	Connected to booking, CRM, inventory, or other core systems
Project size	Smaller, faster to deploy	Larger, part of a broader process redesign

If your project sits somewhere in between, that is a genuine scoping question worth raising with your implementation partner and, ultimately, with EnterpriseSG or the GoBusiness portal guidance, rather than guessing.

Budgeting for the reimbursement gap

Because both PSG and EDG reimburse after the fact, your business needs to fund the full project cost upfront and wait for the claim to be processed before recovering the supported portion. This cash flow timing is worth planning for properly rather than assuming the grant money arrives alongside the invoice. We cover this in more detail in budgeting an AI project when grants reimburse later.

How does the grant conversation fit into vendor selection?

It is worth raising grant eligibility with a shortlist of vendors early, not after you have already chosen one. A vendor who regularly scopes EDG or PSG-eligible chatbot projects will typically be able to tell you, honestly, whether your intended project is likely to fit a pre-approved PSG solution or needs the fuller EDG process, and will structure their proposal accordingly. A vendor who cannot answer this clearly, or who promises grant approval as part of their pitch, is a signal worth taking seriously. Our article on red flags when hiring an AI vendor in Singapore covers this in more depth, and promising or guaranteeing grant approval is one of the clearest red flags on that list.

What happens if your chatbot project spans both tracks?

Some chatbot projects genuinely blend elements of both: perhaps you adopt a pre-approved base platform (PSG territory) but then commission custom integration work on top of it (closer to EDG territory). Whether and how such a hybrid project can be structured, and which costs fall under which scheme, is a specific question for EnterpriseSG or a grant advisor familiar with current scheme rules, since combining or sequencing applications incorrectly can create complications. Do not assume you can simply apply to both schemes for the same cost items.

Ready to see what AI can do for your business?

If you are weighing up a chatbot for your business and want an honest read on whether it fits PSG, EDG, or neither, request a quote and we will scope it with you properly, grant fit included. WhatsApp us at +65 9184 9908, email glenn@freemansland.co, or reach out via our contact page.

Frequently Asked Questions