Agentic engineering, with grown-up infrastructure.
We are an eighteen-year-old Singapore software studio that re-formed around AI agents. We ship agent crews — not slide decks — into the kinds of systems regulators actually inspect. Same encryption, audit logs and PDPA discipline as before. Roughly an order of magnitude faster.
- 01The work moved from writing code to specifying intent and reviewing output. We re-tooled the studio around it.
- 02IMDA published the world's first agentic-AI governance framework in Jan. Buyers will start asking. We already build to it.
- 03Most "AI agencies" are eighteen months old. We've held production for eighteen years. The boring parts compound.
Three rooms behind the lobby. Walk into the one that's yours.
Most of our work this year falls into three buckets, and each has a slightly different conversation, procurement style, and shape-of-team. We split them on purpose so the proposal you receive isn't the generic AI-agency one.
Your stack is fine. Your speed isn't.
We can drop an agent crew into your current .NET / MS SQL / AWS estate without rewriting it. You get faster delivery and the same audit trail.
Agentic AI, the way IMDA wrote it.
We build inside the Model Governance Framework for Agentic AI launched at WEF 2026. PDPA, audit logs, role-scoped autonomy. Not bolted on after.
Embed a crew. Ship every week.
Our embedded delivery team runs Claude Code + custom evals against your real domain. We do it weekly for WaterDoctor, an NUS spinoff we co-invested in. We can do it for you.
We don't sell "an AI agent." We field crews.
One agent on its own is a demo. A small team of agents, with a human editor and a real eval harness, is a system. Below are three crews running inside our studio right now — including the one we embedded with a deep-tech client.
1 crew : 1 outcome
1 human : 1 final approval
1 eval : every commit, no exceptions.
Reads inbound, enriches it against ACRA, LinkedIn and tender feeds, drafts a tailored response, and hands it to a human within the hour. Our pipeline runs while we sleep.
- · scout.agent — inbound triage + enrichment
- · drafter.agent — proposals from past-win library
- · scheduler.agent — calendar + follow-up loop
- · human-in-the-loop — every send is approved
Most of this site’s articles are produced by this crew, with a senior engineer as editor. Vibe-coded drafts, but every claim is grounded in a real wGrow project or a cited source.
- · researcher.agent — sources + Singapore angle
- · drafter.agent — long-form, voice-controlled
- · fact-checker.agent — citations and numbers
- · editor (human) — every piece, before publish
Four agents and two senior engineers embedded with WaterDoctor — an NUS-spinoff (and a wGrow investee) building AI-integrated biofilm reactors. Sensor data → adaptive control loops → reports a regulator can read. The hard kind of agentic.
- · ingestor.agent — sensor + lab telemetry
- · controller.agent — adaptive treatment loop
- · reporter.agent — auditable run summaries
- · two senior wGrow engineers, on the ground
Industrial agentic AI for WaterDoctor.
WaterDoctor is an NUS spinoff building AI-integrated biofilm reactors for water and aquaculture. wGrow is a strategic partner and co-investor — we designed and operate the agent crew that runs WaterDoctor's adaptive treatment loops. Sensor and lab telemetry in. Regulator-readable run reports out.
Disclosure: wGrow holds equity in WaterDoctor. We say so.
Read the engagement →- Pollutant discharge
- −50%+
- Water exchange
- −90%
- Energy / unit
- −30%
The boring track record an AI agency can't fake.
A short list of systems we built and still patch. The rebrand is real; the foundation is older than most of the agencies announcing themselves this quarter.
- Patient ManagementAWS · MS SQL · field-level encryption · PDPA
- Legal Case Management10-step case workflow · auto billing · client portal
- eCommerce PlatformVitasg · Xpressflower · Paynow / Paylah
- TECOM Order ProcessingLazada · Shopee · TikTok · Amazon · unified inventory
- Grants ManagementApplication portal · expert review · claims · audit reports
- Green Data Centre ReportsSS 564 · IoT sensor ingest · PUE reporting
- Pharma Production PlanningSales↔production balancing · safe-stock guards
- Investment ManagementEncrypted client data · annual invoicing · commission ledgers
- Course & Class ManagementQR attendance · SMS reminders · billing
Notes on AI coding, vibe coding, and the discipline that comes after.
Long-form pieces from the studio. Most are produced by our Article Crew with a senior engineer as editor. We try to publish what we actually learned that week, not what's trending.
Vibe coding is the on-ramp. Agentic engineering is the runway.
Karpathy named the move from typing code to specifying intent. We've spent twelve months in production with it. Here's what stays, what breaks, and what the discipline actually looks like once the novelty wears off.
IMDA's Model Governance Framework for Agentic AI, read by builders.
A clause-by-clause reading of Singapore's Jan 2026 framework, with an opinion on which controls cost real engineering hours and which are zero-cost if you architect for them up front.
If it doesn't have an eval harness, it's still a demo.
Five rules we use on every agentic build, drawn from a year of live client work. Includes the eval template we ship to every new engagement on day one.
Shorter, more often. The notes we'd email a client.
Field notes, infra write-ups, agent-team updates, and the slow rewrite of our 2008–2024 Team-Notes archive. Updated weekly.
Hello from the 2026 wGrow blog.
We relaunched the studio site, opened a separate blog for shorter notes, and started rewriting our 2008–2024 Team-Notes archive for the AI era.
SQL Server hardening checklist, rewritten for 2026.
Our 2023 SQL Server hardening checklist has been our most-shared Team-Notes post for two years. Here it is rewritten for 2026 — with the controls that aged well kept, the ones that aged badly cut, and the ones that need new framing in light of MGF and modern Azure SQL.
AWS Network Firewall in front of an app server: the 2026 setup we'd actually use.
Our 2023 walkthrough of putting AWS Network Firewall in front of a public-facing app server is still the right shape. The defaults, the MGF angle, and the agent-era addition have all moved.
Cloud security architecture for a medical group, three years on.
Our 2023 architecture for a medical service group — VPN, segmentation, ELK, AWS+Azure dual-cloud — held up. The pieces that aged are exactly the ones that became MGF-relevant in 2026.
Have a problem that
a small crew of agents could chew on?
Tell us the shape of it. If we're a good fit, you'll meet a team-lead and one of our crews within a week. If we're not, we'll point you at someone who is.
- @ [email protected]
- tel +65 8942 6252
- 📍 CT Hub 2, 114 Lavender St, Singapore