Flow Designer, IntegrationHub, App Engine, Service Portal, Now Assist, Virtual Agent, ATF, Studio — the shared platform capabilities that make custom apps and integrations possible.
Every ServiceNow product — ITSM, ITOM, HR, CSM, SecOps, GRC — runs on the shared Now Platform. Learning the platform capabilities means you can build on any of them, integrate them, extend them, and support them.
For custom applications, the Now Platform is a low-code enterprise application platform. For integrations, it's a workflow engine with hundreds of prebuilt connectors. For portals, it's a modern web frontend. For AI, it's a native LLM-powered assistant surface across the platform.
VanPaulTek's platform practice supports every other ServiceNow engagement we deliver — plus standalone platform work like custom applications, integration architecture, and Now Assist AI feature rollouts.
Master these, and you can extend any ServiceNow product to fit your organization.
Visual workflow authoring — business logic, approvals, orchestration. Both citizen developers and pros can use it.
Prebuilt integration spokes for hundreds of enterprise systems, plus a custom-spoke authoring model.
The modern web frontends for both employees and customers. Employee Center is the current standard for internal users.
The low-code environment for building custom applications on the Now Platform.
The regression coverage that survives upgrades and instance clones — non-negotiable for production platforms.
Native LLM-powered features across ITSM, HR, and CSM — case summarization, knowledge generation, virtual agent.
NLU + LLM chatbot for deflection — integrated with Microsoft Teams, Slack, Employee Center, web.
Time-series metrics, targets, and executive dashboards — beyond operational reports.
Design, architect, develop, implement, and support — five phases, one accountable team.
Platform decisions have long-term consequences — design deliberately.
Scoped app + data + integration + performance architecture.
Development on the platform with real engineering discipline.
Deployment discipline — because platform code lives forever.
Platform apps evolve — support keeps them healthy.
Sample roadmap based on real implementations — adjustable to your scope, but grounded in what actually works. Not vendor marketing timelines.
Practical fixes that don't need a project charter. Ordered by timeframe and impact — the stuff experienced practitioners just do.
Delegated admin lets scoped-app owners manage their app without global admin rights. Cuts admin bottleneck.
Now Assist can generate business rules, UI actions, and script includes. Developer velocity up 20-40%.
Centralize ATF suite for cross-app critical flows. Run pre-deploy. Regression coverage jumps immediately.
For non-API systems, RPA Hub creates browser-based automation. Legacy system integration in hours.
Extract common patterns (approvals, notifications, task creation) to reusable subflows. Slims flows by 30%+.
VA can answer 'how do I request X in tool Y?'. Deflection + user education.
Track scoped-app-specific KPIs with time-series trend. Data-driven roadmap.
Enforce coding standards via Studio. Prevents technical debt at PR time, not upgrade time.
Application-level view: errors, performance, usage. Ops team knows what's degrading before users complain.
Real KPIs and targets from mature implementations. Track these; if they trend the wrong way, something is off.
% of critical business flows with automated test. Below 60% = upgrade risk.
% of update-set promotions that succeed without rollback. Below 95% = deploy discipline issue.
% of transactions with error. Above 1% = quality issue; investigate immediately.
95th percentile page load time. Above 5 sec = usability issue; user complaints imminent.
% of flow executions with error. High = poor error handling or upstream data issue.
% of AI suggestions accepted by users. Below 40% = tuning + training needed.
Integration reliability. Below 99% = production data flow at risk.
Assess → upgrade → regress → cutover time. Well-run: 2-4 weeks. Painful: 8+ weeks.
Honest warnings from many deliveries — the mistakes that cost time, money, and adoption. These aren't in vendor guides.
Why it fails: Global scope = permission chaos, upgrade brittleness, cross-scope conflicts. Every senior developer regrets Global scope.
Do this instead: Scoped applications by default. Cross-scope contracts explicit. Upgrade-safe.
Why it fails: Business Rules are hard to debug, hard to test, easy to loop-cause. Flow Designer is visual + testable.
Do this instead: Flows for orchestration; Business Rules for record-level data integrity only. Change your defaults.
Why it fails: Client Scripts are hard to maintain, break silently on form changes. UI Policies declarative + robust.
Do this instead: UI Policies for visible/mandatory/readonly. Reserve Client Scripts for genuine JS logic.
Why it fails: 'Later' = 'never'. Every skipped test = manual regression run every upgrade forever.
Do this instead: ATF coverage requirement in Definition of Done. No merge without tests.
Why it fails: First real production incident = spoke fails silently, no retry, no alert. Days before anyone notices.
Do this instead: Every spoke: retry logic, timeout handling, error notification. Design for failure.
Why it fails: Customizing base portal widgets breaks on upgrade. Fixing = every cycle. Costs pile up.
Do this instead: Clone widgets before customizing. Or use UI Builder / Now Experience Framework. Upgrade-safe.
Why it fails: AI-generated responses shipped without review = hallucinations reach users. Trust craters.
Do this instead: Human review gate initially. Selective auto-post as confidence builds.
Why it fails: Loose update-set discipline = missing changes on prod deploy, or duplicate changes = record chaos.
Do this instead: Update-set per feature, promoted in order. Automated update-set validation.
Why it fails: Prod has 10M records; dev has 10K. Performance issues surface only in prod = user pain.
Do this instead: Load test with prod-scale data. Query hotspot analysis before go-live.
Build a new business application on the Now Platform with a proper data model and workflows.
IntegrationHub-based bidirectional integrations with SAP, Salesforce, Workday, and others.
Modernize employee-facing experience with the current-generation portal.
Enable AI features across ITSM/HR/CSM — case summarization, response drafting, knowledge generation.
Deploy Virtual Agent in Teams / Slack / portal for repetitive request deflection.
Bring a platform up to 60%+ test coverage so upgrades are boring.
Depends on the use case. If it's close to ITSM/HR/CSM — extend. If it's a distinct business function — scoped app. We help you decide in design.
App Engine Studio + Flow Designer support citizen developers. But scale, complex logic, and integrations still benefit from pro developers. We often pair pro + citizen.
For case summarization, response drafts, knowledge suggestion, and Virtual Agent answers — yes, with human-review gates initially. For fully autonomous action — human-in-the-loop still recommended.
For internal-employee experiences: Employee Center (modern). For customer-facing portals: Service Portal is still common in CSM, or Portal Experience is the newer option.
ATF coverage + a systematic upgrade playbook (clone → assess → upgrade → regress → cutover). We do this twice a year for many clients.
Yes. REST APIs both directions, MID Server for on-prem access, IntegrationHub for orchestration. We build this regularly.
Reach out — we get back within 1 business day.
