Raffles Consulting Services

Startup SG Tech POC or POV: choose the right track

Choose Startup SG Tech POC or POV by testing technical uncertainty, market evidence, milestones, proprietary technology and commercial readiness.

Startup SG Tech POC or POV is a stage decision, not a choice between a smaller and a larger grant. Proof-of-Concept should answer whether the proprietary technology can work. Proof-of-Value should test whether a more developed technology can create credible commercial value. A startup that cannot state the uncertainty to be resolved will struggle to define useful milestones for either track.

Separate technical proof from commercial proof

Write the unresolved proposition in one sentence. For a POC, identify the technical mechanism, performance threshold and evidence that would show feasibility. For a POV, identify the intended user, operating setting, measurable value and evidence that would show the technology is ready for commercialisation. Do not turn ordinary product development into deep-technology research by changing the label.

The current Startup SG Tech page describes competitive support for POC and POV projects and says the technology should be proprietary. The Enterprise Singapore startup support directory places the programme within deep-tech commercialisation. Off-the-shelf system integration alone is not the same as proprietary technology.

Build a track-choice evidence table

Create columns for current technology readiness, intellectual property ownership, test environment, data required, customer evidence, technical risk, commercial risk and the next funding decision. Record what already exists and what the project must prove. A laboratory result, prototype demonstration and signed customer pilot answer different questions and should not be treated as interchangeable.

Use the table to reject premature POV plans and overextended POC plans. A POC that also promises full production deployment may hide unresolved engineering work. A POV with no credible user or operating context may test a demonstration rather than value. Preserve contrary evidence because it often explains why a milestone needs redesign.

Convert the choice into measurable milestones

Define each milestone by an output, test method, acceptance threshold, owner and evidence source. Link payments and internal decisions to achieved evidence rather than elapsed time. Include a stop or redesign decision when a core assumption fails. Startup SG Tech awards are milestone-based, so vague activity lists create both technical and grant-control problems.

Keep the equity component and other award terms visible in the board decision. Model the company-funded cash requirement and do not assume an application will be approved. Link the chosen track to the Startup SG Founder capital sequence only if the company is separately considering that route; one programme does not establish eligibility for the other.

Turn the decision into a controlled file

Use a dated decision record that identifies the applicant, business need, current official source, chosen route, responsible owner, costs, milestones and evidence. Separate facts already verified from forecasts and assumptions. A catalogue listing, supplier statement, consultant recommendation or portal acknowledgement does not establish approval. The company remains responsible for its declarations and commercial decision.

Give each quotation, contract, invoice, payment and deliverable a stable reference. Preserve earlier versions and explain material changes instead of silently replacing them. Where the authority, tax adviser, auditor or another professional must decide a point, record the open question and obtain the required view. Do not convert uncertainty into a confident eligibility statement.

Review before commitment and again before closeout

Run four reviews: suitability, authority, implementation and closeout. At suitability, test the entity, activity and business outcome. Before commitment, freeze the proposed scope, vendor and financial assumptions. During implementation, compare actual work with approved terms. At closeout, reconcile deliverables, accepted results, invoices, full payment, operating evidence and obligations that continue.

Name the person who may approve each stage and the records that person must see. Procurement should not treat a draft application as permission to contract. A project team should not treat supplier completion as company acceptance. Finance should not treat a submitted claim as cash received. Clear status words prevent accidental commitments and weak reporting.

Handle exceptions without rewriting history

Maintain an exception log for changed facts, delayed milestones, supplier variations, cost movements, missing records and failed tests. State the effect on scope, eligibility, timing and expected value. If an authority decision or formal variation is required, use the published route before relying on the change. Silence and helpdesk receipt are not approval.

If a material defect appears, pause the affected acceptance, filing or claim item. Keep original evidence, assign corrective action and set a review date. Do not backdate records, move costs between categories or adjust a baseline after seeing the result. A candid exception with an owned resolution is more credible than a clean-looking file that cannot explain what happened.

Plan handovers before the original project team disperses. The handover should identify the current version, source locations, system access owner, next review date, open exceptions and any condition that continues after payment or filing. Restrict personal, financial and commercially sensitive records to authorised users, while giving each responsible owner enough information to perform the assigned control. Record the external event that should trigger an earlier review, such as a changed programme page, revised authority letter, supplier failure or material business change.

Verify the final outcome independently

Ask someone who did not prepare the final pack to compare the decision, current official source, approved terms, deliverables, payments and operating evidence. Recalculate totals and sample source records. The reviewer should be able to reproduce the conclusion without relying on the preparer’s memory. Record unresolved points with named owners and dates.

Use the Singapore business support decision guide for the wider decision and keep this article as the narrower operating guide. After submission, preserve the receipt and reconcile questions, adjustments and the final registered or paid outcome. Continue any reporting, retention, asset-use or other condition that survives closeout.

Practical review checklist

  • Proprietary technology identified
  • POC and POV questions separated
  • Readiness evidence recorded
  • Milestones have test methods
  • Cash and equity implications reviewed

The track is ready for discussion when the startup can show what is proprietary, what remains uncertain, why POC or POV fits that uncertainty and how each milestone will change the next commercial decision.