Stop selling hours. Start shipping products.

Clients want fast, working software they own. Open Mercato enables fixed-price projects on a reusable foundation with sensible margins.

the math

Same client project. Completely different economics.

A typical CRM/portal project for a mid-market client. Here's what changes when you stop building from scratch.

Auth, RBAC, multi-tenancy
CRM core + entities
Design system + UI
Search, events, caching
Client-specific features
Testing & security audit
Total devliery

Without Mercato

3 weeks
4 weeks
2 weeks
2 weeks
4 weeks
2 weeks
17 weeks

With Mercato

Included
Included
Included
Included
3 weeks
1 week
4 weeks

3× the margin.

Same scope. Same price to the client. 
4 weeks instead of 17.
Your workflow

Clone → Overlay →
→ Ship → Repeat.

01

Clone the base

Fork Open Mercato for the new client. Auth, CRM, design system — running in 5 minutes.

Day 1
02

Overlay their workflow

Your team (or AI agents) drops files in src/apps/. Core never modified. Clean separation.

Week 1–3
03

Ship & handoff

Client gets a fully-owned codebase on their infra. No vendor lock-in. No recurring platform fees.

Week 4
04

Maintain & upsell

Sell ongoing feature development. Each overlay is scoped — easy to estimate, profitable to deliver.

Ongoing
What your team gets

Mid-level devs ship senior-quality output.

The architecture and AI guardrails do the heavy lifting. Your team learns real skills — not workarounds.

Architecture that enforces quality

OCP overlays mean your devs can't accidentally break core modules. The structure prevents the mistakes before code review catches them.

AI agents that follow the rules

AGENTS.md and .ai/specs/ ship with the repo. Claude, Cursor, Copilot — they all generate code that fits the architecture, not fights it.

Real AI engineering skills

Your team learns spec-driven development and context-first workflows. Skills compound across projects.

Enterprise security out of the box

Field-level encryption, RBAC, audit trails, GDPR. Stop spending 3 weeks on auth for every client. Pass security reviews on day one.

Reusable across clients

Build a logistics overlay once. Use it for 5 clients with minor customization. Your IP compounds. Your margins grow.

No vendor lock-in (for you or them)

MIT licensed. Client gets full source. You're not reselling someone else's SaaS — you're delivering owned software on open infrastructure.

Before vs. After

What changes on your next project.

Dimension

Pricing model
Time to first demo
Auth & security
Junior dev effectiveness
Client ownership
Maintenance revenue
IP reuse across clients
Typical gross margin

T&M / From Scratch

3 weeks
4 weeks
2 weeks
2 weeks
They own the code
Ad-hoc, hard to scope
Start over each time
15–25%

With Mercato

Fixed-price packages
Day 1 (clone + run)
Pre-built, pre-audited
Architecture enforces quality
They own the code
Overlay-scoped, predictable
Overlays reusable across projects
50–65%
what teams ship

Case Studies

Air&Ocean Logistics ERP

Built in 6 weeks
No license fees
No lock-in
Live Track & Trace

A secure portal where DBAs can’t read PII. Per-tenant encryption, field-level AES-GCM, full audit trail - ready for regulated enFreightTech.org built a fully owned logistics ERP on Open Mercato in 6 weeks — covering CRM with automated quote handling, estimated vs. actual cost control, and live Track & Trace integration with major shipping lines and AIS vessel positioning data. One platform for the full operational cycle. No license fees, no lock-in.vironments.

FreightTech logo with a stylized blue globe on the left and black text on the right.

Software is about to be built
completely differently.

Start with 80% done.
$ git clone https://github.com/open-mercato/open-mercato.git
Clone the Repo