Acquiry Labs · Supplier intelligence

Who actually supplies this brand?

Reading supplier evidence before it reaches an acquisition shortlist. A buyer can recognise the same checkout on ten shops and still have the wrong software supplier on its shortlist. Counting only independently supported shops changes which founder the buyer calls first in one case, and leaves the shortlist membership unchanged in another.

10shops initially counted
3links still supported
7links left open

Joash Boyton, Research lead · Acquiry Labs · Research edition 1.1. Prepared 13 November 2026. Release date is set when this edition is published. Companion data: Embedded payments provider map, dataset edition 1.1. Teaching fixture 1.1.

Squarespace and Stripe are the real-world opening example. The ten provider-map rows reviewed in section 8 are public sourcing records. Both ranking scenarios use fictional shops and suppliers (Arc, Birch, Cove and Dune).

The question for the founder

When one piece of evidence turns out to be shared, every count built on it has to be rechecked and the whole shortlist reordered. Ask:

Which operators, contracting entities and dates support the customer count you have given us, and which of those customers did you sign directly?

The real record: read one role at a time

Public evidence · checked 13 November 2026

The real record, one role at a timeSquarespace is the merchant-facing brand. Stripe describes the payments infrastructure underneath. The evidence is Stripe's own customer story. The real record, one role at a time BRAND Squarespace Branded payments launched 2023 SUPPLIER Stripe Connect and Payments as infrastructure EVIDENCE Stripe customer story Party disclosure, checked 13 Nov 2026
The real record, one role at a time. Squarespace is the merchant-facing brand. Stripe describes the payments infrastructure underneath. The evidence is Stripe's own customer story.
Data behind this figure
Brand: Squarespace, branded payments launched 2023.
Supplier: Stripe, Connect and Payments as payments infrastructure.
Evidence: Stripe customer story, a party disclosure, checked 13 November 2026.
Not established: contracting entity, exclusivity, payment volume, merchant count.
The Squarespace and Stripe record
RoleWhat the evidence saysSource
BrandSquarespace introduced its branded payments offering in 2023.Stripe customer story
SupplierStripe says its Connect and Payments products provide payments infrastructure for Squarespace merchants.Stripe customer story
EvidenceThe disclosure comes from Stripe, a party to the relationship. A copy of that account has the same origin and adds no independent support.Origin: Stripe

Passages relied on: “Stripe Connect and Stripe Payments providing the payments infrastructure.” and “In 2023, Squarespace launched a white-labeled payments platform.” Read Stripe’s customer story · Inspect the dataset row

The customer story publishes growth figures but no merchant count. This note derives none.

What belongs in a buyer memo

“Stripe identifies a payments infrastructure relationship with Squarespace (Stripe customer story, checked 13 November 2026).”

What still needs commercial diligence

The merchant’s contracting entity, any exclusivity, payment volume, customer-level revenue and the commerce software behind any particular shop. Each needs commercial diligence; a visible checkout settles none of them.

Scenario A: one correction changes the third call

Worked example · fictional

An analyst first credits Arc with all ten shops showing a shared checkout. A correction establishes that the checkout identifies a payments provider. S01 to S03 have separate records supporting Arc; S04 to S10 become unresolved.

Scenario A counts and ranks (fictional)
SupplierInitial countSupported afterRank before → after
Arc1031 → 4
Birch882 → 1
Cove663 → 2
Dune444 → 3
Scenario A: one correction changes the third callBefore the correction the top three are Arc, Birch, Cove. After it they are Birch, Cove, Dune. Arc falls from 10 counted shops to 3 supported shops. Scenario A: one correction changes the third call Before: analyst count After: supported shops Arc 10 (#1) (#4) 3 Arc Birch 8 (#2) (#1) 8 Birch Cove 6 (#3) (#2) 6 Cove Dune 4 (#4) (#3) 4 Dune Scenario A: one correction changes the third call Solid line: in the top three after the correction. Fictional suppliers. Rank by count, then name A–Z.
Scenario A: one correction changes the third call. Before the correction the top three are Arc, Birch, Cove. After it they are Birch, Cove, Dune. Arc falls from 10 counted shops to 3 supported shops.
Data behind this figure
Arc: 10 (rank 1) -> 3 (rank 4)
Birch: 8 (rank 2) -> 8 (rank 1)
Cove: 6 (rank 3) -> 6 (rank 2)
Dune: 4 (rank 4) -> 4 (rank 3)

The top three move from Arc, Birch, Cove to Birch, Cove, Dune. Dune enters without a single new shop.

Scenario B: the same three suppliers remain, in a different order

Alternative fictional scenario · tested separately

Dune has two supported shops instead of four. Everything else is identical.

Scenario B counts and ranks (fictional)
SupplierInitial countSupported afterRank before → after
Arc1031 → 3
Birch882 → 1
Cove663 → 2
Dune224 → 4
Scenario B: the same three suppliers remain, in a different orderBefore the correction the top three are Arc, Birch, Cove. After it they are Birch, Cove, Arc. Arc falls from 10 counted shops to 3 supported shops. Arc falls from first to third on three supported shops. The same three suppliers remain on the shortlist, in a different order. Scenario B: the same three suppliers remain, in a different order Before: analyst count After: supported shops Arc 10 (#1) (#3) 3 Arc Birch 8 (#2) (#1) 8 Birch Cove 6 (#3) (#2) 6 Cove Dune 2 (#4) (#4) 2 Dune Scenario B: the same three suppliers remain, in a different order Solid line: in the top three after the correction. Fictional suppliers. Rank by count, then name A–Z.
Scenario B: the same three suppliers remain, in a different order. Before the correction the top three are Arc, Birch, Cove. After it they are Birch, Cove, Arc. Arc falls from 10 counted shops to 3 supported shops. Arc falls from first to third on three supported shops. The same three suppliers remain on the shortlist, in a different order.
Data behind this figure
Arc: 10 (rank 1) -> 3 (rank 3)
Birch: 8 (rank 2) -> 8 (rank 1)
Cove: 6 (rank 3) -> 6 (rank 2)
Dune: 2 (rank 4) -> 2 (rank 4)

Arc falls from first to third on three supported shops. The same three suppliers remain on the shortlist, in a different order.

From evidence to decision

Evidence item, affected assertion and acquisition decision
Evidence itemAffected assertionAcquisition decision
Shared checkout on S01–S10 (identifies the payments provider)“Arc supplies the commerce software for S01–S10” (10 shops)Withdrawn as support. S04–S10 become unresolved; Arc’s supported count falls to 3.
Separate platform records for S01–S03“Arc supplies S01–S03” (3 shops)Survives. Arc stays a prospect on 3 supported shops.
Dune’s own supported records (4 in A, 2 in B)“Dune supplies 4 shops” / “Dune supplies 2 shops”Unchanged evidence, changed position: Dune enters the top three in A; stays fourth in B.
Stripe customer story (real)“Stripe provides payments infrastructure for Squarespace merchants”Supports a role statement in the memo. Does not support exclusivity, volume or a merchant count.

Field worksheet

Check one supplier yourself
AskRecord
Who made the disclosure?Publisher, date checked and the exact passage.
What exactly is supplied?The service, and each party in its stated role.
Is the evidence independent?Trace copies back to the first disclosure. Record any separate source.
What if it is withdrawn?Recheck every affected shop, keep surviving evidence, re-rank the whole list.
What still needs diligence?Contracting entity, exclusivity, payment volume, customer revenue.

Reproduce the result

Download the teaching kit and run python3 verify.py. It recomputes Scenario A and Scenario B and stops on any mismatch. Checksums are in SHA256SUMS.txt.

How the dataset rows were checked

Dataset edition 1.1 rows re-read on 13 November 2026
RecordSource and originResult
jobber-stripeJobber’s own terms (party disclosure).Supported as written.
lightspeed-adyenAdyen case study (party disclosure).Supported as written.
lightspeed-tyroLightspeed support article (party disclosure).Supported; limited to already-enabled accounts.
cloudbeds-windcaveCloudbeds gateway list (one source, two rows).Supported as a compatibility listing only.
cloudbeds-authorizenetSame Cloudbeds page as the row above.Supported as a compatibility listing only. Common origin with cloudbeds-windcave.
mindbody-stripeStripe case study (party disclosure).Supported as written.
squarespace-stripeStripe case study (party disclosure).Supported as revised in edition 1.1.
roller-adyenAdyen partner page (party disclosure).Supported as written.
fresha-adyenAdyen press release (party disclosure).Supported for payments; the capital product is a separate claim.
toast-adyenAdyen press release, 10 Aug 2026.Supports an announcement; merchant rollout is dated evidence still to come.

Limits

Cite, credit and corrections

Acquiry Labs. Who actually supplies this brand? Research lead Joash Boyton. Research edition 1.1, prepared 13 November 2026. Companion dataset: Embedded payments provider map, edition 1.1. https://www.acquiry.com/labs/who-supplies-this-brand/

About the research lead

Joash Boyton is the founder and managing director of Acquiry, an M&A advisory firm for digital businesses. He leads Acquiry Labs research: he set the question this note answers, how a buyer should treat supplier evidence that later proves to be shared, and directed the tests behind it.

Correction history
DateItemChange
13 Nov 2026Field note 1.0 (four-page PDF)First retail field note. Scenario A only.
13 Nov 2026Earlier page version (Brightwell Commerce, Kestrel Pay)Briefly live with different fictional names and organisational credit. Withdrawn; kept here as history.
13 Nov 2026Live edition 1.0 (/labs/who-supplies-this-brand/)Arc, Birch, Cove and Dune; Scenario A; credits Joash Boyton, Research Lead. Seven downloads under /editions/1.0/.
13 Nov 2026Research edition 1.1 (prepared)Adds Scenario B, the evidence-to-decision grouping, the founder question, the review of all ten dataset rows, the tagged PDF, HTML, figures with text equivalents, briefs and teaching kit 1.1. Edition 1.0 stays unchanged.

Spot an error? Send the edition, the row or figure and the source through the corrections channel.