Building a Simple Internal Business Case for a Grant Project

Short answer: most owners never write anything down before pursuing support for a project. The chance appears, the project sounds worthwhile, and they move straight to the application without ever pausing to ask the harder question: is this project actually worth doing for our business, on its own terms, regardless of whether any help is available? The result is a lot of effort spent chasing projects that sounded good in the moment but were never really justified - projects taken on because support existed rather than because they earned their place. There is a simple discipline that prevents this: build a short internal business case before you do anything else, a plain, honest argument written for yourself about why this project deserves your business's time and money. This guide teaches how. It names no schemes and quotes no criteria or figures, because those are set officially and change - always confirm the current details on gobusiness.gov.sg.

A business case is for you, not the reviewer

The first thing to understand is who this document is for, and the answer is you - not anyone reviewing an application. A business case in this sense is not paperwork to submit or a box to tick. It is an honest argument you build for yourself to decide whether a project is worth doing at all. That distinction matters, because a case written to impress someone else tempts you to dress things up, to overstate the benefits and quietly shrink the costs, whereas a case written for your own eyes only has every reason to be brutally honest.

The whole value comes from that honesty, from a private document where you tell yourself the truth about what a project will really take and really give. Keep it internal, keep it candid, and treat it as a thinking tool rather than a presentation, because its job is to help you make a good decision, not to sell anyone on a decision already made.

Start with the problem, and define success

Every good business case starts not with the project but with the problem it is meant to solve - the specific weakness, gap, or opportunity in your business that makes this worth considering. Owners often fall in love with a solution first - a piece of equipment, a system, a shiny improvement - and then work backwards to justify it, which is exactly the wrong order. Start instead by naming the problem clearly: what is not working, what it is costing you, why it matters. Only then ask whether the project in question is genuinely the best way to solve it.

This keeps you honest, because a project that cannot be tied back to a real problem is one you probably do not need, however appealing it looks. When you lead with the problem, you naturally test whether the solution fits, and often discover either that the problem was not as pressing as you thought or that a simpler answer would do.

Then, before committing, force yourself to describe what success would actually look like, in concrete terms you could recognise later. Vague hopes that things will be better or more efficient are useless as a test, because anything can be called an improvement after the fact. Name what specifically will change, what your business will be able to do that it cannot now, and how you would know it worked. This sharpens your thinking before you start and gives you a genuine way to judge the result afterwards, rather than quietly declaring victory regardless of outcome.

Count the full cost - money and effort

When owners weigh a project, they usually look at the obvious price - the cost of the equipment or the service - and stop there. But the full cost of a project is almost always larger than its price tag. There is the time it will take from you and your people, time that has real value and is pulled away from other work. There is the disruption while the change beds in, the temporary dip in productivity as everyone adjusts. There are the ongoing costs that follow the initial outlay - maintenance, updates, the effort of keeping the new thing running.

A business case that counts only the upfront price flatters the project and sets you up for unpleasant surprises later. Count the full cost honestly - the money, the time, the disruption, and the ongoing burden - because only against the true total can you judge whether the benefit is really worth it, and working through how to budget a supported project properly is the discipline that keeps the hidden costs from ambushing you.

Effort deserves its own attention, because it is the resource small businesses most consistently underestimate. Every project competes for the same limited pool of attention that keeps the business running, and one that looks affordable in money can still be ruinously expensive in effort. Be honest about who will actually do the work, how much of their time it will take, and what will not get done while they are doing it. Owners routinely assume projects will run on spare capacity that does not really exist - and effort, not money, is usually the real constraint.

Weigh it against doing nothing, and against going wrong

A good business case always includes a comparison people instinctively skip: the option of doing nothing at all. It is tempting to weigh a project only against other projects, or to assume that because a problem exists something must be done, but the honest baseline is always to ask what happens if you simply carry on as you are. Sometimes the answer reveals that the problem, while real, is tolerable, and the business would be better off leaving things alone and putting its limited energy elsewhere.

Other times it confirms that doing nothing carries a genuine cost - that the problem will grow or the opportunity will pass - which strengthens the case for acting. Either way, comparing against doing nothing keeps you honest about whether the project is truly necessary or merely attractive, and knowing when it is better not to apply at all is the same honesty pointed at the whole decision.

You should also spend a moment on the uncomfortable question of what happens if the project does not work out as hoped. Ask what could go wrong, how likely it is, and crucially how much it would hurt if it did, because a project whose failure would be a minor disappointment is very different from one whose failure could seriously wound the business. This does not mean avoiding all risk, which would mean never improving anything; it means going in with your eyes open and making sure the possible downside is one your business could survive. That is what separates a considered decision from a hopeful gamble dressed up as a plan.

Keep it short and plain

A business case for a small business should be short and plain - a page or two of clear thinking, not a thick document full of impressive language and elaborate projections. The purpose is to help you think and decide, and a bloated case actually works against that, burying the few things that matter under a pile of detail that creates false confidence without adding real insight. Write it in plain words, as if explaining to a sensible friend why this project is worth doing, and if you cannot make the argument simply, that is usually a sign the argument is not yet clear in your own mind.

Keeping it short also means you will actually do it, whereas a demand for something elaborate guarantees you will skip the whole exercise and go back to deciding on gut feel. A simple, honest page you actually write beats a sophisticated case you never get around to.

Decide before support enters the picture

The crucial discipline is to reach your decision about whether a project is worth doing before you let any thought of support enter the picture. Build your case, weigh the costs against the benefits, compare against doing nothing, and decide whether the project earns its place purely on its own merits. Only once you have decided the project is genuinely worth doing should you then ask the separate question of whether any help might be available to make it easier.

Doing it in this order protects you from the most common trap - letting the availability of support talk you into a project you would never have chosen on its own. When the decision comes first and the funding second, support can only ever improve a project you already wanted, never conjure one you did not. A sound project becomes even better if help happens to be available; but if the only thing that turns a project from not worth it into worth it is the presence of support, then it was never really justified. Your business case is exactly the test that catches this, and it feeds naturally into a clear-headed go or no-go decision once all the pieces are in front of you.

Because what is available shifts continually, anything you assume today about what might support a particular project is only a guess - another reason to build your case on the project's own merits. When you have decided a project is worth doing and want to check whether any help exists, that is the moment to go to gobusiness.gov.sg and see what genuinely applies then.

Frequently asked questions