Client-owned AI systems for e-commerce

Your AI agents and tools in one custom dashboard.

We build the dashboard, connect your tools and create agents for the work you want to hand over. It runs in your accounts, with support after launch.

How your workspace connectsIllustrative
Your businessOne shared workspace.Context · work · decisions

Explore a connection. Your build follows your scope.

How the build works

We handle the build, from first workflow to handover.

  1. Find the work worth handing over

    We review your daily tasks, tools and existing AI. Together, we choose what to improve and what to keep.

  2. Agree the build and price

    Your proposal names the workflows, stores, connections, inputs, approval rules and acceptance checks. We assess unfamiliar requirements before committing to a fixed scope.

  3. Get ready to build

    You provide access, business knowledge and a lead who can make decisions. Work starts once the agreement, cleared deposit and essential inputs are in place.

  4. Build and test the workflows

    We connect your tools and build the agreed dashboard and agents. Tests cover everyday tasks, permissions and what happens when something goes wrong.

  5. Review and accept delivery

    We check the agreed work with you and complete handover. The final build payment is due at completed and accepted delivery.

  6. Support the system after launch

    Fourteen calendar days of included stabilization begin the day after completion confirmation. After that, you can choose optional ongoing management or manage the system yourself.

Your business knowledge

Give your agents the knowledge to do the job.

Your policies, product information and brand direction shape how the agents work. We connect the sources they need, with access limited to their role.

Inside the knowledge networkSix connected areas

Loading the network…

Drag to explore · scroll to zoom · right-drag to pan.Drag to explore · pinch to zoom · two fingers to pan. Select a node to look closer.

Illustrative demo
Browse example knowledge30
  • Product & creative inputs

  • Product & creative inputs

  • Product & creative inputs

  • Product & creative inputs

  • Product & creative inputs

  • Support & policies

  • Support & policies

  • Support & policies

  • Support & policies

  • Support & policies

  • Email & lifecycle rules

  • Email & lifecycle rules

  • Email & lifecycle rules

  • Email & lifecycle rules

  • Email & lifecycle rules

  • Business & marketing data

  • Business & marketing data

  • Business & marketing data

  • Business & marketing data

  • Business & marketing data

  • Approvals & boundaries

  • Approvals & boundaries

  • Approvals & boundaries

  • Approvals & boundaries

  • Approvals & boundaries

  • Shared business context

  • Shared business context

  • Shared business context

  • Shared business context

  • Shared business context

Illustrative roles and sample context for e-commerce workflows. No actions run here. Roles and permissions are scoped for your business.

What do you need from our team?

One lead to provide access, answer questions and make decisions. Depending on the workflow, we also need policies, product imagery, brand assets, campaign instructions or cost definitions. We agree the schedule around your scope, access and feedback. WhatsApp is the standard day-to-day channel; scope decisions and acceptance also go in the project record.

How do we give feedback during the build?

Show the screen or task, what you expected and what happened instead. A specific example or screenshot helps us check the issue. We agree practical feedback windows with you before the build.

Ownership and control

You own the system and set the rules.

Your delivered code, accounts and data remain under your control, subject to vendor licenses and your agreement. Handover includes source and access details, configuration, supported workflows and operating or recovery instructions.

You decide what agents can access, which actions they can take and when your team steps in. Reading an order and issuing a refund have separate permissions.

Read about ownership and permissions
A support request, from inbox to outcomeIllustrative

An address change, connected.

  1. 01
    Customer request

    “Can you update my delivery address?”

  2. 02
    Order + policy

    Check the order and fulfilment status.

  3. 03
    Eligible next step

    Apply the agreed approval rules.

  4. 04
    Recorded outcome

    Update the address and the conversation.

Example only. Access and actions are agreed for your store.

Your custom AI team

Give each agent a clear job.

We create agents around the roles and processes in your business. They work together through your dashboard, using the company knowledge and tools their tasks need.

Inside the AI team31 example roles

Loading the office…

Drag to explore · scroll to zoom · right-drag to pan.Drag to explore · pinch to zoom · two fingers to pan. Select an agent to look closer.

Illustrative demo
Browse the example roles31
  • Connects specialists around the selected workflow and brings decisions back to your team.

  • Organizes approved product assets and reference ads for a brief.

  • Proposes static-ad concepts from the supplied product and brand direction.

  • Prepares accompanying copy using approved product facts and claims.

  • Prepares static variations in the formats agreed for the workflow.

  • Flags product, format and brand issues against agreed review criteria.

  • Classifies requests and routes exceptions to the right owner.

  • Uses approved knowledge to prepare a useful response.

  • Brings order and delivery context into a customer request.

  • Prepares a policy-based resolution and flags exceptions.

  • Finds recurring themes across customer conversations.

  • Organizes the campaign instructions, offer facts and required assets.

  • Prepares campaign copy using the supplied brand and product direction.

  • Places approved content into the email templates selected for the workflow.

  • Maps a selected lifecycle use case to agreed triggers, timing and exclusions.

  • Flags missing links, product details or required exclusions before review.

  • Organizes the agreed store data using the selected dates and definitions.

  • Compares agreed platform and campaign measures within their attribution limits.

  • Flags missing cost inputs against the agreed profitability definitions.

  • Checks supported product mappings and identifies unmatched records.

  • Brings agreed business and marketing measures into a consistent report.

  • Flags proposed replies or order actions that need the designated human.

  • Collects selected assets, copy and unresolved feedback for the approver.

  • Checks the configured approval requirement before an email action proceeds.

  • Brings unsupported requests and missing inputs to the responsible person.

  • Checks proposed actions against the boundaries configured for the workflow.

  • Organizes approved reference material and flags gaps.

  • Prepares document updates when confirmed context changes.

  • Organizes approved product facts and flags conflicting claims.

  • Retrieves relevant information with its source context.

  • Surfaces recurring exceptions and suggests improvements.

Illustrative roles and sample context for e-commerce workflows. No actions run here. Roles and permissions are scoped for your business.

Project and service terms

Agree the full cost before we build.

After our call, your custom proposal sets out a fixed build fee, any optional management fee and applicable taxes and vendor costs. One store is the baseline; additional stores are scoped separately, with shared foundations counted once.

Build
50% upfront and 50% at completed and accepted delivery
Stabilization
14 consecutive calendar days included, beginning the day after completion confirmation
Ongoing management
Optional support, system reviews and agreed refinements, quoted separately
Service billing
If chosen, paid in full monthly in advance, on the service-start anniversary
Service renewal
Monthly renewal until cancelled with at least 14 calendar days’ notice before the applicable renewal
Other costs
Applicable taxes and direct vendor subscriptions or usage, as stated in the proposal

Ongoing management is optional. Choose support and improvement for your installed system, or take over its management after handover.

Existing client agreements retain their own accepted terms.

After delivery

Keep your system working and improving.

With optional ongoing management, you get responsive support, regular reviews and agreed improvements to your installed workflows. We review the system even when you send no requests.

Fix issues

Diagnose problems and maintain the workflows and connections covered by your agreement.

Review the system

Check how it is working, flag useful changes and send you a concise update. A review may find no changes are needed.

Improve existing workflows

Refine the setup and apply relevant upgrades after checking compatibility and permissions.

Standard support is Monday–Friday, 09:00–18:00 Europe/Amsterdam. Out-of-hours help is discretionary. Response and resolution depend on the issue and the agreed service responsibilities.

What needs a separate quote?

New workflows, modules, integrations, major redesigns and material additional-store work. Ongoing service covers the agreed installed system; unlimited development, a monthly output quota and ongoing campaign management are not included.

Your options after delivery

Keep the system when you stop the service.

If you choose ongoing management, it renews monthly. Give at least 14 calendar days’ notice before renewal to end it. The delivered system stays in your accounts; you take over maintenance and vendor costs.

When does cancellation take effect?

Notice received at least 14 calendar days before an eligible renewal prevents that renewal. Later notice takes effect at the next eligible renewal boundary.

Can we add another solution later?

Yes. We assess the new workflow, reuse suitable foundations and quote the incremental scope. Adding a new module is not automatically an included refinement.

What does included stabilization cover?

Defects or failures against the agreed scope and agreed completion items. Qualifying issues reported during that period remain included until resolved. New workflows are scope changes, not stabilization fixes.

What work would you hand over first?

Tell us what keeps repeating and which tools you use. We’ll discuss what your AI system could take off your team’s plate.