What Offshoring Builds, Keeping Compliance In-House Means for Logistics Companies in Switzerland

Direct answer: Swiss logistics companies are increasingly comfortable sending the actual software build abroad but are drawing a hard line at compliance and data-residency decisions, which they keep controlled internally or with Swiss-based oversight. In practice this means a logistics firm can hire an outside development team for a tracking platform, a carrier portal, or a warehouse system, but the choices about where data lives, who can access it, and how it satisfies Swiss and EU rules stay owned by people inside the company. The build gets faster and cheaper; the accountability for compliance does not move an inch.

Swiss SME technology commentary from 2026 has been tracking a pattern that will feel familiar to anyone running a mid-sized logistics operation in Switzerland: SMEs are outsourcing more of their software development work outside the country while simultaneously tightening their grip on compliance and data-residency governance. This is not a contradiction — it is a division of labor that Swiss companies have been quietly formalizing as offshore and nearshore development have become normal rather than exotic. For logistics companies specifically, this split matters more than it does for, say, a consumer app business, because logistics software routinely touches customs data, cross-border shipment records, partner integrations with carriers in multiple jurisdictions, and increasingly, data-residency-sensitive information tied to Swiss data protection law (the revised Federal Act on Data Protection, FADP) and, for many operators, EU GDPR obligations on cross-border freight. The commentary doesn't hand us a precise percentage of Swiss logistics firms doing this — a specific figure isn't publicly available for this exact niche — but the general direction is clear enough to build a strategy around: build where it's efficient, govern where it's accountable.

Why This Split Is Happening Now

The instinct to outsource the build but not the governance isn't new in principle — plenty of regulated industries have separated "who writes the code" from "who owns the risk" for years. What's changed in 2026 is that Swiss SMEs, including logistics operators that historically kept everything close to home, now have enough experience with distributed development teams to trust the mechanics of the work while remaining understandably protective of two things: where their data physically and legally sits, and who gets to make the call on compliance posture.

The Practical Driver: Cost and Speed Pressure on Mid-Sized Firms

Swiss engineering talent is expensive relative to most of the markets logistics companies compete with internationally. A mid-sized freight forwarder or 3PL operator trying to modernize a dispatch system, build a customer-facing tracking portal, or integrate with a new customs data feed faces a real trade-off: hire locally at Swiss rates and move slowly, or work with an external development partner and move at a pace that matches the urgency of the business. As margins in logistics stay tight and digitization expectations from shippers and customers keep rising, more firms are choosing the second path for the build itself.

The Governance Driver: Why Compliance Doesn't Follow the Code

What doesn't get outsourced is the decision layer. A logistics company can tell an external team "build us a shipment-tracking API," but it cannot outsource the answer to "where does this data live, and who is legally accountable if it's mishandled." That answer has to come from inside the company, because FADP liability, customer contracts, and often insurance and customs bonding arrangements all point back to the Swiss legal entity, not to whichever development team wrote the code. This is the structural reason the split exists: legal accountability isn't transferable in the way a coding task is.

There's also a maturity dimension to this. A decade ago, offshoring software work from Switzerland often meant handing over a vague brief and hoping the result matched expectations, with limited visibility into how the vendor actually handled data along the way. That model made Swiss companies understandably nervous about anything touching customer or shipment data, which is part of why logistics in particular was slower than other sectors to embrace external development. What's shifted is the tooling and process maturity on both sides: version-controlled infrastructure, environment segregation between build and production, and clearer contractual norms around data handling have made it possible to separate "who writes the code" from "who controls the data" without pretending the risk has disappeared. The risk hasn't disappeared — it's been made explicit and assigned to a specific internal owner instead of being diffused across whoever happens to be involved in a project.

Why This Isn't Just a Cost Story

It would be easy to read this trend as purely about saving money, but that undersells what's actually happening. Swiss logistics companies that have been through a few offshore or nearshore engagements have generally learned that the build itself — the code, the interface, the integration logic — is a commodity skill available in many markets at many price points. What's scarce, and what stays valuable to keep close, is institutional knowledge of your own regulatory exposure, your own customer contracts, and your own risk tolerance. No external team, however skilled, can substitute for that. So the split isn't a cost-cutting shortcut that happens to also handle compliance; it's a recognition that these two kinds of expertise were never really the same skill in the first place, and treating them as one function was often inefficient in both directions — either overpaying local developers for commodity build work, or under-resourcing the compliance judgment that only makes sense to keep internal.

Why This Matters Specifically for Logistics Companies in Switzerland

Logistics is one of the more data-dense, cross-border-native industries there is, which makes this trend land harder here than in most sectors.

Freight and shipment records routinely include consignor and consignee personal data, customs declarations, payment and invoicing details, and sometimes sensitive commercial terms with carriers and partners across the EU, UK, and beyond. A Swiss logistics company operating a dispatch platform or a customer portal is, in effect, running a data pipeline that crosses several regulatory regimes at once. If the underlying software is built by an external team — which is increasingly likely given the cost pressure described above — the company still has to be able to answer, in detail, exactly where every category of data is stored, processed, and backed up, and to whom it is exposed during development, testing, and production.

This is where a lot of Swiss logistics companies get caught out. It's not that offshoring the build introduces new risk by itself — a competent Custom Software Development partner should be building to whatever data-residency and access-control requirements you specify. The risk shows up when a company doesn't specify those requirements clearly upfront, or worse, doesn't have the internal expertise to know what to specify. Outsourcing the build while keeping compliance in-house only works if "in-house" means an actual person or small team with the authority and technical literacy to define data-residency rules, review architecture decisions for compliance implications, and sign off before anything touches production data.

There's a second, less obvious reason this matters for logistics specifically: the industry runs on partner integrations, and each partner brings its own compliance posture into the mix. A Swiss freight forwarder working with carriers in Germany, France, and the UK is already juggling multiple regulatory contexts before a single line of new software gets written. Layering an offshore development relationship on top of that without a clear internal compliance owner means nobody has full visibility into the combined risk picture — the development team sees its slice of the project, each carrier integration is handled somewhat independently, and no one is looking at the whole system end to end. Logistics companies that get this right tend to have one person or team whose job includes exactly that end-to-end view, even when they don't write a single line of the code themselves.

It's also worth being honest about the reputational stakes. Logistics is a trust-based industry — shippers and customers hand over sensitive information about what they're moving, where, and for whom, often for high-value or time-sensitive goods. A data-handling failure traced back to an offshore development lapse doesn't just create a regulatory problem; it damages the kind of client trust that logistics companies spend years building. That asymmetry — a small, avoidable process gap creating an outsized reputational cost — is part of why the compliance-in-house instinct has held even as the build side has opened up.

What Changes in Practice for Your Website, App, or Platform

If your logistics company is going down this path — or already has, informally — a few concrete things need to change in how projects get scoped and run.

Data Residency Has to Be a Spec, Not an Afterthought

Before any external team writes a line of code, the data-residency requirements need to be written down: which data categories must stay on Swiss or EU infrastructure, which can move, what encryption and access-logging standards apply, and how backups and disaster recovery are handled without violating those same constraints. This becomes part of the technical specification the way authentication or performance requirements would be — not a compliance memo attached after the fact.

Access Control Needs to Survive the Handoff

When an external development team is involved, especially through the build phase, access to production data (or realistic production-like data) needs to be scoped tightly and time-boxed. Many logistics companies handle this by giving development teams access only to synthetic or anonymized data during build and testing, and restricting real data access to a small internal team that handles deployment and monitoring. This is directly relevant to security architecture — our guide on AI Application Security: Complete Guide to Securing AI Software in 2026 covers the access-control and data-handling patterns that apply whether or not AI is involved in the system itself.

Vendor Contracts Need Explicit Compliance Language

A statement of work with an external development partner should name the applicable data protection framework (FADP, GDPR, or both), specify where code repositories and any test data are hosted, and define what happens to any data or credentials at project close. This is a small amount of upfront legal and technical diligence that prevents a much larger cleanup problem later — and Swiss companies increasingly build it into every offshore engagement as standard practice, not a special case.

Testing and Staging Environments Need the Same Discipline as Production

It's easy to focus data-residency and access rules entirely on the production environment and forget that staging and testing environments often contain data that looks and behaves exactly like production data, sometimes because it literally is a copy of it. An external development team working through a staging environment that hasn't been properly anonymized has effectively the same access as if they were working directly against live customer and shipment records. Any data-handling specification worth writing should explicitly cover staging, testing, and any sandbox environments the offshore team touches, not just the production system everyone naturally thinks of first.

Multi-Sided Platforms Raise the Stakes

If your logistics business is building or expanding a platform that connects multiple carriers, shippers, or warehouse partners — increasingly common as logistics companies try to capture more of the value chain digitally — the compliance surface gets larger, not smaller. Each additional party accessing the platform is another set of data flows to account for. Our piece on Marketplace Development: Building a Multi-Seller Platform From Scratch walks through how multi-party platforms need to be architected so that each participant's data access is properly scoped, which is exactly the kind of design decision that should stay under internal compliance control even when the platform itself is built externally.

What to Actually Do About It

The practical response for a Swiss logistics company isn't to avoid offshoring the build — the cost and speed benefits are real and the commentary suggests this is where the industry is heading regardless. The response is to formalize the in-house compliance function before you formalize the offshore development relationship.

Concretely, that means: designate a person or small team internally who owns data-residency and compliance decisions for every software project, regardless of who builds it. Require a written data-handling specification before any external team starts work. Keep architecture and infrastructure decisions — where things are hosted, who has keys, how data moves between systems — reviewed and approved internally, even if implementation is external. And build in a compliance review checkpoint before go-live, not just at the contract-signing stage.

None of this needs to slow the project down in any meaningful way if it's built into the process from the start rather than bolted on. A well-run engagement looks something like this: internal stakeholders draft the data-handling specification and get sign-off from whoever owns compliance, that specification becomes part of the technical brief handed to the development partner, the partner proposes an architecture that satisfies it, internal review confirms the architecture before build begins, and a final compliance check happens before go-live alongside the usual QA pass. Each of these steps adds a few days at most when planned for — the delays only happen when compliance gets discovered as a blocker partway through development, forcing rework on decisions that should have been made upfront.

It's also worth planning for change over time. A platform that satisfies your data-residency requirements at launch can drift out of compliance months later as new integrations get added, new partners come online, or infrastructure gets migrated to a different provider or region for cost or performance reasons. Building a lightweight recurring review into your operating rhythm — even a short quarterly check against the original specification — catches this drift before it becomes a live incident rather than after.

It's also worth watching how other jurisdictions are formalizing AI and software governance, since Swiss regulators tend to track international regulatory direction closely. Our overview of Australia's AI Regulation Roadmap: Inside the New National Standards and Office of AI is a useful reference point for the kind of formal governance structures — named accountable owners, documented decision trails — that regulators globally are converging on, and that Swiss logistics companies would do well to adopt proactively rather than reactively.

Where This Fits Budget-Wise

The scale of work involved — from a scoped tracking portal to a full multi-party logistics platform — maps onto a few general tiers, framed around what this kind of engagement typically falls under:

Tier	Typical scope for logistics software	Starting at
Essential	A single-purpose tool: a tracking portal, a carrier status dashboard, a focused integration	$1,000
Growth	A more complete platform: dispatch system, customer portal with multiple data sources, compliance-aware architecture	$2,000
Enterprise	Multi-party platforms, complex customs/carrier integrations, full compliance and audit tooling	$4,000+

These are starting points, not fixed quotes — the right tier depends on how many data sources, partners, and compliance requirements the build has to account for from day one.

Key Takeaways

• Swiss SMEs, including logistics companies, are outsourcing software builds abroad while keeping compliance and data-residency decisions internal — this is a deliberate split, not a gap.
• Logistics data is cross-border and dense (customs, consignee/consignor data, partner integrations), which raises the stakes of getting this split wrong compared to less data-heavy industries.
• Data-residency and access-control requirements need to be written into the technical spec before an external team starts building, not added afterward.
• Vendor contracts with offshore or external development partners should name the applicable data protection framework and specify data/credential handling at project close.
• Multi-party platforms (carrier, shipper, warehouse integrations) multiply the compliance surface and need internal architecture sign-off even when built externally.
• Designate an internal owner for compliance and data-residency decisions on every software project, independent of who does the actual development work.

Getting the split right between what you outsource and what you keep in-house is a scoping conversation worth having before a project starts, not after. If you want help figuring out where that line should sit for your specific systems, book a meeting with our team.

Frequently Asked Questions

What does it mean to outsource the build but keep compliance in-house?

It means the actual software development work — writing code, building features, integrating systems — is done by an external team, often abroad, while decisions about data residency, access control, and regulatory compliance stay controlled by people inside the logistics company. The company retains legal and operational accountability even though it doesn't retain every line of code.

Why are Swiss SMEs doing this now rather than keeping everything in-house?

Cost and speed pressure on mid-sized firms is the main driver — Swiss development talent is expensive relative to competitive markets, and offshore or nearshore teams let companies modernize faster without the same cost base. Compliance stays internal because legal accountability under Swiss law doesn't transfer to an external vendor.

Is this trend specific to logistics, or does it apply to all Swiss SMEs?

The pattern of outsourcing builds while keeping compliance in-house appears across Swiss SMEs generally, according to 2026 Swiss SME technology commentary. It matters more acutely for logistics companies because their data — customs records, cross-border shipment details, partner data — is unusually dense and cross-jurisdictional.

What is data residency and why does it matter for a logistics platform?

Data residency refers to the physical and legal location where data is stored and processed. For a logistics platform handling shipment records, customs declarations, and customer data across borders, residency determines which laws apply, who can lawfully access the data, and what happens during audits or disputes.

Does the revised Swiss FADP apply to a logistics company's software even if the developers are abroad?

Yes — the Federal Act on Data Protection applies based on where the data subjects and the responsible company are, not where the code was written. A Swiss logistics company remains accountable under FADP regardless of whether its development team is local or offshore.

Do we also need to worry about GDPR if we ship within the EU?

If your logistics operations involve EU shippers, consignees, or partners, GDPR likely applies alongside FADP for the relevant data flows. Many Swiss logistics companies end up designing to the stricter of the two frameworks to avoid maintaining separate compliance logic.

Can an external development team be trusted with real shipment or customer data during a build?

It depends entirely on what you specify and enforce. Best practice is to limit external teams to synthetic or anonymized data during build and testing, and to restrict real production data access to a small internal team responsible for deployment and monitoring.

What should be in a data-residency spec before we hire an external developer?

It should specify which data categories must stay on Swiss or EU infrastructure, encryption and access-logging standards, backup and disaster recovery locations, and who is authorized to access which data during and after development. This becomes part of the technical requirements document, not a separate compliance afterthought.

How do we vet a Custom Software Development partner for this kind of work?

Ask directly about their experience with regulated, cross-border data handling, request their standard approach to environment segregation between build and production, and confirm they'll work to a data-residency spec you provide rather than their own default assumptions. A partner offering Custom Software Development for logistics should expect this line of questioning as routine.

What happens to our data and code access when a project with an external team ends?

This should be defined in the vendor contract from the start: credentials revoked, any local copies of data destroyed or returned, repository access transferred cleanly to your internal team. Leaving this undefined is one of the more common gaps in offshore engagements.

How long does a compliant logistics software build typically take?

Timeline depends heavily on scope — a single-purpose tracking portal with a clear data spec can move in a matter of weeks, while a multi-party platform with several carrier integrations and full audit tooling takes considerably longer. Building the compliance spec upfront tends to shorten the overall timeline by avoiding rework later.

Does keeping compliance in-house mean we need to hire a dedicated compliance officer?

Not necessarily a full-time hire for smaller firms — it can be a designated existing employee with the authority and enough technical literacy to review architecture decisions and sign off before go-live. What matters is that the role is explicit and consistently exercised, not informal.

What's the risk if we don't formalize this split and just let the offshore team make data decisions?

The risk is that architecture and hosting decisions get made for engineering convenience rather than compliance, and by the time it's noticed, data may already be sitting in the wrong jurisdiction or accessible to more people than intended. Retrofitting compliance after launch is materially more expensive than designing for it upfront.

How does this affect a carrier or shipper-facing customer portal specifically?

A customer-facing portal usually holds live shipment data, contact details, and sometimes payment information, all visible to external users in real time. That combination makes access control and data segregation more urgent than for an internal-only tool, since a breach or misconfiguration is immediately visible to customers.

What is a multi-seller or multi-party logistics platform, and why does it complicate compliance?

It's a platform connecting multiple independent parties — carriers, shippers, warehouses — each with their own data and access needs, similar in structure to what's described in our guide on marketplace development. Each additional party is another data flow and another set of access permissions to design and audit, multiplying the compliance surface compared to a single-user application.

Should carrier and warehouse partners have direct access to our internal systems?

Generally no — direct access to internal systems should be avoided in favor of scoped APIs or partner portals that expose only what each party needs. This limits the blast radius if a partner's own security is weaker than yours.

How do we handle customs data specifically when using offshore developers?

Customs data often carries additional regulatory sensitivity, so it should be treated as a distinct data category in your residency spec with explicit rules on storage location and access, separate from general shipment data. Offshore development teams should typically work against synthetic customs data rather than live records.

What's the difference between offshoring and outsourcing in this context?

Offshoring usually implies the development team is in a different country, often chosen for cost, while outsourcing more broadly means using any external team rather than internal staff, whether local or abroad. The compliance-retention principle in this trend applies to both — the location of the team matters less than who controls governance decisions.

Is nearshoring to a nearby European country a safer alternative to offshoring further afield?

Nearshoring can simplify some legal and time-zone considerations, particularly around GDPR alignment, but it doesn't eliminate the need to define data-residency and access rules explicitly. The governance discipline described here applies regardless of how far away the development team is.

How does AI use in a logistics platform change the compliance picture?

If your platform uses AI for route optimization, demand forecasting, or document processing, you add another layer of data handling and model-access considerations on top of standard data residency. Our guide on securing AI software covers the additional access-control and data-handling patterns relevant once AI is part of the stack.

Can we use an offshore team for AI features specifically, or does that need extra caution?

Extra caution is warranted because AI features often require larger, richer datasets during development and testing, increasing the temptation to use real data. The same principle applies more strictly here: use synthetic or heavily anonymized data during offshore AI development wherever possible.

What internal skills do we need to manage this split effectively?

You need at least one person who can read and evaluate a technical architecture proposal well enough to flag compliance risks — not necessarily a developer, but someone technically literate enough to ask the right questions before approving a design.

How do we know if our current offshore development arrangement already has compliance gaps?

A quick audit checklist: do you know exactly where your production data is hosted, who has access to it, what happens to test data, and what your vendor contract says about data handling at project end. If any of those questions don't have a clear answer, there's likely a gap worth closing.

Does this trend mean Swiss logistics companies are moving away from local development entirely?

No — it's a shift in proportion and structure, not a wholesale move away from local capability. Many companies keep architecture, compliance, and product strategy roles local while distributing implementation work more broadly.

What's a realistic first project for a logistics company testing this offshoring approach?

A contained, well-defined project — like a single tracking portal or one carrier integration — is a reasonable way to test both the vendor relationship and your internal compliance process before committing to a larger platform build.

How do we price a project that has significant compliance requirements built in?

Compliance requirements add scoping and review time on top of core development, which is typically reflected by moving from an Essential-tier engagement toward Growth or Enterprise tiers depending on how many data sources and access rules need to be designed and audited.

What happens if a data breach occurs and the software was built by an offshore team?

Legal and regulatory accountability under FADP or GDPR sits with the Swiss company, not the offshore development team, regardless of where the underlying vulnerability originated. This is precisely why compliance decisions need to stay in-house — the liability doesn't follow the code.

Should our compliance requirements be part of the initial contract or added later?

They should be part of the initial statement of work and technical specification, not added after development starts. Adding them later usually means retrofitting architecture decisions that were made without those constraints in mind.

How often should we review our data-residency setup once a platform is live?

At minimum, whenever you add a new integration, partner, or data category, and otherwise on a regular cadence — many companies tie this to an annual or semi-annual compliance review alongside broader security audits.

Can existing legacy logistics software be retrofitted for this kind of compliance clarity?

Yes, though it usually requires an audit of current data flows and access patterns before any new development work continues, essentially producing the data-residency spec that should have existed from the start. This audit itself is often a worthwhile standalone engagement.

What role does encryption play in satisfying data-residency requirements?

Encryption at rest and in transit reduces risk but doesn't substitute for correct data-residency decisions — data can be encrypted and still be sitting in a jurisdiction or under access permissions your compliance requirements don't allow. Both need to be addressed together.

How do we handle backups when data-residency rules restrict where data can live?

Backup locations need to be specified explicitly in the same residency requirements as primary data storage, since backups are a common place where residency rules get accidentally violated. This should be confirmed with any development or infrastructure partner before go-live.

What's the biggest mistake logistics companies make when starting to offshore development?

The most common mistake is treating compliance as something to handle after the build is functional, rather than writing residency and access requirements into the spec from day one. This almost always costs more to fix retroactively than to design correctly upfront.

Does keeping compliance in-house slow down the offshore development process?

It adds some upfront time for specification and review, but it typically speeds up the overall project by avoiding rework, renegotiation, or emergency remediation later. The upfront cost is smaller than the downstream cost of getting it wrong.

How do we structure a vendor contract to protect against compliance risk?

Name the applicable data protection framework explicitly, specify where code and any test data are hosted, define data and credential handling at project close, and include the right to audit compliance-relevant practices during the engagement.

Are there Swiss-specific certifications or standards a development partner should hold?

There isn't a single mandatory certification for this kind of work, but familiarity with FADP requirements and demonstrated experience with EU GDPR-adjacent engagements are reasonable things to ask a potential development partner about directly.

What's the relationship between this trend and broader AI regulation internationally?

Regulators globally, including in jurisdictions like Australia, are formalizing governance structures with named accountable owners and documented decision trails for software and AI systems. Swiss logistics companies adopting similar internal accountability structures now are likely to be ahead of where regulation is heading rather than reacting to it later.

Should smaller logistics companies with limited budgets still separate build and compliance ownership?

Yes — the principle scales down even for smaller engagements; it doesn't require a large compliance team, just a clearly designated owner and a written data-handling spec, both of which are low-cost relative to the risk they mitigate.

How do we evaluate whether our current software vendor already follows this model?

Ask them directly how they handle data residency, what access controls exist between build and production environments, and whether they can point to a written data-handling agreement from your engagement. Their answer will tell you quickly whether this is already formalized or informal.

What kind of logistics features most commonly require careful data handling?

Customer-facing tracking, customs documentation, carrier rate and contract data, and any payment or invoicing integration tend to carry the most sensitive data and warrant the closest attention to residency and access design.

Is it possible to combine an offshore build with Swiss-hosted infrastructure?

Yes, and this is a common and sensible pattern — the development team can be located anywhere while the actual production infrastructure and data storage remain hosted in Switzerland or the EU, satisfying residency requirements independently of where the code was written.

How does this affect API integrations with third-party carriers or customs systems?

Each third-party integration is an additional data flow that needs to be documented in your residency and access spec, including what data is sent, what's received, and where each party's systems are hosted. This is often overlooked because integrations feel like a technical detail rather than a compliance one.

What's a reasonable timeline to formalize an in-house compliance function before starting an offshore project?

For most mid-sized logistics companies, a few weeks is enough to designate an owner, draft a data-handling specification, and review it against the planned project scope, assuming the internal technical literacy already exists.

Can this compliance-in-house model work if we don't have any in-house developers at all?

Yes — the compliance owner doesn't need to be a developer, just someone technically literate enough to evaluate architecture proposals and enforce the data-handling spec. Many logistics companies with fully outsourced development still maintain this role internally.

What should we ask a development partner about their own internal security practices?

Ask how they segregate development, testing, and production environments, how they handle credentials and access revocation at project end, and whether their own staff undergo any data-handling training relevant to the sensitivity of your data.

How do we handle compliance when working with more than one external development team over time?

Each engagement should be governed by the same internal data-handling specification, updated as needed, so that compliance standards don't vary based on which vendor is doing the work at a given time. Consistency here matters more than any single vendor relationship.

Does moving to cloud infrastructure change any of these compliance considerations?

Cloud infrastructure adds another layer to specify explicitly — which cloud regions data is stored and processed in, and what the cloud provider's own data-handling terms are — on top of the development team's practices. This should be confirmed as part of the same residency spec.

What's the first concrete step a logistics company should take after reading this?

Write down, in one page, where your current shipment, customer, and customs data is stored, who has access, and who inside the company is accountable for that answer. That single document is the foundation everything else in this piece builds on.

How can Scult help with this specific challenge?

Scult's Custom Software Development work is built around exactly this kind of scoping — defining data-residency and access requirements as part of the technical specification before development starts, so the build moves fast without compliance becoming an afterthought.

What's the best way to start a conversation about this with a development partner?

Bring your current data flows and any known compliance constraints to the first conversation rather than starting from a blank page — it lets the partner scope the project accurately and surface any gaps early, which is exactly the kind of conversation you can start with a book a meeting request.