Mesos Lab / Investor overview
Commerce is the starting point. A connected economy is the ambition.
Mesos is building a merchant operating platform that connects business software and financial services—then extends that foundation into agent-led transactions and capital workflows.
Commerce
Merchant operating platform. The initial focus.
Agent
Agent-led demand. In development.
Capital
Capital workflows. Planned.
02 — The initial problem
One merchant. Too many disconnected systems.
Take a café that also takes bookings and online orders. Sales, stock, reservations, payments, settlement and reporting often live with different tools and providers. The work happens in the gaps between them.
Illustrative example. Setups vary by merchant; not every business faces every gap.
Where manual work appears
- Re-entering operational information
- Matching payments to sales
- Understanding settlement differences
- Connecting financial services to business activity
The institution side
Banks and payment providers can offer more useful merchant experiences when their financial services connect to the merchant's daily operations — rather than sitting beside them.
03 — The first product
Start with the merchant workspace.
01
Daily operations
Sales, inventory, orders and supported business workflows in one workspace.
02
Connected financial services
Supported payment and provider connections alongside the activity they relate to.
03
Structured business context
Records and permitted actions that later products can use — with permission.
What the demo shows — and doesn't
The Commerce demo is an interactive front-end with sample data. It shows the intended workflow; it is not evidence of production integrations, live merchants or processed payments.
VC-1048 · Walk-in
10:42 · In-store · Oat flat white × 1, Mushroom toast × 1
40,500 ₮
Paid
VC-1047 · Enkhjin B.
10:36 · Online · Salmon bagel × 1, Matcha tonic × 1
52,000 ₮
Preparing
VC-1046 · Munkh T.
10:21 · In-store · Long black × 1, Almond croissant × 2
33,500 ₮
Ready
VC-1045 · Walk-in
10:08 · In-store · Yuzu soda × 1, Oat flat white × 1
27,000 ₮
Paid
04 — Distribution
Build distribution through existing relationships.
Mesos intends to reach merchants through the institutions that already serve them.
Why each side participates
Stages are not the same thing
A partner's merchant base is potential reach, not adoption. Mesos counts merchants only once they are activated and using the product.
05 — Progress and evidence
Progress that can be examined.
Each claim carries its status. Where something has not happened yet, we say so rather than fill the space.
| Category | What | Status | What it means |
|---|---|---|---|
| Product evidence | Interactive Commerce demo | Demonstrated | Front-end workflow across sales, orders, inventory, customers, online store, banking and reports, using sample data. Open to inspect. |
| Product evidence | Agent, Capital and Mesos Fabric product definitions | Designed | Product pages describe the intended workflows. Illustrative walkthroughs — not working products. |
| Signed commercial progress | — | Not yet reported | Signed agreements will be listed here with status and date once they can be confirmed. |
| Technical integrations | — | Not yet reported | No production integrations are claimed on this page. |
| Pilots | — | Not yet reported | Pilot scope, partner and dates will appear here once agreed. |
| Live usage & revenue | — | Not yet reported | Active merchants, usage and revenue will be shown only when verified. |
As of September 2026.
06 — Expansion
One foundation. A deliberate expansion sequence.
Connect merchant workflows, services and relevant transaction records.
Reused across products
- Identity
- Permissions
- Service connections
- Workflow coordination
- Relevant records
Still built separately for each
- Product-specific rules
- Integrations
- Partnerships
- Customer acquisition
- Operating arrangements
07 — Business model
Recurring software revenue. Additional transaction opportunities.
All pricing and revenue streams below are proposed. Not every fee applies to every transaction, and no pricing has been confirmed.
| Product | Potential payers | Value purchased | Proposed revenue |
|---|---|---|---|
| CommerceIntended first revenue | Merchants and/or distribution partners | Merchant software and connected operating services | Subscriptions, institutional licensing, agreed service fees |
| Agent | Distribution partners and/or service providers | Embedded service access and completed workflows | Usage fees; eligible transaction, referral or commission arrangements |
| Capital | Issuers, institutions or relevant participants | Workflow software, administration and servicing | Platform and service fees, subject to the operating model |
08 — Defensibility
Build advantages through use, integration and distribution.
Integration depth
Handling operational exceptions across providers, not only the happy path.
Merchant adoption
Becoming part of daily workflows, which is harder to replace than a single tool.
Embedded distribution
Being part of partners' merchant propositions.
Structured service access for agents
Permissioned, machine-readable merchant services.
Reusable infrastructure
One foundation shared across Commerce, Agent and Capital.
Network-effect hypothesis
- Useful merchant software
- More merchants and supported services
- More opportunities for agent-led demand
- More value for merchants and partners
…which makes the software more useful again.
A hypothesis until evidence demonstrates it. Customer information is used only as permitted — more records do not mean unrestricted rights to use them.
09 — Market and initial focus
Start with a defined market. Expand through repeatable distribution.
These are three different opportunities, and they are not added together. Numerical sizing will be published once it can be built bottom-up from sourced inputs.
Entry market
Merchants reachable through initial bank and payment partners, starting with businesses that run daily sales, stock and payments together.
Adjacent expansion
Further partners, merchant segments and connected services — including agent-led demand once Commerce use is established.
Longer-term vision
Capital workflows and a wider network of merchants, institutions and service providers on one foundation.
Sizing method: addressable merchants × expected adoption × annual revenue per customer
10 — Execution
Each phase earns the next.
Milestones are gates, not dates: each one opens only when the previous one is proven.
- 01In progress
Validate Commerce
Demonstrate the core merchant workflow and confirm initial partner requirements.
- 02Next gate
Activate distribution
Complete agreed integrations and onboard initial participating merchants.
- 03Gate
Prove repeat use and economics
Measure activation, retention, paid usage, support burden and transaction economics.
- 04Gate
Expand selectively
Introduce Agent and Capital when product readiness and partner arrangements support them.
Metrics investors should see as we progress
Not yet achieved. These will be reported as they become measurable.
Next step
Help build the next layer of connected commerce.
Explore the product and the thinking behind Mesos Lab.