SME proposal · Kim Pong Engineering
A finished job should be billable.
Kim Pong Engineering · a proposed sales–service–finance system. Jarvis assists the owner; WhatsApp captures enquiries; one ERP retains the authoritative customer, job and invoice records.
The operating loop
- 01SalesApproved quotation → accepted order
- 02OperationsSite/asset → scheduled job → completion
- 03FinanceBillable evidence → approved invoice
- 04OwnerExceptions, receivables and outcome evidence
Use an existing suitable ERP when possible; justify any necessary bespoke choice.
Diagnose reconstruction, not “lack of AI”
Kim Pong publicly describes commercial ACMV design, installation and maintenance. Verify whether sales, technicians and finance reconstruct the same facts across chats, spreadsheets and accounting. Obtain twenty sample quote–job–invoice chains and actual handling/rework before choosing a platform.
Source: Kim Pong Engineering ↗
Source: BCA Built Environment PSG ↗
Two valid architectures
If the current or a suitable approved ERP already covers the necessary functions, keep it. Add a bounded WhatsApp intake adapter, Jarvis approval/exception interface and outcome report. Price genuine new scope without pretending the entire existing ERP is newly eligible.
This can be the lower-risk delivery choice. A separate AI enhancement is not automatically a new integrated ERP grant; evaluate its own activity or self-funded/EIS treatment.
Implement one platform with sales/customer engagement, service operations and finance. Select an approved package where suitable. Use CyberG7 as another vendor only when the required-function gap is evidenced, with the published ten-week assessment path.
ERPNext or another platform is a discovery candidate, not an existing CyberG7 deployment. Actual entitlements, licence/hosting/services and renewal must be quoted honestly.
Three functions, one transaction
| Required connection | Acceptance test | Owner |
|---|---|---|
| Accepted quote creates linked service order | Scope, customer/site and approved values match | Sales lead |
| Order allocates job and asset/site history | Technician sees authoritative current scope | Service lead |
| Completion creates correct invoice draft | Finance does not contact sales/technician to reconstruct facts | Finance lead |
| Retries preserve one billable event | No duplicate job or invoice; errors can be recovered | Delivery lead |
| Jarvis approval binds to final action | Any value change requires appropriate re-approval | Commercial/finance owner |
AEO/Launch pages may attract enquiries; Academy/GRC support use and controls; Analytics reconciles acquired leads to accepted jobs. Those assets have real roles but are not substitutes for service operations or finance.
Prove the other-vendor justification
Build a dated comparison of suitable pre-approved packages, required functions, demonstrations/vendor responses and operational consequences. “We prefer Jarvis” or “it has more agents” is not a functional gap.
| Candidate requirement | Required proof |
|---|---|
| Site/asset maintenance history linked to orders | Actual approved-package demonstration or written response. |
| Completion evidence supplies billable items | Whether finance can issue the invoice without reconstructing work. |
| Scoped WhatsApp intake into the same ERP | Supported adapter and data/tenant boundary. |
| Approval bound to quoted/invoiced values | Workflow capability, roles and audit trace. |
Source: Integrated ERP activity ↗
If approved options satisfy the requirements, use that route. The grant is assessed for the client’s solution, not CyberG7’s whole estate.
Whole cost and benefit, before subsidy
| Planning line | Amount |
|---|---|
| Three genuine software access modules, 12 months | S$18,000 |
| Integration/migration | S$6,000 |
| Training/handover | S$2,000 |
| Annual maintenance/support | S$2,400 |
| Annual usage allowance | S$1,200 |
| Full first year / annual renewal | S$29,600 / S$21,600 |
| Conditional grant on software basis only | S$9,000; zero if the basis/route is not accepted |
Software amounts are proposed bundle entitlements, not vendor list prices. A free underlying ERP must not be given a fictitious paid licence. Validate all genuine software, hosting and services with a real cost/entitlement breakdown.
Capacity scenario from the earlier worksheet is 85.33 hours/month. A separate realisation assumes 40 paid overtime hours avoided at S$35/hour plus 16 hours of existing backlog fulfilled at S$75 contribution/hour: S$31,200/year. Do not add the S$28,672 capacity valuation to it; both describe the same recovered hours.
Planning assumptions in S$. Edit them to test the business case. Benefit means avoided expenditure plus incremental contribution, after new client-side supervision/rework costs. Capacity is reported separately.
How the calculation works
Cost = one-off cost + annual cost × horizon. Benefit = annual benefit × horizon. Grant = selected rate × assessed basis, limited by the activity ceiling where stated and never more than project cost. Horizon surplus = benefit − cost + conditional grant.
Steady-state payback = one-off cost ÷ monthly recurring surplus, without the grant. This compares operating value; it is not a cash-flow schedule for annual prepayment. The SME must finance the full first-year cost until any reimbursement. Payback excludes application/delivery delays, tax and financing. GST and any unpriced costs must be added to the real budget. No approved cost basis or award is established by this calculator.
The base no-grant 24-month case yields S$11,200 surplus; half realisation loses S$20,000 and cannot support renewal. Benefits start after go-live, so the assessment and delivery calendar still matters. Customer cash need includes the full project cost, GST where applicable and contingency.
Deliver one complete operating loop
| Period after approval | Result | Acceptance |
|---|---|---|
| Weeks 1–2 | Detailed scope, clean records and reconciled migration | Sales, service and finance agree fields and totals. |
| Weeks 3–4 | Three configured ERP functions | Connected sandbox order/job/invoice, not separate screenshots. |
| Week 5 | WhatsApp/Jarvis adapter and approvals | Persistent intake, tenant checks, retries and action receipts. |
| Weeks 6–7 | Representative pilot and role training | Twenty actual representative chains; ≥80% eligible adoption; no critical invoice/access failure. |
| Week 8 | Stabilisation, UAT, export and recovery drill | Finance can issue correct invoices without reconstruction; sponsor signs. |
| After completion/full payment | One final claim packet | Actual award, identifiers, invoices, acceptance and payments reconcile. |
Open the worked application and evidence explainer →
Source: Integrated ERP activity ↗ · EDGE FAQ ↗