Nullstar CommerceDiscuss a pilot

Your store.
The next buying journey.

Bring one real commerce problem. Let’s define a useful way to test it.

Describe your store
A pilot starts with your store, one question and an agreed scopeA FOCUSED PILOTStart with one real question.Your storeCatalogue & platformCurrent buying journeyThe problem to exploreAgreed scopeOne limited testPermitted accessEvidence & next stepsA conversation comes before implementation.
A focused question, grounded in your catalogue.Product facts · Merchant control · Customer permission

First, a conversation.

We discuss the store, the buying journey and the evidence you need. A pilot only starts once its scope, access and terms are agreed.

Explore the possible scopes

Tell us about your store.

Send your inquiry to bonclay@nullstarlabs.com. We’ll use the details to reply and discuss a possible pilot.

Email us about your store.

Include your store URL, platform and the problem you want to explore.

Email about a pilot

Three ways to explore
a better buying journey.

Agent-readiness pilot

Find the gaps in your store facts and access.

Storefront evidence, prioritized gaps and the limits of each finding.

Nullstar Match pilot

Test one campaign-to-product journey.

One campaign, approved page variations and a clear testing baseline.

Agent Commerce design partner

Define one supported, authorized agent journey.

One supported task, customer authorization and documented failure handling.

A real store.
A narrow question.

Useful pilots begin with an active catalogue, someone who understands the storefront and a willingness to review evidence.

For any pilot
A working ecommerce store, a real product catalogue and a person who can help define scope and access.
For Nullstar Match
Measurable acquisition traffic and a focused campaign or product group to test.
For Agent Commerce
A conversation about catalogue structure, platform constraints, permitted actions and what happens when a flow fails.

After your email.

  1. ReviewWe review the store and use case for a plausible fit.
  2. DiscussA qualification conversation clarifies the problem and access.
  3. DefineWe set one limited scope and evidence for success.
  4. AgreeAccess, responsibilities, timing and commercial terms are confirmed before work starts.

Sending an inquiry does not guarantee pilot acceptance.

Before we talk.

Scope and availability come first.

Is the pilot free?

Scope, access, responsibilities and any commercial terms are discussed before work starts. No standard price or free-pilot promise has been established.

How do I request a readiness assessment?

Send your store URL and the question you want to explore. We agree on the assessment scope and explain which findings can be established from public information and which require additional access.

Do you need customer or payment data?

Start with public store information and the use case. Any later access must be justified, limited and agreed separately. Do not send customer records, passwords or payment information in your request.

Can an agent buy without permission?

No. The intended purchase journey requires customer review, explicit authorization, a compatible flow and a verifiable result.

Which platforms do you support?

Tell us which platform you use. Compatibility depends on the proposed flow, available storefront information and permitted integrations; it must be checked for the specific pilot.

What evidence would we receive?

That depends on the agreed pilot: observed storefront evidence and priorities, a comparison of approved page variations, or a documented test of one agent flow. Acceptance criteria are defined before implementation.