Nullstar CommerceDiscuss a pilot

A useful first step.
Built around your store.

One catalogue. One buying journey. A focused pilot to find out what works.

Talk to sales

Scope and any charges are agreed before work begins.

One store model supports three possible pilot scopes: readiness, Nullstar Match and Agent CommercePOSSIBLE PILOT SCOPESOne store. A focused test.Your store modelProduct facts · Merchant rules · Customer permissionReadinessUnderstand the gaps.Nullstar MatchTest one campaign journey.Agent CommerceDefine one authorized task.
Your store is the starting point.Its information. Its customers. Its rules.

Choose the question.
Then define the work.

Three proposed starting points, built around the same store model. Explore a scope before we talk.

What would you like to explore?

Proposed pilot scope

  1. Review public evidence
  2. Prioritize the gaps
  3. Agree the next step

Can agents understand your store?

Start with the evidence your public storefront makes available. Find the missing, inconsistent or inaccessible facts before choosing an integration.

What we would define together

  • An evidence review with sources and limitations
  • Prioritized product-data and access gaps
  • A proposed next step and validation method

Bring to the conversationA public store URL and a person who understands the catalogue.

Discuss this scope Explore readiness

Proposed pilot scope

  1. Define the hypothesis
  2. Review the variations
  3. Set a clear baseline

Does the page match the reason they clicked?

Choose one campaign and product group. Define merchant-approved emphasis and a controlled way to compare the buying journey.

What we would define together

  • A defined campaign-to-product hypothesis
  • Merchant-reviewed page variations
  • A baseline and documented testing conditions

Bring to the conversationA focused campaign, measurable traffic and approved product information.

Discuss this scope Explore Nullstar Match

Proposed pilot scope

  1. Define the allowed task
  2. Confirm authorization
  3. Validate the behavior

Can an agent complete one permitted task?

Select one storefront, agent interface and allowed task. Define the product facts, customer review and failure behavior before implementation.

What we would define together

  • A scoped store model and supported actions
  • An explicit customer-authorization boundary
  • A documented integration and validation plan

Bring to the conversationA store owner who can discuss catalogue access, platform limits and permitted actions.

Discuss this scope Explore Agent Commerce

Clear scope.
Clear expectations.

Pricing depends on the agreed scope. The first conversation establishes the work, the evidence and the commercial terms.

Talk to sales
Your store
Catalogue, variants, languages and available product facts.
The test
One campaign, product group or supported agent task. A baseline and acceptance criteria.
Access and ownership
Permitted data, platform constraints and each party’s responsibilities.
Timing and terms
Deliverables, timing and any implementation or recurring charges, confirmed in writing.

Before we talk scope.

Start with one store URL and the question you want to test.

Talk to sales
Why is pricing scoped with sales?

The right scope depends on the store, the state of its data, the journey being tested and the integration work. We define those together before discussing commercial terms.

Do I need to commit to the full platform?

Start with one store and one buying problem. A pilot can be scoped around readiness, a Match journey or one agent use case.

Are there setup fees or subscriptions?

Your written scope identifies any implementation fees, recurring charges and agreed services before work starts.