Approve the build plan
01 · You approve the plan first.
Builds run in phases with checkpoints, so you see what will change before anything is written.
Develop
Develop — The whole change, built and staged for your approval.
Phyllis builds the real records on your instance — tables, fields, business rules, client scripts, UI actions, flows, ACLs, catalog items. The whole change lands in scoped update sets, every field diff-verified, staged for your approval. Nothing ships unattended.
14.2%
Build the warranty claim flow with approval over $5k.@ for records · / for commands
Build
acmedevProject
acmedevProject Created the claim tablex_acme_warranty_claimCreated
Built the approval flowsys_hub_flow · over $5kCreated
Read back every write9 / 9 matchVerified
Update set readyacme-dev · waiting for your approvalReview
Built for the platform
3,000+typed ServiceNow tools~230expert skill packsHundredsof health checks8acceleratorsISO 27001 certifiedPer-user OAuthApproval on every changeLands in your update setsATF on every build
What you can ask Develop to do.
Phyllis builds the change on your instance — real records and config, scoped update sets, every field diff-verified and staged for your approval before anything ships.
Build · asset return4 records
u_asset_returnextends taskTable
Auto-assign on submitroutes to fulfilment groupBusiness rule
Return requestvariables + UI policyCatalog item
Return fulfilmenttrigger → tasks → closeFlow
Develop
Build this — real records, not snippets
Phyllis doesn't hand you a code sample to paste. She creates the actual tables, fields, business rules, client scripts, UI actions, flows, ACLs and catalog items on your instance — named, linked, and working against your real schema.
Update set · asset_return_v1Complete
sys_db_object · u_asset_returnInsertTable
sys_script · Auto-assign on submitInsertScript
sys_hub_flow · Return fulfilmentInsertFlow
Instance ScanClean
ATF4 / 4 passed
Develop
Show me exactly what you changed
After every write, Phyllis reads the record back and diffs it against what she sent — no silently dropped fields, no fields that ServiceNow lied about saving. The whole change stays staged in scoped update sets until you approve it. Nothing ships unattended.
Review gate · x_acme_assetPassed
Scoped to x_acme_assetnothing left in GlobalPass
Naming conventionu_ prefix · readable labelsPass
No hard-coded sys_ids3 references resolved by namePass
ACL coverageread / write / create on every tablePass
Develop
Will this pass review?
Every artefact is built to your standards. Phyllis follows your naming conventions, target scope and estimation rules — and stages ATF tests alongside the change — so what lands reads like your best engineer wrote it, not a bot.
How Develop works. Step by step.
Update set4
02 · Built in your instance.
Real records, in the right scope and update set, following your team’s conventions.
7 / 7 matchRead back
03 · Every write, read back.
After each write Phyllis reads the record back and checks it matches what she meant to change.
The whole change, not a snippet. Across the platform.
Configuration and code across the platform — each artefact built in your instance, in your update set.
Tables & fields
sys_db_objectBusiness rules
sys_scriptScript includes
sys_script_includeFlows & actions
sys_hub_flowACLs
sys_security_aclCatalog items
sc_cat_itemPortal widgets
sp_widgetUI Builder pages
WorkspacesNow Mobile apps
MobilePlatform Analytics
DashboardsAI agents
Now AssistATF tests
sys_atf_test3,000+typed ServiceNow tools
~230expert skill packs
Hundredsof health checks after every build
Approve how it behaves. Not just how it looks.
Preview · Laptop refreshInteractive
Laptop modelMacBook Pro 14 · $2,400
Manager approvalShown · over the $2k thresholdRequired
Cost centreMandatory for this modelMandatory
TotalRecalculated · $2,400Live
Catalog item previews run the real rules before anything is built — conditional fields appear, mandatory flags toggle, prices recalculate and order guides step through.
What’s included
Clickable catalog and order-guide previews
Live HTML mock-ups for portals and workspaces
Screenshots checked against what was actually built
Built to a discipline, not a demo.
Phyllis builds real records and config on your instance — scoped update sets, every field diff-verified against what ServiceNow actually saved, staged for your approval.
Scoped and review-ready
Every field diff-verified
Build · asset return4 records
u_asset_returnextends taskTable
Auto-assign on submitroutes to fulfilment groupBusiness rule
Return requestvariables + UI policyCatalog item
Return fulfilmenttrigger → tasks → closeFlow
Develop, across the platform.
CAT-118: Hardware Return Catalog Item6 records
Hardware Return item under Hardwaresc_cat_itemCreate
Variables + asset-details setitem_option_newCreate
Collection fields show/hide + mandatoryCatalog UI PolicyCreate
Asset-tag validation lookupCatalog Client ScriptCreate
Ready to deploy?6 records — 6 to create
Approve & DeployRejectEsc to go back
Catalog
Catalog items & requests
Catalog items with variables, UI policies, client scripts, and fulfillment — built end-to-end from a sentence.
Read the use caseAUT-118: Governed Request-to-Fulfilment Flow6 records
Request-to-fulfilment flow + triggerFlowCreate
Hardware/software branches + error handlerFlow LogicCreate
Fulfilment subflowSubflowCreate
Licence-assignment actionActionCreate
Ready to deploy?6 records — 6 to create
Approve & DeployRejectEsc to go back
Automation
Flows & automation
Flow Designer flows, business rules, AI agents, notifications — automation built, tested, and approval-gated.
Read the use caseUX-118: Portal & Workspace Experience5 changes
Homepage hero + services gridPortal pageCreate
Open-case & breach KPI tilesKPI dashboardCreate
Cases-by-channel trend chartChartCreate
Contextual case side panelSide panelCreate
Ready to deploy?5 changes — 5 to create
Approve & DeployRejectEsc to go back
UX
Portals and workspaces that look built for your brand — and your agents.
Phyllis builds and extends your entire employee-and-agent experience — any portal page, workspace or brand theme — grounded in your live instance and staged for your approval.
Read the use caseDevelop, answered.
Does she follow our naming and scoping?
Yes. Your conventions are part of every build — prefixes, scopes and patterns — and she reuses what already exists instead of duplicating it.
Where do the changes go?
Into an update set in your instance, in the right application scope, staged for your approval. Nothing is promoted without you.
What if she gets something wrong?
Every write is read back and checked, builds pause at checkpoints, and an Instance Scan runs after every build. You review before anything moves.
Can we limit what she can touch?
Yes. Per instance, owners and admins can make it read-only, block tables or switch off tools — enforced on every request.
The rest of the lifecycle.
One teammate from the first question to a promoted, tested change.
CMDB health scorecardcmdb_ci · 48,213
68of 100
CriticalDuplicate servers across SCCM and Discovery2,114 CIsFix with Phyllis
Analyze
Ask your instance anything
Phyllis grounds herself in the full context of your ServiceNow instance — its tables, ACLs, flows, update sets, configurations, and dependencies. Every answer is evidence-backed and traceable to the records it came from.
Explore AnalyzeImplement ITSM · 24 storiesITSM-101
ITSM-102Incident categories & assignment rulesDone5
ITSM-103Major incident workflowReady8
ITSM-104Change CAB approvals by riskReady5
ITSM-105Problem → known error handoffPlanned3
ITSM-106SLA definitions for P1–P4Draft3
Plan
From a sentence to a sprint-ready backlog
Say “I want to implement ITSM” and Phyllis returns sequenced stories with priorities, points, and acceptance criteria — synced both ways with Jira or ServiceNow Agile 2.0.
Explore PlanPromote · Feature: Warranty claim flowAwaiting approval
devtestprod
Records14
ATF12 / 12 passed
Instance ScanClean
Rollback planAttached
Promote to prod?Platform owner
Approve & promoteReject
Deploy
Sequence and promote from one canvas
Batch and release update sets through chat — in the right order, with conflicts surfaced before you promote.
Explore Deploy
