Developing a project business case is the practical bridge between a project idea and the funding decision. For a funding application, your business case must prove three things clearly: need, feasibility, and value for money—all supported by evidence and realistic financials. In South Africa, where funders often assess risk, compliance, and sustainability, a well-structured business case can be the difference between “insufficient information” and “approved to proceed.”
This study guide focuses on the end-to-end process of creating a business case suited to funding applications for small businesses and entrepreneurs—written to align with how learners are assessed in common South African project management and finance modules (including UNISA-style project planning and funding justification content), while also reflecting realistic grant/loan scrutiny.
1) Understanding the Funding Business Case: Purpose, Audience, and Decision Criteria (UNISA/PM basics for small businesses)
A business case is not just a narrative. It is a structured argument—supported by data, assumptions, and calculations—that explains why a project should receive funding and how it will deliver outcomes.
What a funding authority expects
In most South African funding contexts (municipal grants, national development programmes, sector funders, bank lending committees, incubators, CSR funds, and blended finance schemes), reviewers evaluate your proposal using a consistent logic:
-
Problem / Need
- What market gap, service gap, or operational constraint exists?
- Who is affected and how many?
- Why is your solution necessary now?
-
Solution / Scope
- What exactly will be done (deliverables)?
- What is in scope and out of scope?
- How will the project be implemented?
-
Feasibility & Capacity
- Do you have the capability (team, partners, systems)?
- Are inputs obtainable (equipment, suppliers, approvals)?
- What are the realistic timelines?
-
Financial viability & value for money
- Do the financials add up?
- Is the requested amount justified?
- What are costs vs benefits over time?
-
Risk management
- What could go wrong?
- How will you mitigate key risks (cash-flow, demand shortfalls, regulatory delays, procurement issues)?
-
Sustainability & impact
- After funding ends, will the project continue?
- What measurable outcomes will be delivered?
- Are there social or economic benefits (jobs, skills, enterprise development, local procurement)?
A funding business case that fails at any one of these points typically fails to progress to due diligence.
Business case vs project proposal vs feasibility study
Learners often confuse three documents used in the project lifecycle:
- Project proposal: a persuasive “pitch” summarizing what you want to do and why. It may include a rough budget but is often lighter on rigorous financial logic.
- Feasibility study: a technical and market deep-dive assessing whether the project is viable (demand, technical options, site analysis, operations).
- Business case: a decision document that combines feasibility evidence with justification for funding. It usually includes governance, costs, benefits, financial models, and risk.
For funding applications, your business case usually needs to behave like an “investor-grade decision memo” even if your format stays simple.
Common South African contexts for small business funding
South African funding applications vary, but small-business business cases typically target one or more of the following:
- Working capital to stabilize trading, reduce stockouts, or fund production cycles
- Equipment or capex funding to increase capacity or quality
- Expansion projects (new premises, new product lines, new service offerings)
- Formalization and compliance (registration, certification, systems)
- Green or energy-efficiency projects (solar, efficiency upgrades)
- Skills and employment creation (training programmes linked to deliverables)
Your business case must match the funder’s objective. For example, a grant aimed at job creation expects stronger employment and training detail than a bank loan focused primarily on repayment capacity.
Audience-specific writing: who reads what
Funding reviewers differ in what they prioritize:
-
Finance committee / credit committee focuses on numbers:
- affordability, repayment, cash-flow realism
- justification of costs and budgets
- controls and monitoring
-
Programme manager / grant assessor focuses on outcomes:
- measurable benefits and evidence of need
- governance, reporting, compliance readiness
-
Technical reviewer focuses on implementation:
- whether activities can be delivered
- whether procurement and vendor capability exists
- technical risks and timelines
To satisfy all, structure your business case so each section answers the likely questions of at least one reviewer type.
“Evidence-based” assumptions (and why they matter)
A business case is full of assumptions: market demand estimates, unit costs, uptake rates, cost of capital, staff productivity, delivery timelines. If assumptions are vague, the reviewer may assume the risk is high.
Your goal is to create assumption traceability:
- Where did the demand estimate come from?
- How did you estimate costs (quotes, supplier rates, historical invoices)?
- What did you base timelines on (vendor lead times, procurement periods)?
- How will you validate results?
Funders often reward proposals that show learning capability: plans for monitoring, validation, and corrective action if early indicators fail.
Case example: small business requesting R750,000 for a production upgrade
Imagine a small manufacturer in Gauteng applying for R750,000 to buy packaging machinery and fund installation. The funder asks:
- How does this R750,000 change output?
- What is the payback period?
- Can the business maintain quality and supply chain continuity?
- What risks exist (supplier delays, machine downtime, market demand)?
- What jobs will be created or sustained?
A weak business case might only say “we will grow.” A strong business case links:
- outputs (units packaged per hour)
- outcomes (increased sales to specific customers)
- financials (incremental margin and cash-flow)
- risk plan (maintenance schedule, backup supplier, lead-time buffers)
- measurement (weekly output KPIs, customer acceptance testing)
Mini-exam style checklist (use during study and before submission)
Use this checklist to self-audit readiness for funding applications:
- Problem/need is supported by data (surveys, invoices, order history, market research)
- Target beneficiaries are described clearly (numbers and location)
- Project scope lists deliverables (what will be delivered by whom)
- Implementation plan shows timeline and dependencies
- Costs are itemized with credible basis (quotes, historical cost, supplier rates)
- Financial model is coherent (revenue, costs, cash-flow, break-even logic)
- Risks are mapped with mitigation actions and owners
- Monitoring and reporting plan exists (KPIs, reporting frequency)
- Sustainability plan explains continuity after funding ends
This structure is repeatedly reflected in university-level assessments for project planning, business justification, and practical finance reasoning.
2) Building Blocks of a Strong Business Case: Problem, Objectives, Scope, and Benefits Logic (linking to UNISA-style project planning components)
Once you understand what a business case must achieve, the next step is building the content in a way that naturally answers funding questions. This section focuses on the “logic” behind good proposals: how you move from need to objectives, scope, and benefits.
The benefits logic: from outputs to outcomes to impact
A common weakness in proposals is confusing outputs and outcomes.
- Outputs are what you deliver:
- a machine installed
- a training programme completed
- a website launched
- a new store opened
- Outcomes are changes resulting from outputs:
- increased production capacity
- reduced customer delivery delays
- higher conversion rates
- improved customer retention
- Impact is the longer-term effect:
- employment sustained
- improved local economic resilience
- reduced environmental harm
- improved access to services
Funders want to see a “cause-and-effect chain” supported by a plan and measurable indicators.
Defining the problem with precision
A strong “problem statement” avoids generic phrases like “there is a need” without data. Instead, use a structured approach:
- Current situation
- What is happening today?
- How do customers/customers experience the problem?
- Evidence of the problem
- What data demonstrates the gap?
- Orders lost? Long queues? Stockouts? Revenue leakage?
- Root cause
- Why is the problem occurring?
- Consequences of not acting
- What will worsen if funding is not secured?
Example problem statement (production capacity constraint)
- Current situation: customer orders exceed current packaging speed; orders wait 7–10 days.
- Evidence: 12 orders delayed in the last 3 months; average penalty costs of R1,200 per order; lost repeat orders.
- Root cause: packaging line capacity is limited; manual packing creates bottlenecks.
- Consequences: recurring penalties, customer churn risk, and inability to accept larger contracts.
Notice the measurable specifics; they become the foundation of your benefits.
Objectives that can be measured
In funding applications, objectives must be SMART:
- Specific
- Measurable
- Achievable
- Relevant
- Time-bound
For a project, you typically need:
- 1–3 strategic objectives
- several operational objectives linked to deliverables
Example objectives for the machinery project
- Strategic objective: Increase packing throughput to reduce customer delivery delays.
- Operational objectives:
- Install and commission packaging machinery by 30 September 2026
- Reduce average order turnaround time from 7–10 days to 3–5 days within 6 months after commissioning
- Achieve at least 20% increase in monthly packaged units by March 2027
- Reduce penalties associated with late delivery by at least 60% by December 2026
These objectives become your KPIs later.
Scope management: what is included and excluded
Funding reviewers may question whether the request is too broad or unclear. A good scope section prevents “scope creep” and shows you understand delivery constraints.
Use scope statements such as:
- In scope
- machine purchase
- installation and testing
- operator training
- maintenance plan creation
- safety compliance checks
- Out of scope
- new facility construction
- unrelated product redesign
- hiring additional sales staff (unless justified elsewhere)
When you exclude items, explain why they are excluded:
- timeline constraints
- funding amount limitations
- planned as separate phase
Benefits mapping: financial and non-financial
Benefits should be both:
- quantitative (financial value, throughput, cost savings)
- qualitative (customer satisfaction, compliance capability, resilience)
Quantitative benefits examples
- Cost reduction from lower penalties due to improved delivery times
- Margin increases from higher production and ability to accept more contracts
- Reduced waste from better packaging quality
- Revenue increase due to higher capacity to meet demand
Qualitative benefits examples
- Better customer relationships due to reliable delivery
- Improved worker skills through training
- Improved safety and compliance environment
Value for money: what makes the request “worth it”
Value for money is not only “cheapest option wins.” It’s:
- outcomes achieved relative to costs
- ability to justify each expenditure item
- consideration of alternatives
In your business case, show that you considered at least two option routes:
- Do nothing / maintain current system
- Alternative investment / alternative vendor / lease vs buy
- Requested solution
Even if you select one option, reviewers expect evidence you evaluated alternatives.
Logic model (a clean, funding-friendly structure)
A logic model ties your project narrative into a consistent framework. Here’s a text version you can replicate in your application:
- Inputs: funding (R750,000), staff time, vendor support
- Activities: procure, install, train, commission; develop maintenance and quality processes
- Outputs: packaging machinery operational; staff trained; SOPs in place
- Outcomes: reduced turnaround time; higher throughput; reduced penalties
- Impact: sustained customer retention; increased job stability
In the next step, you will quantify these where possible.
Case example: mapping benefits to measurable KPIs
Assume the machinery project targets:
- Current: 7–10 days turnaround, 12 delayed orders in last 3 months
- After: 3–5 days turnaround and fewer delays
Your KPIs might include:
- Weekly average turnaround time
- Number of delayed orders per month
- Monthly packaged units
- Late delivery penalty costs
- Machine uptime percentage
- Training completion rates and competency test outcomes
Funders like measurable KPIs because they can verify progress during monitoring.
Common counter-arguments funders raise—and how to pre-empt them
Funders may question:
- “Will demand exist to use increased capacity?”
Pre-empt with customer pipeline evidence, contract commitments, or letters of intent. - “Is the budget realistic?”
Pre-empt with itemized costs based on quotes and historical invoices. - “What if the machine breaks down?”
Pre-empt with warranty details, maintenance plan, spare parts readiness. - “Can you deliver within the proposed timeline?”
Pre-empt with lead-time evidence and procurement steps.
If you build these counter-arguments into the business case proactively, reviewers encounter fewer uncertainties.
3) Financial Case Development: Costs, Funding Use, and Coherent Financial Model (with a worked example for applications)
The financial case is often the highest-stakes part of a funding application. A reviewer may forgive a weak narrative but rarely forgives incoherent calculations. Your financial case should show that the requested funds are:
- correctly scoped
- costed with credible assumptions
- linked to outcomes
- manageable in terms of cash-flow and sustainability
This section provides both guidance and a fully worked financial example you can adapt.
What to include in the financial case
A comprehensive funding financial case commonly includes:
- Budget summary (total project cost and requested amount)
- Budget breakdown (line-item costs with basis)
- Funding structure (how much requested, co-funding, equity, in-kind contributions)
- Financial model assumptions (revenue drivers, cost drivers, timelines)
- Cash-flow impacts (timing of inflows/outflows)
- Affordability metrics (break-even, payback, DSCR for loans where relevant)
- Sensitivity analysis (best/base/worst scenarios)
- Monitoring of financial performance (how you track deviations)
The budget: move from “amounts” to “justified line items”
A budget is not a list of expenses; it is a cost logic.
Use a budget table with:
- cost category
- description
- quantity/units
- unit cost
- subtotal
- basis (quote number, supplier reference, historical average, estimate method)
- payment timing (important for cash-flow planning)
Example budget logic for the R750,000 project
Let the project request be R750,000 for packaging machinery upgrade. A plausible itemization might be:
- Packaging machinery purchase
- Installation and commissioning
- Safety compliance and testing
- Operator training
- Spare parts and maintenance supplies for first year
- Contingency (typically a percentage to cover uncertainties)
To keep consistency across the model, you must define specific amounts. The next subsection provides a complete example budget and financial model.
Worked example: building a coherent 12-month financial model
Assume the business currently earns revenue of R2,500,000 per month and has packaging as a bottleneck. After commissioning machinery, it expects incremental improvements.
To make the example concrete and usable for study, we model only the incremental changes and present a simplified view of profitability impact.
Step 1: Define the baseline and incremental effects
Baseline (before project):
- Monthly packaged units: 50,000 units
- Average selling price: R1.50 per unit
- Variable cost per unit (materials/labour/packaging inputs): R0.95 per unit
- Monthly fixed costs (rent, administration, overhead): R1,000,000 per month
- Average late delivery penalty costs: R12,000 per month (based on 12 orders delayed in last 3 months: 12/3 = 4 per month; at R3,000 average penalty each = R12,000; keep consistent)
Incremental impact after commissioning:
- Monthly packaged units increase by 20%: from 50,000 to 60,000 units
- Penalty costs reduce by 60%: from R12,000 to R4,800 per month
- Variable cost per unit increases slightly due to more packaging consumables: new variable cost per unit becomes R0.98 (an increase of R0.03 per unit), reflecting modest additional inputs.
Step 2: Calculate incremental revenue and costs after commissioning
After commissioning (assume steady state for the year):
- New monthly revenue = 60,000 units × R1.50 = R90,000
- Baseline monthly revenue = 50,000 × R1.50 = R75,000
- Incremental revenue = R15,000 per month
Variable cost after commissioning:
- New monthly variable cost = 60,000 × R0.98 = R58,800
Baseline variable cost: - 50,000 × R0.95 = R47,500
Incremental variable cost = R11,300 per month
Penalty reduction:
- Penalties decrease by R12,000 − R4,800 = R7,200 per month savings (treated as reduction in costs)
Incremental contribution margin per month:
- Incremental revenue − incremental variable cost + penalty savings
= R15,000 − R11,300 + R7,200
= R10,900 per month
So, the project yields incremental profit contribution of approximately R10,900 per month, excluding tax and ignoring any one-off costs.
Important study point: This simplified model isolates packaging-driven changes. In a real financial model, you would integrate the full P&L and cash-flow, but the incremental method helps you avoid double-counting and keeps the logic transparent.
Step 3: Include timeline effects (construction/commissioning months)
Assume:
- Installation and commissioning complete by 30 September 2026.
- Deliverables begin generating incremental benefits from October 2026 onward.
Then:
- Months with no incremental benefits: June, July, August, September 2026 (if commissioning finishes end of September).
- Incremental benefit months in a 12-month horizon starting June 2026: October 2026 to May 2027 inclusive = 8 months.
Total incremental profit impact over the period:
- R10,900 per month × 8 months = R87,200
Step 4: Compare the financial return against the requested R750,000
From this simplified model, incremental profit impact R87,200 over 8 months is far smaller than R750,000. If this were the full financial story, the payback would be very long and could cause funding rejection—unless there are additional benefits (for example, winning larger contracts, improved customer retention leading to higher base revenue beyond the packaging segment, or reduction in variable costs due to efficiency).
In real funding applications, your incremental model must reflect the true value driver. For the purpose of study, this example demonstrates a key lesson:
If your business case asks for R750,000, your model must show credible, scaled benefits that match the funding size.
So we adjust the example to include a realistic additional revenue effect: increased capacity enables acceptance of larger contracts and stabilizes recurring orders rather than only shifting existing production.
Revised worked example: incorporate a larger demand/contract effect
Assume that improved delivery performance allows the business to:
- secure additional monthly orders worth extra revenue beyond the packaging segment.
Let’s define this as an additional “capacity-related revenue uplift” of R200,000 per month starting October 2026, with a gross margin of 40% after variable costs (i.e., contribution margin = 40% of added revenue).
Additional monthly contribution margin from contract uplift:
- R200,000 × 40% = R80,000 per month
Now combine with penalty savings and any incremental margin from unit change (to avoid double-counting, we treat the earlier unit/price changes as part of the capacity uplift rather than separate). To keep consistency, we’ll simplify:
- Treat the total incremental contribution margin after commissioning as:
- penalty savings component and capacity uplift integrated into an overall incremental contribution margin of R90,900 per month (R80,000 uplift contribution + R10,900 from earlier incremental packaging logic), but only if those elements don’t overlap.
To prevent overlap, set the contract uplift contribution to exclude penalty savings already counted. We already counted penalty savings as R7,200. If the uplift contribution includes only normal operations and not penalties, we can add both safely.
So:
- Incremental contribution margin from capacity uplift: R80,000
- Incremental contribution margin from packaging bottleneck relief (including variable change logic): we computed R10,900 as net effect including penalties. To avoid overlap, we need clarity.
Simpler approach:
- Use only the net incremental number including penalties as the contribution from the machinery effect.
- Therefore, set total incremental contribution after commissioning to R10,900 per month and separately add contract uplift that is purely revenue-side with no penalty component.
Thus total contribution margin:
- Capacity uplift contribution: R80,000 per month
- Net packaging logic contribution: R10,900 per month
- Total: R90,900 per month
Total over 8 months:
- R90,900 × 8 = R727,200
Now compare:
- Requested amount: R750,000
- Incremental contribution over 12-month horizon: R727,200
This yields a near break-even level over the period, which is plausible for a funding justification.
One-off costs and cash timing
Real models also include:
- initial deposit for machinery
- installation payments
- training costs upfront
- working capital increase due to purchasing consumables and inventory
In a funding application, you must reflect cash timing even if the P&L break-even looks good.
Assume the R750,000 spending schedule:
- June 2026: R150,000 deposit
- July 2026: R300,000 machinery delivery/install
- August 2026: R200,000 remaining install and safety testing
- September 2026: R100,000 training, spare parts, commissioning
Total = R750,000
Then cash outflows happen before revenue uplifts start October 2026. This matters for whether the business can survive the pre-benefit months. A cash-flow model can show that the business needs bridging support or co-funding to cover the gap.
A simple cash-flow narrative (what reviewers look for)
Even without full spreadsheets, reviewers want assurance:
- the business can fund interim outflows
- revenue increase starts on a realistic date
- any working capital needs are planned
For the example:
- If revenue uplift begins October 2026, but outflows peak June–September, the funder may require evidence of existing cash reserves or co-funding to cover the gap.
Budget narrative: linking each cost to deliverables
Cost category linkages:
- Packaging machinery purchase (major capex)
Links to output: operational packaging line. - Installation and commissioning
Links to output: tested and compliant machinery. - Safety compliance and testing
Links to output: legal compliance and safe operations. - Operator training
Links to output: staff capable of running and maintaining machinery. - Spare parts and maintenance supplies (first year)
Links to risk mitigation: reduce downtime. - Contingency
Links to risk: cover small uncertainties without halting project progress.
This prevents a common reviewer reaction: “Why do you need this spend category?”
Sensitivity analysis: planning for uncertainty
Funders expect some scenario thinking. Provide:
- Base case (your main assumptions)
- Downside case (lower demand, delayed commissioning, higher cost)
- Upside case (faster ramp-up, higher contract uptake)
Define sensitive drivers:
- Commissioning delay (e.g., 1 month late)
- Contract uplift revenue lower by 20%
- Penalty reduction lower by 30%
- Variable cost per unit higher by R0.03
Illustration:
- If commissioning is 1 month late, benefits reduce from 8 months to 7 months.
- If contract uplift contribution drops from R80,000 to R64,000 per month (20% drop), total contribution decreases accordingly.
Even a simple sensitivity table demonstrates control.
Value for money: cost per outcome indicator
Sometimes funders appreciate “unitized value” metrics:
- cost per installed and commissioned capability
- cost per month of incremental contribution
- cost per job created (if jobs are part of outcomes)
If your business case includes job outcomes, show cost-effectiveness:
- cost per job created = R750,000 / number_of_jobs_created
You must use a consistent job number throughout (see next section for governance and monitoring).
4) Implementation, Governance, Risk, and Monitoring: Turning the Business Case into a Deliverable Plan (risk controls aligned to small enterprise realities)
A business case is judged not only on why you want funding but also on how you will manage delivery and protect the funder’s investment. This section focuses on implementation planning, governance structures, risk management, and monitoring systems—key areas in project management modules and funding due diligence.
Implementation plan: activities, milestones, dependencies
A strong implementation section uses milestones aligned to funding drawdown and measurable deliverables.
For the machinery example, assume this timeline:
- June 2026: deposit paid; procurement order placed
- July 2026: delivery and installation commence
- August 2026: safety checks; operator training planning; testing begins
- September 2026: commissioning and final acceptance tests
- October 2026: full operational ramp-up; KPI tracking begins
- Monthly: reporting to funder
- December 2026: mid-term results review
- May 2027: final reporting and sustainability plan check
In your application, milestones should map to:
- drawdown dates
- evidence required (invoices, acceptance certificates, training registers)
- operational readiness checks (SOPs in place)
Governance: who owns delivery and who reports
Funding bodies often require clarity:
- project owner (accountable)
- project manager (day-to-day)
- finance administrator (budget control)
- technical lead (specification and acceptance)
- procurement role (vendor management)
- monitoring and reporting officer
For small businesses, roles can be held by the same people, but the accountability must be explicit.
Example governance arrangement:
- Project Owner: CEO / business owner (accountable for outcomes and approvals)
- Project Manager: operations manager (schedules, vendor coordination, milestone tracking)
- Finance Coordinator: bookkeeper/accountant (budget tracking, drawdown documentation)
- Technical Lead: production supervisor (acceptance testing, SOP development)
- HSE/Compliance Contact: safety officer (or trained representative)
Even if you keep it short, show a reporting line and decision-making process.
Procurement and vendor management: reducing delivery risk
One of the biggest risks in delivery projects is vendor performance and delays. Mitigate with procurement controls:
- Request quotes from at least two suppliers where possible
- Evaluate:
- lead times
- warranty terms
- installation support scope
- training inclusion
- Include acceptance criteria:
- performance test acceptance
- documented commissioning sign-off
- Define payment milestones tied to delivery stages
For a funding application, show that payment is linked to progress:
- deposit after order confirmation
- installment after delivery and installation
- final payment after acceptance testing
Risk management framework: register, severity, mitigation
A risk register is essential. It should list:
- risk description
- likelihood (Low/Medium/High)
- impact (Low/Medium/High)
- severity rating
- mitigation actions
- owner
- early warning indicators
For example risks:
-
Delayed commissioning
- Likelihood: Medium
- Impact: High (revenue uplift starts later)
- Mitigation: buffer lead time; track vendor schedule weekly; escalate early.
- Early warning: installation not on track by mid-August.
-
Machine downtime
- Likelihood: Medium
- Impact: High
- Mitigation: warranty usage; spare parts; preventive maintenance schedule; operator competency training.
- Early warning: uptime below 90% in first two months.
-
Demand shortfall / inability to use capacity
- Likelihood: Low to Medium (depending on evidence)
- Impact: Medium to High
- Mitigation: customer pipeline validation; contract letters; flexible scheduling.
- Early warning: sales order intake below forecast for first 6 weeks.
-
Cost overrun
- Likelihood: Medium
- Impact: Medium
- Mitigation: contingency (built into budget); fixed-price contract for installation where possible.
- Early warning: spending variance > 5% by end of August.
-
Compliance/safety issues
- Likelihood: Low
- Impact: High
- Mitigation: certified installer; documented safety testing; compliance sign-off before operations.
- Early warning: missing documents before commissioning week.
Funders want to see that risks are anticipated with response strategies.
Monitoring and evaluation (M&E): KPIs and reporting cadence
Your business case must include how you will measure progress. For funding applications, typical reporting cadence might be:
- monthly progress report
- quarterly financial report
- milestone-based evidence submissions
- mid-term and final evaluations
KPIs for the example project:
- Output KPI: machine uptime percentage
- Delivery KPI: average order turnaround time
- Quality KPI: packaging defect rate (e.g., % rework)
- Commercial KPI: monthly orders fulfilled (or revenue from increased contract uplift)
- Financial KPI: penalty costs and variance vs budget
- Operational KPI: training completion and competency sign-off
A simple KPI table can clarify:
| KPI | Target | Measurement | Frequency | Evidence |
|---|---|---|---|---|
| Machine uptime | ≥ 90% | uptime logs | Weekly/Monthly | maintenance log |
| Avg turnaround time | 3–5 days | order tracking | Monthly | ERP/order system report |
| Delayed orders | Reduced | delay register | Monthly | incident log |
| Penalties | ↓ 60% | penalty ledger | Monthly | finance report |
| Training completion | 100% of operators | training register | One-time + confirmation | signed attendance |
Your targets should align with earlier objectives:
- reduce turnaround from 7–10 days to 3–5 days
- reduce penalties by 60% (from R12,000 to R4,800 monthly)
Data quality and reporting credibility
If you claim targets, you must show how data is reliably collected:
- order tracking system
- finance ledger for penalties
- machine logs
- training records
Weak data undermines credibility. A reviewer may ask: “How do we know the machine uptime is real?”
Sustainability plan: what happens after funding ends
Sustainability is often misunderstood as “the business will keep going.” Funding bodies expect more specific mechanisms:
- Maintenance costs budgeted after year 1
- Preventive maintenance schedule owned by operations
- Spare parts procurement plan
- SOPs and training refresh plan for new operators
- Customer relationship management plan to preserve contract uplift
If funding ends at project completion, show how operational budgets absorb ongoing costs.
Governance risk counter-arguments and responses
Typical reviewer questions:
- “What if the project owner changes roles?”
Response: documentation and continuity plan, including SOPs and reporting templates. - “How will you ensure funds are used for intended purpose?”
Response: procurement controls, expense categories, and approval workflow; keep invoices and evidence. - “What if KPIs do not hit targets by month 3?”
Response: root cause analysis process and corrective action plan (vendor troubleshooting, production scheduling changes, customer pipeline adjustments).
5) Writing the Business Case for Funding Applications: Structure, Style, Evidence, and Common Failure Points (tailored to SA learners and UNISA-style assessments)
Even if your business case content is strong, the submission can still fail due to weak presentation. This section focuses on writing quality, document structure, evidence packaging, and typical reasons funding applications are rejected. It also includes practical templates and guidance for aligning with expected academic/project management assessment expectations.
Document structure that matches reviewer logic
A funding application business case should be structured so reviewers can “find answers fast.” Use headings and consistent numbering.
A strong structure includes:
- Executive summary (1–2 pages)
- Project background and problem statement
- Objectives and expected outcomes
- Scope and deliverables
- Implementation plan and timeline
- Budget and financial case
- Risk management and mitigation
- Governance and capacity
- Monitoring and reporting plan
- Sustainability plan
- Appendices (quotes, letters, supporting documents, CVs)
Even if the funder provides a form, adapt your narrative to the sections above.
Executive summary: what must be included
The executive summary is often read first. It must include:
- Project title and location (use consistent location throughout)
- Funding amount requested and funding period
- The problem and who it affects
- The core solution (deliverables)
- The outcomes and KPIs
- The financial justification (summary of key numbers)
- Risk controls summary
- Sustainability statement
For the example project, an executive summary might include:
- “Requesting R750,000 to purchase, install, and commission packaging machinery, completing commissioning by 30 September 2026.”
- “Expected outcomes: reduce average order turnaround from 7–10 days to 3–5 days, reduce monthly penalties from R12,000 to R4,800 (a 60% reduction), and deliver incremental contribution of approximately R727,200 over October 2026–May 2027.”
- “Governance: monthly reporting, machine uptime KPI tracking, and documented acceptance tests.”
These numbers must match what appears in later sections.
Writing style: concise, evidence-based, and numeric
Avoid:
- vague statements (“we will improve efficiency”)
- unquantified claims (“significant growth”)
- over-technical language that hides key meaning
Use:
- short paragraphs
- bullet lists for deliverables and KPIs
- tables for budgets and cost breakdowns
- consistent terms for projects, timelines, and targets
Consistency matters: if you say commissioning completes by 30 September 2026 in the executive summary, the implementation plan and financial model must also assume the same timing.
Evidence packaging: appendices that increase approval probability
Strong evidence reduces reviewer uncertainty. Useful appendices include:
- supplier quotes (machine price, installation scope, lead time)
- letters of intent or customer demand evidence
- historical sales reports demonstrating capacity bottlenecks
- penalty ledger showing past late delivery penalties
- maintenance and training plan documents
- CVs of project leaders
- proof of registrations or compliance readiness
Even if appendices are not required, they often help in due diligence.
Common failure points in funding business cases
Funding rejections often come from avoidable problems:
-
Budget mismatch
- Requested amount does not match line items.
- Contingency is included without justification.
-
Unrealistic timelines
- Commissioning promised earlier than vendor lead times.
- Procurement plan ignores required lead time.
-
Vague benefits
- No measurable outcomes or no evidence that outputs lead to outcomes.
-
Incoherent financial model
- Revenue uplift does not align with operational capacity changes.
- Penalties reduction not reflected in costs.
-
No risk controls
- Risks are listed but no mitigation actions or owners.
- No monitoring plan for early warning indicators.
-
Sustainability missing
- Operations cannot continue after funding ends.
- Maintenance costs not budgeted.
Templates you can replicate (study and adapt)
Below are templates you can use as study aids or to draft your own submission.
Template: logic statement format
Use:
- We will [deliverable]
- to achieve [outcome]
- measured by [KPI]
- by [date].
Example:
- “We will commission the packaging machinery by 30 September 2026 to reduce average order turnaround from 7–10 days to 3–5 days, measured by order tracking KPIs monthly.”
Template: budget line item description
For each line item, include:
- What it buys
- Why it is required
- Basis for cost (quote/historical)
- Timing within the project
- Evidence to be provided
Template: risk register row
Use:
- Risk: delayed commissioning
- Likelihood/Impact: Medium/High
- Mitigation: weekly schedule tracking and escalation
- Owner: project manager
- Early warning: installation behind by mid-August.
Integrating academic expectations into funding writing
South African university coursework in project management often rewards:
- clear structure
- logical linking of components
- realistic assumptions
- identification of risks and controls
- evidence of stakeholder alignment
Even though a funding application is practical, those academic assessment principles still apply. Your business case should demonstrate “project management thinking”:
- integration of scope, schedule, cost, risk, and monitoring
Mini case study: why similar proposals succeed vs fail
Consider two hypothetical submissions for the same R750,000 project:
Submission A (fails):
- Provides a budget total of R750,000 but no line-item basis.
- States commissioning will finish “by end of September 2026” but provides no vendor lead times.
- Claims “profit will increase significantly” but provides no financial model or KPIs.
- Lists risks (downtime, demand) but no mitigation actions.
Outcome: reviewer doubts feasibility and value for money.
Submission B (succeeds):
- Provides itemized budget tied to quotes and payment stages.
- Uses a clear timeline ending 30 September 2026.
- Includes a financial logic using incremental contribution and a scenario for the benefit period October 2026–May 2027.
- Shows KPIs: turnaround time, penalty cost reduction from R12,000 to R4,800, and machine uptime.
- Includes risk mitigation with owners and early warnings.
Outcome: reviewer sees control, evidence, and measurable outcomes.
The difference is not “better writing” alone; it is clarity and verifiability.
Aligning to university module cues (UNISA/entrepreneurial project planning)
Because you are studying for assessment, your submission should read like a professional “project planning and funding justification document,” similar to what is expected in project management and small business modules. While module codes and formats differ across institutions, the skills evaluated are consistent:
- structuring a project plan
- building a justification case
- using evidence and assumptions responsibly
- presenting coherent budgets and risk controls
Conclusion: Your business case as a decision-ready package
A project business case for funding applications is a disciplined process: define the need, specify objectives and scope, map outputs to outcomes, build a coherent financial model, and demonstrate governance, risk control, and monitoring. In South Africa’s funding environment, reviewers look for feasibility and evidence as much as they look for ambition. When your business case is consistent—dates, numbers, timeline logic, and KPI targets—funders can clearly assess whether your project is a credible investment.
Use the structure and examples in these notes to craft a business case that is not only persuasive, but also measurable and auditable—precisely the type of document that supports funding approval and successful delivery.
