The Rival Country-Entry Read: Committed, Probing, or Signal Only

A rival has shown one sign of moving into your country: a country-manager posting, a localized page, or a new currency on the pricing page. Now leadership wants to know by Friday whether it is a real entry. This guide is the scoring model for that call. It gives strategy, competitive-intelligence, and talent-intelligence analysts six evidence families to score from public sources, a rule for turning those scores into Committed, Probing, or Signal Only, and a method for dating when the rival will start winning local deals.

It covers one rival and one country at a time. It is not a role-by-role guide to job postings, and if the trigger is an engineering hub rather than a sales move, use the Rival Capability-Center Read instead.

What do Committed, Probing, and Signal Only mean?

Committed means the rival can sell, bill, and serve customers in the country and has a legal footing to stay. Probing means it has spent real money but at least one essential piece is still missing. Signal Only means the trigger has nothing behind it yet.

The verdict has three levels, not two, because the pages that rank for "competitor international expansion signals" treat the trigger as the answer. One calls a Country Manager hire "one of the most unambiguous signals in business". Another says "a single Country Manager posting is a strong signal". Neither page weighs the trigger against other evidence, says what to do when signals conflict, or says when the rival will actually start competing.

A job title costs almost nothing. A country title can cover a whole region, belong to a remote seller, or be a company's entire presence in that country for years. So the verdict has to rest on evidence that costs more to produce than a job ad.

The six evidence families and what each one proves

Each family tells you something different about how committed the rival is, and each scores 0, 1, or 2. A 2 means a dated public source corroborates it. A 1 means the evidence exists but is ambiguous. A 0 means you checked and found nothing.

The trigger itself rarely scores above 1. A country-manager posting counts as a 1 for local leadership until you know where the person sits and which countries the role covers. A localized page counts as a 1 for commercial plumbing until the checkout actually bills in local currency. Treat the trigger as the reason to run the read, not as its result.

How do you check legal presence in a foreign company registry?

Search the national registry for a branch or foreign-company record, note the entity number and filing date, and compare them with the date the rival claims to have opened. Some countries set fixed filing windows, so in those countries the registry also tells you about timing.

UK. An overseas company that opens a UK establishment files OS IN01 within one month of opening, and the fee is £124. Once registered, the branch's details become public on the Companies House register. The trigger is physical presence. A company whose only UK presence is one individual working on its behalf does not have to register.

India. Under Section 380 of the Companies Act, 2013, a foreign company that establishes a place of business in India must file Form FC-1 with the Registrar within 30 days. After that, FC-3 is due within 6 months and FC-4 within 60 days of the year-end. Sources disagree on when the 30 days start. Some date it from when the place of business is established, others from RBI approval. Record both dates if you can find them.

Australia. A foreign company must not carry on business in Australia unless it is registered with ASIC or has applied to register (s601CD), and lodgment is due within one month of commencing. The ARBN, the Australian Registered Body Number, must appear on the branch's public documents. That gives you a second check: look for an ARBN in the footer of the rival's Australian site or on its local terms.

Using the registry as a timing check

UK and Indian filings are due roughly 30 days after opening. So in those two countries, a dated "no record" more than about six weeks after a claimed office opening means something. The extra two weeks are a buffer, not a measured figure. How long it takes for a filing to appear in search is not established for any country. To learn it for the registries you use, note the filing date on each record you find alongside the date it first appeared in your searches.

For Germany, France, the Netherlands, and Japan, this guide does not establish the trigger, the window, or the identifier. Score legal presence there only from records you actually find, and never score a 0 just because a window has passed.

Scoring legal presence:

• 2: a registry record with an operating address, plus filings that show staff or an office.
• 1: a record that looks like a shell, such as a registered-agent address with no sign of staff, or a claimed opening still inside the filing window.
• 0: a dated "no record" after the window has passed in a country that has one, where the trigger implies a physical office.

In regulated markets, legal presence also needs the relevant licence, or a public application for one, before it can score a 2.

How do you read local leadership and hiring depth?

Confirm where the country leader is based, which countries the title covers, and whether the role is remote or on-site. Then count dated in-country postings by function. A named leader scores local leadership but tells you almost nothing about depth.

The weakest reading of any trigger is taking a title at face value. Refolk's index holds 608 profiles titled "Country Manager" in Germany, across all industries. In a 25-profile sample, only 15 held that exact title.

Source: Refolk's index, n=25 of 608. Shares are derived from the sample.

Three findings from this sample change how you score leadership:

• Regional titles are common. "Head of Business Development UK & Germany" is one person covering two markets, not a country commitment. A regional scope scores 1 at most.
• City matters. The leaders are spread across Berlin, Hamburg, and Frankfurt. Record the city, because it tells you which local buyers the rival is close to, and check it against the registered address from the registry step.
• One person is often the whole team. The top 10 employers in the sample each have exactly one country manager. Examples include Yazen Health, Xopero Software, Hansen Technologies, adMarketplace, Logitech, and DEKRA. A single titled hire is a common long-term setup, not an early stage that predicts more hiring.

The structured industry tag cannot carry this search. The same title filtered to the Computer Software industry returned 0 for Germany and 0 for France in Refolk's index, so an industry-filtered title search will miss nearly everyone. A plain-English description of the people works better, including the regional variants. That is the friction Refolk removes: you ask for the people you want across LinkedIn, GitHub, and the open web, and you get them back without guessing which field the data provider filled in.

Scoring local leadership

• 2: the leader is located in the country, the title covers that one country, and the role is on-site or tied to a local office.
• 1: the title is regional, or the person works remotely from another country, or the role is posted but not yet filled.
• 0: nobody holds a role that owns this country.

Scoring hiring depth

One vendor blog says that, according to LinkedIn Talent Solutions data, Country Manager hires are typically followed by 5 to 15 more local hires within 6 months. It links no primary study, so treat the claim as unverified and do not score against it. The usable threshold is observable: a cluster of postings in a new city within a 60-day window.

• 2: dated postings in the country cluster within 60 days and span at least two functions, for example sales and customer success.
• 1: one or two postings, or postings in a single function.
• 0: the leader is the only in-country role.

Hiring depth is also where Refolk earns its place a second time. Postings show intent. Profiles show people who have actually started. Counting people who now list the rival and the country tells you whether the postings were filled.

How do you read commercial plumbing, data residency, and customer proof?

Commercial plumbing shows whether the rival can bill locally, data residency shows whether it can pass local procurement, and customer proof shows whether it is already winning. Date all three with archived captures, because "it's on the site now" says nothing about when it started.

Commercial plumbing: dating the pricing page

Use the Wayback CDX API, a query interface that lists every archived capture of a URL. It returns seven default fields: urlkey, timestamp, original, mimetype, statuscode, digest, and length. The parameters that matter here:

• collapse=digest drops consecutive identical captures, so each row left is a change.
• from= and to= limit the date range.
• filter= restricts the results, for example to one status code.
• matchType= widens the scope, up to a scan of the whole domain, which is how you spot a new country subdirectory.

Run it on the pricing, terms, and privacy pages, and on the domain to catch new country paths. The output you need is three first-seen dates: local currency, local terms, and the country subdirectory. If you prefer Python, the EDGI wayback client wraps the same API.

A first-seen date from the archive is an upper bound, meaning the change happened on or before that date. How often pages get captured varies, and no published gap statistics exist. Then check the live checkout. A currency shown on the pricing page is a 1. A checkout that bills in local currency, under terms naming a local contracting entity, is a 2.

Data residency: the sub-processor list as a leading indicator

A sub-processor list is a vendor's public list of third parties that process customer data. When a rival adds an in-country hosting provider, that list usually changes before any data is processed there. The GDPR requires notice in time for the customer to object but sets no number of days. In practice, vendors usually give about 30 days.

Windows of 15, 30, 60, and 90 days all appear in negotiated data processing agreements. So read the rival's own published term, not a default. If the rival gives notice by publishing its list, a new in-country entry dates in-country hosting to roughly the list change plus the notice term. How often these lists change ahead of a public announcement is not established, so treat the change as early warning, not confirmation.

• 2: an in-country region appears in the rival's cloud-region documentation, or the new sub-processor's notice period has run out.
• 1: an in-country sub-processor has been added and is still inside its notice window, or a region has been announced but is not yet listed as available.
• 0: neither.

Customer proof: named, dated, local

Customer proof is the only family that shows the rival winning rather than preparing. For public-sector buyers in Europe, search TED. Only Contract Award Notices name winners. They record the winning companies' name, country, city, and size class, along with the awarded value and the contract conclusion date. eForms have been mandatory since 25 October 2023, which makes newer notices easier to compare. TED misses most smaller contracts, which appear only on national procurement portals, so search those too. For private buyers, search local-language case studies and press.

• 2: a named in-country customer with a date.
• 1: an unnamed or undated claim, such as a logo with no case study.
• 0: none found after searching TED, the national portals, and local-language sources.

The step-by-step read

The full read takes about ten working hours, which fits a Monday-to-Friday deadline with time left to write it up. Run the steps in order. The early steps tell you which later sources matter, and each step has a defined output.

How do you score the verdict and date the response?

Add the six family scores for a total out of 12, then apply two gates before choosing a verdict. The gates stop a high score built on cheap evidence from reading as Committed.

Verdict rules:

1. Committed: total of 8 or more, legal presence scores 2, and either commercial plumbing or customer proof scores 2.
2. Probing: total of 4 to 7, or a total of 8 or more that fails either gate.
3. Signal Only: total of 3 or less, or only the trigger's own family scores above 0.
4. Licence cap: in a regulated market, a rival with no licence and no public licence application is capped at Probing, whatever its total.

When signals conflict:

• The deeper layer in the stack wins. A named local customer outweighs the lack of a local job posting.
• Dated evidence beats undated evidence. A first-seen currency date beats a press claim with no date.
• A missing signal counts against the rival only when a rule says it should exist. No UK record from a remote seller is neutral. No record six weeks after a claimed office opening is not.

Structural commitment combines legal presence, local leadership, hiring depth, and data residency. Commercial readiness combines commercial plumbing and customer proof.

Dating when the rival starts winning local deals

No public figure exists for the typical lag between an entry signal and a first named local win, so do not quote one. Build a window from your own dated evidence:

• Customer proof scores 2: the rival is already winning. Give the date of its earliest named award or case study.
• Plumbing is live but there is no proof yet: the earliest date is the first-seen date of local checkout or local terms. The rival can close deals from that day.
• Residency is pending: for buyers who require in-country hosting, the earliest date is the sub-processor list change plus the rival's own notice term.
• Only a leadership posting exists: the ranking sources disagree. One places the Country Manager posting 6 to 12 months before market entry. Another says postings appear 6 to 12 weeks before any official announcement. Use 12 months from the posting date as the outer limit, and shorten the window as plumbing dates appear.

Rival:
Country:
Trigger: <what was seen> | first seen <date> | archived <link>
Read date:

Family              Score (0/1/2)   Evidence                        Source + capture date
Legal presence
Local leadership
Hiring depth
Commercial plumbing
Data residency
Customer proof

Total: __ / 12
Gate 1: Legal presence = 2?                      Y / N
Gate 2: Plumbing = 2 or Customer proof = 2?      Y / N
Licence cap (regulated market, no licence)?      Y / N / n.a.

Verdict: Committed / Probing / Signal Only
First-local-win window: earliest <date> because <dated evidence>; latest <date> because <dated evidence>
Response: <owner, action, date>
Re-score on: <date>

How does this read go wrong?

Most wrong verdicts come from taking a cheap signal at face value or from treating a gap in the record as proof of absence. Each family has a typical false positive, a typical false negative, and a check that catches it.

Legal presence, both directions. An entity opened for tax or hiring looks like an office. A remote-only seller in the UK leaves no record at all. Read the registered address and the filings before you score, and remember that UK registration depends on physical presence.

Leadership inflation. Forty percent of the Germany sample in Refolk's index held titles other than "Country Manager", some of them regional, such as "UK & Germany". A ranking page that calls a single posting "unambiguous" is scoring the title, not the role.

Benchmark substitution. The 5 to 15 follow-on hires figure gets repeated as if it were measured. It has no primary source. If you find yourself predicting hires from it, stop and count.

Archive false negatives. A CDX response of HTTP 200 with an empty body means the URL was never archived. It does not mean the page did not exist. Never write "the pricing page had no euro option before" based on an empty archive.

Hidden residency notice. Some rivals give sub-processor notice only through a trust portal that requires a login, so a public diff shows nothing. Check the cloud-region documentation before scoring a 0.

Durability blindness. This failure costs the most, because it hits the verdicts that look strongest. N26 launched in the UK in October 2018, with about 80 people across the UK and Germany working on that market, and reached about 200,000 UK customers. It never applied for a UK banking licence. It announced its UK exit on 11 February 2020 and closed accounts on 15 April 2020. In November 2021 it also announced it would leave the United States in January 2022. Every effort signal was present. The one missing piece was the regulatory basis for staying, which is why the licence cap exists.

Effort is not commitment: N26 had staff, customers, and a launch, and still left about 18 months later.

The evidence for pure software companies is thinner. I found no documented SaaS withdrawal with registry evidence behind it. So outside regulated markets, the licence cap does not apply, and the closest equivalent check is whether a local contracting entity and in-country hosting both exist.

How do you keep the read current?

Re-score on a fixed date set by the verdict, and re-score immediately when a deeper-layer signal appears. A verdict is a dated snapshot, and rival entries move one layer at a time.

• Committed: re-score each quarter, mainly to track customer proof and hiring depth, which show how fast the rival is scaling.
• Probing: re-score in 30 days. That matches the UK and Indian filing windows and the most common sub-processor notice term, so the missing piece often shows up within one cycle.
• Signal Only: re-score at 60 days, the window for a hiring cluster.
• Any verdict: re-score at once if a registry record, local checkout currency, in-country sub-processor, or named local customer appears.

Keep the CDX queries saved with their from= dates, so each re-score only looks at new captures. Keep the people search saved as well. Re-running the same plain-English query in Refolk shows who has joined in-country since the last read, which is the cheapest way to see whether postings turned into hires.