Runtime
Commercial Signal Radar Market Assessment for LongTermCapabilities
Report summary
A paid, human-reviewed Commercial Signal Radar is commercially plausible , but not as a broad lead-generation database, autonomous scoring product, or inexpensive general newsletter. The strongest product is a managed named-account monitoring service , optionally sold through a white-label or subcon
Key topics
- Runtime
- AI
- Privacy
- Research Archive
- Strategy
- Audit
- Architecture
- Governance
Research provenance
For citation, use the report title and canonical URL. Archival presence does not establish authorship or promote report statements into portfolio evidence.
Source availability: 29 citation markers in the source export have no recoverable source links. Those markers are omitted from this reader; any supplied bibliography and ordinary links remain. Check the original sources before relying on the cited claims.
This page renders the archived Markdown as safe, formatted HTML. It is background research and does not become a portfolio claim without evidence review.
Full report
On this page
Executive conclusion
A paid, human-reviewed Commercial Signal Radar is commercially plausible, but not as a broad lead-generation database, autonomous scoring product, or inexpensive general newsletter. The strongest product is a managed named-account monitoring service, optionally sold through a white-label or subcontract relationship with an established consultancy. Its defensible value is not data collection; most underlying public data is already free or inexpensive. The value is evidence classification, cross-source interpretation, explicit unknowns, and a bounded decision process.
LongTermCapabilities already publishes the operating principles needed for such a product: source-to-test-to-review-to-decision traceability, separation of observed results from inference, explicit limitations, client-owned artifacts, and fixed-scope entry work. Its public commercial model also supports a paid trust bridge: a $5,000 Joint Discovery Workshop, $20,000 AI readiness sprint, $30,000 modernization blueprint, and $9,500–$12,500 monthly Architecture & Reliability Office.
Recommended initial offer: a four-week Managed Commercial Signal Radar Pilot covering 25 named organizations, six source classes, weekly evidence records, one principal decision session, and a final continue/change/stop recommendation. The recommended test price is $3,500–$5,000 for the pilot, followed by $2,500–$3,500 per month for a three-month managed subscription. A white-label version should begin at $7,500 for setup and the first month, then $5,000–$7,500 per month.
The initial market should be limited to two adjoining groups:
| Priority market | Commercial rationale | Initial route |
|---|---|---|
| Boutique Microsoft, Azure, software-modernization, and AI consultancies | Highest fit with LongTermCapabilities’ architecture expertise and existing partner positioning | Direct named-account subscription or partner add-on |
| Government capture, proposal, and business-development consultancies | Strongest public evidence that customers already pay for competitive intelligence and decision support | White-label, co-branded, referral, or subcontract route |
MSPs are a secondary test market. Private-equity operating teams and specialist software vendors have higher theoretical contract values, but they also have greater access difficulty, higher expectations, more legal sensitivity, and more established intelligence alternatives. They should not be the first market without a warm introduction and a narrowly defined decision use case.
Verified public facts. LongTermCapabilities positions itself as a lean, principal-led practice rather than an undisclosed delivery bench, and emphasizes direct principal accountability, exportable evidence, public-safe qualification, and disclosed partner roles. Public data sources required for the radar include free official APIs and feeds from the SEC, USAspending, SAM.gov, GitHub, Greenhouse, Lever, and public status pages.
Analyst inference. The product can become sustainable if it reaches approximately eight to ten managed named-account subscribers at $3,000 per month, or three to four white-label clients at $7,500 per month, without allowing bespoke research to consume the principal’s consulting capacity.
Unknowns. No public evidence reviewed establishes that the existing radar implementations are production-ready, that their source adapters are legally and operationally maintainable, or that current customers will pay for the resulting records. The codebase, historical precision, review time per signal, and source-failure rates were not publicly inspectable.
Required human decision. LongTermCapabilities must decide whether the radar is primarily a profitable research product or a consulting-market-development capability. Attempting to make it both a low-price newsletter and a high-touch bespoke advisory service would create conflicting economics and brand expectations.
Evidence base, source architecture, and operating burden
The underlying source environment is favorable. Most high-value sources are organization-controlled and programmatically accessible, but each needs a source-specific interpretation and retention policy.
| Signal class | Verified public source availability | What can be established | Important limitations |
|---|---|---|---|
| SEC enterprise-change filings | The SEC provides company submissions and extracted XBRL through official JSON APIs and offers full-text search across more than 20 years of EDGAR filings. | Filing date, form, disclosed transactions, risk changes, acquisitions, dispositions, restructuring language, capital allocation, material agreements | A filing is evidence of a disclosure, not proof that a buyer needs consulting |
| Form D operating-company events | Form D is a public notice of an exempt offering, generally due within 15 days after the first sale. | Issuer, offering date, offering size fields, amendments and related entities | Form D is not SEC approval, may contain limited information, and should never be converted into an investment recommendation or distress signal. |
| Repeated technology hiring | Greenhouse’s public Job Board API exposes published jobs without authentication; Lever’s official postings API exposes public company job postings. | Repeated roles, technologies, locations, seniority bands, newly created or removed public postings | Hiring may represent replacement, backlog, ordinary growth, experimentation, or standing requisitions; it is not buying intent |
| Organization-level GitHub changes | GitHub provides organization events, repository metrics, organization APIs, and authenticated rate limits that are adequate for bounded monitoring. | New public repositories, archived repositories, release cadence, public organizational activity, language and project changes | Public event APIs are not real-time and may have latency of 30 seconds to six hours. Personal contribution profiling should be excluded. |
| Incidents and postmortems | Statuspage supports integrations, APIs, RSS, Slack, incident histories, and public subscriptions. | Incident timing, affected components, organization-published cause, remediation and follow-up commitments | An incident is not evidence of commercial distress. Only resolved incidents and organization-published follow-up should normally enter the paid product |
| Government procurement | SAM.gov publishes pre-solicitations, solicitations, awards and sole-source notices; USAspending provides award and recipient endpoints. | Notice type, agency, dates, award history, incumbent, obligated amounts, vehicle and recompete chronology | SAM.gov’s terms distinguish public APIs from sensitive responses; only public-facing data may be disseminated externally. |
| Product, partner and migration announcements | Organization websites, technical documentation, support lifecycles, RSS, partner portals and monitored page changes are available, sometimes through inexpensive change-detection tools | Announced retirement date, migration path, changed eligibility, changed product packaging and partner requirements | Page changes can be cosmetic, regional, temporary or incorrectly detected; original and changed source states must be retained |
The sources are inexpensive relative to the human-review burden. Visualping’s published pricing ranges from a low-cost individual tier to business plans around $100–$250 per month, while HigherGov offers an entry government-market-intelligence plan at $500 per year. Feedly’s more expansive Market Intelligence plan is $1,600 per month billed annually and includes 100 AI feeds, newsletters, company insights and team collaboration. These alternatives establish a wide price spectrum: cheap monitoring at one end and enterprise intelligence infrastructure at the other.
The product should use a five-stage record pipeline:
| Stage | Required record |
|---|---|
| Collection | Source URL or API identifier, retrieval time, source authority, organization and signal type |
| Normalization | Canonical organization, event date, publication date, source excerpt or structured field, previous state where applicable |
| Evidence review | Verified fact, analyst inference, unknown, contradictory evidence and exclusion reason |
| Commercial interpretation | Potential operating problem, applicable service boundary, likely buyer titles and whether any credible route exists |
| Publication | Customer-specific relevance, review date, correction status, expiry or next-review date |
Analyst inference on volume. For a 25-account pilot covering public filings, jobs, GitHub, status pages, product documentation, partner notices and government procurement, a reasonable starting expectation is 250–1,000 raw changes per week, reduced to 30–80 candidate records and approximately 8–20 publishable records. For a 100-account white-label feed, the raw count could reach 1,000–4,000 weekly changes. These are capacity-planning estimates, not observed LongTermCapabilities performance.
The largest false-positive sources are likely to be routine SEC filings, reposted jobs, location duplicates, automated GitHub dependency changes, incident-status updates that add no new facts, cosmetic web-page changes, procurement amendments that do not affect scope, and product documentation reorganizations. A 60%–85% rejection rate at the machine-generated candidate stage would not by itself mean the system is failing. The meaningful measure is review minutes per accepted record, decision relevance, source correction rate, and customer use, rather than the total number of alerts.
Required human decision. Before commercial launch, the owner should require a measured four-week corpus containing at least 500 raw events. Each event should have a final disposition and review-time measurement. No pricing or staffing model should be treated as dependable until that sample exists.
Target customers, willingness to pay, alternatives, and retention
The market is not one homogeneous category. Each segment has a different decision cadence and different substitution risk.
| Customer segment | Decision the radar could support | Likely buyer titles | Price hypothesis | Retention and churn assessment |
|---|---|---|---|---|
| Boutique technology consultancies | Which accounts, ecosystem changes and technical triggers deserve principal attention; which bounded assessment should be proposed | Founder, Managing Partner, Principal Consultant, VP Sales, VP Alliances, Head of Delivery | $1,500–$3,500 monthly for 15–40 accounts; $4,000–$7,500 for a managed vertical feed | Good retention if records are connected to account reviews; high churn if delivered as generic “leads” |
| MSPs | Vendor retirement, Microsoft ecosystem, customer-sector, acquisition and technology-change monitoring | Chief Strategy Officer, VP Marketing, VP Alliances, VP Managed Services, Corporate Development leader | $750–$2,500 monthly | Moderate price sensitivity; likely churn when the feed duplicates vendor newsletters or ordinary page alerts |
| Government contractors | Recompete chronology, award changes, agency notices, incumbent changes, partner activity and technical requirements | VP Growth, Chief Growth Officer, Capture Director, Business Development Director, Market Intelligence Director | $1,000–$4,000 monthly per market or account set | Strong potential when tied to capture calendars; weak when positioned as another opportunity search tool |
| Government capture and proposal consultancies | White-label evidence feed for client briefings, pipeline reviews, competitive-analysis workshops and account plans | President, Managing Director, VP Consulting, Practice Lead, Director of Competitive Intelligence | $5,000–$10,000 monthly, plus setup | Strongest channel retention if embedded in client delivery; significant concentration risk |
| Private-equity operating teams | Portfolio technology-change monitoring, vendor and product risk, acquisition integration and operating-company signals | Operating Partner, Technology Operating Partner, Portfolio Operations Director, Head of Digital | $5,000–$15,000 monthly | Potentially high value, but high expectations and high churn if analysis is not tied to an active operating program |
| Specialist software vendors | Named-account, partner, competitor, open-source and platform-change intelligence | VP Strategy, VP Product Marketing, VP Partnerships, Competitive Intelligence Director, Corporate Development leader | $2,000–$7,500 monthly | Moderate to strong if focused on a narrow technical ecosystem; substantial substitution from existing CI platforms |
The lower-priced alternatives are formidable. A customer can combine official source subscriptions, SAM.gov, USAspending, SEC EDGAR, GitHub notifications, Google Alerts, RSS and a page-change monitor for a modest cash cost. HigherGov’s $500 annual entry price makes it difficult to sell raw federal opportunity data at a large premium.
At the other end, enterprise competitive-intelligence platforms monitor websites, product pages, pricing, news and internal intelligence. Klue describes dedicated competitive-intelligence platforms as commonly costing from the low thousands to approximately $15,000–$40,000 annually, while Feedly’s published standard market-intelligence price is $19,200 annually. Contify advertises monitoring across more than one million sources, newsletters, dashboards and machine filtering of irrelevant changes.
The Commercial Signal Radar therefore cannot differentiate on “we monitor many sources.” Its differentiators must be:
| Defensible differentiation | Why it matters |
|---|---|
| Source authority and date retained with every claim | Customers can independently inspect the evidence |
| Verified fact, inference, unknown and decision separated | Prevents a public event from becoming a fictional lead score |
| Technical-principal review | Adds architecture, reliability, Microsoft-stack and AI-production interpretation that general CI platforms usually do not provide |
| Explicit bounded engagement mapping | Each record either maps to a credible assessment, workshop or research decision—or is rejected |
| Corrections and expiry | Prevents old hiring, award, incident or migration records from becoming permanent unsupported claims |
| No personal enrichment or autonomous outreach | Reduces privacy, reputational and misuse risk |
| White-label evidence package | Allows established consultancies to add technical depth without pretending LongTermCapabilities is the account owner |
Analyst inference on retention. A broad weekly brief will probably have the highest churn because its relevance varies week to week. Named-account monitoring should retain better because the watchlist is customer-specific. Principal sessions can improve retention but become capacity-limited. White-label feeds can be sticky once embedded in another consultancy’s client process, although losing one partner may create an outsized revenue shock.
Unknowns. Public competitors generally do not disclose independently audited retention, precision, false-positive rates or customer-level churn. Those metrics should therefore be treated as unknown rather than replaced with industry folklore.
Product-form comparison and delivery economics
The cost model below uses a conservative, explicit planning basis. The Bureau of Labor Statistics reports a May 2024 median annual wage of $76,950 for market-research analysts. Private-industry wages represented approximately 69.9% of employer compensation costs in March 2026, implying a loaded median-cost equivalent near $110,000 annually before company-specific equipment, recruiting and management overhead.
The model assumes:
| Cost component | Planning assumption |
|---|---|
| One full-time researcher, loaded | $9,000–$10,000 per month |
| Principal review capacity | 20–28 hours per month |
| Principal internal opportunity cost | $175–$225 per hour |
| Source tools, hosting, storage and monitoring | $750–$2,000 per month |
| Editorial administration, corrections and contingency | $1,000–$2,000 per month |
| Total monthly cost envelope | $16,500–$19,500 |
| Protected monthly revenue floor | At least $22,000, preferably $25,000–$30,000 |
The principal cost is an opportunity-cost assumption, not a published salary. It is consistent with LongTermCapabilities’ public $5,000 paid workshop and higher-priced architecture engagements, where principal time must not be displaced by a low-margin subscription.
| Product form | Credible scope | Price tests | Delivery requirement | Conservative margin and viability |
|---|---|---|---|---|
| Weekly research brief | One vertical, 10–20 reviewed records weekly, no custom watchlists | $99, $249 and $399 monthly | Approximately 130–160 researcher hours and 12–20 principal hours monthly, largely fixed | Below 50 subscribers it is unlikely to cover a researcher. Roughly 85 subscribers at $249 or 55 at $399 are needed to approach the protected cost floor. Viable only with meaningful presales |
| Named-account monitoring | 25 organizations, weekly evidence memo, watchlist changes, correction register, monthly summary | $1,500, $2,500 and $3,500 monthly | Approximately 8–14 researcher hours and 1–2.5 principal hours per customer monthly after setup | Best core form. At $3,500, seven to eight subscribers can support $24,500–$28,000 monthly revenue within one-researcher capacity. Estimated gross margin: 32%–45% |
| Monthly principal decision session | One monthly decision memo and 60–90 minute session based on existing radar evidence | $2,000, $3,000 and $4,000 monthly | Approximately 4–6 researcher hours and 3–4 principal hours per customer | Not viable as the only product: principal capacity limits the service to about six customers. Best as a $1,500–$2,500 add-on to named-account monitoring |
| White-label intelligence feed | 50–100 monitored organizations, partner taxonomy, co-branded or unbranded evidence records, monthly editorial review | $5,000, $7,500 and $10,000 monthly; setup fee $5,000–$10,000 | Approximately 30–45 researcher hours and 4–7 principal hours per customer monthly | Strong channel form. Three clients at $7,500 create $22,500 monthly revenue; four create $30,000. Estimated gross margin: 30%–48%, with customer-concentration risk |
The smallest self-service brief should not be built as a software portal. A four-week founding edition can be delivered through email and a private, exportable HTML or PDF evidence pack for $299–$499. A dashboard becomes justified only when customers repeatedly need filtering, history, watchlist administration or exports.
The named-account product should begin at $3,500 for a paid four-week pilot and $2,500–$3,500 monthly thereafter, depending on account count and principal involvement. A price below $1,500 would probably require removing principal review and materially weakening the differentiation.
The high-touch managed version should be priced at $5,000–$7,500 monthly for 50 accounts, a monthly principal session, watchlist administration and customer-specific decision mapping. That remains below LongTermCapabilities’ existing Architecture & Reliability Office while preserving the distinction between public intelligence and client-system architecture work.
Minimum subscriber requirement.
| Portfolio | Approximate subscriber requirement | Capacity implication |
|---|---|---|
| $249 weekly brief | 85–100 subscribers | Economically possible, but substantial acquisition and churn risk |
| $399 weekly brief | 55–65 subscribers | Better economics, still a publishing business rather than a consulting-adjacent service |
| $2,500 named-account subscription | 9–10 subscribers | Near researcher capacity and only modest margin |
| $3,500 named-account subscription | 7–8 subscribers | Preferred sustainable range |
| $7,500 white-label subscription | 3–4 partners | Financially attractive, but highly concentrated |
| Mixed portfolio | Two white-label partners plus three or four $3,500 named-account clients | Best balance of capacity, access and concentration |
The protected target should be $25,000–$30,000 in monthly recurring revenue before hiring a full-time researcher. Below that level, the service should remain a principal-reviewed pilot using fractional research capacity.
Viable candidate organizations and bounded opportunities
The organizations below are not asserted to be distressed, actively buying, or dissatisfied with their current systems. They are candidates because their own public materials show that they already deliver, consume, or monetize work adjacent to competitive intelligence.
| Candidate and public signal | Evidenced operating change | Bounded opportunity |
|---|---|---|
| OST Global Solutions. Its 2026 official training schedule includes Competitive Analysis, Black Hat and Price to Win with AI Insights; its current catalog and service navigation also include competitive analysis, market analysis, account planning and federal pipeline support. | OST is incorporating AI-assisted research and competitive analysis into current training and consulting delivery | White-label technical and organization-level evidence feed for selected federal IT pursuits |
| Lohfeld Consulting Group. In March 2026 it published guidance on ethical AI competitive intelligence; in June 2026 it published a 100-source GovCon intelligence guide; in July 2026 it addressed AI acquisition tools and rapid federal-market changes. | Lohfeld is actively educating customers about AI-assisted intelligence, agency forecasts and changing acquisition practices | Co-branded or subcontract technical-signal appendix supporting capture and recompete work |
| Shipley Associates. Shipley markets Pricing to Win training based on competitive intelligence and offers 2026 federal capture training at $1,645 per participant. | Shipley continues to productize competitive positioning, capture and customer intelligence through current training | Specialist technical-signal module for training, consulting or pre-RFP review |
| Ntiva. Ntiva announced the September 15, 2025 acquisition of Site Tech Services to expand vertical expertise in the automotive market, following other MSP acquisitions and regional expansion. | Acquisition-led vertical and geographic expansion | Named-account radar for MSP consolidation, vendor retirement, Microsoft ecosystem and vertical-market changes |
OST Global Solutions
Verified public facts. OST sells government-business-development consulting, market analysis, competitive analysis, Price to Win services, pipeline support and training. Its 2026 schedule specifically incorporates AI-assisted competitive analysis.
Analyst inference. OST may have an addressable need for a repeatable technical evidence layer—especially for public GitHub, technology hiring, cloud/platform migration, incidents, partner announcements and product lifecycle signals that ordinary procurement databases do not fully interpret.
| Required item | Assessment |
|---|---|
| Likely business or technical problem | Keeping account plans and competitive-analysis engagements current across fragmented technical sources without increasing senior-consultant research time |
| Likely buyer roles | President, Chief Executive Officer, VP Consulting, Competitive Analysis Practice Lead, Market Intelligence Director, Training Director |
| Smallest credible paid engagement | Four-week white-label pilot on 10 named federal IT recompetes or contractors |
| Deliverables | Source map, 15–30 reviewed evidence records, two weekly briefs, one correction register, technical-change appendix, final editorial and integration recommendation |
| Price hypothesis | $6,000–$8,000. The price sits above a two-day training purchase but below a major consulting engagement; OST already monetizes adjacent analysis and training |
| Delivery hours and internal cost | 32–40 researcher hours, 5–7 principal hours; estimated internal cost $3,200–$4,400 |
| Conservative gross margin | Approximately 35%–55% |
| Probable sales cycle | 30–75 days for a pilot; longer if client-specific flow-downs or data terms are required |
| Procurement path | Direct professional-services agreement, subcontract, or white-label content agreement |
| Route | Partner or subcontract route, not mass outreach |
| Thirty-day validation | Produce a public-safe demonstration covering three announced federal technology recompetes; offer a paid 10-account pilot with no exclusivity |
| Stop conditions | Requests for personal enrichment, undisclosed scraping, fictional win scores, broad free research, client-confidential data before contract, or resale rights broader than the source terms permit |
Lohfeld Consulting Group
Verified public facts. Lohfeld currently presents ethical AI-assisted competitive intelligence, public agency forecasts, capture strategy and recompete intelligence as important GovCon capabilities.
Analyst inference. Lohfeld is likely more sophisticated than a basic radar buyer. The only credible offer is a narrow technical-signal complement that does not compete with its account strategy, capture consulting or human intelligence.
| Required item | Assessment |
|---|---|
| Likely problem | Technical source review may be expensive to repeat across client pursuits, particularly where public repositories, cloud/product transitions and reliability records matter |
| Likely buyer roles | Chief Executive Officer, President, Managing Director, VP Capture, Competitive Intelligence Practice Lead, Research or Content Director |
| Smallest paid engagement | Four-week technical-signal appendix for five pursuits in one agency or technology category |
| Deliverables | Source taxonomy, evidence records, contradiction log, technical operating-change summary and handoff template for Lohfeld consultants |
| Price hypothesis | $5,000–$7,500. Lohfeld’s public emphasis on disciplined, ethical intelligence supports paying for reviewed evidence, but it is likely to reject undifferentiated monitoring |
| Delivery hours and internal cost | 26–34 researcher hours, 4–6 principal hours; estimated cost $2,700–$3,800 |
| Conservative gross margin | Approximately 35%–58% |
| Probable sales cycle | 45–90 days |
| Procurement path | Subcontract, referral or white-label research agreement |
| Route | Partner introduction, event relationship or direct practice-level conversation |
| Thirty-day validation | Deliver one public demonstration that adds technical sources not present in a standard procurement brief; ask for a paid limited-use pilot |
| Stop conditions | The proposed records merely repeat SAM.gov or commercial GovCon databases, the partner will not expose a real editorial use case, or requested exclusivity prevents service to the broader market |
Shipley Associates
Verified public facts. Shipley explicitly teaches competitive intelligence, customer price-capability trade-offs and competitive positioning, and sells current two-day capture training for $1,645 per participant.
Analyst inference. Shipley has demonstrated willingness to monetize intelligence methods, but it may view the radar as content supply rather than a strategic product. A generalized subscription is unlikely to be compelling.
| Required item | Assessment |
|---|---|
| Likely problem | Maintaining current technical examples and evidence for courses, client reviews and pre-RFP positioning |
| Likely buyer roles | President, VP Consulting, VP Training, Capture Practice Lead, Product or Curriculum Director |
| Smallest paid engagement | One co-branded technical-signal module or evidence pack for a defined training or consulting use case |
| Deliverables | 10–15 reviewed technical signals, source notes, facilitator guidance, limitations and a reusable evidence template |
| Price hypothesis | $4,000–$6,000 for a limited module; the $1,645 participant price provides evidence that clients pay for structured capture expertise, but not that Shipley will buy an external subscription |
| Delivery hours and internal cost | 22–30 researcher hours, 4–5 principal hours; $2,400–$3,300 |
| Conservative gross margin | Approximately 30%–55% |
| Probable sales cycle | 60–120 days |
| Procurement path | Content license, subcontract or consulting-services agreement |
| Route | Partner or referral |
| Thirty-day validation | Offer a paid single-module pilot rather than a platform demonstration |
| Stop conditions | Broad perpetual content rights, extensive custom curriculum work, or a request to imply that public signals reveal customer intent |
Ntiva
Verified public facts. Ntiva has used acquisitions to expand its geography and sector expertise, including its September 2025 Site Tech Services transaction in the automotive sector and prior MSP acquisitions.
Analyst inference. A corporate-strategy or alliance team might benefit from monitoring MSP consolidation, Microsoft and security partner changes, vertical hiring and product retirements. However, the public evidence is weaker than for GovCon consulting candidates because no public source establishes an unmet intelligence need.
| Required item | Assessment |
|---|---|
| Likely problem | Fragmented monitoring of competitors, acquisition markets, vendors, product lifecycles and vertical technology changes |
| Likely buyer roles | Chief Strategy Officer, VP Corporate Development, VP Marketing, VP Alliances, VP Managed Services |
| Smallest paid engagement | Four-week 25-account MSP and vendor ecosystem pilot |
| Deliverables | Watchlist, weekly reviewed changes, acquisition and partnership chronology, product-retirement register, final account-priority discussion |
| Price hypothesis | $3,500–$5,000 for the pilot, then $2,500–$3,500 monthly |
| Delivery hours and internal cost | 18–26 researcher hours, 3–5 principal hours; $2,000–$3,000 |
| Conservative gross margin | Approximately 30%–55% |
| Probable sales cycle | 45–120 days, including ordinary vendor onboarding |
| Procurement path | Direct corporate-services purchase order or short professional-services agreement |
| Route | Direct only with a warm referral or identifiable strategic initiative |
| Thirty-day validation | Build a public-safe MSP-market demonstration, but perform no custom unpaid watchlist build beyond five organizations |
| Stop conditions | No warm route, no named decision owner, pilot framed as sales-lead generation, or expectation that acquisitions and hiring prove financial distress |
No-action account: 3Cloud should not be pursued as an initial direct customer. Cognizant completed its acquisition of 3Cloud effective January 1, 2026, creating a larger enterprise procurement environment and uncertain post-acquisition ownership of any intelligence need. A subcontract opportunity could emerge later, but there is no presently evidenced small, direct and fast procurement route.
Validation design, governance, liability, and no-go rules
The radar should be sold as decision support based on reviewed public evidence, not as lead scoring, investment intelligence, diligence assurance, vulnerability intelligence or proof of organizational intent.
The public-record taxonomy should use four mandatory fields:
| Classification | Publication rule |
|---|---|
| Verified public fact | Must cite an organization-controlled or authoritative source, include the signal date and state exactly what changed |
| Analyst inference | Must state the reasoning and identify plausible alternative explanations |
| Unknown | Must identify information that cannot be established from public evidence |
| Required human decision | Must identify the decision owner and the additional evidence needed before action |
Each customer record should include an intent prohibition such as: “This event does not establish budget, distress, procurement authority, vendor dissatisfaction or willingness to purchase.”
The system should never collect or publish personal contact enrichment, inferred personality, private-repository activity, personal contribution scoring, home information, speculative employee movement, automated outreach sequences or vulnerability exploitation guidance. GitHub’s terms specifically require API and data collectors to comply with acceptable-use, privacy and intellectual-property requirements.
The product also requires source-specific controls:
| Risk | Required control |
|---|---|
| Incorrect or amended filing | Retain accession number, filing date and amendment status; provide correction workflow |
| Form D overinterpretation | State that it is a notice, not SEC approval, and that the SEC may not have verified completeness |
| Job reposting and duplicates | Normalize job IDs, locations and posting-system changes; report repeated patterns rather than isolated vacancies |
| GitHub personal-data leakage | Monitor organization and repository state only; do not create personal developer profiles |
| Incident sensationalism | Publish only resolved incident facts and organization-authored remediation; no “company in trouble” language |
| Copyright and resale | Store short factual extracts and metadata, not republished articles or full proprietary reports |
| Procurement-sensitive data | Use public SAM.gov and USAspending outputs only; do not distribute sensitive API responses |
| Stale inference | Apply a review or expiry date and show when the source state last changed |
| Customer misuse | Contractually prohibit automated outreach, employment decisions, investment decisions and claims of buying intent based solely on radar records |
The first 30-day market test should be run as a paid-service experiment rather than a software build.
| Week | Test |
|---|---|
| First week | Select one vertical and 25 organizations. Capture every raw event and measure collection, normalization and review time |
| Second week | Publish the first reviewed brief. Ask customers to label each item “decision-relevant,” “context only,” “already known,” or “not useful” |
| Third week | Conduct a 60-minute principal session using the evidence. Record which decisions changed, narrowed or stopped |
| Fourth week | Deliver a decision memo showing source yield, rejection rate, correction rate, review hours, customer use and renewal terms |
The experiment should test three paid prices rather than survey hypothetical willingness:
| Test cohort | Offer |
|---|---|
| Three founding named-account customers | $3,500 four-week pilot |
| One prospective high-touch customer | $5,000 pilot including principal session and 40–50 accounts |
| One white-label consultancy | $7,500 setup and first-month pilot |
The experiment succeeds only if customers pay. Free newsletter signups, demonstration compliments, social engagement and interview enthusiasm are not substitutes for a purchase.
Commercial stop conditions should be predetermined:
- Stop the broad weekly brief if fewer than 20 customers prepay at least $249 after a bounded launch campaign.
- Stop the named-account product if median human review exceeds 20 minutes per published record after normalization, unless customers will support prices above $5,000 monthly.
- Stop or narrow a source class if more than 5% of published records require substantive correction.
- Stop the white-label form if a partner demands unbounded custom research, perpetual exclusive rights, removal of evidence labels or claims of buyer intent.
- Do not hire a full-time researcher until contracted recurring revenue reaches at least $20,000 monthly, with a credible path to $25,000–$30,000.
- Do not proceed with private-equity or investment customers until counsel reviews disclaimers, permitted uses, data retention and the boundary between operating intelligence and investment advice.
- Do not productize automated outreach, personal enrichment or lead scores, even if prospective buyers request them.
Ranked opportunities and required decisions
| Rank | Opportunity | Fit with LongTermCapabilities | Public-evidence strength | Speed to first revenue | Contract value | Recurring potential | Delivery risk | Access difficulty |
|---|---|---|---|---|---|---|---|---|
| First | Managed named-account monitoring for boutique Microsoft, software and AI consultancies | Very high | Moderate | Moderate to fast through existing partner relationships | $30,000–$60,000 annualized per customer | High | Moderate | Moderate |
| Second | White-label technical signal feed for GovCon capture consultancies | High | Strong | Moderate | $60,000–$100,000 annualized per partner | High | Moderate to high because of customization | Moderate |
| Third | Named-account MSP ecosystem monitoring | High | Moderate | Moderate | $24,000–$42,000 annualized | Moderate to high | Moderate | Moderate to high |
| Fourth | Monthly principal decision session as an add-on | Very high | Strong internal fit | Fast after a monitoring customer exists | $18,000–$30,000 incremental annualized | Moderate | High principal-capacity risk | Low after initial sale |
| Fifth | Paid weekly vertical brief | Moderate | Strong evidence that alternatives exist, weak evidence for LTC-specific willingness | Potentially fast to launch, slow to reach break-even | Low per subscriber | Moderate | High churn and acquisition risk | Low per customer, high in aggregate |
| Sixth | Private-equity operating-team service | Moderate | Weak for an initial LTC purchase route | Slow | Potentially high | High if successful | High liability and domain-expectation risk | Very high |
| Seventh | Generic specialist-vendor competitive-intelligence feed | Low to moderate | Strong competitor presence, weak differentiation without a niche | Slow | Moderate | Moderate | High substitution risk | High |
The four product forms should therefore be treated as a sequence, not parallel launches:
First, sell a paid named-account pilot. Second, add a principal session only when the customer has evidence worth discussing. Third, adapt the same reviewed records into one white-label partnership. Last, publish a paid weekly brief only after customer work reveals a repeatable vertical taxonomy.
The following human decisions remain before launch:
| Decision | Recommended answer |
|---|---|
| Is the radar a lead-generation product? | No. It is reviewed evidence and decision support |
| Should it cover all proposed signal classes at launch? | No. Begin with procurement, official filings, jobs, GitHub, product/partner changes and resolved incidents for 25 accounts |
| Should a software dashboard be built first? | No. Use exportable evidence packs and email until repeated customer behavior justifies workflow software |
| Should the first hire be full-time? | No. Use fractional research until recurring revenue reaches at least $20,000 monthly |
| Should principal review be included in the cheapest tier? | No. Include it in managed tiers and white-label editorial review |
| Should financing, hiring or incidents trigger sales outreach? | No. They are contextual evidence only |
| Should the product claim “opportunities” or “buying signals”? | Avoid those terms unless the record is an actual public procurement notice. Use “commercial signals,” “operating changes” and “decision relevance” |
| Should PE operating teams be targeted immediately? | No, absent a warm route, counsel-reviewed terms and a defined portfolio-operations decision |
| What is the launch threshold? | At least three paid pilots, one renewal, measured review economics and no material evidence-governance failures |
The recommended commercial decision is proceed with a narrowly bounded paid pilot, not a full subscription launch. The product becomes a business only when customers repeatedly pay for the distinction between a public fact, an analyst inference, an unknown and a decision. Without that distinction, it is another alert feed; with it, the radar is closely aligned with LongTermCapabilities’ existing evidence-oriented architecture practice.