The 44 Questions Arco Asks Before Entering a Market
The operational questions Arco works through before committing to any market.
Last reviewed May 2026 · 44 questions
Market Structure
10 questionsWhat makes a market structurally ready for autonomous reconstruction?
A market is structurally ready when its core value delivery relies on repetitive, rules-based human coordination rather than genuine judgment. We look for high transaction volume, low outcome variance, and a labour cost structure that represents the majority of operating expense. These are the conditions that make Operational Arbitrage both achievable and durable. → Operational Arbitrage
How do we define a proven market versus an emerging one?
A proven market has demonstrated demand, established pricing, and a customer base that is already paying for a solution — however inefficient that solution is. We do not enter markets to create demand; we enter markets where demand already exists and the incumbent delivery mechanism is structurally expensive. Emerging markets carry validation risk that autonomous reconstruction cannot eliminate. → Memo #05: Markets That Work
What revenue concentration patterns indicate a reconstructable market?
Markets where the top three to five incumbents hold less than 40% combined market share signal Fragmented Competition — the structural condition we target most deliberately. Fragmentation means no single operator has achieved the coordination efficiency that autonomous design makes possible, and switching costs remain low enough for a leaner entrant to capture share quickly. → Fragmented Competition
How large does a target market need to be to justify reconstruction?
We set a minimum addressable revenue threshold before beginning any reconstruction assessment — the market must be large enough that a 10–15% share generates meaningful operating revenue without requiring scale that outpaces our build capacity. Size alone is not sufficient; the combination of size, fragmentation, and labour concentration determines whether the opportunity is worth the Rebuild Tax. → Rebuild Tax
Can a market be too large for autonomous reconstruction to be viable?
A market can be too large if the coordination surface required to serve it scales faster than the autonomous systems we can deploy. We evaluate the ratio of coordination events to revenue-generating events — if coordination dominates, the market may require a staged entry targeting a defensible vertical segment before expanding. Market size is an opportunity; coordination density is the constraint. → Coordination Surface
What transaction characteristics make a market most suitable for agentic operations?
High transaction frequency, low per-transaction complexity, and bounded outcome variability are the three structural signals we prioritise. Markets where most transactions follow predictable patterns — even if the individual transactions appear bespoke — are precisely the markets where an Agentic Core can replace human coordination without degrading service quality. → Agentic Core
How do we assess whether a market's pricing reflects its true labour cost?
We model the market's current pricing against its delivered labour cost — if the margin between them is thin, the market is either already efficient or the incumbents are absorbing labour cost through pricing power that a leaner operator can undercut. Thick margins with high labour intensity indicate a market that has not yet faced a credible autonomous competitor. → Memo #03 — Overhead Is a Design Choice
What does customer concentration tell us about a market's reconstruction potential?
High customer concentration — where a small number of clients represent the majority of a market's revenue — signals that relationship dependency has substituted for operational excellence. We target markets where customer acquisition is process-driven rather than relationship-driven, because autonomous systems can replicate process at scale but cannot replicate relationship history. → Administrative Density
How do we distinguish a market that is broken from one that is simply mature?
A mature market has reached structural efficiency — margins are thin, operations are optimised, and incumbents have already extracted most of the available coordination gain. A broken market has high margins, labour-heavy operations, and incumbents that have grown overhead linearly with revenue. The distinction is visible in the ratio of headcount to revenue across the leading operators. → Memo #06 — Legacy Liability
What market structure signals cause us to walk away immediately?
We walk away when the market's value delivery depends on non-replicable human judgment at every transaction — legal counsel, medical diagnosis, and bespoke creative work are examples. We also exit the evaluation when regulatory requirements make autonomous operation legally non-viable in the target jurisdiction within a five-year planning horizon. Ambition without a viable path to autonomous operation is not a market; it is a project. → Autonomous Business
Labour Concentration and Arbitrage
10 questionsWhat is Workforce Arbitrage and how do we measure it?
Workforce Arbitrage is the structural cost differential between delivering a service with human labour in a high-cost geography and delivering the same service with agentic systems operating without geographic constraint. We measure it as the ratio of the incumbent's fully-loaded labour cost per transaction to our projected compute cost per equivalent transaction — the wider the ratio, the stronger the arbitrage case. → Workforce Arbitrage
How do we identify markets running on unnecessary human labour?
We map the full transaction lifecycle and tag every human touchpoint against the T1/T2/T3 task tier classification. T1 tasks — rules-based, low judgment, high frequency — are the primary arbitrage surface. When T1 tasks represent more than 60% of a market's labour spend, we treat the market as structurally underpriced. → Task Tier Classification
What is the minimum human-to-logic ratio that justifies entry?
We do not use a universal minimum ratio — the relevant threshold depends on the market's transaction volume and margin structure. The Human-to-Logic Ratio becomes actionable when replacing a single full-time equivalent with autonomous systems produces enough operating surplus to fund the next layer of reconstruction. In practice, markets with a ratio above 10:1 in favour of human labour are our primary targets. → Human-to-Logic Ratio
How do we assess whether labour arbitrage is durable or temporary?
We assess durability by modelling the incumbent's response capacity. If the incumbent can replicate our cost structure within 18 months by deploying the same tools, the arbitrage is not structural — it is a timing advantage. Durable arbitrage exists when the incumbent's legacy technology stack, existing headcount commitments, and customer contracts make rapid reconstruction operationally impossible. → Legacy Liability
What role does geography play in evaluating labour arbitrage?
Geography matters at the cost input level, not the output level. Markets where the incumbent's service delivery is geographically anchored — requiring staff on-site, in-market, or within regulatory jurisdictions — carry higher structural labour costs than markets where delivery is location-agnostic. Autonomous systems eliminate the geographic constraint entirely, which is why we specifically target markets where geography has historically justified premium labour cost. → Operational Arbitrage
How do we model compute cost against current labour cost for a target market?
We start with the incumbent's published headcount-to-revenue ratio and apply industry-standard fully-loaded cost per employee for the relevant geography. We then model the equivalent transaction volume using current agentic tooling at current API pricing, with a 30% efficiency reserve for orchestration overhead. The gap between these two figures is the gross arbitrage — the net figure accounts for Rebuild Tax and time-to-operation. → Labor-to-Compute Substitution
What happens to the arbitrage case if AI compute costs continue falling?
Falling compute costs compress the arbitrage case only if the incumbent responds by reducing their own labour dependency at the same rate — which structural and contractual inertia makes unlikely at scale. In practice, falling compute costs widen our margin rather than eroding our advantage, because our cost base adjusts automatically while the incumbent's labour cost remains fixed. → Memo #01 — Automated vs Autonomous
How do we evaluate markets where labour arbitrage already exists at an offshore level?
Markets that have already offshored their labour delivery have partially arbitraged the geographic premium, but they have not eliminated coordination overhead — they have relocated it. Offshore delivery models still require management layers, quality control processes, and communication infrastructure that autonomous systems remove entirely. The arbitrage in these markets is at the coordination layer, not the wage layer. → Coordination Tax
What labour dependency patterns signal that a market cannot be fully reconstructed?
Markets where the highest-value transactions require licensed practitioners — lawyers, doctors, accountants in regulated filings — cannot be fully reconstructed because the licensing requirement creates an irreducible human dependency. We do not avoid these markets entirely; we target the surrounding coordination and administrative work, which is often 60–80% of total labour spend in these industries. → Judgment Layer
How does Administrative Density affect our assessment of a market's arbitrage potential?
Administrative Density — the proportion of total operating effort consumed by coordination, reporting, and compliance tasks rather than direct value delivery — is one of our most reliable entry signals. High Administrative Density means the incumbent is paying human labour rates to perform work that autonomous systems execute at compute cost. It is overhead with a price tag, and it is the first layer we target in reconstruction. → Administrative Density
Legacy Technology Liability
8 questionsWhat is Legacy Liability and why does it matter in market evaluation?
Legacy Liability is the accumulated cost of technical debt, contractual lock-in, and organisational inertia that prevents an incumbent from restructuring its operations even when it recognises the need to do so. It matters because it is our primary structural protection — an incumbent that cannot reconstruct itself in response to our entry is not a threat; it is a customer pipeline. → Legacy Liability
How do we estimate the incumbent's Rebuild Tax?
We estimate the Rebuild Tax by modelling three components: the cost of retiring existing technology (licensing exit fees, migration costs, data transfer), the cost of retraining or replacing the workforce for an autonomous operation model, and the revenue at risk during the transition period. A high Rebuild Tax is a strong entry signal — it means the incumbent faces a worse version of the problem we are solving from scratch. → Rebuild Tax
What signals indicate an incumbent is already attempting autonomous transformation?
Public announcements of "digital transformation" programmes, new executive hires with AI or automation titles, and acquisition activity targeting workflow automation companies all signal that the incumbent has identified the problem but is attempting to solve it through the existing organisational structure — which rarely succeeds. An incumbent in transformation mode is slower, more distracted, and more willing to lose margin than one that has not yet recognised the threat. → Memo #09 — The Mechanics of Failure
What contractual structures create legacy liability for incumbents?
Multi-year software licensing agreements, enterprise SaaS contracts with high switching costs, and employment contracts with notice periods longer than three months all create legacy liability. Each of these represents a financial commitment that the incumbent cannot exit quickly, which means their cost structure remains fixed even as their competitive position deteriorates. → Rebuild Tax
How does the age of the incumbent's founding affect legacy liability assessment?
Incumbents founded before 2010 were designed around a pre-cloud, pre-API, pre-LLM architecture. Their systems, processes, and organisational structures reflect the constraints of that era. We treat age as a proxy signal — not a determinative one — for the depth of legacy liability. A 30-year-old company has 30 years of accumulated workarounds, custom integrations, and institutional inertia to overcome before it can operate autonomously. → Legacy Liability
What does a high headcount-to-revenue ratio signal about legacy technology?
A high headcount-to-revenue ratio is the most visible symptom of a market that has compensated for technological inadequacy with human labour. When the incumbent requires one full-time employee per $200,000 of annual revenue, the gap between their cost structure and an autonomous equivalent is measured in orders of magnitude, not percentages. We treat this ratio as a first-pass market filter. → Headcount Decoupling
How do we assess legacy liability when incumbents are privately held and opaque?
Privately held incumbents leak legacy signals through indirect channels: job board hiring patterns, pricing structure rigidity, customer complaint themes on review platforms, and the age profile of their documented integrations. Where permissible, we gather insights from former employees to gain a comprehensive understanding of the organization's historic operational environment, ensuring all discussions respect ongoing confidentiality obligations. → Memo #05 — Markets That Work
At what point does legacy liability become a disqualifier rather than an entry signal?
Legacy liability becomes a disqualifier when it is concentrated in regulatory or legal infrastructure rather than technology or process. If the incumbent's position is protected by licensing agreements with regulators, governmental contracts, or statutory monopoly arrangements, no amount of operational efficiency on our part can displace them within a commercial time horizon. We want markets where legacy is a burden, not a moat. → Memo #06 — Legacy Liability
Regulatory and Compliance Surface
6 questionsHow do we assess the regulatory surface of a target market?
We map the full regulatory surface across three dimensions: licensing requirements for operators, data handling obligations, and jurisdictional variation in service delivery rules. A market with complex but predictable regulation is preferable to one with light but volatile regulation — predictable rules can be systematised; volatile rules create intervention thresholds that autonomous systems cannot manage without constant recalibration. → Intervention Thresholds
Can regulatory complexity be an entry advantage rather than a barrier?
Yes, and we treat it as one of our most reliable signals. High regulatory complexity raises the barrier to entry for undercapitalised competitors and creates a compliance overhead that legacy operators have absorbed into their cost structure as permanent expense. An autonomous business that systematises compliance — encoding it into the Agentic Core rather than staffing it — converts the regulatory burden into a structural cost advantage. → Agentic Core
What regulatory signals indicate a market is about to open for autonomous entrants?
Regulatory sandboxes, consultation periods on automation frameworks, and public sector procurement guidelines that explicitly reference algorithmic decision-making are early signals that a regulatory environment is preparing to accommodate autonomous operators. We monitor these signals as leading indicators — they typically precede viable market entry by 18 to 36 months. → Market Determinism
How do data protection requirements affect our autonomous business model?
Data protection requirements — GDPR, CCPA, and equivalent frameworks — impose constraints on data retention, processing purpose, and cross-border transfer that we encode directly into the data architecture of our autonomous systems before launch. These constraints are not afterthoughts; they are design inputs. A business that processes personal data through human workflows and attempts to automate afterward faces retrofit costs that a purpose-built autonomous system avoids entirely. → Auditable Autonomy
What is the MTTI and why does it matter for regulatory compliance?
MTTI — Mean Time to Intervention — is the average elapsed time between an autonomous system identifying an anomaly and a human operator reviewing and acting on it. Regulatory frameworks increasingly specify maximum acceptable MTTI thresholds for different risk categories. We design our intervention architecture around the most demanding MTTI requirement in our operating jurisdictions, not the average. → MTTI
How do we handle markets where regulation is actively hostile to automation?
We do not enter markets where regulation is actively hostile to autonomous operation and the regulatory trajectory shows no sign of liberalisation. The Rebuild Tax of designing a product to current hostile regulation and then redesigning it when regulation shifts is a compounding cost that undermines the economics of reconstruction. We wait for the regulatory environment to move toward us rather than building against it. → Rebuild Tax
Competitive Density
2 questionsHow do we assess whether a competitor has genuine autonomous capability?
We look past marketing language to operational signals: headcount-to-revenue ratio, average ticket resolution time, documented API integrations, and public engineering output. A competitor claiming autonomous operation with a headcount-to-revenue ratio indistinguishable from a traditional services firm has automated some tasks, not reconstructed its operating model. The distinction between an automated business and an autonomous one is architectural, not cosmetic. → Automated Business
What does low pricing power among incumbents signal about market defensibility?
Low pricing power signals that the market has not yet produced a defensible operator — one whose cost structure, quality consistency, or speed of delivery commands a premium. This is an entry signal, not a warning: a market where no one has achieved defensibility is a market where autonomous reconstruction can establish the first genuinely defensible position. → Operational Selection
Capital Requirements
8 questionsWhat is the relationship between Rebuild Tax and capital efficiency in market selection?
A market with high Rebuild Tax for incumbents but low build cost for an autonomous entrant is our highest-priority target class. The asymmetry between what it costs us to enter and what it would cost the incumbent to respond is the core capital efficiency argument. We select markets where this asymmetry is structural — built into the technology and organisational constraints of the incumbent — rather than merely situational. → Rebuild Tax
What capital structures are incompatible with the autonomous business model?
Capital structures that require us to distribute equity to operators, advisors, or investors in exchange for market access are incompatible with our Stewardship Model. We maintain majority equity in every business we build — the compounding value of the portfolio depends on ownership concentration, not on co-investment at the individual company level. Capital that comes with governance strings is evaluated against what those strings cost in operational autonomy. → Stewardship Mode
What is the minimum revenue threshold at which an autonomous business becomes self-sustaining?
Self-sustainability thresholds vary by market and cost structure, but we model every new business against the point at which operating revenue covers fully-loaded operating costs — including the Coordination Tax of studio support — with a 20% buffer. Below this threshold, the business requires continued studio investment to operate; above it, the Arco Flywheel begins — the business funds its own growth and contributes to the next reconstruction cycle. → Arco Flywheel
How do we evaluate markets where customer acquisition cost is prohibitively high?
High customer acquisition cost is a disqualifier only if it is structural — driven by the nature of the buying decision, long sales cycles, or category education requirements — rather than situational. We model acquisition cost against lifetime customer value and the operational leverage available once a customer is onboarded. Markets where autonomous service delivery dramatically extends customer lifetime value can absorb high acquisition cost at the top of the funnel. → Headcount Decoupling
What technology infrastructure costs should we model before committing to market entry?
We model three infrastructure cost categories: foundation costs (cloud infrastructure, base LLM API access, data storage), orchestration costs (workflow management, monitoring, intervention tooling), and integration costs (connecting to market-specific data sources, compliance systems, and customer-facing channels). Foundation costs are largely predictable; integration costs are the most frequently underestimated category and require direct technical assessment of the target market's data ecosystem. → Agentic Core
How do we model the impact of AI infrastructure cost changes on long-term economics?
We model two scenarios: one where compute costs remain at current levels and one where they continue declining at the historical rate observed over the past three years. Both scenarios must produce acceptable unit economics — if the business is viable only under one of them, the model is fragile. The downward trajectory of compute costs provides structural tailwind; it is not a dependency we build the base case around. → Labor-to-Compute Substitution
What financial signals in a target market indicate the timing is right for entry?
Rising incumbent pricing without corresponding quality improvement, increasing industry headcount growth in operational roles, and declining venture funding for traditional service delivery models in the sector all indicate that the market is approaching a structural inflection point. We treat these signals as timing indicators — they do not create the opportunity, but they indicate that the window for establishing a defensible position is open. → Breakable Market
How do we evaluate the risk that capital-intensive entry requirements delay our time to revenue?
We sequence the build to generate revenue as early as operationally possible — not to validate the model (we have already validated it through market analysis), but to compress the period of capital consumption before self-sustaining operation begins. The build sequence is designed around the minimum viable autonomous operation threshold, not around the full-featured product vision. Scope is managed against the time-to-revenue objective, not against a feature roadmap. → Memo #04 — Why We Don't Build MVPs
