ServiceNow (NYSE:NOW) — Reading the Technical Signals

Price Action and Volume

In the trading session under review, ServiceNow (NOW) opened at $284.28 and closed at $285.84, representing an intraday decline of approximately 1.69%. The session low touched $280.97. Reported trading volume for the session was approximately 1.66 million shares, consistent with the stock’s average daily volume at that time — suggesting the price move was not driven by an unusual surge in activity.

When a stock’s volume closely matches its average and yet shows a notable intraday swing, it can indicate that the directional move may lack conviction — a neutral-to-cautious signal for short-term traders.

Analyst Consensus and Price Target

At the time of reporting, the analyst consensus price target for NOW was approximately $316.16, implying roughly 6.5% upside from the most recent closing price. A consensus target above the current trading price is generally interpreted as a bullish signal by the analyst community, indicating that the majority of covering analysts expected the stock to appreciate over the following 12 months.

Additional market metrics at the time included:

• Public float: approximately 183.21 million shares
• Market capitalization: approximately $51.48 billion USD

Technical Indicators: RSI, Stochastic, and Moving Averages

Two commonly used momentum oscillators — the Relative Strength Index (RSI) and Stochastic — were highlighted in the original analysis.

Stochastic reading for NOW: 32.61%

The Stochastic oscillator compares a security’s closing price to its price range over a given period, producing a value between 0 and 100. Readings below 20 are typically considered oversold, while readings above 80 suggest overbought conditions. A reading of 32.61% places NOW in a neutral zone — neither overbought nor oversold — suggesting the stock could trade sideways in the near term without a strong directional catalyst.

The 200-day Moving Average (200 MA) was also noted as supportive of a bullish trend at that time. When a stock’s price trades above its 200-day MA, it is broadly interpreted as a long-term bullish indicator, as the stock is holding above its longer-term average cost basis.

The 200-day moving average is one of the most widely watched technical levels in equity markets. A stock trading above it is considered to be in a long-term uptrend; below it signals a potential downtrend.

Impinj (NASDAQ:PI) — A Sharp Intraday Move

Intraday Performance and Volume Surge

Impinj (PI), an RFID semiconductor company, recorded a notable single-session gain during the period covered. The stock opened at $35.33 and closed at $39.94, a jump of approximately 13.05% in a single session. Trading volume reached 518,640 shares, well above the prior 100-day average of roughly 340,339 shares — a volume increase of approximately 52% above average.

Volume spikes accompanying large price moves are a closely watched signal in technical analysis. When price rises sharply on above-average volume, it often indicates stronger conviction behind the move than a price change on thin volume would suggest.

Volatility and Moving Average Metrics

Key volatility and trend metrics reported for PI at the time included:

• Weekly volatility: 7.23%
• Monthly volatility: 4.88%
• Distance from 50-day moving average: 37.00% above
• Trading range for the period: 17.37%
• 5-day gain: approximately 18.34%
• 200-day average price: approximately $21.59
• Recovery from 52-week low: +201.43%
• 12-month gain: approximately 174.50%

A stock trading 37% above its 50-day moving average is a significant deviation and often raises the question of whether a short-term pullback or consolidation is likely before the trend can continue sustainably.

Analyst Consensus for Impinj (PI)

According to the Reuters analyst rating scale referenced in the original report, PI’s consensus rating improved slightly — moving from 2.43 to 2.29 — over the prior month. On the Reuters scale, lower numbers typically indicate a more bullish average recommendation (closer to a strong buy).

The 12-month consensus price target for PI was reported at $39.94 per share — coinciding closely with the closing price on the day of reporting. This suggests that, as of that session, PI was trading at or near analyst fair value, meaning there was limited additional upside priced into consensus expectations at that specific moment. The high-end consensus target was reported as showing only a 0.15% premium to the current price.

Intraday Trading Volume — Follow-Up Session

A subsequent session showed PI trading approximately 1.17 million shares, a significant increase over the trailing average of roughly 430,950 shares. The 52-week low was reported at $13.25, with the stock having recovered 201.43% from that level by the time of reporting. Over the most recent one-month period, PI had also added approximately 39.55% in value.

Key Takeaways for Technical Traders

• ServiceNow (NOW): Neutral Stochastic reading (~32%) and position above the 200-day MA suggested a consolidating stock with a mildly bullish longer-term bias. Analyst consensus implied ~6.5% upside at the time.
• Impinj (PI): A sharp 13% single-session gain on elevated volume, combined with a 201% recovery from 52-week lows, signaled strong momentum — though the stock trading 37% above its 50-day MA and at consensus target price suggested caution around near-term overextension.
• Both RSI and Stochastic oscillators are useful for identifying overbought or oversold conditions, but they work best in conjunction with volume analysis and moving average context rather than in isolation.

All data in this article reflects conditions reported in early August 2019 and is provided for educational and historical reference only. This is not financial advice. Always consult a qualified financial professional before making investment decisions.

What Is ServiceNow?

ServiceNow Inc (NYSE: NOW) is an enterprise cloud platform vendor that provides workflow automation and integration tools for large organisations. Rather than stitching together a patchwork of point solutions, ServiceNow offers a unified ecosystem that lets workers move across departments — IT, HR, customer service, security operations — while sharing data and processes on a single platform.

The company focuses on four primary verticals: Healthcare, Education, Government, and Financial Services. Each of these sectors faces strict compliance requirements, complex approval chains, and large numbers of internal service requests — exactly the kind of structured workflow problems that ServiceNow is designed to solve.

The Problem ServiceNow Solves

For smaller organisations, building a modern tech stack is relatively straightforward: pick a cloud provider, add a CRM that doubles as a support tool, bolt on an HR system, and wire them together with integration middleware. Imperfect, but manageable.

For large enterprises, that piecemeal approach quickly becomes unworkable. Hundreds of business units, thousands of employees, strict audit trails, and regulatory obligations mean that ad-hoc integrations introduce risk and operational drag. ServiceNow addresses this by providing a common data model and a workflow engine that sits across all of those domains, so a change in one system propagates correctly through others.

In DevOps terms, ServiceNow occupies a similar conceptual space to a service mesh or an internal developer portal: it abstracts the complexity of underlying systems so that teams can focus on outcomes rather than plumbing.

ServiceNow in the Enterprise IT Landscape

ServiceNow competes with larger platform vendors — including IBM — that also offer middleware and enterprise integration tooling. Its competitive advantage, at least as of the original 2019 article, was described as agility: being large enough to support enterprise-scale deployments, but small enough relative to incumbents to avoid the legacy architectural assumptions that slow down bigger vendors.

Key platform capabilities that matter to DevOps and IT teams include:

• IT Service Management (ITSM): Incident, problem, and change management built around ITIL processes.
• IT Operations Management (ITOM): Discovery, service mapping, and AIOps capabilities that help teams understand infrastructure dependencies.
• DevOps integration: Native integrations with CI/CD pipelines, allowing change requests to be created, approved, and tracked automatically as part of a deployment workflow.
• Security Operations (SecOps): Vulnerability response and threat intelligence workflows integrated into the same platform.
• HR Service Delivery: Onboarding, offboarding, and employee service requests managed through the same workflow engine used for IT.

ServiceNow and DevOps Workflows

One area where ServiceNow has become increasingly relevant to DevOps practitioners is automated change management. Many regulated industries require a formal change approval process before production deployments. Historically, this was a manual bottleneck that conflicted with the continuous delivery model.

ServiceNow’s DevOps module allows pipeline tools such as Jenkins, GitLab CI, and Azure DevOps to automatically create change requests, gather approvals, and update configuration management databases (CMDBs) as part of the deployment process. This means teams can maintain audit compliance without abandoning automation.

For organisations in financial services or healthcare — two of ServiceNow’s core verticals — this kind of integrated change control is not optional. It is a regulatory requirement, and ServiceNow positions itself as a way to meet that requirement without sacrificing deployment velocity.

The Business Context (as of Mid-2019)

The following figures come from the original June 2019 source article and reflect conditions at that time. They are included for historical context only.

• ServiceNow was founded approximately 15 years before the article was written (around 2004).
• The company carried an approximate market capitalisation of $47 billion at the time of writing.
• Year-to-date stock performance as of early June 2019 was approaching 50% gains.
• Q1 2019 earnings were described as strong enough to lift the broader cloud sector.
• The original analyst commentary described ServiceNow as the “best house on the block” in its category.

The original piece was written by Louis Navellier, a growth-focused investment newsletter editor, and reflected his assessment at the time. His commentary noted that ServiceNow’s predominantly US-based client base — particularly in financial services — insulated it somewhat from trade-war uncertainty that affected other technology stocks in 2019.

Why This Matters for DevOps Professionals

Whether you are evaluating ServiceNow as a platform for your organisation, being asked by leadership to integrate with an existing ServiceNow deployment, or simply trying to understand why your enterprise’s change advisory board runs through a NOW workflow, a few things are worth knowing:

• ServiceNow is a platform, not a point tool. Implementations tend to be organisation-wide and involve significant configuration. Expect a longer evaluation and procurement cycle than you would see with a SaaS tool.
• The CMDB is central. The quality of ServiceNow’s ITOM and DevOps capabilities depends heavily on the accuracy of the CMDB. If your organisation’s asset and dependency data is incomplete, that will limit what you can automate.
• APIs and integrations are first-class citizens. ServiceNow exposes a REST API and maintains a marketplace (the ServiceNow Store) with pre-built integrations for common DevOps tools. Check the Store before building custom integrations from scratch.
• Governance is a feature, not a bug. For teams coming from a startup or greenfield DevOps background, ServiceNow’s approval workflows can feel heavy. In regulated enterprise environments, those workflows exist for defensible compliance reasons.

Summary

ServiceNow occupies a well-defined niche in the enterprise IT market: large-scale workflow automation and integration across IT, HR, security, and customer service functions. For DevOps teams operating in regulated industries, it is frequently the system of record for change management and incident response. Understanding how it works — and how to integrate your pipelines with it — is a practical skill for engineers working in enterprise environments.

Original source: investorplace.com (June 2019). Attribution: Louis Navellier, Growth Investor newsletter. This editorial rewrite is for informational purposes only and does not constitute investment advice.