In technical scoping, the buyer's engineers and a solution architect map how the product connects to their systems. They name the data or rails it touches and what the pilot must test. The output is one written scope, agreed before any sandbox work starts.

Who needs to be in the room?

The buyer's engineers and your most technical person. Scoping is stage 2 of the enterprise B2B sales cycle, after discovery. For the buyer, invite the engineer who owns the system you connect to, the architect who approves new connections, and the champion. Add a security engineer if the product touches customer data.

For the seller, send a solutions engineer, or a founder who can answer integration questions on the spot. Keep the account executive to the start and the close. Engineers speak more freely to another engineer.

What does the scope document cover?

Eight areas, each with a buyer owner. Fill them in during the session. Leave none blank, and write "out of scope for the pilot" where it applies. First, how the product connects:

  • Integration points (integration engineer): each system, the direction of data, API or file, and who builds each side.
  • Identity and access (identity or platform engineer): sign-in, account creation and removal, and service authentication.
  • Data or rails (data owner): fields read and written, the source of truth, rails or data sources, and sample data.
  • Data location (security or privacy lead): where data is stored and processed, each subprocessor, and any cross-border transfer.
  • Environments (platform engineer): sandbox, test credentials, the path to production, and who grants access.

Then, how the pilot runs:

  • Volumes and limits (solution architect): peak and average volume, rate limits, and the pilot volume cap.
  • Failure handling (operations or on-call lead): retries, duplicates, rollback, who gets paged, and how the pilot stops.
  • Pilot pass criteria (champion): each discovery metric, its threshold, its data source and who signs the result.

The last area is the reason for the session. A written threshold lets the champion sign the result, and that signature opens the MOU or LOI.

Why does scoping get so much scrutiny from engineers?

Engineers carry the cost if the integration goes wrong. Capterra surveyed 3,385 software decision-makers in 11 countries (Capterra, October 2025). Integration issues, data migration problems and delays were the most common disruptions.

Of the buyers who regretted a purchase, 89% had first met an unexpected implementation disruption. Among successful adopters, 54% made a detailed implementation plan. The scope document is the first draft of that plan. Give every unknown an owner and a date, so the surprise comes up in a meeting.

Which technical standards will the buyer's engineers check?

Bring your position on identity and API security. These references are current on 8 November 2026.

  • Sign-in. OpenID Connect is an authentication protocol built on OAuth 2.0 (OpenID Foundation). Ask which identity provider the buyer uses, and if the pilot needs single sign-on.
  • OAuth security. RFC 9700 (January 2025) says clients should avoid the implicit grant (IETF). Public clients must use PKCE (Proof Key for Code Exchange). State which flows you use.
  • Account provisioning. SCIM is the HTTP standard for managing identities across domains (RFC 7644). Ask if the buyer wants it, and say if you support it now.
  • API protection. NIST SP 800-228 sets controls across the API lifecycle. Cite the version with updates as of 13 March 2026 (NIST).

Declare any gap. Write it in the scope with a date, and agree if it blocks the pilot or only production.

Why does data location belong in scoping?

The answer changes the contract, and it is cheaper to learn now. Under GDPR, a controller may use only processors that give sufficient guarantees (Article 28). The processing needs a contract, and a new subprocessor needs the controller's authorisation. Transfers of personal data outside the EU need set conditions (Article 44).

DORA has applied to EU financial buyers since 17 January 2025. Its Article 30(2) requires ICT contracts to state where services run and data is processed. Write each location into the scope for the stage 6 reviewer (EUR-Lex). Read how B2B startups get through vendor due diligence faster.

How small should the pilot scope be?

Scope the smallest unit that can prove the discovery metrics: one integration, one data flow or rail, one team. Test each item that a buyer's engineer adds:

  1. If the item does not change whether the pilot metric passes, move it to the production list.
  2. If the item needs a contract or data agreement first, plan the paperwork or use test data.

Give each item on the production list an owner, so engineers see the cut items recorded for later.

What ends technical scoping?

Both sides agree in writing what the pilot tests. That means four things:

  • The engineering owner and the solution architect approved the scope document.
  • Each pass criterion has a threshold, a data source and a named signer.
  • Sandbox access has an owner and a date.
  • The pilot has a start date and an end date in both calendars.

If the buyer cannot name a data source for a metric, go back to the discovery questions with the champion before you build.

To reach engineering teams with a dated reason to scope a new integration, get five named buyers, free.