Signals Desk Weekly Take via FMP API | Five Names With Persistent Earnings Beats (April 13-17)
This week's earnings scan flagged a small cluster of names where execution continues to outpace expectations—quarter after quarter, not just once. Running a full-universe pull through the FMP Earnings Surprises Bulk API surfaced five companies with persistent beat patterns, spanning software, industrials, healthcare, and infrastructure. The dispersion in sectors is notable; the consistency in outcomes is the signal.
The takeaway isn't the beats themselves—it's the lag. Consensus is adjusting, but not quickly enough to fully price in operational repeatability. In this piece, we break down those names and walk through the exact process behind the screen, starting with the FMP Earnings Surprises Bulk API.
Key Takeaways
- Persistent earnings beats across multiple sectors point to a consistent lag in how quickly consensus adjusts to improving fundamentals.
- The signal is not sector-driven—software, industrials, healthcare, and infrastructure all show similar patterns of expectation gaps.
- A full-universe screen using the FMP Earnings Surprises Bulk API helps isolate repeat performers.
- Cross-referencing earnings surprises with margins, cash flow, and estimate revisions is critical to distinguishing durable execution from short-term variance.
Five Companies With Long Earnings Beat Streaks
Intuit Inc. (INTU)
Beat Streak: 16 quarters.
Next quarterly report: May 28 — EPS: $12.54; Revenue: $8.53B (consensus).
Sixteen consecutive quarters of earnings beats places Intuit in a category where execution consistency begins to carry more informational weight than any single quarter's upside. The pattern reflects a business model that has steadily compounded across its core franchises—consumer tax, small business software, and credit—while layering in higher-margin services. What stands out is not just top-line durability, but the company's ability to guide and deliver within relatively tight bands, suggesting internal forecasting discipline that has repeatedly exceeded external expectations.
The signal here is less about growth acceleration and more about expectation calibration. Consensus models for subscription-heavy software platforms tend to adjust incrementally, especially when revenue visibility is already perceived as high. That creates conditions where even modest operational outperformance—margin expansion, cross-sell efficiency, or seasonal strength—translates into repeatable earnings surprises. Monitoring segment-level revenue breakdowns and operating margins from the income statement dataset helps contextualize whether the streak is being driven by pricing power, mix shift, or cost control rather than purely demand expansion.
Aptiv PLC (APTV)
Beat Streak: 14 quarters.
Next quarterly report: May 5 — EPS: $1.62; Revenue: $5.03B (consensus).
Aptiv's fourteen-quarter beat streak is notable given its positioning in the automotive supply chain—a segment typically exposed to cyclical volatility and production variability. Sustained outperformance in this context suggests that the company's exposure to higher-value content—advanced driver-assistance systems, electrical architecture, and software integration—has provided a buffer against traditional volume swings. The consistency points to execution within a structurally shifting industry rather than a benign operating backdrop.
From a signal perspective, Aptiv's streak reflects how estimate frameworks can lag structural changes in product mix. As OEM demand shifts toward electrification and software-defined vehicles, suppliers with differentiated content often see margin resilience that is not immediately reflected in consensus assumptions. Evaluating order backlog data alongside segment-level revenue growth and margin trends can help clarify whether the earnings consistency is tied to secular content gains or short-term cost dynamics. The persistence of beats across multiple automotive cycles suggests the former is at least partially in play.
Telos Corporation (TLS)
Beat Streak: 13 quarters.
Next quarterly report: May 8 — EPS: $0.02; Revenue: $44.6M (consensus).
Telos operates at a different scale, but its thirteen-quarter beat streak highlights a similar theme: consistency emerging in a segment where expectations are often uneven. As a cybersecurity and government IT contractor, Telos sits in a niche where contract timing, renewals, and federal budget cycles can introduce variability into quarterly estimates. Repeatedly exceeding those estimates suggests a degree of operational predictability that the market has not fully incorporated into its modeling.
The signal here is subtle. In lower-coverage names, earnings surprises can sometimes reflect estimate dispersion rather than underlying strength. However, when beats persist across multiple reporting cycles, it points toward improved visibility in contract execution or cost structure management. Reviewing contract backlog disclosures, revenue concentration, and operating expense trends provides a clearer lens into whether the consistency is tied to stable government demand or internal efficiency gains. The relatively low absolute EPS base makes the streak more sensitive to small deviations, which reinforces the importance of examining the underlying drivers rather than the headline alone.
Vertiv Holdings Co (VRT)
Beat Streak: 12 quarters.
Next quarterly report: April 22 — EPS: $1.01; Revenue: $2.63B (consensus).
Vertiv's twelve-quarter run of earnings beats aligns with one of the more visible infrastructure buildouts in the current market cycle: data centers and AI-related capacity expansion. As a provider of power and thermal management systems, Vertiv is positioned downstream of hyperscale and enterprise capex decisions. The persistence of earnings outperformance suggests that demand visibility—particularly tied to data center expansion—has been stronger and more durable than consensus estimates initially captured.
What differentiates Vertiv's pattern is the interaction between volume growth and margin improvement. In capital equipment and infrastructure businesses, operating leverage can amplify relatively small shifts in demand into more pronounced earnings outcomes. The repeated beats indicate that this dynamic has played out across multiple quarters. Tracking order intake, backlog growth, and gross margin progression within the income statement and segment reporting datasets helps determine whether the signal is being driven by sustained demand or by pricing and cost efficiencies layered on top of that demand.
Bristol-Myers Squibb Company (BMY)
Beat Streak: 10 quarters.
Next quarterly report: April 30 — EPS: $1.45; Revenue: $10.88B (consensus).
Bristol-Myers Squibb's ten-quarter streak stands out within large-cap pharmaceuticals, where earnings variability is often tied to patent cycles, drug launches, and pipeline developments. Sustained outperformance in this context suggests effective cost management and disciplined capital allocation alongside stable performance from key therapies. It also indicates that consensus expectations—particularly around revenue durability for established drugs—have been incrementally conservative.
The underlying signal reflects how large pharmaceutical companies manage transition periods between legacy products and newer pipeline assets. Earnings beats in this phase often come from a combination of expense control, portfolio optimization, and slower-than-expected erosion in mature products. To evaluate the durability of this pattern, it is useful to examine product-level revenue data, R&D spend, and pipeline progression metrics, as well as analyst estimate revisions over time. The consistency of beats implies that internal assumptions about product performance have been more accurate—or more conservative—than those embedded in market expectations.
Decoding the Signal Behind Sustained Earnings Beats
Across these five names, the pattern isn't about sector alignment—it's about a recurring mismatch between how companies execute and how they're modeled. Once that gap holds across 10+ quarters, it stops reading as variance and starts pointing to a structural lag in expectations. In effect, these businesses are not just outperforming—they are being systematically underestimated as their underlying economics evolve faster than consensus frameworks adjust.
The drivers of that gap differ, but the outcome converges. In software, it tends to show up through margin layering and monetization efficiency; in industrial and infrastructure names, through operating leverage tied to demand cycles; in pharma and government services, through stability where decay or volatility is expected. Different mechanics, same result: expectations trailing execution.
That's where a single earnings-surprise view becomes incomplete. To determine whether the streak reflects durable improvement or favorable conditions, the analysis needs to connect across datasets. Aligning surprise data with multi-period margin trends from income statement data, then cross-referencing with analyst estimate revisions, begins to show whether consensus is structurally behind the curve. Extending that further—into cash flow durability and valuation resets—helps separate accounting-driven beats from operational consistency. In practice, this kind of layered workflow is only possible when datasets are standardized across endpoints, which is where Financial Modeling Prep platform becomes part of the analytical infrastructure rather than just a data source.
Taken together, persistent outperformance is less about surprise and more about calibration. The signal sits in how slowly expectations converge toward reality—and whether that convergence is still in motion.
Building a Repeatability Screen with FMP Data
Screening for consistent earnings outperformance works best when you start from the entire dataset rather than a curated list of names. Pre-selecting companies introduces bias upfront—especially when the objective is to uncover patterns that may not be obvious within familiar coverage. A cleaner approach is to begin with the full distribution of earnings outcomes and let the filtering process surface repeat performers on its own.
The FMP Earnings Surprises Bulk API is the practical entry point for that process. It standardizes quarterly EPS results against consensus estimates across a broad equity universe, which makes it possible to scan for surprise patterns without needing to stitch together multiple sources. Before running any calls, the only requirement is a valid API key.
1. Pull Bulk Earnings Surprises
Begin by hitting the Earnings Surprises Bulk API, which aggregates every quarterly EPS surprise — positive or negative — for the year you specify:
https://financialmodelingprep.com/stable/earnings-surprises-bulk?year=2025&apikey=YOUR_API_KEY
Sample Response:
[
{
"symbol": "AMKYF",
"date": "2025-07-09",
"epsActual": 0.3631,
"epsEstimated": 0.3615,
"lastUpdated": "2025-07-09"
}
]
From here, the first cut is mechanical: isolate the entries where epsActual > epsEstimated. That gives you the universe of names that beat expectations at least once during the period — essentially a raw pool before you evaluate whether any of them can deliver that result consistently.
2. Retrieve Company-Level Details
With that universe in hand, the analysis moves from identifying events to evaluating consistency. For each ticker that cleared the first filter, pull its complete quarterly earnings history using the Earnings Report API:
https://financialmodelingprep.com/stable/earnings?symbol=AAPL&apikey=YOUR_API_KEY
Looking at the complete sequence of reported quarters makes it possible to evaluate frequency and clustering. This is where judgment enters the workflow. Some analysts require three or more consecutive beats to qualify as a streak; others impose minimum surprise thresholds or remove near-zero deviations. The parameters can be adjusted, but the intent stays the same: separate sustained execution from statistical noise.
By this point, the screen has moved beyond identifying isolated surprises. What began as a broad event scan turns into a structured assessment of earnings reliability, highlighting companies where internal forecasting and operational control have proven more consistent than the market's expectations over time.
Scaling the Screen: Testing the Signal Across Broader Coverage
A repeatability screen earns its credibility not by how many companies it includes, but by how well it holds up as the data environment becomes less predictable. The most effective way to test that is to widen the scope in stages—starting with tightly modeled segments and moving outward into areas where estimates are looser and coverage is thinner. The goal is simple: see if the signal survives as conditions become less controlled.
The first pass sits within the Free plan, where the dataset is anchored in widely covered large-cap names like Apple Inc., Alphabet Inc., and JPMorgan Chase & Co.. This is the most efficiently modeled part of the market—analyst coverage is dense, estimates tend to cluster, and expectations are generally well-defined. If a streak-based approach produces consistent outputs here, it suggests the framework is functioning on stable ground rather than reacting to noise in the data.
Moving into the Starter plan expands the universe to include a wider range of U.S. equities, bringing in smaller-cap and more specialized companies. At this level, estimate dispersion becomes more visible as coverage thins out. That shift acts as a natural pressure test. When the same criteria continue to surface repeat performers, the pattern begins to look less dependent on tightly managed forecasts and more tied to actual operating consistency.
The final step, via the Premium plan, extends the screen across international markets such as the U.K. and Canada. The methodology remains unchanged, but the inputs become more varied. Differences in reporting conventions, sector mix, and estimate reliability introduce additional complexity. Applying the same framework across these regions helps validate that the signal—earnings consistency—remains comparable even as the underlying data becomes more heterogeneous.
From Analyst Workflow to Standardized Research Framework
When a screening process continues to produce stable signals across multiple earnings cycles, it stops being a personal tool and starts to look like institutional infrastructure. What begins as an analyst's method for tracking repeatable earnings beats becomes a candidate for how the broader research platform defines and measures consistency. At that point, the shift is less about expanding coverage and more about aligning methodology—establishing a shared way to interpret operational reliability across sectors.
In practice, that transition is usually driven from within the analyst ranks rather than mandated from above. The people closest to the data—those refining filters, resolving inconsistencies, and testing assumptions quarter after quarter—are the ones who surface what actually holds up. As those workflows mature, they naturally expose the inefficiencies of fragmented approaches: siloed spreadsheets, slightly different definitions across teams, and duplicated effort in reconciling results. A standardized framework replaces that with a common reference point, allowing different coverage groups to work from the same underlying logic.
The operational impact is immediate. Shared dashboards take the place of isolated models, making outputs visible across teams rather than confined to individual desks. Changes to thresholds or screening criteria become transparent and reviewable, instead of being embedded in private files. That visibility improves auditability—inputs, calculations, and assumptions are clearly defined—and creates a foundation for governance. Time spent reconciling discrepancies across teams is reduced, shifting focus toward interpreting what the data is actually indicating.
At that stage, scaling the workflow becomes less about efficiency and more about preserving consistency as adoption widens. Centralized infrastructure, such as the Enterprise plan, allows a process that has already been validated at the desk level to operate across the firm with unified data access, version control, and shared visibility. The goal is not to alter the analysis, but to ensure that as more teams rely on it, the methodology remains intact and comparable across the entire research organization.
Keeping Earnings Consistency in Motion
The value of a streak isn't in identifying it once—it's in tracking whether it holds as new data comes in and expectations adjust. That process starts with a consistent input, which is why revisiting the full earnings dataset through the FMP Earnings Surprises Bulk API keeps the signal grounded in what's actually changing.
Want more? Explore our earlier article: Weekly Signals Desk | Five Notable Valuation Disconnects from the FMP API (April 6-10)
Disclosure: Signals Desk content is provided for informational and analytical purposes only and does not constitute investment advice or trade recommendations. The analysis reflects interpretation of market data and publicly disclosed or third-party information, including data accessed via Financial Modeling Prep APIs, at the time of publication. Signals discussed are probabilistic, can be wrong, and may change as market conditions and consensus data evolve. This content should be considered alongside broader research, individual objectives, and risk assessment.
Weekly Signals Desk analysis and API-driven market workflows
David Kirakosyan writes the Weekly Signals Desk for FMP, breaking down market signals while showing readers how to build similar workflows using the FMP API. His work focuses on turning raw API data into practical market analysis and repeatable workflows that developers and analysts can adapt to their own research.
Financial data for every need
Real-time quotes and 30+ years of historical data, including prices, fundamentals, and insider transactions — all accessible via API.
Create Free Account