EDGE vs EDG, PSG and MRA: What Singapore Businesses Should Do Now

Separate the application date from the project delivery date

The first sorting question is when the application was submitted. EDG, PSG and MRA ceased for new applications on 29 September 2026; EDGE opened the following day. An older approved project may still be running in October, and that does not make it an EDGE project. Its original approval remains the starting point for delivery, qualifying costs and claim preparation.

Create a register with the scheme name, application reference, submission date, approval status, project period and claim deadline. Add the internal owner and the location of the approval documents. This turns a confusing transition into a manageable list. Check the actual record rather than relying on a vendor's email subject line, which may continue using an old grant name out of habit.

For an unsubmitted proposal, review the current activity requirements before treating it as ready. A quotation drafted around EDG or PSG may need a different scope, evidence set or cost presentation for EDGE. Renaming the proposal is insufficient. Ask which assumptions were based on the old scheme and resolve them individually before the business commits.

Keep the commercial purpose while rebuilding the funding map

The old scheme labels provided a familiar shorthand. EDG was associated with transformation and capability building, PSG with supported productivity solutions, and MRA with overseas market development. These labels remain useful when discussing the history of a project, but they should not determine the conditions for new work after the transition.

Build the new funding map from the intended activity. Start with a sentence such as improving order accuracy, developing a strategy for a specific customer segment or assessing overseas partners. Then identify the relevant current scope and required outputs. This makes it easier to see whether several ideas belong to one activity or need separate applications.

Preserve the evidence that remains useful. A process map, a customer analysis or a carefully defined specification may still support the business decision. Revalidate the administrative assumptions around it, including vendor requirements, eligible costs, support rate and duration. Treat this as a structured review, not a reason to discard all earlier planning. The business need may be unchanged even though the route to support has moved.

Translate a PSG-style purchase into a deployment decision

A digitalisation project should begin with the work users need to perform. List the transactions, approvals, records and reports that currently cause friction. Then decide whether one function needs improvement or whether several functions must share consistent information. That distinction helps the company compare focused software with a wider integrated system.

The SMEs Go Digital ecosystem remains relevant to pre-approved digital solutions. IMDA's role in digital solution pre-approval should not be confused with blanket approval of a company's grant application. Check the selected solution and activity conditions, and confirm that the actual package quoted is the one being considered for support.

Also review what happens after installation. Who prepares the data, grants access, trains part-time users and resolves errors during the first month? Which existing subscriptions can be retired, and which must remain? A business moving from the PSG era to EDGE should use the transition to improve procurement discipline. Paying for an approved package is only the beginning; the value comes when staff can reliably complete the intended work using it.

Translate an EDG-style proposal into clear capability outputs

Businesses familiar with EDG may already have broad transformation proposals covering strategy, processes, organisation and technology. For current support, examine the specific EDGE activity and identify the output that the business will retain. A substantial proposal can still be too vague if it promises general growth without explaining what management or employees will be able to do differently.

Separate diagnosis from implementation. Diagnosis might establish why a margin problem exists; implementation might introduce pricing rules, a review process and a dashboard. Explain how each part contributes to the intended capability, then check which parts sit within the chosen activity. Do not assume every element of an old EDG proposal carries over unchanged.

For an illustrative service business, a useful output could be a consistent method for pricing complex jobs. The work might examine historical estimates, actual delivery effort and common exceptions, then develop an approval framework. The deliverable has practical meaning because the team can use it on future quotations. This is a stronger starting point than describing the project as a generic strategy transformation.

Translate an MRA-style plan into a specific market decision

Overseas expansion needs a target customer and route to market before it needs a grant budget. A business may be exploring distributors, attending a trade event or preparing local registration. These activities answer different questions. Keep the market objective explicit so that costs do not accumulate around an overseas trip without a credible follow-up plan.

For new applications, check EDGE internationalisation requirements directly. Historical MRA guidance, including its earlier market-based limits and activity allocations, should be used only in the correct legacy context. An old worksheet can be helpful for organising tasks while still being unsuitable for estimating current support.

Define what management will decide after the activity. A partner search could produce a shortlist assessed against distribution coverage, commercial fit, technical capability and conflicts. A trade event might test demand among a defined buyer group and generate qualified follow-up conversations. Establish who will act on the findings and how quickly. Grant support is most useful when the activity reduces uncertainty and enables the next commercial decision, rather than producing a collection of names with no owner.

Manage a shared grant budget across competing priorities

Under EDGE, the S$100,000 annual support cap is shared across activities, with a S$30,000 sub-cap for specified digital and equipment activities inside it. This makes portfolio planning more important. Different departments should not negotiate independently as if each were drawing from an unrelated scheme with its own untouched allowance.

Create a common list of candidate projects. For each, estimate the business value, total cash requirement, possible support, internal workload and earliest realistic start. Mark dependencies. If inventory information is unreliable, overseas sales expansion may increase service problems; an operational improvement could deserve priority even if a market opportunity appears more exciting.

Use a simple ranking conversation rather than an elaborate scoring model. Which project addresses the most costly constraint? Which is ready? Which unlocks another worthwhile initiative? Which becomes unattractive without optimistic grant assumptions? Record why management chooses the sequence. The grant balance is one constraint among several; leadership attention, implementation capacity and working capital may be the tighter limits. Do not spend merely because a support ceiling exists.

Keep old and new evidence apart without duplicating effort

Use separate project folders and expense references for legacy and EDGE work. A company can have both underway, but the team must be able to explain which approval covers each invoice and output. Shared supplier names or similar project titles make this discipline particularly important. Never seek support twice for the same project costs.

Maintain a central calendar containing the actual deadlines from each approval. Do not copy the claim timing of one scheme into another project. Add an internal preparation date ahead of each formal deadline so there is time to collect evidence, resolve invoice discrepancies and obtain any required verification. The person who monitors the calendar should have access to the relevant portal notifications.

Finally, update internal templates and vendor instructions. Old language can quietly reappear in board papers, cash forecasts and sales proposals. Label historical guidance with its scheme and period, and ask staff to confirm current requirements when starting new work. A clean transition preserves useful project planning while removing assumptions that no longer belong in a new application.

Frequently asked questions