Built for revenue teams running international sales motions

The CRM for sales teams who sell in more than one currency and more than one timezone.

Global sales operations is not US-centric sales with a currency field bolted on. Multi-currency, FX snapshots per deal, timezone-aware activity timelines, region-scoped Layouts, local tax fields, and regional compliance each need first-class support. Strkr ships the primitives inside one CRM.

Start free trial See pricing
What this audience is actually dealing with

The pains that bring buyers here.

An international sales motion looks tidy on a slide. On a Monday pipeline review across London, Singapore, and New York it is anything but. The forecast rolls up in the wrong currency, the FX rate moved 4 percent since the deal was created, the activity timeline shows times in the admin time zone, the German rep sees US-only Layouts because nobody built a regional variant, and the compliance partner just flagged a GDPR Article 30 record of processing gap on the EU buyer data. Most CRMs sell themselves as global and ship a currency dropdown. That is not global sales operations, that is a shim. The six pains below are what we hear from revenue leaders running a real international motion across 3 to 7 regions. If any of them look familiar, the rest of this page shows the primitives Strkr ships to handle the motion without a professional services engagement.

USD-only forecast surface

The CRM shows USD and the rep works in EUR.

The sales leader runs a global pipeline review and the CRM renders every deal in USD because the admin set USD as the tenant default. The German rep works deals in EUR, enters EUR values on the deal, and the CRM silently converts at an outdated rate. The rep sees the deal value in USD on the board and the EUR value hidden in a secondary field. Discussions with the rep get confusing fast. Strkr renders both the deal currency (EUR, GBP, SGD, JPY, AUD, CAD, INR, BRL, and 40+ more) and the reporting currency on every surface, with the FX rate used for the conversion visible on hover.

FX moves and the forecast lies

The deal was created 60 days ago and FX moved 4 percent.

A 500,000 EUR deal booked at 1.08 USD per EUR drifted to 1.12 three weeks later. The CRM renders the deal at the current FX rate so the forecast number moves without any sales activity. The sales leader cannot tell whether the forecast changed because of sales execution or because of a currency swing. Strkr captures an FX snapshot on every deal at creation (and at manual override), so the forecast picture holds steady on the originating rate while a secondary report surfaces the FX delta for finance review.

Timezone-blind activity timeline

The timeline says 3am and the Singapore rep is actually working.

A sales manager in New York reviews the Singapore rep activity timeline and sees entries at 3am local to New York. The manager cannot tell whether the entries happened in a reasonable Singapore working hour or at 3am Singapore. The follow-up conversation is awkward because the manager flagged the rep for after-hours activity that was actually 3pm Singapore. Strkr renders activity timelines in the viewer time zone by default with a per-event tooltip showing the actor local time, so a global roll-up is readable from any desk.

No local tax or regulatory fields

The German deal needs a VAT ID and the US CRM has no field for it.

The German B2B deal needs a VAT ID on the invoicing contact, the UK deal needs a VAT ID plus a VAT scheme flag, the Indian deal needs a GSTIN, the Brazilian deal needs a CNPJ, and the US CRM shipped with a US-only tax exemption field. The rep stores the IDs in a free-text notes field, the finance partner cannot build a clean invoice export, and the compliance partner has a nervous Monday. Strkr region-scoped Layouts render the right local-tax fields on the deal based on the account country, so the rep captures the right field and the invoice export runs clean.

One Layout for every region

The APAC rep sees US fields they will never fill.

The CRM admin built one Layout for every account record and shipped it globally. The APAC reps see US-centric fields (state, zip code, US revenue segment), the EU reps see fields that violate the local segmentation they actually use, and the Latin American reps see nothing useful. Every rep ignores half the Layout and the data quality suffers. Strkr region-scoped Layouts render per-region variants (field order, section grouping, required fields) based on the account country or the user region, so the rep sees the fields that matter and the compliance partner gets the data that matters.

Region-specific compliance

GDPR, LGPD, PIPL, and PDPA each need their own posture.

The EU deals need GDPR Article 30 records of processing, Article 6 lawful basis flags, and DPIAs where applicable. The Brazil deals need LGPD lawful basis and data subject rights handling. The China deals need PIPL cross-border transfer approvals. The Singapore deals need PDPA consent capture. A US-only CRM ships with a US privacy posture and leaves the global compliance partner stitching the gaps in spreadsheets. Strkr compliance primitives ship region-aware, with lawful basis fields, consent capture, cross-border transfer flags, and audit trails sized to each regulation.

Multi-currency primitives

What a real multi-currency CRM looks like.

Multi-currency is not a dropdown on the deal form. It is a set of specific primitives that compose into a sales motion that works across 20 currencies without the sales leader having to explain the forecast swing on every Monday review. The cards below describe the primitives Strkr ships out of the box, with real behavior and real controls the sales operations lead can configure without an engineering ticket. The pattern is deliberate: every value is captured in the deal currency, converted on the fly for reporting with an FX snapshot that holds the picture steady, and surfaced with full transparency so finance can audit the conversion.

Deal currency per record

Every opportunity carries its own currency.

Every opportunity record carries a currency field (ISO 4217 code) that defaults to the account country but can be overridden at deal creation. The deal value, line items, discounts, and products all render in the deal currency on the record. The rep enters EUR for the German deal and never sees a USD conversion the rep did not ask for. The deal currency flows through to proposal and invoice generation.

FX snapshot on creation

The forecast holds steady on the originating FX rate.

When a deal is created, Strkr captures the FX rate to the tenant reporting currency as a snapshot on the deal. The forecast number uses the snapshot rate so a 500,000 EUR deal booked at 1.08 stays at 540,000 USD in the forecast until the deal closes or the sales operations lead manually refreshes the snapshot. A secondary report surfaces the FX delta from current rate for finance review, so the forecast lies caused by FX movement go away.

Dual-currency rendering

Every board shows deal currency and reporting currency.

The pipeline board, the forecast surface, the opportunity report, and the dashboard all render the deal in its native currency with the reporting-currency equivalent on hover or in a secondary column. The sales leader scans the EUR deals in EUR and the aggregate roll-up in the tenant reporting currency. The German rep never has to mentally convert their deal value to understand the record.

Multi-currency products and pricing

Products priced per currency with per-region price books.

The Products module supports per-currency pricing for each SKU. A software license can list at 999 USD, 899 EUR, 749 GBP, 1,249 SGD, and the price book flows through to proposal and invoice generation. Regional price books (US, EU, UK, APAC, LATAM) scope which products are available in which markets, and the admin surface controls the price list without an engineering ticket.

FX rate source and refresh

Daily rate feed with manual override on specific deals.

Strkr pulls a daily FX rate feed from a tier-1 financial data provider with 20+ supported currencies. The admin surface sets the refresh cadence (daily, weekly, or on-demand). Individual deals can override the FX snapshot if finance has negotiated a hedge rate or if the deal uses a non-standard conversion for a customer agreement.

Multi-currency forecast rollup

Forecast rolls up in the tenant reporting currency.

The forecast surface rolls up weighted pipeline, submitted commits, and the gap to quota in the tenant reporting currency using the FX snapshot on each deal. A regional breakdown view surfaces the per-region forecast in each regional reporting currency (EUR for the EU region, GBP for UK, SGD for APAC) so the regional sales leader sees the picture in a currency that matches the regional business plan.

Timezone and localization primitives

Primitives that make the global roll-up readable.

A global sales motion runs across 10 to 15 time zones with reps in 4 to 7 regions. The CRM needs to render every surface so the viewer sees times in a sensible frame, so dates and numbers format to the local convention, so the Flows fire at business hours in the right region, and so the admin surface does not force the APAC sales leader to think in US time. The cards below describe how Strkr ships timezone and localization support without a professional services engagement to retrofit it.

Viewer time zone rendering

Every timestamp renders in the viewer local time.

Activity timelines, task due dates, meeting times, email send timestamps, and audit log entries all render in the viewer local time zone by default. A per-event tooltip surfaces the actor local time (so a New York manager hovering a Singapore rep activity sees the Singapore local time alongside the New York local time) and a per-view toggle lets the viewer switch to a zone for a global roll-up.

User time zone profile

Every user carries a profile time zone the rendering respects.

Every user record carries a time zone field (IANA zone identifier) that defaults from the user region on provisioning and can be edited on the user profile. All timestamp rendering, business hour calculations, and Flow trigger evaluations respect the user time zone. The Monday 9am follow-up task fires at 9am local to the user, not 9am local to the admin.

Locale number and date formatting

Numbers and dates format to the viewer locale.

Numbers (thousands separators, decimal marks), dates (DD/MM/YYYY vs MM/DD/YYYY vs ISO), currencies (symbol placement, decimal places), and percentage formatting all respect the viewer locale. The EU rep sees 500.000,00 EUR with the EU convention, the US rep sees 500,000.00 USD with the US convention, and the system does not force one convention on a region that reads differently.

Business hours per region

Flows and SLAs honor regional business hours.

The admin surface defines business hour profiles per region (EU 9am to 6pm Mon to Fri, APAC 9am to 7pm with Saturday half-day where applicable, India 10am to 7pm with regional holiday calendars). SLA timers tick against the right business hour profile for the owning rep region, Flow triggers evaluate against the right calendar, and the 4-hour SLA on a Friday afternoon in the EU does not count the weekend as elapsed time.

Regional holiday calendars

Public holidays per country honored on SLA and Flow timers.

Public holiday calendars per country ship as a managed data set and update annually. Golden Week in Japan, Diwali in India, Easter and Christmas across EU, Chinese New Year across APAC, Carnival in Brazil all land as non-business days on the regional calendar, so SLAs and Flow timers do not fire against holidays. The admin surface overrides specific days for company holidays or regional variations.

Language-aware templates

Message templates render in the recipient language.

Message templates (email, SMS, in-app) support per-language variants. The admin builds the English template once, adds German, French, Portuguese, Japanese, and Chinese variants, and the template engine picks the right variant based on the recipient contact language field. The rep selects the template by concept, not by language, and the right localization goes out.

Regional Layouts and compliance

Region-scoped field surface plus region-aware compliance.

The last two pieces of a real international sales operation are the field surface the rep sees (which fields render on the record, which are required, which are grouped together) and the compliance posture around personal data processing. Both need to be region-aware, and both are typically retrofitted on a US CRM through a professional services engagement that costs more than the first year of licenses. Strkr ships region-scoped Layouts and compliance primitives natively, so the admin surface handles the global motion without a vendor engagement.

Region-scoped Layouts

Different fields render for different account regions.

Layouts can be scoped to a region (EU, UK, APAC, LATAM, NAM, EMEA, custom groupings). An account record in Germany renders the EU Layout with VAT ID, lawful basis flag, and the EU-specific segmentation. A Singapore account renders the APAC Layout with GST registration and PDPA consent fields. The rep sees the fields that matter for the region and the data stays clean per-region.

Country-specific tax fields

VAT ID, GSTIN, CNPJ, ABN all first-class.

The admin surface ships pre-built field groups for the common per-country tax identifiers: EU VAT ID with VIES validation hook, UK VAT number, India GSTIN, Brazil CNPJ, Australia ABN, Mexico RFC, Canada BN. The rep enters the ID, the field validates against the format, and the invoice export runs clean against the right identifier.

GDPR primitives

Article 6 lawful basis, Article 30 records, DPIAs tracked.

EU personal data processing captures lawful basis per contact (consent, contract, legitimate interest, legal obligation), surfaces an Article 30 record of processing by Flow and automation, and tracks DPIAs where high-risk processing applies. The compliance partner audits the posture from the admin surface without a weekly spreadsheet reconstruction.

CCPA and US state privacy

California plus 10+ US state privacy regimes handled.

California CCPA ships with consumer rights handling (right to know, right to delete, right to opt-out of sale), and the same primitives handle the growing US state privacy regimes (Virginia VCDPA, Colorado CPA, Connecticut CTDPA, Utah UCPA, and newer regimes as they roll in). The compliance partner tracks the posture per state from one admin surface.

Regional data residency

US, EU, APAC regions available on enterprise contracts.

Enterprise contracts cover regional data residency with Strkr tenants provisioned in US, EU, or APAC regions depending on the primary customer-data location. Cross-border transfer flags on specific contacts and accounts let the compliance partner track where personal data is actually processed, and the audit log captures the pattern for the record of processing.

LGPD, PIPL, PDPA, DPDP

Regional privacy regimes beyond EU and US.

Brazil LGPD, China PIPL cross-border transfer flags, Singapore PDPA consent capture, and India DPDP compliance primitives ship as region-aware field groups and audit configurations. Enterprise contracts cover the regional controls on request, and the open API lets the compliance team export the audit trail for regulator inquiries.

Head-to-head

Strkr vs US-centric CRM (HubSpot or Pipedrive style).

The common competitive stack for an international sales motion is a US-centric CRM (HubSpot, Pipedrive, Salesforce Essentials) with a currency dropdown bolted on and a professional services engagement for the regional variants. The sales operations lead ends up maintaining spreadsheets for FX, regional tax, and compliance that the CRM cannot handle natively. Strkr collapses the gap by shipping the primitives in the paid tier with no additional module cost. The comparison runs line by line.

Feature Strkr US-centric CRM (HubSpot/Pipedrive)
Deal currency per record Native with 50+ ISO 4217 codes Available in enterprise tiers, often add-on
FX snapshot on deal creation Native, forecast holds steady on originating rate Current rate only, forecast swings with FX
Dual-currency rendering Deal and reporting currency on every surface Reporting currency only on most views
Multi-currency product pricing Per-currency SKU pricing in Products module One price book, manual overrides
Timezone-aware activity Viewer time zone with actor tooltip Admin time zone default, limited tooltips
Regional business hours Per-region profile with holiday calendars One business hour profile
Region-scoped Layouts Per-region field surface and required fields One Layout for all accounts, professional services for variants
Country-specific tax fields VAT, GSTIN, CNPJ, ABN pre-built with validation Custom fields the admin builds
GDPR Article 30 and lawful basis Native primitives in the admin surface Partial, add-on compliance module
Regional data residency US, EU, APAC on enterprise contracts US primary, EU on enterprise with contract
Language-aware templates Per-language template variants native One template, manual language variants
Pricing model Flat per-seat covers all global primitives Base per-seat plus modules plus professional services
How teams use Strkr

How global sales teams run Strkr.

The patterns below show up across real international sales motions: a US headquarters selling into EU and APAC, an EU-headquartered firm selling across the EU plus UK plus APAC, a global SaaS company with 7 regional sales teams, a professional services firm with multi-currency project billing, and an enterprise company with regional data residency requirements. Each playbook names the primitives the team runs and the gap it closed from the previous CRM.

US HQ selling into EU and APAC

US reporting with regional pipeline integrity.

A 25-rep US headquartered SaaS company with 8 reps in the EU and 4 in APAC moved off a US-centric CRM where the forecast rolled up in USD only and the regional reps worked around the system. Strkr multi-currency ships EUR and SGD deals in native currency with FX snapshots, the global forecast rolls up in USD using the snapshot rates, and regional dashboards render in EUR and SGD for the regional sales leaders. Forecast accuracy climbed from 71 percent to 88 percent in two quarters.

EU HQ across EU, UK, APAC

VAT compliance plus regional Layouts out of the box.

An 18-rep EU headquartered firm sold across EU, UK, and APAC with VAT compliance requirements across 14 countries. Strkr region-scoped Layouts rendered the right local tax fields per account country, EU VAT ID validation ran against VIES on save, and the invoice export flowed clean into the finance system per-country. The compliance partner audit cycle shortened from 3 weeks to 2 days per quarter.

Global SaaS with 7 regional teams

Regional pipelines, global rollup, timezone-sane activity.

A 60-rep global SaaS company ran 7 regional sales teams (US East, US West, EU North, EU South, UK, APAC North, APAC South). Strkr region-scoped Layouts rendered per-region fields, timezone-aware activity timelines made the global roll-up readable for the CRO in London, business hour profiles per region handled SLAs correctly, and holiday calendars honored regional non-business days. The CRO Monday roll-up took 20 minutes instead of 90.

Pro services with multi-currency projects

Projects billed in local currency with FX-stable revenue recognition.

A 40-person professional services firm billed project engagements in client local currency (USD, EUR, GBP, AUD, CAD, SGD, BRL) and recognized revenue in the firm reporting currency (USD). Strkr multi-currency opportunities with FX snapshots on deal creation kept the revenue recognition picture stable, the Projects module tracked project value in client currency with reporting-currency rollup, and the quarterly finance close ran clean without a spreadsheet reconciliation.

Enterprise with data residency

EU tenant for EU customer data with cross-border tracking.

A 100-rep enterprise company sold across US and EU with EU customer data required to stay in EU regions. Strkr enterprise contract provisioned a dedicated EU tenant for EU customer records with cross-border transfer flags on contacts that needed US-based access. GDPR Article 30 records of processing exported directly from the admin surface, DPIAs tracked per Flow, and the regulator inquiry response time dropped from weeks to days.

See the CRM built for international sales strategy.

Start a 14-day trial with multi-currency, FX snapshots, timezone-aware timelines, region-scoped Layouts, country-specific tax fields, and the GDPR plus CCPA compliance primitives enabled on the full tenant. One workspace, one bill, one admin surface for the global sales motion. The pricing page lays out the per-seat line in full and the enterprise contract page covers regional data residency and SSO details.

See pricing Enterprise overview
Common questions

What buyers in this bucket ask most.

How many currencies does Strkr support?

Strkr supports 50+ ISO 4217 currency codes natively, covering all major developed-market currencies (USD, EUR, GBP, JPY, CHF, CAD, AUD, NZD) and all major emerging-market currencies (CNY, INR, BRL, MXN, ZAR, SGD, HKD, KRW, TWD, THB, MYR, PHP, IDR, VND, PLN, CZK, HUF, TRY, AED, SAR, and more). The admin surface controls which currencies are enabled per tenant, and the FX rate feed updates daily from a tier-1 financial data provider. For currencies with specific hedge arrangements, the admin can override the FX snapshot on individual deals or set a custom rate for a tenant period.

How does the FX snapshot work and when does it update?

When a deal is created, Strkr captures the current FX rate from the deal currency to the tenant reporting currency and stores it as an immutable snapshot on the deal. The forecast number uses the snapshot rate so a deal booked at 1.08 EUR to USD stays at 1.08 in the forecast as the deal progresses. The snapshot refreshes automatically on close (so the closed-won revenue reflects the actual close-date FX for finance recognition) and can be manually refreshed by the sales operations lead when a deal has significantly drifted. A secondary report surfaces the FX delta between snapshot rate and current rate for finance review.

How does Strkr handle timezone-aware activity across global teams?

Every user record carries a time zone field (IANA zone identifier) that defaults from the user region on provisioning. Activity timelines render in the viewer time zone by default with a per-event tooltip showing the actor local time (so a New York manager hovering a Singapore rep activity sees the Singapore local time alongside the New York local time). Task due dates, meeting times, SLA timers, and Flow triggers all respect the user time zone. The 9am follow-up task for a Singapore rep fires at 9am Singapore local time, not 9am local to the admin who created the Flow.

Can I build different Layouts for different regions?

Yes. Layouts can be scoped to a region or a set of countries, so an EU account renders the EU Layout with VAT ID and lawful basis fields, a Singapore account renders the APAC Layout with GST registration and PDPA consent fields, and a US account renders the US Layout with the US-specific tax exemption and segmentation fields. The admin surface controls which Layout applies to which region, and the rep sees the fields that matter for the account they are working. Country-specific tax fields (EU VAT ID with VIES validation, UK VAT, India GSTIN, Brazil CNPJ, Australia ABN, Mexico RFC) ship pre-built with the right validation rules.

How does Strkr handle GDPR, LGPD, PIPL, PDPA, and other regional privacy regimes?

Strkr is GDPR and CCPA compliant with primitives for Article 6 lawful basis per contact, Article 30 record of processing export, and DPIA tracking where high-risk processing applies. Brazil LGPD, China PIPL cross-border transfer flags, Singapore PDPA consent capture, and India DPDP compliance primitives ship as region-aware field groups. Enterprise contracts cover regional data residency (US, EU, APAC tenants provisioned on request), SSO, SCIM provisioning, and tenant-specific key management. The open API lets the compliance team export the audit trail for regulator inquiries without a vendor engagement. Strkr is also HIPAA compliant with a BAA available where applicable, and SOC 2 Type II is in progress through 2026 Q4.

Do regional sales leaders see their region in their local reporting currency?

Yes. The admin surface can define regional reporting currencies (EUR for the EU region, GBP for UK, SGD for APAC, BRL for LATAM) distinct from the tenant global reporting currency (typically USD). The global forecast surface rolls up to the tenant reporting currency using FX snapshots, and the regional dashboards render in the regional reporting currency for the regional sales leader. A regional sales leader in London sees GBP, the APAC sales leader in Singapore sees SGD, and the CFO sees the global USD roll-up. The pattern avoids forcing every regional conversation into the headquarters currency and keeps regional business plans legible in the currency that matches the regional P&L.

Also built for

Related audiences.

Global Sales Enterprise Revenue Operations Forecasting Multi-Currency CRM Sales Operations

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing