MarchAi / Bazaar

Turn work that needs judgment into a product.

Bazaar turns support, taste, partner access, operations, and mission work into products with the right interface, the right people, and one path to the final result.

Customer flow Team workspace Partner portal Final action with receipts

Book demo View the Bazaar deck

Build Define the workflow in Studio

Open Launch the right surface for each side

Finish Keep state and action on one governed path

Bazaar product scene

How Bazaar works

One workflow. All the parts a real product needs.

Teams define the job in Studio, open the right surface for each side of the workflow, and keep the live state and final action together instead of scattering them across separate systems.

Define the job in Studio Builder, cases, installs, and Forge turn a workflow into a real system instead of a loose prompt and a few tools.

Open the right product surface The same workflow can open as a customer frontdoor, a live team workspace, or a bounded partner surface.

Keep the workflow together Shared workspaces, approvals, grants, and one governed action path keep the live job from breaking across separate systems.

What it does

Most important work still mixes judgment and action.

Someone asks for something. Someone else reviews it. A partner needs one slice. An approval happens somewhere else. The final action disappears into a back-office system.

Bazaar keeps that workflow together. The request, the people, the approvals, the live state, and the final action stay in one product from beginning to end.

How it works

Different people should get different versions of the same product.

A customer needs a simple entry. A team needs live state and approvals. A partner needs a bounded portal. A field operator may need a QR flow. Bazaar opens the right version of the same workflow for each side of the job.

Define the workflow

Start in Studio, describe the job in plain language, and capture the systems, people, and judgments the workflow depends on.

Package the judgment

Turn rules, approvals, evidence, and taste into a usable product shape instead of leaving them scattered across tools.

Open the right surface

Launch a frontdoor, workspace, partner view, field entry, or generated console around the same workflow.

Finish with proof

Keep the final action, the receipt, and the workflow history on one governed path.

Autodune

Autodune helps Bazaar find the better version of the product.

It can try different product shapes, compare how people actually use them, and keep improving the workflow after launch.

Choose the product shape

Decide whether the workflow needs a customer flow, a team workspace, a partner portal, a QR flow, or a channel runtime.

Test the whole path

Check the workflow from request to final action: routing, approvals, access boundaries, and completion.

Improve after launch

Watch real usage, compare better variants, and keep improving the product after people start using it.

Examples

Pick a workflow where judgment matters. Bazaar turns it into a product.

That can be personal taste, customer support, partner access, fundraising, field work, or mission operations. Bazaar opens the product. Autodune keeps improving it.

Product scenes

Customer support that can actually finish the job

A customer starts in WhatsApp or the web. Bazaar opens the right room for the team, keeps approvals in context, and runs the final action through one governed path.

01/12

Customer support

From customer message to completed case

A customer should not have to trigger chat, tickets, approvals, and back-office tools separately. Bazaar turns the whole support loop into one product.

Starts withA customer asks for a refund, change, or exception in WhatsApp or the web.

Bazaar opensA customer entry, a live workspace for the team, and one governed action path.

Autodune canCompare support-flow variants, test exception paths, and keep the clearer or faster version.

ResultThe case gets resolved without bouncing between separate queues, forms, and approvals.

Customer sees one simple entry.
Team sees state, approvals, and action in one runtime.
Receipts and final outcome stay visible.

Consumer · user to user

Turn personal taste into something other people can actually use

Most recommendation threads disappear the moment the conversation ends. Bazaar can turn someone's taste into a passport with bounded capsules for coffee, gifts, restaurants, or travel, so the judgment becomes reusable without exposing the person's private context.

Starts withA person has real judgment about what is good, but no clean way to share it without repeating themselves.

Bazaar opensA taste passport plus optional capsules for coffee, gifts, restaurants, trips, or any other slice of that judgment.

Autodune canTest web vs WhatsApp entry, decide what belongs in public taste versus private memory, and keep the version people actually reuse.

ResultTaste becomes a real product: reusable, bounded, and still personal.

Recommendations still feel personal without becoming manual labor.
Different capsules can be shared with different friends or audiences.
The same person can return later and keep using the same taste product.

Consumer · group planning

Keep taste, tradeoffs, and coordination in one shared trip product

Trip planning usually falls apart because the real work is not just logistics. It is taste, budget, timing, and group preference. Bazaar can hold that judgment in one trip product instead of scattering it across chats, maps, and spreadsheets.

Starts withOne person wants to plan with friends without losing the plan every time the conversation moves.

Bazaar opensA trip product with itinerary, options, votes, budgets, and one running version of the plan.

Autodune canCompare planning shapes, simplify how preferences are collected, and improve the flow after seeing where groups stall or split.

ResultThe group's judgment becomes cumulative instead of resetting in every new thread.

Each member gets the right amount of detail for their role in the trip.
Votes, tradeoffs, and changes stay attached to the itinerary.
A good trip can become a reusable product for the next trip, not just a memory of one.

Consumer to org

Turn creator taste into a product for followers and a business surface for brands

Creators usually split taste, audience interaction, and partner work across too many tools. Bazaar can open one creator passport for followers while giving brands a bounded surface around the same underlying product.

Starts withA creator has real taste and audience signal, but no good way to package it for both fans and brands.

Bazaar opensA creator passport, follower entry flow, and brand-facing access surface with bounded rights and reusable capsules.

Autodune canTest better follower journeys, improve brand review flows, and identify which taste or audience slices should become reusable capsules.

ResultThe creator runs one taste-led product instead of a patchwork of links, DMs, and partner docs.

Followers get a cleaner product experience around the creator's taste.
Brands see only the audience and partnership slice they are allowed to review.
The creator keeps one governed operating surface behind both sides.

Partner portal

Give the partner the exact slice they need

Most partner workflows break because the options are too crude: email, PDF, or too much portal access. Bazaar opens a bounded partner product instead.

Starts withA supplier, investor, customer, or outside operator needs updates, evidence, or a live handoff.

Bazaar opensA partner frontdoor backed by grants, bounded state, and revocable access.

Autodune canSee what partners repeatedly ask for and package a cleaner partner view or capsule set.

ResultThe partner sees enough to do the work, but never the whole internal system.

Bounded access instead of broad logins.
Live workflow state instead of stale exports.
Revocation and receipts built in.

Fundraising

Turn fundraising into a product, not a sequence of handoffs

A startup can open a founder-facing surface, investor access flow, and selective diligence path without forcing everyone into email threads and static folders.

Starts withA founder wants investors to understand the company quickly without exposing everything at once.

Bazaar opensA public story, a bounded investor view, and grants around the deeper workflow.

Autodune canTest different access paths, improve investor clarity, and suggest better product shapes over time.

ResultFounders control the surface and investors get a clearer, faster path through the workflow.

Public story and deeper access can stay separate.
Investor access can be granted and revoked cleanly.
The workflow keeps state and receipts instead of becoming a loose diligence thread.

Vendor qualification

One vendor workflow instead of ten separate review steps

Qualification is usually a maze of requests, artifacts, reviews, and signoff. Bazaar keeps the evidence, reviewers, and final approval in one place.

Starts withA buyer needs proofs, certifications, sample data, or readiness evidence from a supplier.

Bazaar opensA bounded qualification product with requests, uploads, reviews, and signoff.

Autodune canSee where the process stalls and publish a clearer or faster qualification flow.

ResultThe organization gets a reusable qualification product instead of repeating the same review loop by hand.

Evidence stays attached to the decision.
Outside parties get bounded access.
The final qualification state is explicit and reusable.

Internal ops

Generate the team console around the job

Many internal workflows need the same pieces: queue, room state, approvals, assignments, metrics, and a final action path. Bazaar can generate that runtime around the workflow instead of making the team adapt to a generic dashboard.

Starts withA team has a repeatable internal job that still lives in multiple tools and handoffs.

Bazaar opensA generated console with workflow state, approvals, and the governed action path already wired in.

Autodune canTest different console shapes, panels, and sequence designs until the work resolves more cleanly.

ResultThe team gets a product that fits the workflow instead of a dashboard they have to work around.

Generated console instead of manual admin-tool wiring.
Rooms, grants, and approvals stay in the same runtime.
Better internal throughput and visibility.

Field service

Open a simple field surface without losing the system behind it

Field work usually starts with a simple need: scan, ask, upload, or confirm. Bazaar can make that entry simple while keeping the governed workflow behind it intact.

Starts withA technician, operator, or site partner scans a QR or opens a lightweight runtime.

Bazaar opensA field entry surface tied to the same room, approvals, and execution path the team sees internally.

Autodune canImprove the field flow, simplify the steps, and compare clearer handoff designs over time.

ResultThe field workflow stays simple at the edge without breaking the governed core of the product.

Simple QR or deep-link entry.
Field updates stay in the main workflow.
No separate edge tool for the same job.

Space operations

Ground time and mission operations without the document maze

In space operations, the workflow often spans requests, proofs, approvals, counterparties, and a final reservation or commitment. Bazaar turns that into one product instead of a pile of documents and meetings.

Starts withA team requests ground time, downlink capacity, or a mission-side operational slot.

Bazaar opensA workflow with proofs, constraints, approvals, and a commit path tied to the same request.

Autodune canCompare operational flows, identify bottlenecks, and suggest better reservation or evidence packages.

ResultThe reservation is committed and tracked in one product instead of being reconstructed across documents and calls.

Proofs and constraints stay attached to the request.
Approvals stay in the same runtime as the operation.
The commit path is visible and auditable.

Robotics rollout

Go-live, acceptance, and release in one shared product

Robotics deployments involve operators, integrators, evidence, milestone signoff, and release conditions. Bazaar turns that into one visible system instead of a stitched rollout spreadsheet.

Starts withA deployment needs commissioning checks, acceptance criteria, and a final go-live release.

Bazaar opensA shared workflow with milestones, proofs, approvals, and release controls.

Autodune canCompare rollout shapes, identify bottlenecks, and improve the go-live path across repeated deployments.

ResultEveryone can see what is complete, what is blocked, and when the final release can happen.

Shared rollout state for operators and vendors.
Proofs and approvals tied to release.
A reusable deployment product instead of a bespoke go-live ritual.

Drone missions

Mission clearance without losing the evidence trail

When a drone mission needs timing, route, corridor, counterparties, and compliance checks, the workflow gets messy fast. Bazaar keeps the request, clearance, approvals, and final mission package connected.

Starts withAn operator requests a mission corridor, route approval, or airspace clearance.

Bazaar opensA coordination flow with proofs, counterparties, approvals, and a final mission package.

Autodune canCompare safer or faster clearance flows and keep the one that works better in the real mission process.

ResultThe team moves from request to approved mission without losing the operational record.

Clearance, proofs, and final mission package stay together.
Counterparties can be part of the same governed flow.
The workflow can improve over repeated missions.

More workflows

Bazaar is broader than one team, one portal, or one vertical.

If the job has people, live state, permissions, approvals, and a final action that must finish cleanly, Bazaar can usually turn it into one product and Autodune can keep improving it.

Gift guides

Turn personal judgment about what fits different people into a reusable product instead of rewriting recommendations by hand.

Autodune can separate public taste from private context and keep the version people return to.

Membership and concierge

Package high-touch judgment, recommendations, and service into one member product instead of hiding it behind email and ops rituals.

Autodune can improve the member path as repeat requests reveal where the product should feel more personal or more direct.

Quote and approval flows

Turn pricing, holds, and final commitment into one product instead of splitting them across sales, ops, and finance systems.

Autodune can compare faster or cleaner approval layouts and keep the better path.

Claims and exceptions

Open one customer flow, one team runtime, and one governed exception path instead of scattering the work across systems.

Autodune can test clearer exception paths and keep the one that resolves better.

Hiring loops

Give candidates a clean frontdoor while recruiters and hiring managers work from the same live workflow.

Autodune can improve the candidate journey and recruiter flow over time.

Portfolio updates

Turn founder updates, investor follow-up, and partner visibility into one live product instead of a reporting ritual.

Autodune can improve the investor path as questions repeat.

Retail and product passports

Package product information, service rights, and downstream access into a usable product instead of a static page.

Autodune can refine what each audience should see, ask, or import.

Cross-company programs

Use rooms, grants, contracts, and governed action to run shared workflows across organizations without exposing the whole internal stack.

Autodune can identify what should become reusable templates across repeated programs.

Why teams trust it

The product stays connected to the real work.

Bazaar is useful because the runtime stays connected to the actual workflow: the live state, the people involved, the approvals, the final action, and the judgment that tells the system what matters next.

Taste does not have to stay trapped in one person's head. Bazaar can package it into passports and capsules, share it selectively, and let Autodune keep improving the product after people start using it.

Studio and Forge

Teams can define the workflow and assemble the product without wiring every surface by hand.

Shared state

Live workflow state stays visible instead of disappearing into separate tools and threads.

Approvals and access

Access and decisions are part of the product, not an external workaround.

Generated runtimes

The same workflow can open as the right product for customers, teams, partners, or field operators.

Final action

The workflow still runs through one governed path with visible outcomes and receipts.

Autodune

It can compare shapes, test outcomes, and keep the version that works better in the real workflow.

See Bazaar on your workflow

Bring one workflow that still depends on judgment. We’ll show you the product it should become.

Support, partner access, internal operations, field work, consumer taste, or a cross-company program — the fastest way to understand Bazaar is to map one workflow you already run today.

Book demo View the Bazaar deck