EDGE Grant Singapore: A Practical Guide to Your Next Growth Project

Start with the problem your business needs to solve

Write a short description of what is holding the business back today. Avoid starting with a shopping list. Buying software, commissioning research and hiring a consultant are possible responses; none explains the underlying problem. A useful description identifies the affected process, the people involved and the commercial consequence of leaving it unchanged.

For an illustrative distributor, the issue might be that stock information reaches the sales team too late. Orders are accepted for unavailable items, service staff spend time arranging substitutions and customers lose confidence. That description creates several possible responses: cleaning up inventory data, changing purchasing rules or connecting operational systems. It also prevents an attractive software demonstration from becoming the entire business case.

Collect a small baseline before comparing responses. Count delayed orders, hours spent correcting information or customer complaints over a normal operating period. Record how the numbers were measured. You do not need a perfect analytics system to make a useful start. Consistent definitions and honest assumptions give the project a foundation that can survive a change of vendor or project manager.

Match the activity to the work, then test the boundaries

EDGE uses activities to define what support is available. Treat an activity description as a boundary around a particular piece of work. Compare your intended outputs with the required deliverables, supported cost components, vendor conditions and project period. A broad similarity between a project title and a grant category is only a starting point.

Divide your plan into work packages. A company considering an overseas launch might need market research, changes to product packaging, an operating system and sales follow-up. These are connected commercially, yet they do not automatically belong in one grant application. EDGE generally requires a separate application for each activity. Keep the business roadmap integrated while giving each application an intelligible scope.

Ask what the project must produce that the business can inspect. A report should answer a decision; a system should perform a defined workflow; a standards project should result in the required implementation and assessment evidence. Remove nice-to-have extras that have no clear role in the outcome. If an activity does not fit, seek guidance before stretching its wording to accommodate a purchase.

Understand the funding before treating it as a discount

The headline support rate is a ceiling, subject to the selected activity and assessment. Standard support can reach 50% for SMEs and 30% for non-SMEs; eligible internationalisation and sustainability activities can reach 70% and 50% respectively. Your actual approval depends on the supported scope and costs, rather than the entire amount shown in a sales proposal.

The annual EDGE support cap is S$100,000 per company, refreshing on 1 April. A S$30,000 limit for specified digital solutions and pre-scoped equipment sits within that total. It does not create an additional pot. Check the available balance before prioritising several projects, and distinguish approved commitments from ideas that are still under discussion.

Prepare two budgets. The first shows the complete cash expenditure, including implementation work, recurring fees and any items outside grant support. The second shows the possible net cost after an approved claim. Keep the first budget visible throughout procurement. A project that appears inexpensive after reimbursement can still create a difficult cash shortage while invoices are being settled.

Check whether the organisation can absorb the change

A promising project can fail because the business is too busy to implement it. Before applying, identify the people who will supply information, make decisions, attend workshops, test outputs and teach colleagues. Their contribution should appear in the schedule as real work. A vendor cannot clean information that nobody inside the company owns or settle decisions that management has postponed.

Assess dependencies early. A new order system may require reliable product codes and a settled pricing policy. A market-entry project may require product specifications, an agreed distributor profile and somebody responsible for answering overseas enquiries. A strategy exercise may require segment-level financial data that the accounts team has never previously prepared.

Resolve the most serious gaps before fixing an ambitious end date. This preparation is distinct from starting the proposed funded work: the general rule is no project delivery or payments before submission, subject to express activity exceptions. Check the selected activity before signing or paying. Use the planning stage to establish readiness, not to commission part of the project informally and hope to include it later. If readiness is weak, a smaller, well-owned activity may deliver greater value.

Give every part of the project a named owner

Create a simple division of responsibilities. The business sponsor decides why the project matters and approves trade-offs. The project owner coordinates delivery and maintains the working plan. Finance checks affordability, invoices and payment records. Operational users test whether the promised improvement works in daily conditions. In a small company, one person may perform several roles, but the responsibilities should still be explicit.

External advisers can help scope work, explain documentation and challenge assumptions. They should leave you with a proposal that your own team understands. Applications, change requests and claims on the Business Grants Portal must be submitted by the applicant's authorised employees or staff. Assign the appropriate Corppass roles before a deadline approaches, and keep a second internal contact familiar with the project.

Agree how decisions will be recorded. A short weekly note identifying completed work, open issues, upcoming decisions and document gaps is often enough. Keep important approvals in the project folder rather than scattered across individual messaging accounts. Good internal ownership reduces the risk that the departure of one employee leaves the business unable to explain its project or prepare its claim.

Compare the complete offer and the alternatives

Ask vendors to show the price before any assumed grant support. Then compare like-for-like scope: implementation, training, licence duration, user limits, maintenance, equipment ownership, data migration and exit arrangements. A low first-year net price can hide expensive renewals or an incomplete deployment. Clarify who retains access to your data and how it can be exported if the relationship ends.

Keep at least one credible alternative in the decision. It could be another vendor, a smaller deployment or a process change undertaken without grant support. The point is to understand the commercial value of the proposed work. Funding should improve an already sensible choice; it should not prevent management from noticing that the total package is more expensive than another workable route.

Build acceptance criteria into the scope. For a hypothetical scheduling tool, staff might need to create jobs, assign qualified workers, update completion status and export a service report. Demonstrating those tasks using realistic business scenarios is more revealing than counting features on a brochure. Ask the vendor to explain limitations before the contract is settled.

Use your first week to build a decision-ready project brief

Set aside a focused first week for a short internal brief. Begin with the business problem and a baseline. Add the intended outcome, the activity you believe fits, the people who will participate and the assumptions that still need checking. Attach an initial budget and list the information needed from prospective vendors. The aim is a shared understanding of the project before application preparation becomes a document exercise.

Next, test the brief with the people who will use the result. Ask what would make the project fail in practice. Staff may identify inaccurate customer records, seasonal workload, missing equipment or a dependency on an overseas partner. Addressing these issues now is usually cheaper than discovering them after deployment has begun.

Finally, decide whether to proceed, narrow the scope or pause for preparation. A pause can be a sound business decision when cash, leadership attention or data is missing. If you proceed, maintain one current scope and one evidence folder from the outset. The strongest outcome is a useful business capability that continues producing value after the grant claim has been completed.

Frequently asked questions