EDG Proposal Structure That Survives First Review

Across the 100+ EDG projects I've advised Singapore SMEs on, the same thing happens almost every time: the owner spends two weeks on a beautifully designed proposal — 30 slides, custom diagrams, a deck their designer is proud of — and three days after submission, an email lands that reads like a templated rejection.

I've watched enough owners panic at that email to know it's the most misread moment in the whole process. It is not personal. It is not a rejection. It is the front-line officer telling you, politely, that they haven't read the proposal yet and need you to make their job easier.

This is the structure I've seen survive that first pass, distilled from advising on real EDG proposal applications. It is not how to write a beautiful EDG proposal. It is how to write the EDG proposal that gets read.

---

TL;DR — the 60-second version

1. The first email is almost always templated. Your assigned officer is usually a junior Assistant Trade Development Partner with an enormous case load. They send a template before reading. Do not panic.
2. Lead with two pages. Page 1 = cashflow capacity. Page 2 = financial benefit. Save the deck for round two.
3. Pre-validate against the PSG catalogue. If a PSG-eligible vendor already does what you propose to custom-build, EDG will route you back. Check vendors first.
4. Map the project to IDP Stage 2 or Stage 3 of your sector's Industry Digital Plan. Stage 1 builds get rejected because the government's push is to move SMEs to baseline Stage 2.

The full structure follows.

---

Why the first email looks like a rejection

Front-line EDG officers are typically junior Assistant Trade Development Partners. They are assigned a case load that is larger than they can read in detail, and the easiest move for them on the first pass is to send a templated clarification email — "please elaborate on the project rationale, expected outcomes, and capability uplift" — and let the applicant do the work.

If your EDG proposal structure triggers that template, you have not failed. You have been told: make my next read easier. The owners who win EDG are the ones who interpret that signal correctly and respond with a tight clarifying two-pager rather than re-sending the original deck with more diagrams.

This is also why a beautifully designed 30-slide pitch deck is almost always wasted effort at the proposal stage. Reviewers are not designers. They are looking for two things, and those two things fit on two pages.

---

The two pages that decide whether your proposal gets read

Page 1 — Cashflow capacity (can this company actually take on the project)

The officer's first question, never written down anywhere, is: "If we award this, can the company actually execute it?" If the answer is no, nothing else matters.

Demonstrate, on one page:

• Most recent annual revenue and gross margin
• Cash balance and any committed credit lines
• The grant rate you are applying under (50% SME / 30% non-SME)
• The full project cost AND your company's share of that cost in cash terms
• A one-sentence statement of where your 50% share comes from (working capital / shareholder loan / committed line of credit)

A reviewer who can see in 30 seconds that the company can fund its half of a S$200k project will move you to the next stage. A reviewer who has to dig for that number will send the template.

Page 2 — Financial benefit (does this project pay back)

The second question is: "Is the projected uplift credible against the project cost?" This is where most proposals over-engineer and under-deliver.

You do not need a 12-month financial model. You need:

• One sentence describing the function being transformed
• The current cost or revenue baseline for that function (with the source — last year's P&L, an internal report, etc.)
• The post-project target (with the assumption that produces it)
• The expected payback period as a single number, with a believable methodology

Reviewers see hundreds of these. They can spot a number that has been reverse-engineered to look good. Conservative assumptions with a clean trail beat aggressive assumptions with a fancy chart.

If the project does not have a clear financial benefit at all (e.g. pure R&D, pure capability build with no immediate revenue tie), be honest about it and frame the benefit in capability terms — but understand that EDG is harder to win on those terms.

---

The two unwritten rules every owner misses

These are the most common reasons an EDG proposal gets rejected on first reading, and almost nobody publishes them.

Rule 1 — EDG checks the PSG catalogue first

If a pre-approved PSG vendor already offers a solution similar to what you propose to custom-build, EDG will route your application back to PSG. This is the single most common silent rejection.

Before you scope an EDG project, check the PSG vendor directory honestly. If a vendor in the catalogue can deliver 80% of what you need, the right move is to apply for PSG on that and use EDG only for the 20% custom layer that wraps around it.

Rule 2 — EDG rejects IDP Stage 1 builds

Even if your custom solution is not in the PSG catalogue, EDG officers cross-check whether the functionality maps to Stage 1 of your sector's Industry Digital Plan (IDP). Stage 1 = basic digital adoption — POS, accounting, e-invoicing, basic CRM. The government's policy is to move SMEs from Stage 1 to baseline Stage 2 across all sectors.

If your build maps to Stage 1, EDG will not support it — even if it is technically custom — because the funding mechanism for Stage 1 is PSG and the GoBusiness catalogue. To get strong support, the proposal must demonstrate Stage 2 or Stage 3 functionality within your sector's IDP.

Stage 3 (the highest current tier in most sector IDPs) is where serious capability builds live: integrated data platforms, AI/ML-powered analytics, fully redesigned workflows that couldn't exist before the build. Scope your project there and the case becomes easier to make.

---

The proposal structure that survives first read

For most projects, this is the structure that lands cleanly:

Page	Section	What it answers
1	Cashflow capacity	Can the company fund its share?
2	Financial benefit	Does the project pay back?
3	Project scope (1 paragraph)	What are you building, in plain English?
4	IDP Stage mapping	Which IDP Stage 2/3 functions does this address?
5	Why not PSG	Why this can't be solved with a PSG-catalogue vendor
6	Vendor + consultant	Who is delivering it, why credible
7	Milestones + claim schedule	When the money moves

Seven pages, not thirty. Diagrams only where a sentence cannot do the same job.

When the officer is ready for the deeper deck, they will ask. Until they ask, a clean seven-page document outperforms a beautiful thirty-slide deck.

---

What to send when the templated reply arrives

When you receive the first templated clarification email, do not re-send the proposal with more decoration. Reply with a one-page email that:

1. Acknowledges the specific clarifications requested (even if the email reads generic)
2. Re-states the cashflow capacity number from page 1
3. Re-states the financial benefit and payback number from page 2
4. Adds the IDP Stage mapping if you didn't lead with it
5. Offers a 30-minute call to walk through any of these

The combination of (a) treating the templated reply as a normal step rather than a rejection, and (b) handing the officer a tight summary they can paste into their internal note, is what moves the application past the first gate.

---

The 3 most common ways EDG proposals die at first read

Death 1 — The project is actually PSG

Owner proposes a custom AI chatbot. The PSG catalogue has 12 pre-approved AI chatbot vendors. The proposal is silently bounced back. Fix: do the PSG check before you scope EDG.

Death 2 — The project is IDP Stage 1

Owner proposes a "custom POS with AI inventory." Functionality maps to IDP Stage 1 across most sectors. Rejected. Fix: scope upward — Stage 2 = integration across multiple data sources; Stage 3 = predictive or automated decision-making, not just digital basic operations.

Death 3 — The proposal reads like a wish list, not a project

"Improve productivity through AI" is not an EDG proposal. EDG funds projects with measurable outcomes against a defined scope. Fix: every claim must have a number, a baseline, and a methodology.

---

A note on choosing an advisor

EDG is consultant-led by design — Enterprise Singapore requires an appointed consultant for most projects, and the consultant fee is itself an eligible cost. But that does not mean every EDG advisor is worth what they charge.

Two things to look for before working with anyone:

1. PMC certification (or equivalent SAC certification under TR 43 / SS 680). This is the official Management Consultant certification recognised under the EDG framework — not all "AI consultants" hold it.
2. A demonstrated EDG track record in your sector. Ask them to walk you through two real projects — which IDP Stage they mapped to, and where the proposals nearly came unstuck.

If an advisor cannot answer those two in a 15-minute call, they haven't been close enough to the process.

For context on where I'm coming from: I hold PMC certification (PMC-10960), and I've advised on 100+ EDG projects across multiple sectors. I don't submit applications on anyone's behalf or work on success fees — what I do is advise owners on whether a project fits EDG at all, and how to shape it so it survives that first-pass review. If you want a 30-minute conversation to pressure-test your own project, message me. No charge for it.

---

Related reading

• PSG vs EDG vs CTC — which grant should you actually apply for? — the parent decision tree
• The MRA vs DTDi sequencing guide — the parallel piece for overseas expansion
• How to form a Company Training Committee in Singapore — when EDG + CTC are stacked
• /grants/edg — the canonical EDG landing page
• PSG Vendors Directory (593 approved) — the pre-check before any EDG proposal

---

Frequently Asked Questions

What happens if my EDG proposal gets the templated rejection email?

Don't panic — it's standard process. The front-line officer hasn't read your full deck yet. Reply with a one-page email restating your cashflow capacity and financial benefit figures, add your IDP Stage mapping, and offer a call. This tight summary is what moves you past the first gate. Avoid resending the full proposal with more slides.

Why does EDG reject proposals that seem to match PSG vendors?

Enterprise Singapore cross-checks the PSG vendor catalogue first. If a pre-approved vendor can deliver 80% of what you propose to custom-build, EDG will route you to PSG instead. Always check the PSG directory honestly before scoping an EDG project. You can stack both grants — PSG for the vendor layer, EDG for the custom 20% on top.

What's the difference between IDP Stage 1 and Stage 2, and why does it matter?

Stage 1 is basic digital adoption: POS systems, accounting software, e-invoicing, basic CRM. Stage 2 adds integration across multiple data sources. Stage 3 includes predictive analytics and automated decision-making. EDG prioritises Stage 2 and Stage 3 builds because government policy is to move SMEs from Stage 1 via PSG. If your project maps to Stage 1, it will be rejected — scope upward instead.

How many pages should my EDG proposal actually be?

Seven pages is the sweet spot: one on cashflow capacity, one on financial benefit, then sections covering project scope, IDP Stage mapping, why it's not PSG, vendor credibility, and milestones. Skip the 30-slide beautiful deck at proposal stage — the officer will ask for more detail once they've read the tight version.

What qualifications should an EDG advisor have?

Look for PMC certification (PMC-XXXXX) — this is the official Management Consultant credential recognised by Enterprise Singapore. Ask the advisor to walk you through two real EDG projects in your sector and explain which IDP Stage they mapped to. If they can't answer that in 15 minutes, they haven't been close enough to the actual process.