FRACT Territory Mapping Evolved Into Wanderland Intelligence
How FRACT Territory Mapping Became a Broader Location Decision Intelligence Platform
LOCATION DECISION INTELLIGENCE SERIES · WHITE PAPER
FRACT territory mapping established the foundation. Wanderland Intelligence retains that map-centered experience and expands it with adaptive scoring, automated territory checks, governed sharing, reporting, AI, integrations, APIs, usage controls, and stronger administration.
EXECUTIVE ABSTRACT
FRACT established a practical foundation for digital territory mapping. During August and September 2026, Wanderland Intelligence retained that foundation and expanded it into a broader location decision platform. The change reaches every layer of the product: customer experience, territory building, scoring, availability checks, collaboration, reporting, artificial intelligence, integrations, APIs, usage controls, administration, security, and reliability. This paper provides a direct, fact-based comparison of 112 documented capability improvements. It also distinguishes production capabilities from provider integrations that remain in staged evaluation.
THE CONCLUSION
FRACT proved the value of making territory work visible on a map. Wanderland Intelligence keeps that foundation and connects it to the decisions that surround the map. A territory can now carry a configured score, an explanation, an availability decision, a share policy, a report, an activity record, an API representation, and a usage event. That continuity is the central product change.
The result is broader than a rebrand. Wanderland is designed to support the operating life of a location decision, from analysis through communication and automation. The comparison that follows documents the work completed during August and September 2026 and states clearly which provider connections still require staged validation.
DIRECT COMPARISON: FRACT TERRITORY MAPPING VS. WANDERLAND INTELLIGENCE?
Product Role
FRACT: Map-centered territory planning and analysis.
Wanderland: A location decision platform connecting territories, evidence, scoring, automation, reporting, AI, and external systems.
Customer Experience
FRACT: Established interface and project workflows.
Wanderland: Updated branding, navigation, authentication, responsive layouts, consistent controls, and clearer project context.
Territory Intelligence
FRACT: Territory construction and demographic analysis.
Wanderland: Project-specific scoring, Ideal Customer Profile targets, adjustable weights, score explanations, territory rankings, Brand Profiles, and Market Twins.
Availability Decisions
FRACT: Territory records available for customer review.
Wanderland: Configurable territory availability checks through public links and APIs, including blocking-territory identification, alternatives, and stored decision history.
Sharing and Reporting
FRACT: Project outputs and territory information.
Wanderland: Governed sharing packages, expiration controls, central link management, Report Studio, portfolio reports, and secure downloads.
Artificial Intelligence
The FRACT comparison baseline did not include an embedded Wander decision workspace.
Wanderland introduces project-aware AI grounded in territories, lists, stores, demographics, scores, and market data.
Connectivity
FRACT: Legacy customer API workflows and selected data movement.
Wanderland Intelligence: A common integration framework, Salesforce, HubSpot,
Zapier, webhooks, expanded APIs, and staged location-data providers.
Operating Model
FRACT: Subscription access and legacy administration.
Wanderland Intelligence: Decision Credit accounting, platform metrics, account controls, audit interfaces, and deliberate deletion workflows.
Security and Reliability
FRACT: Exisiting application controls and deployment practices.
Wanderland Intelligence: Stronger OAuth handling, rate limits, outbound-request protections, provider retries, idempotency, secure downloads, and smoke tests.
MODERNIZATION WITHOUT DISCARDING THE FOUNDATION
A credible product migration must protect the work customers already depend on. Wanderland therefore retains the FRACT customer API workflows, the map-centered workspace, territory construction, lists, demographic analysis, map presentation, and familiar project concepts. The strongest comparison is not old product versus unrelated new product. It is a working territory platform becoming a more complete location
decision system.
That distinction also matters for public claims. Established FRACT functions are described here as retained,modernized, or expanded. Capabilities introduced during the Wanderland build are labeled added. Security and reliability changes are labeled strengthened. Provider integrations that have not completed live certification are labeled staged. This language gives customers a useful view of progress without overstating product maturity.
Wanderland uses specific language to distinguish different types of product changes.
Retained means compatibility continues.
Modernized means an established FRACT function has a redesigned experience.
Expanded means the function now covers more work.
Added means a capability was introduced in Wanderland.
Strengthened describes security, control, or reliability improvements.
Staged identifies an integration that is still being evaluated.
This distinction matters because it allows existing FRACT customers to understand what remains familiar, what has changed, and which capabilities are new.
WHAT CHANGED DURING THE TWO MONTH BUILD
The interface became consistent Authentication, navigation, project context, panels, dialogs, lists, mapping tools, and administrative screens now follow one product system.
The score became configurable Accounts and projects can define the customer profile, factors, importance, and context that make a territory relevant to the business.
Availability became a service Rules can produce a repeatable answer through a public link or API, identitfy the blocking territory, and recommend an alternative.
Sharing became governed Customers can control content, package depth, expiration, plan limits, active links, and revocation.
Reporting became portfolio ready Report Studio and expanded exports support executives, territory teams, analysts, and downstream geospatial workflows.
AI became project aware Wander uses the active project and labels the Wanderland evidence used in its response.
Connectivity became a platform layer CRM, automation, webhooks, customer APIs, events, jobs, health records, retries, and idempotency now share an operating model.
Usage became measurable Decision Credits connect specific actions to an auditable balance and alert system.
Administration became operational Platform metrics, account management, role controls, audit views, and deletion safeguards support scale.
COMPLETE CAPABILITY COMPARISON
The following inventory covers all 112 documented improvements supplied for this release comparison. Each statement identifies how Wanderland relates to the FRACT foundation and why the wording is appropriate for public use.
CORE PLATFORM
Wanderland Intelligence keeps the map at the center of the work while reducing the friction around it.
The redesign creates a consistent path from project selection to territory construction, analysis, reporting, and administration.
Experience and Identity (MODERNIZED)
FRACT's application experience is reintroduced through the Wanderland Intelligence brand with updated navigation, authentication, password recovery, panels, dialogs, and responsive layouts.
Map Centered Workspace (EXPANDED)
The established map workflow is organized around Dashboards, Territories, Lists, Reports, and integrations.
Project Context and Controls (MODERNIZED)
Project context is clearer, and controls are more consistent across mapping tools and administrative screens.
Territory Builder (MODERNIZED)
Territory construction now combines geography selection, custom shapes, ZIP or postal search, tags, colors, manual and automatic modes, and encroachment controls in a modernized workflow.
Team Territories (ADDED)
Customers can review territory portfolios across projects instead of opening each project separately.
Map Areas (EXPANDED)
Users can draw and save supporting geographic context without treating every relevant shape as a territory.
Business Lists and Team Lists (MODERNIZED)
Navigation, search, sorting, logos, and project assignment controls have been improved.
Map Presentation Tools (MODERNIZED)
Thematic maps, heatmaps, labels, satellite views, clustering, rulers, and print tools have been modernized.
TERRITORY INTELLIGENCE AND SCORING
FRACT helped customers see and analyze territories. Wanderland makes the decision model configurable and easier to explain. The score belongs to the account and project strategy rather than to one universal view of what makes a market attractive.
Scoring Activation (EXPANDED)
Scoring can be activated at the account level and configured for individual projects.
Primary Ideal Customer Profile (EXPANDED)
Each project can select a primary Ideal Customer Profile and define target values.
Weighted Advanced Scoring (EXPANDED)
Scoring can combine ICP concentration, household income, distance or radius, drive time, competitors, and market amplifiers.
Factor Importance (EXPANDED)
Customers can adjust importance percentages so the model reflects the business and use case.
Score Recalculation (EXPANDED)
Territory scores are recalculated when the project scoring model changes.
Score Components (ADDED)
The interface displays the factors behind the overall score instead of presenting the result as an unexplained number.
Rankings and Comparisons (ADDED)
Territories can be ranked and compared across the portfolio.
Demographic Indicators (EXPANDED)
Territory views include totals, density, rates, and secondary ICP indicators.
Brand Profiles (ADDED)
Brand Profiles combine ICP targets, avoid signals, territory preferences, country focus, AI context, and default scoring settings.
Market Twins (ADDED)
High-performing territories can serve as benchmarks for identifying similar markets.
AUTOMATED TERRITORY CHECKS
Territory availability can now move beyond an internal map review. Wanderland Intelligence turns customer rules into a repeatable decision service that can be used by development teams, prospects, websites, and connected systems.
Availability Rules (ADDED)
Customers can configure the rules used to determine territory availability.
ZIP and Postal Checks (ADDED)
Availability checks can be initiated with a ZIP code or postal code.
Decision Outcomes (ADDED)
The system can return available, pending, unavailable, or not-found outcomes.
Assignment and Distance Review (ADDED)
Checks evaluate existing territory assignments and minimum-distance requirements.
Blocking Territory Identification (ADDED)
The result identifies the matching or nearest territory that blocks availability.
Alternative Recommendations (ADDED)
When a requested geography is unavailable, the workflow can recommend another geography to keep the conversation moving.
Public Territory Check Links (ADDED)
A customer can publish a territory-check experience without exposing the internal Wanderland Intelligence workspace.
Territory Check API (ADDED)
Customer systems and automated workflows can request an availability decision through the API.
Decision Integrity and History (ADDED)
Idempotency prevents duplicated automated decisions or charges, and stored history supports auditing and reporting.
SHARING AND COLLABORATION
Wanderland treats sharing as a governed product workflow. Customers decide what the recipient sees, how long access remains active, and whether the link should continue to work.
Public Sharing (EXPANDED)
Projects, territories, and Map Areas can be shared outside the internal workspace.
Share Packages (ADDED)
Focused, standard, and detailed territory-sharing packages support different audiences.
Information Controls (ADDED)
Customers can select the information included in a shared view.
Expiration (ADDED)
Share links can have expiration dates.
Central Link Management (ADDED)
Active shared links can be reviewed from one management area.
Access Changes (ADDED)
Sharing controls can be edited and access can be turned off.
Customer Availability Links (ADDED)
Territory availability links are separated from broader project and territory shares.
Team Collaboration (EXPANDED)
Teams can collaborate across territories and projects.
Decision History (EXPANDED)
Territory activity, comments, changes, and decision history create a more complete record.
Plan Controls (ADDED)
Project, territory, and Map Area sharing can be governed by plan-level limits.
REPORTING AND EXPORTS
The reporting layer now serves executives, territory teams, analysts, and downstream systems. Report Studi connects the portfolio view to formatted reports while expanded exports preserve the geospatial data needed outside Wanderland.
Report Studio (ADDED)
Report Studio is integrated into the dashboard and Team Territories.
Executive Portfolio Report (ADDED)
Executive Portfolio reports summarize the territory portfolio for leadership review.
Territory Benchmark and Ranking Report (ADDED)
Benchmark and ranking reports compare territories using the configured decision model.
Demographic Composition Report (ADDED)
Demographic Composition reports explain who and what sits inside the selected geography
Data Quality and Readiness Report (ADDED)
Data Quality and Readiness reports identify whether the information is sufficient for the intended analysis.
Territory Portfolio Report (ADDED)
Territory Portfolio reports provide a consolidated view of the territory set.
Geographic Detail Report (ADDED)
Geographic Detail reports document the component geographies and territory structure.
Report Output Formats (EXPANDED)
Reports can be generated in Excel, CSV, and PDF formats.
Territory Export Formats (EXPANDED)
Territories can be exported as CSV, Excel, PDF, GeoJSON, and Shapefile files.
Secure Downloads (STRENGTHENED)
Generated reports use secure, temporary download links instead of public files.
Temporary File Cleanup (STRENGTHENED)
Temporary report files are automatically removed after one day.
WANDERLAND AI
Wander places an AI decision workspace beside the map. Its value comes from project context and governed access to Wanderland data, not from a disconnected general-purpose chat window.
Embedded Decision Workspace (ADDED)
Wander is available alongside the map so the conversation remains connected to the work.
Project Aware Conversations (ADDED)
Wander automatically uses the user's active project as context.
Grounded Questions (ADDED)
Questions can use Wanderland territories, lists, stores, demographics, scores, and market data.
Project and Territory Summaries (ADDED)
Wander can summarize the active project and its territories.
Comparisons and Explanations (ADDED)
The assistant can compare territories, explain rankings, and identify market observations.
Source Labels (ADDED)
Responses clearly distinguish Wanderland data from fallback information.
Service Guardrails (STRENGTHENED)
When an upstream service is unavailable, the assistant reports the limitation instead of inventing a result.
AI Usage Accounting (ADDED)
AI activity is tracked through Decision Credits.
INTEGRATIONS
Wanderland replaces isolated integration work with a shared operating framework. Connections, mappings, events, jobs, retries, and health records can be managed consistently even when the external provider is different.
Shared Integration Framework (ADDED)
Connections, mappings, events, sync jobs, sync history, webhook subscriptions, and
delivery attempts use a common integration layer.
Salesforce (ADDED)
Salesforce support includes OAuth connection, configurable field mapping, connection
tests, and territory synchronization.
HubSpot (ADDED)
HubSpot support includes connection, field mapping, testing, retry handling, and
territory synchronization.
Zapier OAuth and Fields (ADDED)
Zapier uses scoped OAuth access with dynamic project, territory, and tag fields, polling
triggers, and territory actions.
Zapier Actions (ADDED)
Zapier actions can create activity, apply tags, update status, and initiate Salesforce
synchronization.
Outbound Webhooks (ADDED)
Customers can configure secure webhook destinations and subscribe them to selected
events.
Duplicate Prevention (STRENGTHENED)
Database-level controls prevent duplicate integration jobs and events.
Credential and Health Records (STRENGTHENED)
Provider credentials are encrypted, and connection health is maintained centrally.
Provider Retries (STRENGTHENED)
Supported providers use retry handling for rate limits and temporary outages.
Placer.ai (STAGED)
A Placer.ai connector for venue and location-intelligence workflows is in staged
evaluation.
FranConnect (STAGED)
A FranConnect connector for franchise company and unit data is in staged evaluation.
Data Axle (STAGED)
A Data Axle connector for business discovery and place records is in staged evaluation.
TomTom Road Exposure and Accessibility (STAGED)
TomTom Road Exposure and Accessibility is in staged evaluation.
TomTom Analysis (STAGED)
The staged TomTom work covers traffic volume, direction, peak periods, weekday and
weekend patterns, congestion, accessibility, travel-time reliability, and location
similarity.
Provider requirements (GOVERNED)
Newer provider integrations require the customer's corresponding provider account, API access, and final live-provider certification.
CUSTOMER API
The migration preserves compatibility for existing customers while making the API easier to govern and broader in scope. The objective is to let customers use Wanderland intelligence inside their own applications and operating processes.
Legacy Workflows (RETAINED)
Existing FRACT customer API workflows remain available for compatibility.
OpenAPI Documentation (MODERNIZED)
Updated OpenAPI documentation is published inside Wanderland.
Scoped Bearer Tokens (EXPANDED)
Scoped bearer tokens are available in addition to legacy credential-based
authentication.
Token Management (ADDED)
Customers can create, inventory, expire, track, and immediately revoke API tokens.
Core Resource APIs (EXPANDED)
APIs cover projects, territories, lists, list records, Brand Profiles, and demographic data.
Comparison and Analytics APIs (ADDED)
Territory comparison and project analytics are available through the customer API.
Spatial decision APIs (ADDED)
The API supports geography availability and exact spatial-overlap analysis.
Managed Geocoding (EXPANDED)
Addresses can be geocoded through Wanderland-managed providers.
Territory Lifecycle APIs (EXPANDED)
Customers can create territories and update lifecycle status by API.
ICP Ranking (ADDED)
Geographies can be ranked using the configured Ideal Customer Profile.
Authorization boundaries (STRENGTHENED)
Customer API access is constrained by account and project authorization.
DECISION CREDITS
Decision Credits connect usage to specific work. The ledger makes consumption visible to customers and administrators and supports both observation-only launches and enforced controls.
Credit Pools (ADDED)
Accounts can use configurable monthly, quarterly, or annual credit pools.
Balance Views (ADDED)
Wanderland distinguishes credits available in the current period from credits available
across the billing cycle.
Control Modes (ADDED)
Credit rules can run in audit-only mode or enforced mode.
Action Rules (ADDED)
Administrators can configure how many credits each action consumes.
Tracked Activities (ADDED)
Territory creation, sharing, AI actions, searches, territory checks, and monthly
maintenance can consume credits.
Credit Ledger (ADDED)
Every entry records the action and the balance after the transaction.
History and Adjustments (ADDED)
Monthly utilization history and manual adjustments are recorded.
Remaining Balance Alerts (ADDED)
Accounts can receive alerts at configurable remaining-credit thresholds.
Administrator previews (ADDED)
Administrators can preview whether an action will be allowed or blocked before enforcement.
ADMINISTRATION AND GOVERNANCE
Wanderland adds the operating controls required to manage customers, permissions, usage, deletion, and platform health. These controls make growth easier to govern without hiding consequential changes behind one-click actions.
Admin Control Panel (ADDED)
Wanderland includes a dedicated administrative control panel.
Platform Metrics Dashboard (ADDED)
The dashboard measures customers, users, projects, territories, lists, sharing, integrations, AI usage, and credits.
Trends and Drilldowns (ADDED)
Administrators can review month-over-month trends and drill into individual accounts.
Metrics Exports (ADDED)
Platform metrics can be exported as CSV or JSON.
People Management (MODERNIZED)
People are grouped by account in collapsible sections.
Role Change Controls (STRENGTHENED)
Explicit apply and discard actions reduce accidental role changes.
Privileged Access (EXPANDED)
Super Editor and Super Admin access can be managed directly.
Security Audit Log (ADDED)
Administrators have an interface for reviewing security-relevant activity.
Account Lifecycle (STRENGTHENED)
Account disablement is separated from the deliberate permanent-deletion workflow.
Deletion Safeguards (STRENGTHENED)
Deletion includes a preview, account-name and account-ID confirmation, database
cleanup, and stored-file deletion.
Public and Customer Resources (MODERNIZED)
Terms of Use, Privacy Policy, startup resources, import templates, and customr API documentation have been updated.
SECURITY AND RELIABILITY IMPROVEMENTS
Security work accompanied the visible product changes. The improvements focus on identity flows, outbound connections, provider failure, duplicate execution, controlled downloads, and release verification.
OAuth Validation (STRENGTHENED)
OAuth state validation is stricter, and authorization codes are handled as one-time
credentials.
Authentication Rate Limits (STRENGTHENED)
Integration authentication endpoints are rate limited.
Outbound Network Protection (STRENGTHENED)
Integrations and webhooks are blocked from reaching private or internal network
addresses.
Redirect Validation (STRENGTHENED)
Outbound integration requests validate redirects before following them.
CRM Payload Safety (STRENGTHENED)
Oversized CRM payloads are handled more safely.
Credential Status Detection (STRENGTHENED)
Connection records detect expired or invalid provider credentials.
Retry and Backoff (STRENGTHENED)
Temporary provider failures use retry and backoff handling.
Integration Idempotency (STRENGTHENED)
Database-level idempotency protects integration jobs and events from duplicate
processing.
Report Delivery (STRENGTHENED)
Reports use secure S3 downloads rather than public report files.
Deployment Smoke Tests (EXPANDED)
Release tests cover authentication, maps, territories, lists, reports, APIs, integrations,
credits, and administration.
WHY THE ARCHITECTURE MATTERS
The practical improvement is continuity across the decision. A project can define its Brand Profile and scoring model, rank territories, test whether a requested geography is available, identify a conflict, suggest an alternative, share the result, and preserve the activity. The same customer can expose that decision through an API or connect it to Salesforce, HubSpot, Zapier, or a secure webhook.
The platform also separates questions that should remain distinct. A territory score explains relative fit. An availability check applies assignment and distance rules. A spatial-overlap API answers a geometry question. A Decision Credit records usage. Keeping these concepts separate makes the result easier to explain and audit.
OpenAPI documentation and GeoJSON exports place the customer API and geospatial outputs within widely used interoperability standards.[6][7] Scoped tokens, account and project authorization, and immediate revocation give customers clearer control over automated access.
RESPONSIBLE AI INSIDE THE PRODUCT
Wander is designed to reason with the active project rather than speak as if every answer came from the customer's data. The source label tells the user when Wanderland data supports the response. The upstream-service guardrail reports that a dependency is unavailable instead of filling the gap with a fabricated result. This is essential in location work because an invented territory fact can affect capital, contracts, and customer commitments.
The NIST AI Risk Management Framework describes trustworthiness as a concern across the design, development, use, and evaluation of AI systems.[3] Wanderland's product direction reflects that operating principle through grounded project context, source labels, service failure handling, usage records, and the ability to inspect the factors behind a territory score.
Wander remains decision support. Customers remain responsible for validating current data, local conditions, legal requirements, development feasibility, and the commercial assumptions behind a location decision.
SECURITY AND RELIABILITY AS PRODUCT FEATURES
The integration layer creates value only when customers can trust how it connects to other systems. OAuth state validation, one-time authorization-code handling, scoped tokens, encrypted credentials, redirect validation, and connection-health records address that trust directly. RFC 9700 documents current best practice for OAuth 2.0 security and reflects the need to update older implementation patterns as threats and deployment environments change.[4]
Outbound webhooks and provider connectors require a second class of controls. Blocking access to private or internal network addresses reduces server-side request forgery risk, a threat covered in OWASP guidance.[5] Database-level idempotency protects against duplicate jobs and events when a provider retries or a network response is uncertain.
Generated reports use temporary secure downloads and one-day file cleanup. AWS documents presigned URLs as time-limited access to specific objects.[8] The deployment smoke-test suite then checks the product areas most likely to expose a broken release, including authentication, maps, territories, lists, reports, APIs, integrations, credits, and administration.
AUSTRALIA AND WORLDWIDE USE
Wanderland is designed for customers outside the United States. The platform therefore uses ZIP or postal code where appropriate, allows Brand Profiles to specify country focus, and separates the decision model from one country's default variables. A business-to-business brand can emphasize business presence, for example, while a consumer brand may place more importance on household or population signals.
For Australia, geography versioning matters. The Australian Bureau of Statistics began the progressive release of Australian Statistical Geography Standard Edition 4 in July 2026, while some collections continue to use Edition 3 during the transition.[1] Wanderland customers should know the geography, vintage, and purpose of each layer and should not treat a statistical or postal approximation as a legal territory boundary without the appropriate review.
Australian franchise decisions also operate within a mandatory Franchising Code of Conduct administered by the Australian Competition and Consumer Commission.[2] Wanderland can improve the evidence, consistency, and audit trail behind territory planning. It does not replace disclosure obligations, franchise agreements, legal advice, or local feasibility work.
The same principle applies worldwide. Core platform functions may be consistent across markets, while demographic coverage, postal geography, road data, business data, provider licensing, and regulatory requirements vary by country. Provider integrations require the corresponding customer account, API access, geographic coverage, and final certification before production reliance.
THE COMMERCIAL MEANING OF THE CHANGE
The product now supports more of the conversations that occur before and after a boundary is drawn. A franchise development team can check availability without opening the internal map. An executive can review a portfolio report. An analyst can export GeoJSON or Shapefile data. A customer system can call the API. A CRM can receive territory updates. A team can see why a territory ranked highly and what changed after the decision.
This matters because location work rarely fails from lack of a map. It fails when teams use different assumptions, cannot explain a result, lose the decision history, or move information between systems by hand. Wanderland's improvements target those operating gaps while preserving the territory mapping foundation that made FRACT useful.
FRACT evolved into Wanderland Intelligence because the customer need grew beyond drawing and analyzing territories. The enduring question is how an organization can know where to grow, explain why, act with confidence, and learn from the result. Wanderland is being built around that complete decision.
COMMON QUESTIONS
What happened to FRACT?
FRACT evolved into Wanderland Intelligence. The territory mapping foundation remains, while the product now connects mapping to configurable scoring, automated territory checks, sharing, reporting, AI, integrations, APIs, usage controls, and administration.
Does Wanderland retain FRACT territory mapping?
Yes. Wanderland retains and modernizes the map-centered workflows customers used in FRACT, including territory construction, thematic maps, heatmaps, labels, satellite views, lists, rulers, print tools, and customer API compatibility.
What is the biggest difference between FRACT and Wanderland?
FRACT concentrated on mapping and territory analysis. Wanderland connects those functions to a governed decision process. A customer can configure how markets are scored, test availability, explain a result, share it, automate it through an API, move it into another business system, and preserve the activity history.
Does Wanderland support franchise territory planning?
Yes. Wanderland supports territory creation, portfolio review, Ideal Customer Profile scoring, high-performing territory benchmarks, availability rules, minimum-distance checks, alternative geography recommendations, reporting, sharing, and connected workflows for franchise development.
Does Wanderland support Australia?
Wanderland supports Australian location decisions through country-aware brand profiles, postal-code terminology, and supported Australian geography and data workflows. Available datasets, geographic vintages, and provider integrations depend on licensing, coverage, and the customer's configuration.
Is Wander grounded in customer data?
Wander uses the active project and can ground responses in the customer's Wanderland territories, lists, stores, demographics, scores, and market data. It labels Wanderland sources and reports unavailable upstream services rather than inventing a result.
Are all listed integrations generally available?
No. Salesforce, HubSpot, Zapier, webhooks, and the shared integration framework are described separately from Placer.ai, FranConnect, Data Axle, and TomTom capabilities that remain in staged evaluation. New provider integrations also require the customer's provider account, API access, and final certification.
PRODUCT AVAILABILITY AND CLAIMS
This comparison reflects the Wanderland Intelligence product inventory and release status documented on September 30, 2026. Some capabilities are controlled by customer plan or configuration. Data availability varies by country and provider. Placer.ai, FranConnect, Data Axle, and TomTom integrations are identified as staged because live-provider access, customer credentials, coverage, and certification remain conditions of production use. Product capabilities may continue to change after publication.
ABOUT THE AUTHOR
Jonathan Weston is the founder and CEO of Wanderland Intelligence, a location decision intelligence company building the future of AI for the physical world. Across more than 20 years in sales, business development, partnerships, and enterprise technology, he has built markets, negotiated complex decisions, and helped organizations convert information into commercial action. At Salesforce, he founded an ISV Business Builder program and led partner growth initiatives; earlier work across FIS/CAPCO and Accenture included developing major new business pipelines and complex business cases. He also founded The Wanderland Society and developed a 72-acre outdoor sanctuary on Lookout Mountain, Georgia. His work is guided by simplicity, authenticity, gratitude, and inspiration.
REFERENCES
Accessed September 30, 2026. Product comparisons reflect Wanderland Intelligence release documentation as of the same date.
External references support the standards, governance, security, and Australian context discussed in this paper.
[1] Australian Bureau of Statistics. Australian Statistical Geography Standard Edition 4 July 2026 to June 2031.
[2] Australian Competition and Consumer Commission. Franchising Code of Conduct.
[3] National Institute of Standards and Technology. Artificial Intelligence Risk Management Framework.
[4] RFC Editor. RFC 9700 Best Current Practice for OAuth 2.0 Security. https://www.rfc-editor.org/info/rfc9700/
[5] OWASP Foundation. Server Side Request Forgery Prevention Cheat Sheet.
[6] OpenAPI Initiative. OpenAPI Specification. https://spec.openapis.org/oas/latest.html
[7] RFC Editor. RFC 7946 The GeoJSON Format. https://www.rfc-editor.org/info/rfc7946/
[8] Amazon Web Services. Download and Upload Objects with Presigned URLs.
ABOUT WANDERLAND INTELLIGENCE
Wanderland Intelligence builds decision intelligence for the physical world. Its work helps organizations understand where they are, what matters, and where to go next by combining geospatial evidence, adaptive scoring, and explainable AI. Wanderland's signature TIE framework is being developed as a common decision language for opportunity, fit, risk, health, and action. Learn more at wanderland.earth.
Comments