Potrebujem boljše razumevanje strank.
Na sestanek že pripravljeni.

Signal Reader — demo run

Input: sample-research-packets.md, 4 fictional target companies, seller context given ("forecasting and pipeline analytics platform for B2B sales teams"), 12-month lookback, run date 2026-08-28.

Reminder for this demo: the packets stand in for live search results because the targets are invented. Everything below is scored exactly as it would be against real search output — nothing here is treated more generously because it's a demo.

---

Brief 1 — Thornquist Data Systems

Company snapshot — Data-integration platform vendor, currently expanding into mid-market accounts per its own Series C announcement.

Signals found

The angle — Lead with the CRO quote, not the funding round. Priya Ashwood said, on the record, that forecasting is spreadsheet-driven and that fixing it is her first 90-day priority — as of 2026-08-10, roughly three weeks before this call. The Series C and the Revenue Operations hiring surge both corroborate that she has both the budget and the mandate to act on it now. Open with: "I saw your forecasting process is still spreadsheet-driven — that's exactly the gap we close, and it looks like you're building the RevOps team to fix it this quarter."

Confidence & gaps — This is a strong brief: four independent signals, three within the last six weeks, one direct quote from the actual buyer. Gap: the trade press piece doesn't say whether Ashwood has already selected a vendor or started evaluating — worth asking early in the call rather than assuming this is still open.

---

Brief 2 — Palisade Underwriting

Company snapshot — Underwriting firm; a new VP of Sales was announced in May 2026. No further firmographic detail found in public sources.

Signals found

The angle — Weaker than Thornquist's, and should be presented to the customer that way. There's no funding event, no stated pain point, and no hiring surge — just a new VP of Sales three months in and one supporting ops hire. The honest angle is: "You have a new VP of Sales settling into the role — worth asking what he's changing about the sales process," not a confident claim that Palisade is actively shopping for forecasting tooling. Because no direct signal ties to forecasting/pipeline specifically, this brief does not manufacture that connection.

Confidence & gaps — Low-to-moderate confidence. Both signals are real and dated, but neither is specific to the seller's product category. Treat this as a "worth a call to find out more" account, not a "they're already buying" one.

---

Brief 3 — Grovemont Textiles

insufficient public signal to assess.

No newsroom, no open roles, no named executives, no funding or trade press coverage found anywhere in the 12-month lookback window or before it. The only verifiable facts are firmographic and self-published: a textiles manufacturer, family-owned since 1988, stated headcount under 200.

No brief is produced beyond this snapshot — inventing signals to fill the gap would hand the customer talking points that don't exist. If this account matters, the honest next step is a direct conversation to surface signal that public sources don't carry, not a manufactured brief.

---

Brief 4 — Whitlock Analytics Co

Two signals exist on file — a $14M Series B (2025-04-11) and a VP Sales hire (dated to leadership-page metadata from 2025-06-01) — but both fall outside the 12-month lookback window (16 and 14 months old respectively), and no open roles or newer activity were found to refresh the picture.

Read: this account currently presents as quiet, not urgent. The prior funding and leadership signals are worth knowing as background, but neither supports a "call this week" framing — they are 14-16 months old and nothing found since suggests active movement. Reporting them as fresh signals would manufacture urgency the evidence doesn't support.

---

Honesty check

• 2 of 4 targets produced a genuine, actionable brief (Thornquist, strong; Palisade, weak-but-real). One (Grovemont) hit the insufficient- signal gate outright. One (Whitlock) had signals on file but all stale, and was reported as quiet rather than dressed up as active.
• What would sharpen this: for Palisade and Grovemont specifically, an internal source — a rep's own notes from a prior touch, or a shared contact — would carry more signal than anything public. Signal Reader is bounded by what's actually publishable; private companies with no press presence are its structural blind spot, not a bug to fix with more searching.
• A real limitation surfaced by actually running this: "insufficient public signal" and "stale signal" look similar on the page (both are short, both lack a forward-looking angle) but mean different things for the rep — one means "there's nothing to find," the other means "there was something, eighteen months ago." The output format above keeps them visually distinct on purpose (a labeled gate line vs. a "quiet, not urgent" framing) because collapsing them into one generic "low signal" bucket would lose that difference, and a rep deciding whether to spend a Tuesday on outreach needs to know which one they're looking at.
• Dates drawn from job postings and LinkedIn are the least reliable in this taxonomy — a posting can sit live for months after the role is filled, and a LinkedIn post date is not the same as the actual hire date. Both were used here, flagged as such, and should be treated as approximate signal timing, not confirmed fact, in any real run.

Competitor X-Ray — demo run

Input: sample-competitor-packets.md, two fictional competitors, customer's own product described (mid-market CRM, transparent per-seat pricing, sub-two-week implementation, quote-to-cash for complex B2B pricing, no manufacturing-specific features yet).

---

Teardown 1 — Ferrovia CRM

1. What they say they do — positioning Ferrovia positions itself explicitly as "the operating system for manufacturing sales teams," built around complex quoting, long sales cycles, and channel-partner management. This is a narrow, vertical-specific positioning, not a generic CRM claim. Confidence: solid — drawn directly from their own site copy.

2. Who they're targeting — inferred ICP Three published case studies (industrial parts manufacturer, HVAC equipment maker, an industrial distributor) plus two open roles explicitly tagged "Manufacturing Vertical" and "Channel Partner Manager" converge on the same answer: mid-market manufacturers and their distribution channels, likely 200-800 employees based on the two case studies that disclose headcount. Confidence: solid — case studies, hiring, and positioning all agree.

3. Pricing & packaging Starter at $49/user/month (5-user minimum, core CRM only) and Growth at $89/user/month (adds advanced reporting and API access) are both published with real numbers. Enterprise is gated behind "contact sales" with no published figure — standard for a top tier, not a transparency problem on its own since the two lower tiers are fully disclosed. Confidence: solid for Starter/Growth, opaque for Enterprise only.

4. Where they lead The multi-line quote builder is the one claim independently corroborated by both their own marketing and unprompted customer praise — it shows up in 14 of 40 independently worded reviews as best-in-class for complex B2B quoting. This is a genuine, evidenced strength, not marketing copy alone. Confidence: solid — marketing claim and independent review sentiment agree.

5. Where they're weak Two patterns, not anecdotes: reporting is described as shallow enough that 11 of 40 reviewers independently say they export to Excel to get real insight, and the mobile app logging users out shows up in 7 of 40 reviews, concentrated on iOS. Both are repeated, independently worded complaints rather than a single disgruntled review, which is what makes them usable. Additionally, nothing in the site, case studies, or reviews mentions e-commerce/B2C features or makes any implementation-speed claim at all — an absence worth naming, since the category often leads with speed-to-value. Confidence: solid for the two review-backed weaknesses; the absence-based observations are directional, not proof of a gap, since a company can simply choose not to market a claim it can still satisfy.

6. The angle against them The customer's own product leads with sub-two-week implementation and transparent pricing — Ferrovia makes no implementation-speed claim anywhere found, and its own reviewers are the ones raising reporting friction. The angle: "fast to stand up, and you get the reporting out of the box instead of exporting to Excel" is a real, evidenced contrast, not a generic jab. The one place not to compete is quoting complexity — Ferrovia's quote builder is genuinely well-regarded, and the customer's product doesn't yet have manufacturing-specific quoting features to match it. Confidence: solid — built from the customer's stated strengths and Ferrovia's evidenced gaps, not a template applied blind.

---

Teardown 2 — Meridian Sales Cloud

1. What they say they do — positioning Their own copy is dense with category language — "revenue intelligence fabric," "operationalize your pipeline" — but no page found states in one plain sentence what a user actually does in the product day to day. The positioning claims a category ("revenue intelligence") without the supporting mechanical detail that would make the claim checkable. Confidence: thin — the claim itself is clear, what it concretely means is not, and that gap is being reported as-is rather than filled in with a guess.

2. Who they're targeting — inferred ICP One anonymized case study ("a Fortune 500 financial services company") plus four open "Enterprise Account Executive" roles both point toward large enterprise accounts. But one anonymized case study is weak evidence on its own — no industry breadth, no company size range, nothing to triangulate against. Confidence: thin — enterprise-leaning is a reasonable read, a specific ICP is not supportable from this alone.

3. Pricing & packaging Pricing is opaque — cannot assess published pricing. No tiers, no numbers, no archived pricing page, and no third-party source disclosing real figures were found. Worth naming as a data point in itself: fully hidden pricing with zero self-serve tier usually signals a sales-led, procurement-committee motion rather than a fast, self-serve buy. Confidence: opaque, and reported as such rather than estimated.

4. Where they lead No section written. Nothing in the available material — no independent review data, no specific product claim, no named customer result — supports a specific "this is where they're genuinely strong" claim. Writing one anyway would mean inventing a strength Meridian hasn't demonstrated anywhere found. Confidence: insufficient public information for this section.

5. Where they're weak No independent review data exists to draw a complaint pattern from, so this section is limited to structural weaknesses visible in their own published material: positioning language that never resolves into a concrete mechanical claim, a single anonymized case study standing in for proof, and zero visible price transparency at any tier. These are real, observable gaps — but they are gaps in what Meridian has chosen to publish, which is not the same claim as "customers are unhappy," and the teardown does not blur that distinction. Confidence: thin — real, but bounded to what's publicly absent rather than what customers have said.

6. The angle against them The clearest contrast available is transparency itself: the customer's product has public per-seat pricing and a concrete, statable workflow (quote-to-cash for complex B2B pricing) against Meridian's opaque pricing and abstract positioning language. That is a real, honest angle. It is not possible to say anything evidenced about Meridian's actual feature weaknesses relative to the customer's product, because no feature-level detail about Meridian was found to compare against. Confidence: thin — usable, but should not be oversold as a feature-by-feature win, since Meridian's actual feature set was never disclosed anywhere found.

---

Honesty check

• Ferrovia: 6 of 6 sections fully supported, one (Enterprise pricing) partially opaque within an otherwise solid pricing section. This is what a well-documented public competitor looks like — case studies, reviews, and a published pricing page all agreeing with each other.
• Meridian: 2 of 6 sections solid-or-usable, 1 section (where they lead) could not be written at all, 3 sections thin. This is not a failure of the search — it's an accurate reflection of a competitor that has chosen to publish very little. A teardown that forced six confident sections out of this material would be less honest, not more useful.
• What would sharpen the thin sections: for Meridian specifically, a hands-on product demo or a call with someone who's actually evaluated them would surface the mechanical detail and feature-level comparison this packet couldn't — no amount of additional public search fixes a competitor that doesn't publish specifics. For Ferrovia, the packet was already rich; the one remaining gap (real Enterprise-tier pricing) would need a quote request or a customer who's seen one.
• A real limitation surfaced by running this: the "where they're weak" section is only as good as the review corpus behind it. Ferrovia had 40 reviews to find patterns in; Meridian had zero. The methodology handled that correctly by degrading Meridian's weakness section to structural observations instead of inventing sentiment — but it's worth flagging to the customer directly that a competitor with no review footprint isn't necessarily weaker than one with a well-documented complaint pattern; it's just less visible, which is a different thing a sales team should not conflate when building a battlecard.