Mark43

1.1 Identity and operating model

Mark43 is a public-safety software vendor whose described product set combines computer-aided dispatch (CAD), records management (RMS), mobile tools, and analytics. Inc. Magazine's republished article and Mark43's own product announcement describe workflows spanning dispatch, reporting, investigations, and case summarization; AUVSI's 2025 article describes an open API and integrated systems. Gartner's vendor page and a public-safety technology directory also describe the product category, but those listings are not comparative performance benchmarks. EquityZen and Inc. place the company in New York. The available evidence supports a software platform serving public-safety agencies; it does not establish pricing, contract mix, recurring-revenue composition, or whether every listed module is deployed at every customer. The company profile table separates reported figures from metrics that remain unavailable.[CO001, CO004]

1.2 Leadership and governance

The allocated reporting identifies co-founders Scott Crouch, Matt Polega, and Florian Mayr as Harvard classmates; Polega is also described as Head of External Affairs. EquityZen's profile and Mark43's 2026 survey release identify Bob Hughes as CEO. These sources establish a small set of visible senior figures, not a complete current leadership roster. The source pool provides no board composition, director independence, ownership, voting rights, executive tenure, succession planning, or key-person retention terms. Founder continuity is discussed in Polega's interview, but it does not substitute for governance evidence. The leadership exhibit is therefore a partial enumeration, and diligence should establish who controls the company and how product, security, and customer commitments are governed.[CO002, CO009]

1.3 Financing, stakeholders, and operating scale

EquityZen lists $370 million as Mark43's total funding, and names General Catalyst, Spark Capital, Breyer Capital, Bezos Expeditions, and Tiger Global Management as notable investors. Inc. separately reports an early $78 million funding figure that included General Catalyst, Spark Capital, and Bezos Expeditions; because its article date is not established in the fetched copy, that figure is historical context rather than a current total. Neither source supplies a round-by-round schedule or current ownership terms. Agency counts also vary: EquityZen says over 120, Pulse 2.0 says over 200, and Dealroom reports more than 300 agencies as customers in acquisition coverage. Their dates, definitions, and active-customer denominators are not reconciled. These are reported counts, not independently verified active deployments. ARR, GAAP revenue, growth, margins, valuation, debt, and current headcount are not established by the assigned evidence.[CO005, CO006, CO007, CO008]

1.4 Milestones, execution, and diligence

The available chronology shows a product-led expansion from a Washington, D.C. Metropolitan Police Department project to AI-assisted case summarization and report writing, followed by a 2026 ForceMetrics partnership and acquisition. Dates and descriptions are retained at the precision supplied by the sources; the reported founding year remains inconsistent between EquityZen and Inc. Mark43's announcements describe human review before AI-assisted reports are submitted, while company-issued survey releases report broad interest in AI and sector-wide cyber concerns. Neither kind of company-issued evidence demonstrates product accuracy, customer outcomes, security effectiveness, or a company-specific incident history. EquityZen flags cybersecurity and data-breach exposure as a potential cost and trust risk, but does not document a Mark43 breach. The timeline records dated claims; financing terms, operating metrics, independent controls, and production-scale AI evidence remain diligence priorities.[CO003, CO010, CO011, CO012, CO013, CO014, CO015]

2.1 Market boundary and buying context

The defensible core boundary is software sold to public-safety agencies for computer-aided dispatch, records management, and connected analytics and mobile workflows; Mark43's procurement listing also describes digital evidence and implementation services. Those bundled modules should not be conflated with physical devices, an emergency communications network, or the full cost of an agency's technology stack. EdgeMarket lists a competitive RFP procurement route, while Mark43's own announcements describe deployments across Florida agencies. These establish public agency demand and a route to purchase, not a universal procurement model or the identity of each agency's final budget approver. The incumbent alternative is continued use of legacy or fragmented systems; replacement therefore depends on agency readiness, integration needs, and a funded procurement cycle.[CM001, CM002, CM003, CM004, CM015]

2.2 Market sizing: distinct lenses, not a company TAM

The two public numerical lenses are not additive or interchangeable. An Inc article reposted by Mark43 cites an estimated global police-software market of $11.6 billion, but the fetched copy provides neither a base year nor methodology. Frost & Sullivan's dated estimate concerns U.S. Next-Generation 911 systems, a narrower adjacent infrastructure category; its $1.19 billion 2026 value was a forecast published in 2022, not a current realized market measure. Neither figure isolates CAD/RMS procurement that Mark43 can serve, and neither provides a defensible SAM or SOM. A 2026 public-facing market estimate, source methodology, and agency-level spending denominator remain unavailable, so this chapter does not manufacture a bottom-up total from agency counts or survey interest.[CM005, CM006, CM007, CM016]

2.3 Buyer demand, adoption drivers, and constraints

The strongest demand evidence is directional rather than a measure of purchasing: Mark43-sponsored surveys report interest in AI, consolidated CAD/RMS, and fewer application silos. The 2025 survey's disclosed methodology describes 538 opt-in online respondents overall; the article does not give the subgroup denominators for its law-enforcement percentages. A separate 2026 report gives additional percentages but this article does not disclose its sample size, so the two survey vintages should not be treated as a trend series or market penetration. Reliability and cyber concerns may increase modernization urgency while also raising security review, integration, and continuity requirements. NG911 is a relevant adjacent modernization cycle, but the cited regulatory and grant commentary concerns 911 network transition, not general CAD/RMS budgets. Public contract terms and current agency budget allocations are too sparse to quantify adoption velocity or revenue opportunity.[CM008, CM009, CM010, CM011, CM012, CM013, CM014, CM016]

2.4 Exhibits

3.1 Competitive set and disclosed scale

The clearest direct comparisons are CAD and public-safety operating suites: Mark43, Tyler, GINA Smart CAD, Octave and CentralSquare. GINA's May 2026 competitor-authored comparison presents its own Smart CAD as a multi-sector, on-premises alternative, and characterizes Mark43 as more law-enforcement-focused; that characterization is an interested vendor's view, not an independent benchmark. Tyler's own public-safety page describes multi-agency dispatch alongside Fire & EMS, mobile, records and analytics offerings. Motorola's cited page is a narrower substitute at the emergency-call-handling layer, while Prepared is an adjacent call-intelligence product whose 2025 acquisition announcement does not establish its present ownership or product status. Mark43's 2026 acquisition of ForceMetrics points to a further data-orchestration adjacency. Across these profiles, company-reported user or agency counts are not directly comparable: the units, populations, and reporting dates differ, and most vendors disclose no scale in this pool.[CP001, CP002, CP003, CP004, CP005, CP006, CP007, CP008, CP009, CP012, CP013, CP014]

3.2 Capability, deployment and trust posture

The evidence supports a product-scope comparison, not a measured performance ranking. Public Safety Tech Source describes Mark43 as a cloud-native, integrated public-safety platform, and Gartner's profile lists CAD, RMS, analytics, and property and evidence based on public information updated in 2023. AUVSI's 2025 feature describes an open API and unified environment through Mark43 executives, and reports an executive's FedRAMP High certification statement. Tyler's official page documents multi-agency dispatch, Fire & EMS, mobile operations, records and analytics. Motorola presents cloud-native VESTA NXT and on-premises VESTA 911, plus mapping and analytics, but the assigned page does not establish equivalent CAD/RMS coverage. GINA's comparison describes Octave and CentralSquare deployment choices, but provides no independent validation. No source in the pool compares implementation time, uptime, AI accuracy, interoperability outcomes, security incidents by vendor, or switching effort on a common basis.[CP001, CP004, CP005, CP007, CP008, CP009, CP010]

3.3 Commercial access and pricing evidence

The only concrete channel evidence is EdgeMarket: Edge and Mark43 announced that member institutions could procure Mark43 through Edge's cooperative platform, with the announcement describing relief from individual RFP processes. This is partner-issued distribution evidence, not proof of contract conversion, sales efficiency, or lower realized prices. The reviewed product and comparison pages do not supply comparable license prices, implementation fees, discounts, renewal terms, or total cost of ownership for Mark43 and the named alternatives. Agency procurement documents and redacted proposals are therefore needed before inferring price advantage or a durable commercial moat.[CP011]

3.4 Durability, buyer friction and disconfirming signals

Public evidence supports a plausible value proposition around integrated workflows, mobility and data exchange, but not a demonstrated moat. Gartner Peer Insights showed zero Mark43 ratings on a page for a market marked retired; this is a thin review signal, not evidence of poor satisfaction or product failure. GINA's critique of Mark43's law-enforcement focus is competitor-authored and should be treated as a claim to test in multi-discipline procurements. Mark43's own 2026 survey reports widespread cyber issues and manual data transfer among respondents, which describes sector pain rather than incidents at Mark43 or a comparison of vendor outcomes. Dealroom's report on ForceMetrics and Axon's earlier Prepared agreement indicate strategic activity around consolidating data and call workflows, but do not prove that Mark43 wins or loses against those offerings. The pool contains no customer win/loss evidence, switching-cost data, customer-built alternatives, or independent feature benchmark; these remain diligence priorities.[CP003, CP004, CP012, CP013, CP014, CP015, CP016]

4.1 Product scope is visible; monetization is not

Mark43's own company page presents its platform as core operating software for public-safety agencies [CI001], and its company and CAD pages describe CAD and RMS capabilities [CI002]. A public-safety technology directory also lists mobile field tools and analytics [CI003], but these descriptions establish product scope, not a bundle purchased by any one agency. The assigned pages disclose neither list prices, realized discounts, contract values, billing units, nor revenue-recognition policy [CI012]. The ForceMetrics announcement describes a product integration, not contracted revenue or customer economics [CI005]. The revenue table separates identifiable product streams from unavailable monetization inputs; the flow is an underwriting path, not a verified Mark43 transaction.

4.2 Public-sector routes do not establish sales efficiency

Public-sector distribution can involve procurement and grant-supported customer budgets, but the sources do not establish Mark43's sales cycle, win rates, or sales efficiency. SAM.gov provides access to opportunity, award, and subcontract data [CI008]; the assigned page itself identifies no Mark43 award [CI015]. 911.gov describes federal programs potentially applicable to emergency-communications projects [CI009] and, as captured on 2026-10-26, says no 911 Grants were open for applications [CI010]. A Mark43-issued survey release says 40% of UK respondents cited budget and funding constraints [CI011]. Treat that company-issued finding as a directional demand headwind, not an independent benchmark or a Mark43- specific lost-deal rate. Mark43's May 2026 announcement reported more than 300 agencies [CI006], while Axon describes a product integration [CI007]; neither supplies price, contract, or channel economics. Agency scale is not revenue.

4.3 Unit economics and service-delivery costs remain unquantified

LeadIQ lists Mark43 in a 201-500 employee band without an as-of date [CI004]; Gartner's profile, updated on 2025-02-26, shows zero ratings in a retired category [CI016]. These are limited scale and public-validation signals, not evidence of revenue per employee, customer concentration, satisfaction, or retention. The assigned source set contains no current GAAP revenue, ARR, growth, or renewal metrics [CI012], and it does not quantify customer price, contract duration, gross margin, CAC, sales payback, hosting expense, implementation, support, working capital, or capex [CI014]. Product breadth, an integration, and a company-reported agency count cannot substitute for contribution margin or cohort retention. The unit-economics table leaves unknown values null and gives a specific data request for each.

4.4 Public evidence cannot establish capital adequacy

None of the reviewed assigned sources states current cash, monthly burn, runway, debt or project-finance obligations, use of funds, or a next-round trigger [CI013]. The SAM.gov and 911.gov pages describe buyer-side contracting and grant routes, not money received by Mark43 or proof of a customer contract [CI015]. The evidence supports product scope and commercial relationships, but not cash available to fund implementation, support, or future growth. This is a material underwriting limitation, not evidence that cash is exhausted or that a financing is imminent. Obtain audited statements, cash forecasts, debt and commitment schedules, and customer-level revenue and implementation cohorts before underwriting.

5.1 Product scope and agency workflows

Mark43 sells a public-safety operations platform organized around computer-aided dispatch (CAD), records management (RMS), mobile access, and analytics. AWS describes the suite as mobile-first and cloud-native; AUVSI describes CAD, RMS, and analytics within a unified environment, and the AWS Marketplace seller listing places those functions across dispatch, response, reporting, investigation, and operational management. These are product descriptions, not comparative performance results. Mark43's May 2024 release says New Mexico DPS added CAD, mobile dispatch, analytics, and interfaces to an RMS relationship that began in March 2023. It attributes to agency users the ability to prioritize calls, see responder status and location, and receive field messages on multiple device types.[CE001, CE002, CE003, CE004]

5.2 Architecture, integration, and maturity

The evidence supports a workflow-level architecture rather than a verified technical design: field and dispatch applications feed records workflows, and company or partner materials describe shared data, APIs, analytics, and AI-assisted reporting. Mark43's ReportAI page says the RMS feature drafts reports from CAD data, body-camera transcripts, officer notes, and event context, with configurable roles for generation, editing, review, and approval. AUVSI also describes analytics and mobile CAD features, but its examples are narrative rather than measured tests. A third-party product directory lists additional names such as Evidence, Compliance, and Data Exchange; that listing is not proof of current availability or deployment. The product stack is therefore broader than the independently verifiable implementation record.[CE002, CE005, CE006, CE007]

5.3 Deployment evidence and operating limits

The clearest named implementation in the assigned evidence is New Mexico DPS: Mark43's 2024 release describes a statewide CAD launch with mobile dispatch, analytics, and interfaces, following earlier RMS use. The release quotes agency personnel on field messaging, responder visibility, and a smooth transition, but it supplies no deployment-duration, uptime, recovery-time, or quantified productivity measure. AUVSI recounts a Fort Myers hurricane scenario in which operations continued during a local communications outage; that account is useful as a customer-story lead, not as independently tested resilience evidence. The public record also does not specify offline behavior, integration test coverage, migration burden, or support service levels. Buyers should validate those items against a live deployment and contract-level service commitments.[CE003, CE004, CE014, CE015]

5.4 Trust, cybersecurity, and diligence gaps

Public-safety workflows handle sensitive operational data, and the assigned government sources describe sector-level risks rather than Mark43-specific incidents or validated controls. CISA identifies ransomware, telephony denial-of-service, and malware as relevant 911 threats; the National 911 Program notes that IP-based data sharing expands cyber exposure. FCC NG911 requirements describe dependencies on IP-based delivery and coordination among 911 authorities and originating service providers; they do not establish Mark43's compliance status. The retrieved Mark43 2025 U.S. Public Safety Trends report says 84% of law-enforcement respondents reported that their organization experienced a cybersecurity issue in the last year. Its methodology describes an opt-in online survey of 538 public-safety professionals conducted October 2–23, 2024, with a maximum sampling error of four percentage points at 95% confidence; it does not state the law-enforcement subgroup denominator, and the figure is not a Mark43 product incident rate. No independent security assessment, AI error study, privacy-control evidence, or public developer-activity signal is present in the allocated text. These are material diligence requests, not evidence that a control or incident is absent.[CE010, CE011, CE012, CE013]

6.1 Customer base and segmentation

The public materials position Mark43 primarily for public-sector public-safety agencies, with police departments as the clearest named buyer and police/fire organizations as an adjacent deployment segment. Mark43 describes its platform across dispatch, records, mobile, analytics, and booking workflows. The strongest current scale figure is Mark43's own statement that it is trusted by over 300 agencies globally. That is a company-reported agency count, not an audited active-customer count, revenue measure, or retention statistic. Federal funding may be another purchasing route: 911.gov lists assistance that may apply to 911 and NG911 projects, but does not connect programs to Mark43 deployments. A Nassau County announcement describes four neighboring police departments moving from legacy on-premises systems, with three live and one scheduled to follow. In Massachusetts, Mark43 reports more than a dozen launches over the prior 18 months and separately names police, fire, university, and sheriff organizations. These announcements suggest regional, multi-agency deployments, but disclose neither the full customer mix nor deployment-level contract value.[CU001, CU002, CU003, CU004, CU006, CU007, CU018]

6.2 Adoption evidence and customer proof

The available adoption evidence consists mainly of named deployments and customer quotations carried in Mark43 releases or company-oriented coverage. The Nassau release identifies four agencies and reports three as live at publication, while Mark43's Massachusetts announcement names new agency relationships and reports launch activity. These are useful evidence of selected implementations, but the issuer controls the release and the materials provide no contract records, customer-side implementation measures, or independent confirmation of the aggregate footprint. Quoted agency officials describe legacy-system limitations, mobility, data sharing, and modernization needs; those statements establish the stated rationale, not measured savings or realized outcomes. AUVSI's article recounts a Fort Myers Police Department resilience example, but it is not a customer-authored evaluation. A 2026 Mark43-issued survey article reports that 90% of law-enforcement respondents said their organization had experienced a cyber issue in the prior year, up from 84%; its fetched text does not state sample size or methodology. This is company-reported survey evidence, not proof that respondents use Mark43 or that adoption improves agency performance.[CU003, CU004, CU005, CU010, CU014]

6.3 Durability, expansion, and concentration

Expansion signals are present but narrow: Mark43 says Boston Police Department expanded its existing relationship to Booking, and it announced a partnership with Mi-Case to connect its CAD/RMS/mobile/analytics suite with a jail management system. The partnership describes an intended combined offering, not evidence that a customer has deployed it. Mark43 also reports over 300 agencies in two company releases, but those repeated statements share the same issuer and do not independently corroborate the total. On Gartner Peer Insights, the fetched Mark43 vendor page showed zero ratings; that is a bounded absence of reviews on that page, not evidence that Mark43 has no customers or dissatisfied users. GovWare Reviews calls pricing non-public and positions the product as premium, without providing an underlying quote or customer evidence. The reviewed materials disclose no NRR, GRR, churn, renewal, cohort usage, or top-customer share. Consequently, adoption durability, customer economics, and concentration remain open diligence items rather than conclusions inferred from logos or aggregate agency claims. Motorola Solutions' own command-center page describes an adjacent public-safety software offering, but it does not establish customer overlap, Mark43 displacement, or comparative performance.[CU002, CU011, CU012, CU013, CU015, CU016, CU017]

6.4 Exhibits

7.1 Cybersecurity and service continuity

Cybersecurity and availability are the most consequential evidenced risk categories because public-safety systems support dispatch, records, and investigations. CISA describes emergency communications centers as targets for attacks intended to disrupt operations, and its materials identify ransomware, telephony denial-of-service, and malware as relevant threats (CR003). A Mark43-sponsored survey reported sector-level cyber and availability problems, including RMS and CAD downtime, but those results are not Mark43 incident or service-level data (CR004, CR005, CR006). The 2025 DOI deployment spans six law-enforcement programs and about 3,000 officers across more than 850 locations; a failure in such an operational footprint could have broad impact within that deployment, although no Mark43 uptime or recovery performance is quantified in the retained evidence (CR001, CR002, CR014).[CR001, CR002, CR003, CR004, CR005, CR006, CR014]

7.2 Legal, data, and AI governance

The regulatory exposure is jurisdiction-specific rather than a single disclosed license question. CISA says emergency communications center operators should verify that intended AI uses comply with applicable legal and policy requirements (CR009). Mark43's April 2026 release describes configurable agency permissions, human oversight, audit logs, and controls for its AI products; these are company statements, not independent tests of model accuracy, data handling, or legal compliance (CR010). CISA also describes NG911 as an IP-based environment connecting public and private networks, which makes integration, access controls, and continuity relevant diligence topics (CR007). The available sources do not establish the jurisdiction-by-jurisdiction requirements applicable to each deployment or any current litigation or enforcement status; those remain explicit gaps rather than assumed clean records.[CR007, CR009, CR010]

7.3 Implementation and ecosystem dependencies

A connected CAD/RMS platform can reduce disconnected workflows, but it also makes reliable interfaces, external data sources, and customer-side operations important to service quality. CISA describes NG911 interconnection across a wide range of public and private networks (CR007); an AUVSI feature based on Mark43 personnel describes an open API and integrations as product capabilities, not as independently tested reliability results (CR011). The DOI deployment is evidence of scale at one federal customer, not evidence of customer concentration across Mark43's portfolio or of contracted service performance (CR002, CR014). Diligence should therefore test interface failure modes, agency and supplier responsibilities, data portability, disaster recovery, and customer references across more than one large deployment.[CR002, CR007, CR011, CR014]

7.4 Financial resilience and public procurement

Public evidence is insufficient to underwrite working-capital resilience or customer funding dependence. Tracxn's fetched profile reports $219 million raised and a March 2024 latest-round date, but its displayed valuation is obscured; neither funding raised nor a secondary profile establishes cash available, burn, runway, or current valuation (CR013). 911.gov lists federal assistance programs relevant to emergency communications and states that no 911 Grants are currently open on the fetched page (CR012). That is a time-bound program observation, not evidence that Mark43 customers depend on grants or that all other funding is unavailable. Procurement timing, implementation cost, contract renewal terms, and the company's own liquidity remain unquantified and should be treated as diligence gaps.[CR012, CR013]

7.5 Monitoring indicators and thesis-break conditions

The evidence supports monitoring measurable service and governance outcomes, not assigning a precise probability to a Mark43-specific failure. The cited surveys report sector-level cyber incidents and system unavailability, while the retained material contains no Mark43-specific incident counts, uptime series, service-level agreement, or recovery-test results (CR003, CR004, CR006, CR014, CR015). Escalate diligence if the company cannot provide independently reviewable security attestations, incident disclosure procedures, recovery-time and recovery-point commitments, or customer references for severe disruptions. For AI products, require error and correction rates, audit-log samples, retention and access controls, and evidence that agency controls work in production. Any sustained outage, material breach, failed legal review, or inability to meet contracted recovery obligations would challenge the operating thesis; public evidence does not establish that any such event has occurred.[CR003, CR004, CR006, CR014, CR015]

8.1 Price-sensitive conclusion

Recommendation: research-more, with low confidence and high underwriting risk; valuation stance: unpriceable from the assigned public record. Dealroom reports a September 2026 ForceMetrics acquisition but says its terms were not disclosed, while its article reports more than 300 agency customers without providing revenue per agency, retention, or implementation economics. A federal deployment described by HSToday supports operating reach, not a revenue multiple. The current evidence therefore supports a plausible product-and-market thesis, but not a buy decision, a target return, or a defensible equity value. This is not an assertion that Mark43 lacks those metrics; they are not established by the sources retained for this chapter. Entry discipline should require verified financials and fully diluted capitalization before comparing any proposed price with an intrinsic-value range.[CV001, CV002, CV004, CV014]

8.2 Commercial evidence and what it does not price

The strongest deployment evidence here is HSToday's account of the Department of the Interior rollout across six law-enforcement programs, roughly 3,000 sworn officers, and more than 855 locations; HSToday attributes the account to a press release. This is meaningful implementation proof, but no contract value, recurring revenue, renewal, margin, or customer concentration is disclosed. Dealroom's acquisition coverage and Fundz's acquisition listing add a strategic expansion signal, not a transaction multiple: deal terms remain undisclosed. AWS Marketplace labels Mark43 "Private Offer only," which is a purchasing route, not a public list price. The public record thus offers no directly comparable price-to-ARR or price-to-revenue calculation, and a per-share indication without security class, share count, and transfer terms would not establish enterprise or equity value.[CV001, CV003, CV004, CV005, CV011]

8.3 Demand signals and underwriting constraints

Mark43's own 2026 survey reports support for AI use among U.S. law-enforcement respondents, but the article does not provide survey sample size or methodology in the fetched text; it is company-issued evidence of stated interest, not a willingness-to-pay benchmark. Federal materials describe a real modernization agenda: CISA discusses IP-based NG911 interconnection and associated cybersecurity resources, while FCC rules set phased obligations for originating service providers after valid 911-authority requests. These rules do not establish a Mark43 contract or a purchase mandate for its software. 911.gov lists federal assistance programs relevant to emergency communications and says no 911 Grants are open for application on the page reviewed. CISA's warnings about cyber threats to emergency communications are sector-level diligence context, not evidence of a Mark43 incident. Procurement timing, funding eligibility, security review, and integration costs can therefore interrupt the path from category need to company revenue.[CV006, CV007, CV008, CV009, CV010, CV015]

8.4 Scenario discipline and next evidence

A bull case requires proof that the ForceMetrics acquisition and integrated CAD/RMS, analytics, and AI capabilities expand wallet share while preserving implementation quality, gross margin, and retention. The base case is continued product adoption without enough public financial disclosure to convert agency reach into a price. The bear case is slower procurement or grant conversion, security and integration burdens, or acquisition costs that do not translate into durable customer economics. These are conditional operating paths, not probability-weighted forecasts: assigned sources do not support numeric valuation ranges or target returns. Before investment, request audited revenue and ARR reconciliations, growth and gross-margin history, retention and cohort data, customer concentration, contract and implementation economics, acquisition consideration and integration costs, fully diluted capitalization, debt, and liquidation preferences. Revisit the call only after those inputs can support a model and comparable set; until then, no numeric entry price is defensible.[CV003, CV010, CV012, CV013, CV014, CV015]