CyberG7 Technologies · Research & proposal drafts

One customer journey.
A clear route from WhatsApp to operations.

A grant map, four SME proposal examples, a worked integrated ERP application and revised advertisement drafts. Built around the updated GPT receptionist and the full supplied playbook, checked on 1 October 2026.

Current rules checkedIllustrative budgetsNo grant submitted

Download this editable Markdown draft ↗

CyberG7: from WhatsApp enquiries to a measurable business system

Research date: 1 October 2026, Singapore time. Prepared for CyberG7 Technologies LLP.

Requested reference: the four-route comparison artifact, now supplied in full as the user's “PSG to EDGE: Jarvis Ad Playbook & EDGE Readiness Guide”. This report incorporates that text and independently verifies the rules. The updated GPT receptionist is the product basis.

Recommended direction: sell a narrow, dependable WhatsApp receptionist first; expand successful clients into a connected sales, operations and finance system operated through Jarvis. Choose funding after the workflow and economic case are defined.

Jarvis can participate in all four routes in the question, through different scopes. Its name, number of agents and “AI OS” branding do not determine eligibility. Three agents performing marketing tasks still perform one business function. A grant supports the SME applicant's approved project; it does not approve CyberG7's entire estate.

Companion documents: sample SME proposals, worked integrated ERP application and revised advertisement playbook.

1. The funding map, corrected

New EDGE applications opened on 30 September 2026. Enterprise Singapore's EDG, PSG and MRA closed to new applications after 29 September; existing projects continue under their original schemes. EDGE's overall annual support cap is S$100,000, refreshed on 1 April. Funding is reimbursed after completion and full payment. Enterprise Singapore: EDGE

Built Environment exception: BCA's PSG remains open, with transition to EDGE scheduled for December 2026. Its September 28 notice explicitly distinguishes it from Enterprise Singapore's PSG. Kim Pong's ACMV business merits an eligibility check against this route before deciding on EDGE, but its industry alone does not establish applicant or Jarvis package eligibility. BCA's digital route still requires a pre-approved solution. Do not use an unqualified “PSG is gone” advertisement for this audience. BCA Built Environment PSG

Claims calendar: EDGE accepts one final claim after completion and full payment. Claims open from 1 November 2026 for single-function digital solutions, integrated enterprise systems and pre-scoped equipment, and 1 December 2026 for other activities. A portal opening date does not mean every applicant becomes ready or receives payment that day. EDGE FAQ

Route Appropriate CyberG7 scope Approval position Current SME support
Single-function: GenAI Customer Engagement Chatbot A defined Jarvis receptionist with company knowledge, lead handling, human takeover and reporting Exact vendor/solution package must be pre-approved; CyberG7's status is unverified Up to 50%; S$15,000 activity cost ceiling and S$7,500 grant ceiling
Single-function: GenAI Marketing and Sales Content Generation A specialised Jarvis marketing workspace producing contextual drafts for owner review Exact package requires pre-approval Up to 50%; S$5,000 activity cost ceiling and S$2,500 grant ceiling
Integrated Enterprise Resource Planning A single ERP platform covering at least three core functions, with Jarvis as the assistant and WhatsApp as a channel Pre-approved package, or another vendor when required functions are unavailable in suitable pre-approved solutions Up to 50%; S$60,000 activity cost ceiling and S$30,000 grant ceiling
Other EDGE activity: Large-scale Digital Transformation A substantive redesign integrating business processes and systems, potentially using AI and existing platforms No pre-approved vendor requirement stated on this activity page; project assessment remains necessary Up to 50% for SMEs; eligible costs and awarded amount depend on assessment
EIS AI adoption Qualifying AI systems and AI-related business services bought for the client's trade Tax claim; no IMDA vendor pre-approval mechanism 400% deduction on the first S$50,000 per YA for YA 2027 and YA 2028; no AI cash conversion

Sources for the activity-specific figures: customer engagement, marketing content, integrated ERP, digital transformation, IRAS EIS.

The two single-function categories sit within the first of the user's four routes. They are different activities with different ceilings. Selected digital solutions, integrated systems and selected automation share a S$30,000 annual subcap. A separate application is required per activity; do not duplicate a cost across applications. The ERP page uses broader wording about automation/digitalisation caps than the general FAQ. Confirm the selected activity's treatment in BizSG and the Letter of Offer rather than assuming every transformation project has the same subcap. EDGE FAQ

How to use the EIS route honestly

IRAS includes qualifying AI-related development, deployment, consultancy, data, maintenance and training services, as well as AI systems. Hardware is excluded; mixed packages require allocation and government subsidies reduce the qualifying basis. This is broader than “any AI subscription”, but an AI label alone proves nothing. IRAS EIS

Illustrative company arithmetic: S$12,000 qualifying expenditure × 4 = S$48,000 deduction. At a 17% marginal rate, with sufficient taxable income and ignoring exemptions and rebates, the tax reduction would be S$8,160 in total, of which S$6,120 is additional to an ordinary 100% deduction. The supplier is still paid S$12,000. Confirm the actual tax effect and basis period with the accountant. A December-year-end company's YA 2027 normally relates to 2026, and YA 2028 to 2027. CyberG7 is an LLP; these company-rate illustrations must not be used for its partners' own taxes. IRAS corporate tax basics

2. What “integrated, without vendor pre-approval” means

The official ERP page describes one ERP platform, not a collection of unrelated apps with a chatbot in front. It permits a non-pre-approved vendor when the required functionality cannot be found in suitable pre-approved packages. The published application outcome times are one week with a pre-approved vendor and ten weeks with another vendor. These are assessment times, not project delivery or reimbursement dates. Integrated ERP

For Kim Pong, make the three functions concrete:

Business function Business record Jarvis's contribution Evidence of integration
Customer engagement and sales Customer, enquiry, quotation and order Qualify an enquiry; retrieve approved terms; draft a quote for approval An accepted quote creates a linked service order
Core service operations Asset, maintenance schedule, job and completion record Prepare a work order; flag overdue work; summarise technician notes Completed work changes the same order's fulfilment status
Finance Invoice, receivable and payment status Prepare invoice drafts and owner summaries Invoice references the customer, order and completed job

A marketing assistant, content writer and lead finder cannot stand in for these three functions. GHL plus WhatsApp alone does not establish an ERP. Jarvis Mission Control alone does not establish an ERP either. An underlying ERP such as ERPNext is a candidate for discovery: its documentation covers service sales, accounting, projects and maintenance workflows. This is a proposed foundation, not a CyberG7 deployment or a grant endorsement. ERPNext service organisations, maintenance schedule

CyberG7 should prepare a comparison of suitable approved packages. Document the required function, available package capability, missing requirement, evidence and operational consequence. A preference for CyberG7 or for an “AI OS” is insufficient justification. If an approved package meets the requirements, offer that route honestly, with separately priced CyberG7 services only where appropriate and supportable.

What a credible application contains

The ERP activity explicitly asks for the vendor scope and cost breakdown, a proposal covering at least three deployed/integrated modules for another vendor, and a one-year cost-saving projection. The accompanying worked application adds our recommended evidence: process diagrams, a package comparison, assumptions, acceptance tests, implementation milestones and accountable client owners. These additions make the case reviewable; they are not presented as extra statutory requirements. Integrated ERP application documents

Applicant checks include Singapore operations, at least 30% ultimate Singapore citizen/PR ownership, the SME group-size test, location and prior-support restrictions, sufficient funding, and vendor independence. The ERP route excludes home-based businesses. No project work, payment or deposit should precede submission. The SME submits, pays and claims through its own authorised personnel; CyberG7 supplies the proposal and evidence. Costs committed after submission remain at the SME's risk until approved. ERP eligibility, EDGE FAQ

For ERP, the activity page identifies software costs for up to twelve months and excludes maintenance and GST. The FAQ allows meaningful professional services within assessed solution packages. Consequently, list migration, integration, training, support and software separately and obtain their assessment; do not assume every line is funded or disguise maintenance as licensing. Use the final Letter of Offer as the controlling scope. The applicant must retain deployment identifiers, completion evidence, invoices and payment records. ERP costs and claims, professional services FAQ

A real comparator, and the limit of the evidence

Enterprise Singapore's February 2026 food manufacturing release describes Toh Thye San Farm using AI to capture WhatsApp orders into its platform, alongside integrated accounting, inventory and sales. It reports a 20% improvement in order accuracy and month-end reporting reduced from ten days to four. The same release describes KH Roberts integrating finance, procurement, sales, inventory and CRM. These are strong examples of connected operational outcomes. The release does not disclose an approved non-pre-approved EDGE application, its quotation, assessment or Letter of Offer. Enterprise Singapore and IMDA, company profiles, pages 7–9

I found no verified public successful application under the new ten-week EDGE route. EDGE opened yesterday relative to this research date. The worked packet is therefore an application model, not an approved case or assurance of success.

3. What the CyberG7 estate actually supports

The supplied estate map is a 27 August 2026 snapshot of 54 hostnames. Its counts and domain faults are historical. This review sampled the principal offer pages, three named businesses, relevant local repositories and the current receptionist health endpoint; it did not rescan all 54 properties or perform a production systems audit.

Layer Evidence observed Useful business role Material gap
CyberG7 corporate/agency front doors Agency page remains live; multiple brand/offer destinations Establish credibility and route buyers into one main offer Parent-brand and pricing fragmentation
WhatsApp receptionist Current public site plus runtime source; live health reported five successful outbound deliveries and five model calls, zero recorded failures Demonstrable answer-and-handover product for service SMEs Docs still record no onboarded clients; end-to-end client booking and ERP are unproven
Jarvis public offer Website describes website, leads, content and security work under owner approval Umbrella for expansion and owner controls Broad promises exceed what this review verified
Jarvis/Agent OS Estate identifies Mission Control; available chat context describes an AI command centre Proposed internal orchestration, approvals, memory and reporting No complete client ERP demonstrated in this review
GHL Estate and receptionist code show CRM/escalation links Existing capture and operator handover destination Verify client-specific mappings and actual response ownership
Twenty/OSS migration Local CRM README names Twenty, n8n, Chatwoot, Cal.com and related modules as the direction Future replaceable execution infrastructure Legacy Baserow services are explicitly undeployed; historical “live” sections cannot be sold as current capability
LaunchNow/LaunchFast Current S$288 and S$88 website offers; agency Standard S$288 is described as a refundable reserve Website entry products for firms needing a front door Different pricing and payment meanings need a single clear campaign path
AEO, Ad Analytics, content tools Described in supplied estate Acquisition, attribution and content delivery No assumed causal proof of incremental sales
Academy and GRC Training and governance surfaces in estate Onboarding, operating procedures and controls Course availability or a GRC page is not client adoption or certification

The live /healthz observation at wa.cyberg7.com.sg on 1 October showed tenant_answers: 0, delivered: 5, and an active gpt-5.4-nano composer. Global counters do not establish five customers, production reliability or per-tenant answer coverage. The local September 30 handoff and marketing-site documentation still say there are no onboarded clients. Older READMEs describing a wholly deterministic runtime are stale: the current code includes model composition after safety checks.

The public receptionist page correctly labels Rosewood Nails fictional. Keep that separation. Kim Pong, Lynn Beauty and GetSGPR are described as real client businesses in the estate; their public sites support the business descriptions. This review does not verify their contractual relationship, SME eligibility or AI deployments.

Three claims to reconcile before wider advertising

  1. Approval behaviour. The Jarvis page promises review before sends. The receptionist sends permitted replies automatically. Specify that owners approve the knowledge and automation policy in advance; fresh quotations, discounts, refund decisions, payments and publications require the appropriate approval. Do not use one blanket promise for both modes.
  2. Data location. The receptionist composer calls an external OpenAI endpoint with customer text and configured facts. That cannot be described as “nothing leaves your machines”. Offer a clearly documented hosted deployment, or a separately scoped local-model deployment, with the actual processing chain disclosed. Do not equate Singapore database hosting with wholly local processing.
  3. Outcome proof. Launch pages still display “3,000+ Singapore SMEs launched”; the receptionist has no documented clients. These may refer to different products, but the website count needs its own substantiation. The receptionist's absolute “0 facts it invents” also requires reconsideration with a generative composer. Prefer a testable statement: approved facts, guarded composition and human escalation, with error monitoring. Jarvis public page, LaunchFast, LaunchNow

4. The connected product story

Owner-facing proposition: “Keep customer enquiries moving, without spending your day repeating answers or chasing the next step.”

Suggested product structure:

Offer Buyer and problem Delivered outcome Expansion rule
Jarvis Receptionist Appointment/service SME repeatedly answering WhatsApp Approved answers, useful intake, dependable handover and weekly review Add booking only after availability and calendar integrity are verified
Jarvis Operations SME with separate sales, work and finance records One enquiry-to-job-to-invoice process with clear ownership Offer integrated ERP only when three actual functions and platform integration are evidenced
Jarvis Transformation SME with substantial cross-system bottlenecks Redesigned process, secure integrations and measured adoption Scope an appropriate bespoke EDGE activity or self-funded work
Jarvis AI Adoption Buyer wants a smaller project or cannot use a grant Clearly defined AI system/service with accurate invoice allocation Accountant evaluates EIS; the business case must stand independently

Recommended technical relationship:

Ads / search / website / referral
              ↓
Business-specific WhatsApp channel
              ↓
Receptionist: approved knowledge + guarded composition + human takeover
              ↓
Customer / opportunity / consent records
              ↓
Jarvis: propose → validate → obtain required approval → execute → record
              ↓
ERP: sales ↔ service operations ↔ finance
              ↓
Owner report: unresolved enquiries, next actions, time, bookings and cash status

Keep the public WhatsApp service limited to the SME's customers, orders, bookings and support. Do not expose a general-purpose Jarvis AI OS through the public number. WhatsApp's current terms restrict AI providers where AI itself is the primary functionality; application to a particular deployment remains Meta's determination. This supports a business-specific service wrapper and a protected internal Jarvis console. WhatsApp Business Solution Terms

Recommended integration controls: one persistent customer ID, one order/job ID, tenant-scoped access, signed webhooks, duplicate protection, approval receipts tied to the actual action, retry/error queues, recoverable history and monitoring. Tool access must be limited to the scoped business workflow. Customer messages must not grant system privileges. These are delivery recommendations, not claims that all are implemented today. Map processing purposes, subprocessors, access and retention with each client. PDPC AI guidance

5. Attracting the owner: problem, hook, demo and system

Owner problem Proposed advertisement hook What the demo must show What must run behind it
Repeating the same salon questions between customers “Still answering prices and opening hours after your last appointment?” Correct approved answer; unknown question reaches a person Tenant knowledge, language checks, operator queue
Enquiries stall while technicians are on site “From a WhatsApp enquiry to a service job, without copying the details three times.” Enquiry becomes a draft job; completion links to an invoice Actual three-module ERP, not a slide
Owner fears the AI will promise the wrong price “Ask it something it should refuse. That is the demo.” Unknown price, complaint and safety scenario handled correctly Restrictions, price source, human takeover
Consultancy team repeatedly chases missing documents “Let your team review the case. Let the system organise the follow-up.” Checklist and secure upload request; no eligibility verdict Secure workspace, case management, scoped reminders
Staff struggle to create consistent content “A week's drafts, built from your offer and ready for your review.” Brand-specific drafts awaiting approval Specialised content workflow and approval history

These are draft hooks, not performance claims or published advertisements. Replace forecasts with client evidence once earned. A useful grant line inside a proposal is: “We will assess the appropriate EDGE activity or qualifying AI tax treatment for this scope.” Avoid “guaranteed grant”, “400% cashback”, or suggesting ACRA registration/SME Centre contact means IMDA approval.

Use the receptionist page as the first campaign destination because it shows the actual narrow product and labels its demo. Keep Jarvis as the expansion explanation. Do not funnel this campaign through a cheap website price unless the offer is explicitly a website purchase. Unify naming, pricing basis and the single next step across the ad and destination.

The proposed sales journey is: industry-specific ad or AEO article → labelled demo → owner supplies an anonymised workflow → baseline review → scoped proposal → grant/self-funded decision → client application if relevant → controlled deployment → measured result → client-authorised case study → expansion.

Track the actual journey in the CRM: source, creative, conversation ID, business identity, discovery booked/attended, qualified opportunity, proposed scope, funding route, applicant readiness, won/lost reason and realised gross profit. Cost per conversation is a diagnostic; cost per qualified opportunity and acquired customer's gross profit determine whether advertising works.

6. Success criteria

All numbers below are proposed acceptance targets, not observed CyberG7 or client results. Agree final thresholds after a baseline.

Level Proposed criterion Measurement and decision
Answer quality At least 95% factual correctness on 100 agreed English/Mandarin/Singlish examples; zero critical fabricated price, safety or contractual statements Client-approved answer set; trace each answer to its source; any critical error blocks launch
Handover 100% of agreed safety, refund, complaint and unknown-price scenarios reach the correct operator; no reply continues after human takeover Behavioural tests plus sampled production conversations; never optimise away correct escalations
Integration No duplicate customer/job/invoice in the agreed retry tests; every completed job links to the right invoice draft Test delayed/repeated webhooks and recover failures; obtain client UAT sign-off
Responsiveness 95% of eligible routine replies within 15 seconds during the pilot Delivery timestamps, with operating exclusions stated; human response time measured separately
Adoption At least 80% of in-scope pilot jobs handled through the new process by the final two pilot weeks Compare against the complete eligible-job denominator, not just successful runs
Productivity At least 20% reduction in active handling time for the chosen workflow after stabilisation Two-week baseline and four-week pilot; matched workload and task mix; report rework too
Client economics Conservative measured annual benefit exceeds recurring annual cost; named use for recovered capacity Separate labour capacity, avoided expenditure and incremental contribution margin
Funding readiness Applicant evidence complete; correct activity and independent vendor; scoped quote and cost evidence reconcile Client owns submission; approval is an external decision, not an internal deliverable
CyberG7 commercial Three paying pilots in 90 days; positive contribution on each; target recurring gross margin at least 60% Include onboarding labour, model/API, hosting, support and failure recovery costs
Retention and proof At least two pilots renew or expand; one permissioned before/after case study Use named baseline, date, denominator and attribution limits
Pre-approval readiness Work towards five eligible independent SME references using the same solution for at least six months Same-solution results; unrelated website clients do not count automatically

For IMDA pre-approval, the published vendor criteria also include company age, financial stability, support capacity and customer productivity references. The onboarding process typically spans four to five months once ready. The GenAI checklist requires more than a working model: demonstrate knowledge ingestion, relevant engagement capabilities, dashboard/reporting, exports, privacy requirements and third-party security assessment. The admin shell and absent client proof are meaningful gaps. Vendor criteria, onboarding, chatbot checklist

7. Sequence and responsibilities

Period from decision to proceed Work Accountable owner Completion evidence
Days 1–14 Reconcile claims and offer; obtain Lynn and Kim Pong discovery; baseline enquiry/job handling; check funding eligibility CyberG7 founder plus each SME director Approved scope, real workflow sample, eligibility records, actual quote
Days 15–30 Agree one paid receptionist pilot; complete tenant answers, operator route, monitoring and rollback; prepare ERP package comparison Delivery lead and SME process owner Signed pilot terms, UAT transcript, support ownership
Days 31–60 Deploy only the authorised scope; monitor errors; measure time and commercial outcomes; prepare ERP application Delivery lead; SME's BGP personnel for submission Weekly report, measured benefit, complete applicant packet
Days 61–90 Review renewal; obtain permission for one case study; close next two pilots; start ERP only under the client's agreed funding/risk decision Founder and client sponsor Contribution report, renewal decisions, evidence-backed creative
Months 4–9+ Build a same-solution customer reference cohort and close the formal pre-approval checklist Product and vendor-onboarding owner Six-month usage evidence and completed assessments

If a client chooses a grant-supported project, avoid beginning the proposed funded scope before submission. A demonstration using fictional data is different from commencing their implementation. A paid pilot must not be retrospectively rolled into a later grant; separate any genuinely new phase with its own scope and assessment. Discuss the boundary before charging or deploying.

CyberG7 can also be a grant applicant for a genuinely new qualifying internal project using an independent vendor. It cannot manufacture eligible expenditure by invoicing itself, and existing Jarvis/WhatsApp work cannot be made retrospective. Its own external qualifying AI purchases may merit tax review, with LLP treatment assessed correctly.

8. Evidence status and remaining work

Known: official rules checked on 1 October; accessible August estate; current narrow offer and website price differences; local code contains a model composer; health counters show limited successful activity; local CRM documents explicitly distinguish undeployed legacy systems.

Inferred: salons provide the most accessible initial proof opportunity; Kim Pong has the clearest proposed sales–operations–finance story; GetSGPR benefits from secure casework integration. These are fit hypotheses, not diagnosed client problems.

Assumed: every proposal budget, workload, labour rate, time saving, revenue projection and acceptance threshold. None is a customer quotation or result.

Missing: each applicant's exact legal entity, local ownership, group size, tenancy, financial readiness, prior funding, relationship declarations, systems inventory, transaction baseline, access rights, approved package comparison and signed quote. CyberG7/Jarvis pre-approval was not verified; unsuccessful public searches are not proof of absence.

The first Claude artifact required sign-in; the user subsequently supplied its complete playbook text, which is incorporated here and audited in the revised advertisement playbook. The second artifact was accessible. No ad was published, customer contacted, infrastructure changed or grant submitted. The deliverables are reviewable business/application drafts; they do not certify eligibility or approval.