Three of the most widely used business support schemes in Singapore stopped accepting applications on 29 September 2026, and their replacement opened the following morning. Most of the commentary I read that week treated this as an administrative simplification — three forms become one form, which is good news. That reading misses the part that actually changes decisions. The consolidation did not just merge the paperwork. It merged the budgets, and a company that previously drew on three separate ceilings now works against one.
What Changed on 29 and 30 September
The Enterprise Development Grant, the Productivity Solutions Grant and the Market Readiness Assistance grant all ceased on 29 September 2026. The EDGE Grant commenced on 30 September 2026.
The structure of the replacement is straightforward:
- Coverage: eight business areas spanning more than 150 activities, including automation and digitalisation, business strategy, financial management, innovation, internationalisation, standards and sustainability.
- Support rates: up to 70% for SMEs, up to 50% for non-SMEs.
- Cap: up to S$100,000 in total grant support per year, across all activities, refreshing on 1 April.
- Eligibility: open to all Singapore-registered businesses, including non-SMEs — a genuine widening relative to the SME-focused tiers it replaces.
- Transition: applications and projects already in flight under the previous schemes continue under their original terms.
The authoritative reference is the EDGE Grant page on the Enterprise Singapore site, and anyone planning around specific qualifying costs should confirm them there rather than relying on secondary summaries, this one included.
Our expert take #1
The headline everyone wrote was simplification. The headline I would have written is one queue instead of three. Under the old arrangement, a digitalisation project and an overseas expansion project were funded from different places, so they did not compete. Under a single annual ceiling they do. That is not a worse system — it is arguably a more honest one — but it moves a real prioritisation decision from the finance team to whoever owns the roadmap, and in most companies nobody has yet noticed that it moved.
Three Budgets Became One Queue
This is the whole substance of the change for anyone running a technology function.
Consider a mid-sized Singapore company with three things on its plate: adopting a new internal platform, pursuing customers in a neighbouring market, and a process automation project in operations. Under the previous structure these drew on different schemes with different ceilings, so they were planned largely independently and each one succeeded or failed on its own merits.
Under EDGE they draw on the same annual ceiling. The automation project and the market expansion are now, in a direct and arithmetic sense, alternatives. Fund one fully and the others get what remains of the S$100,000.
That reframing is the reason I went back through five client budgets that week. In four of the five, the plan had implicitly assumed the old separation, and nobody had re-ranked anything.
The Widening Nobody Led With
Most coverage framed this as a change for SMEs, which is understandable given the schemes it replaces. But EDGE is open to all Singapore-registered businesses, including non-SMEs, at up to 50% support.
For a larger local company or the Singapore entity of a regional group, that is a category of support that mostly was not available before. Fifty percent of a qualifying project cost, under a S$100,000 annual ceiling, will not transform a large capital programme. It is, however, very capable of changing whether a mid-sized internal tooling or automation project clears its approval threshold — and those are exactly the projects that quietly die in planning every year.
If you work at a non-SME and stopped tracking Enterprise Singapore schemes years ago because they did not apply to you, that assumption is now out of date.
Funded a project and now need people to build it?
We source and pre-screen engineers in Singapore for exactly this situation — a scoped, time-boxed project that has budget approval and no spare capacity behind it.
Discutons-en — talk to our Singapore teamThe Failure Mode I Expect to See by March
Here is the pattern I would bet on, because I have watched it happen with every funding instrument I have worked around.
A company secures support for two or three initiatives. The approvals are real, the projects are sensible, and the finance team is pleased. Then delivery starts, and it turns out the engineering capacity to execute them was never checked — because funding approval and capacity planning happened in different meetings, months apart, owned by different people.
Twelve months later the company is explaining why funded projects have not shipped. This is worse than not having applied, because now there is a commitment attached.
The single shared cap makes this more likely rather than less, for a slightly counterintuitive reason. When ceilings were separate, the natural question was can we get this funded? With one ceiling, the question becomes what is the most we can get out of the cap? — and optimising a budget ceiling is a very effective way to commit to more delivery than you have people for.
Our expert take #2
Before you submit anything, write one sentence per project naming who delivers it and what they stop doing. If the answer to the second half is “nothing, they will absorb it”, the project is not resourced and the funding will not fix that. This single sentence has killed more bad plans in my experience than any formal capacity model, because it forces the trade-off into the open at the moment it is still cheap to change.
What I Actually Changed in Five Budgets
Across the five plans I reworked that week, the same four moves came up repeatedly.
1. Re-ranked projects against one ceiling instead of three
The mechanical change, and the one everybody needs to make. Put every candidate initiative on a single list, in priority order, with its expected qualifying cost, and draw a line where the cap runs out. Four of my five had never done this because the old structure never required it.
2. Moved the delivery capacity question before the application
For each project above the line, name the team and name what they stop doing. Where the answer was genuinely nobody, the choice was to either drop the project or plan to add capacity — which for most of these is a contract or dedicated-team question rather than a permanent headcount one. Our walkthrough of building an engineering team in Singapore covers how to size that honestly.
3. Treated the 1 April refresh as a real deadline
The cap refreshes annually on 1 April. That makes the period between now and then a defined planning window rather than an open horizon, and it makes sequencing matter: a project you can scope and submit inside this window is worth more than a better project you cannot.
4. Stopped treating grant funding as free money
Support of up to 70% still leaves at least 30% of the cost with you, plus the internal time to scope, apply, administer and report. For a small project, that overhead is a meaningful fraction of the benefit. One of the five budgets I looked at had two projects where, once internal time was counted honestly, applying was not clearly worth it. Dropping those made room under the cap for the one that mattered.
The Case for Doing Nothing
I should be fair to the opposite view, because for some readers it is correct.
If your projects already in flight were approved under EDG, PSG or MRA, those continue under their original terms and nothing is on fire. If your technology spending is well below the level where a S$100,000 annual ceiling is a constraint, the consolidation is genuinely just a simpler form and you can treat it as such. And if your engineering team is already fully committed for the next two quarters, the right response to a new funding instrument is to ignore it until that changes rather than to invent work to fit it.
The companies that should act this month are narrower than the general advice suggests: those with more than one technology project they intend to put forward before April, and those at non-SMEs who previously assumed they were ineligible. Everyone else can read the official page once and move on.
Our expert take #3
The structural signal here is worth more than the money. Consolidating three schemes into one ceiling is a policy choice that rewards companies that can articulate a ranked plan over companies that opportunistically apply for whatever is available. That favours organisations with a real roadmap and a realistic view of their own delivery capacity. If reading this made you realise you cannot currently rank your own technology projects against each other, the grant is the least interesting thing you learned today.
What I Would Do This Week
- Check whether anything is mid-flight. Projects already submitted under the old schemes continue on their original terms. Confirm this before you redo any paperwork.
- Build the single ranked list. Every candidate project, expected qualifying cost, priority order, and a line where the cap runs out. This takes an hour and is the entire exercise.
- Add the capacity sentence to each one. Who delivers it, and what do they stop doing. Projects that fail this test should not be submitted.
- If you are a non-SME, re-check your eligibility assumptions. Up to 50% is now available where it previously was not.
- Work backwards from 1 April, not forwards from today.
If step three leaves you with a funded project and no one to build it, that is a solvable problem and a common one. Our guides to using Singapore job redesign grants alongside tech hiring and scoping backend development work cover the delivery side. For teams planning across the region, the Gulf picture is a useful contrast — our colleagues cover free zone versus mainland hiring structures in the UAE, where the binding constraint is regulatory rather than budgetary, and how worker classification works there.
Budget approved, team at capacity?
We place engineers in Singapore for scoped, time-boxed project work — and we will tell you honestly when your existing team can absorb it and you do not need us.
Discutons-en — brief our Singapore teamFrequently Asked Questions
What exactly happened to EDG, PSG and MRA on 29 September 2026?
The Enterprise Development Grant, the Productivity Solutions Grant and the Market Readiness Assistance grant all ceased on 29 September 2026, and the EDGE Grant commenced on 30 September 2026 in their place. EDGE consolidates support into a single programme spanning eight business areas and more than 150 activities, including automation and digitalisation, business strategy, financial management, innovation, internationalisation, standards and sustainability. Support runs up to 70 percent for SMEs and up to 50 percent for non-SMEs, under an annual cap of up to S$100,000 in total grant support per year across all activities, with the cap refreshing on 1 April. Ongoing applications and projects already submitted under the previous schemes continue under their original terms.
Why does a grant consolidation matter to an engineering leader rather than only to finance?
Because the single shared cap turns previously independent decisions into competing ones. Under the old structure a company could draw on different schemes for different purposes, so a software adoption project and an overseas expansion project did not directly take money from each other. Under EDGE there is one annual ceiling of up to S$100,000 across all activities, which means the internationalisation project and the automation project now sit in the same queue. Deciding which technology work is funded is therefore no longer a finance formality that happens after the roadmap is set. It is a sequencing decision that belongs in the roadmap conversation itself.
Does the EDGE Grant pay for hiring developers?
Enterprise Singapore grants of this kind are generally structured around qualifying project costs such as consultancy, solutions and implementation rather than being a subsidy for ordinary headcount salaries, and employers should confirm the exact qualifying cost categories for their intended activity with Enterprise Singapore before planning around them. The honest way to think about it is indirect rather than direct. Funded projects still have to be scoped, built, integrated and maintained, and that work either lands on your existing engineers or it requires capacity you do not currently have. A company that wins support for an automation project and has nobody to deliver it has converted a funding win into a delivery backlog.
What should a Singapore employer do before 1 April?
Treat the period from now until the cap refreshes on 1 April as one planning window rather than as business as usual. Work out which technology projects you intend to put forward, rank them against the single ceiling rather than against separate scheme budgets, and be realistic about delivery capacity for each one. The most common mistake I expect to see over the next two quarters is a company that successfully secures support for more initiatives than its engineering team can actually absorb, then spends the following year explaining why funded projects have not shipped. Capacity planning and funding planning now need to happen in the same meeting.
Sebastian
Mobile App & Hiring Expert at HireDeveloper.sg. Advises Singapore employers on scoping technology projects and the hiring plan required to deliver them.