Describe a process, review the draft, run it on One3

What Build is

Most small and mid-market teams assemble a three-to-five-tool stack — an app builder, an automation tool, a form tool, a survey tool and a proposal tool — and then integrate it all back into their CRM, desk and finance data. Build is designed to replace that stack with seven modules on the One3 kernel: Automations and Forms in the Year-1 core, Survey and Documents & Reports as add-ons, Apps Builder for tenant-built apps, the Developer Platform for partners, and Factory for governed spec-to-code delivery in W5.

Build on the OS, not beside it

Workflows trigger on kernel events from any subscribed module — a lead created, a ticket closed, a form submitted — and call the typed Actions of those modules. No connector is needed for first-party data. Form submissions land on shared core records such as CRM leads and Desk tickets. Tenant apps are Packs on the same kernel as first-party apps, with the same permissions, audit and events.

Humans, agents and steps on one canvas

A step can be a human approval, a Digital Employee skill or an Action, all under the same approval, disclosure and stop-trigger policy. Approvals can happen in the Approvals Inbox or, for opted-in approvers, on WhatsApp.

AI drafts, humans publish

You describe a workflow, form, survey, template or app in plain language and get an editable draft with an explanation, assumptions and open questions. The generator only proposes Actions you are entitled to and allowed to use. A draft with R3 or R4 steps cannot be published until it passes a test or dry run, and a second person reviews the diff. No agent can publish a definition at any autonomy level.

Governed by default

A published workflow runs as a service identity whose authority is frozen at publish time to the intersection of what it was granted and what the publisher could do. If permissions drift, the run pauses; it never escalates. Entitlements are re-checked at every step, and loop guards, budgets, quiet hours and a kill switch are built in.

Measured, not assumed

Workflow runs — not steps — are metered. Every run, submission and generated document is designed to post cost and, where attributable, outcome to the Investment & ROI Ledger, including human supervision time. Baselines entered by the tenant are labelled as estimates.

India-first building blocks

WhatsApp approvals and WhatsApp Flows forms, Hindi and Tamil, GSTIN, PAN, PIN code and INR fields, UPI payment fields through a licensed partner and DPDP-style consent records per purpose are planned. Each must be verified before launch.